docs: record git-cas v6.4.0 publication

[flyingrobots]

Summary

• record immutable v6.4.0 tag, workflow, npm, provenance, and GitHub Release evidence
• transition STATUS from candidate truth to published artifact truth
• close the publication checkpoint in design 0049
• make the candidate-to-published tracker transition executable in the release-state test

Linked Issue

• Refs Scoped staging workspaces for multi-object promotion #75.
• Refs RootSet retry misses structured update-ref lock races #77.
• Follow-up developer-worktree hardening is tracked by dev: bootstrap linked worktrees before local quality gates #79.
• Issues Scoped staging workspaces for multi-object promotion #75 and RootSet retry misses structured update-ref lock races #77 remain open until this publication evidence is reviewed and merged.

Design / Proof

• Design doc: docs/design/0049-scoped-staging-workspaces/scoped-staging-workspaces.md
• Witness or focused proof: docs/design/0049-scoped-staging-workspaces/witness/release-publication.md
• Release PR: release: prepare git-cas v6.4.0 #78
• Reviewed merge: d47af74a288ef362dba684536cff11c063cfdcc3
• Signed tag object: 3545b8aa81e395e832f112214b301dbe53d9576f
• Peeled target: d47af74a288ef362dba684536cff11c063cfdcc3
• Release workflow: https://github.com/git-stunts/git-cas/actions/runs/29627828620
• npm: @git-stunts/git-cas@6.4.0 with latest -> 6.4.0
• GitHub Release: https://github.com/git-stunts/git-cas/releases/tag/v6.4.0

Validation

pnpm run lint
node --test test/unit/docs/release-state.test.js test/unit/docs/markdown-links.test.js
npm test

• Focused release/docs suite: 31/31
• Complete Node unit suite: 1,993 passed, 2 skipped
• CI: lint, unit, Node, Bun, and Deno all green
• CodeRabbit review was rate-limited after producing no inline findings; strict self-review is recorded in the PR conversation

Release Impact

• Changelog/release evidence updated for the already-published v6.4.0 artifact.
• Public status and design docs updated to reflect published reality.
• Issue labels/milestone will be finalized after merge using source-cited closure comments.
• Downstream git-warp compatibility and performance evidence remain separate open gates.

[coderabbitai]

📝 Walkthrough

Walkthrough

The release documentation now records v6.4.0 as published, adds publication evidence, advances the active queue to v6.4.1, checks the related acceptance criterion, and updates release-state tests for the new markers.

Changes

Release publication state

Layer / File(s)	Summary
Publication evidence docs/design/0049-scoped-staging-workspaces/witness/release-publication.md	Records v6.4.0 identity, release workflow results, npm registry data, provenance, and downstream gate status.
Release status and acceptance STATUS.md, docs/design/0049-scoped-staging-workspaces/scoped-staging-workspaces.md	Marks v6.4.0 as published, advances the active queue to v6.4.1, and checks the publication acceptance criterion.
Release-state assertions test/unit/docs/release-state.test.js	Updates candidate and published-state expectations for the #75, #38, and v6.4.1 markers.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• git-stunts/git-cas#47: Touches the same release-state test loading and assertion code.
• git-stunts/git-cas#68: Updates the related release documentation, witness, and release-state test contract.
• git-stunts/git-cas#78: Modifies the same v6.4.0 release lifecycle assertions.

Suggested reviewers: git-stunts

Poem

I’m a rabbit with a release note bright,
v6.4.0 hopped into published light.
Tags are signed and witnesses sprout,
v6.4.1 is next on route.
Tests twitch true, the queue runs clear—
Carrots for every changelog cheer!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	No pull request description was provided, so none of the required template sections are present.	Add the Linked Issue, Design/Proof, Validation, and Release Impact sections using the repository template.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly matches the main change: recording the v6.4.0 publication evidence for git-cas.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

---

_{Comment @coderabbitai help to get the list of available commands.}

[flyingrobots]

@codex self-review and Code Lawyer pass completed.

Severity	Count
Critical	0
High	0
Medium	1 found and resolved
Low	0

The review found that the initial lifecycle test asserted publication-shaped markers but did not pin the current release's immutable merge, tag object, signing key, workflow run, registry integrity, shasum, or unpacked size. Commit 4e513188 adds exact assertions for every one of those fields and makes the downstream git-warp issue reference directly navigable.

Graft classifies the final diff as three documentation files plus one test file with no structural or public API change. The publication witness deliberately leaves git-warp compatibility and performance gates open.

Validation: focused release-state and Markdown-link tests 4/4; broader focused docs suite 31/31 before the evidence-hardening commit; lint green; complete Node unit suite 1,993 passed with two intentional skips; pre-push repeated lint and all 1,993 unit tests after the final commit.