chore: re-pin nullclaw fork → v2026.5.29-zmb.2 (session-reset fix)#401
Merged
Conversation
…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>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps the
nullclawfork pinv2026.5.29-zmb.1→v2026.5.29-zmb.2.zmb.2folds a greptile P1 (raised on usezombie/nullclaw#1) into the single patch commit:clearSessionState()— the/newand/resethandler — now zeroesprompt_tokens_totalandcompletion_tokens_totalalongsidetotal_tokens(@hasField-guarded, matching the existing pattern). Without it, after a session resettokensUsed()reads 0 whilepromptTokensUsed()/completionTokensUsed()keep stale per-session values.Impact on usezombie: none in practice
The runner forks a fresh
Agentper 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#dd85a21ctag, 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
zig build,zig build --build-file build_runner.zig) compile against the new pin; package hash refreshed viazig fetch.promptTokensUsed()/completionTokensUsed()calls only compile if the pin exports them — build success proves resolution.zmb.2suite 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
nullclawfork from the mutable branch ref used in #399 to the immutable tagv2026.5.29-zmb.2, picking up aclearSessionState()fix that zeroes the new per-side token counters on/new//resetsopromptTokensUsed()/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.clearSessionState()addition and the supersession of zmb.1; drop-when condition unchanged./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 aclearSessionState()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
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 figuresReviews (2): Last reviewed commit: "Merge branch 'main' into chore/m90-004-r..." | Re-trigger Greptile