Skip to content

chore: re-pin nullclaw fork → v2026.5.29-zmb.2 (session-reset fix)#401

Merged
indykish merged 2 commits into
mainfrom
chore/m90-004-repin-nullclaw-zmb2
Jun 12, 2026
Merged

chore: re-pin nullclaw fork → v2026.5.29-zmb.2 (session-reset fix)#401
indykish merged 2 commits into
mainfrom
chore/m90-004-repin-nullclaw-zmb2

Conversation

@indykish

@indykish indykish commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Summary

Bumps the nullclaw fork pin v2026.5.29-zmb.1v2026.5.29-zmb.2.

zmb.2 folds a greptile P1 (raised on usezombie/nullclaw#1) into the single patch commit: clearSessionState() — the /new and /reset handler — now zeroes prompt_tokens_total and completion_tokens_total alongside total_tokens (@hasField-guarded, matching the existing pattern). Without it, after a session reset tokensUsed() reads 0 while promptTokensUsed()/completionTokensUsed() keep stale per-session values.

Impact on usezombie: none in practice

The runner forks a fresh Agent per lease and never issues /new//reset, so #399's billing was already correct. This is dependency-correctness hygiene, not a hotfix — don't pin a release with a known defect.

Also: the tag-anchored ref the earlier pin-swap missed

#399 merged at 7f42f62e, before the in-PR pin-swap commit (28507524) — so main still carried the branch ref ?ref=patch/…#127b5ac4. This PR moves to the immutable ?ref=v2026.5.29-zmb.2#dd85a21c tag, which also removes a fragility: the fork branch was force-pushed past the old commit (kept alive only by the zmb.1 tag), so a tag-anchored pin is the robust form.

Verification

  • Both build graphs (zig build, zig build --build-file build_runner.zig) compile against the new pin; package hash refreshed via zig fetch.
  • The engine's promptTokensUsed()/completionTokensUsed() calls only compile if the pin exports them — build success proves resolution.
  • zmb.2 suite parity: only the same 5 pre-existing redis-environment integration tests fail (identical to upstream v2026.5.29).

🤖 Generated with Claude Code

Greptile Summary

Re-pins the nullclaw fork from the mutable branch ref used in #399 to the immutable tag v2026.5.29-zmb.2, picking up a clearSessionState() fix that zeroes the new per-side token counters on /new//reset so promptTokensUsed()/completionTokensUsed() don't retain stale values after a session reset.

  • build.zig.zon: URL updated from ?ref=patch/split-token-accessors-v2026.5.29#127b5ac4… (mutable branch) to ?ref=v2026.5.29-zmb.2#dd85a21c… (immutable tag); package hash refreshed.
  • Comment updated to document the clearSessionState() addition and the supersession of zmb.1; drop-when condition unchanged.
  • PR notes the runner never issues /new//reset, so billing correctness from fix(m90-004): runner reports split token counts — platform token spend bills #399 is unaffected; this is a dependency-hygiene pin to avoid carrying a known-defective release.

Confidence Score: 5/5

Single-file dependency pin update from a mutable branch ref to an immutable tag; no production logic changes in this repo.

The only change is in build.zig.zon: the nullclaw URL moves from a mutable branch ref to a tag-anchored ref, and the package hash is updated to match. The new tag picks up a clearSessionState() fix in the dependency, which the PR description confirms does not affect the runner's billing path today. There is nothing mechanically wrong with the pin format or the hash update, and the comment accurately describes the fork's state.

No files require special attention.

Important Files Changed

Filename Overview
build.zig.zon Bumps nullclaw fork pin from mutable branch ref (zmb.1) to immutable tag ref (v2026.5.29-zmb.2); updates URL, hash, and explanatory comment accordingly

Sequence Diagram

sequenceDiagram
    participant build as build.zig.zon
    participant pkg as Zig package manager
    participant fork as usezombie/nullclaw (tag v2026.5.29-zmb.2)
    participant runner as Runner (Agent billing)

    Note over build,fork: Before this PR (zmb.1 — mutable branch ref)
    build->>pkg: "ref=patch/split-token-accessors-v2026.5.29#127b5ac4"
    pkg->>fork: fetch branch HEAD
    Note over fork: Branch could be force-pushed past anchor<br/>clearSessionState() missing for split counters

    Note over build,fork: After this PR (zmb.2 — immutable tag ref)
    build->>pkg: "ref=v2026.5.29-zmb.2#dd85a21c"
    pkg->>fork: fetch tag (immutable)
    fork-->>runner: promptTokensUsed() / completionTokensUsed()
    fork-->>runner: clearSessionState() now zeros both counters
    Note over runner: /new and /reset leave no stale per-session figures
Loading

Reviews (2): Last reviewed commit: "Merge branch 'main' into chore/m90-004-r..." | Re-trigger Greptile

…tag anchor)

Bumps the nullclaw fork pin zmb.1 → zmb.2. zmb.2 folds a greptile P1
into the single patch commit: clearSessionState() now zeroes
prompt_tokens_total/completion_tokens_total alongside total_tokens, so
/new and /reset don't leave by-side metering carrying stale per-session
figures. usezombie's runner forks a fresh Agent per lease and never
calls /new, so #399's billing was already correct in practice — this is
correctness hygiene on the dependency, not a hotfix.

Also lands the tag-anchored ref that the earlier in-PR pin-swap missed:
#399 merged at 7f42f62, before the pin-swap commit, so main still
carried the branch ref. This pin uses the immutable v2026.5.29-zmb.2
tag at its commit, removing the branch-ref fragility (the fork branch
has since moved past the old commit).

Both build graphs compile against the new pin; hash refreshed via zig fetch.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 12, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
usezombie-agents-sh Ready Ready Preview, Comment Jun 12, 2026 4:14am
usezombie-app Ready Ready Preview, Comment Jun 12, 2026 4:14am
usezombie-website Ready Ready Preview, Comment Jun 12, 2026 4:14am

@codecov

codecov Bot commented Jun 12, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@indykish indykish merged commit c9fb262 into main Jun 12, 2026
44 checks passed
@indykish indykish deleted the chore/m90-004-repin-nullclaw-zmb2 branch June 14, 2026 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant