release: git-cas v6.5.3

[flyingrobots]

Summary

• version npm, JSR, and runtime metadata as 6.5.3
• publish release notes and v6.5.2-to-v6.5.3 compatibility guidance
• record the unpublished release-candidate witness for the single session-coherence correction
• mark design 0053 landed while preserving all v6.5.2 publication evidence

Issues and provenance

• Refs perf: preserve Git object sessions across coherent writes #94.
• Releases the implementation reviewed and merged in Preserve coherent Git object sessions #95.
• Adapter boundary: [cite: src/infrastructure/adapters/GitPersistenceAdapter.js#93-175@7bdcbf1f9eccd16acd324c94d576e1ecd2e11d98]
• Real-Git proof: [cite: test/integration/git-object-session-coherence.test.js#24-60@7bdcbf1f9eccd16acd324c94d576e1ecd2e11d98]

Verification

• pnpm release:verify: 14/14 steps, 6,829 observed tests
• Node unit: 2,082 passing
• Bun unit: 2,081 passing
• Deno unit: 2,072 passing
• Node/Bun/Deno real-Git integration: 198 passing on each runtime
• focused release-state, release-truth, and package-doc gates: 31 passing
• public type compatibility, examples, npm pack dry-run, and JSR dry-run pass

Review boundary

Graft classifies all 16 files as docs, tests, config, or formatting and reports no added or removed public symbols. Its export heuristic labels the package.json.files array growth as a major signature change; that array grows only to package docs/releases/v6.5.3.md. index.js and index.d.ts are unchanged, and the public type compatibility gate passes.

Publication boundary

This PR is a pre-publication candidate. It makes no tag, npm, provenance, or GitHub Release claim. After review and merge, the exact merge commit will be reverified and signed as v6.5.3; publication evidence will follow separately.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 36 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: b7de57bb-0fea-47b2-ba99-71265a73b646

📥 Commits

Reviewing files that changed from the base of the PR and between 7bdcbf1 and d615f80.

📒 Files selected for processing (16)

• BEARING.md
• CHANGELOG.md
• README.md
• ROADMAP.md
• STATUS.md
• UPGRADING.md
• docs/design/0053-git-object-session-coherence/git-object-session-coherence.md
• docs/design/0053-git-object-session-coherence/witness/release-candidate.md
• docs/design/README.md
• docs/releases/v6.5.3.md
• jsr.json
• package.json
• src/package-version.js
• test/unit/docs/package-docs.test.js
• test/unit/docs/release-state.test.js
• test/unit/docs/release-truth.test.js

---

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

[flyingrobots]

Self-code review

Severity	Count	Disposition
Critical	0	None
High	0	None
Medium	0	None
Low	0	None
Markdown/style	0	None remaining

Reviewed the clean final head d615f80f against freshly fetched origin/main, including all 16 changed files, version alignment, package contents, release-state transitions, historical-evidence preservation, source citations, links, benchmark wording, and publication-negative claims.

The branch changes no implementation source except src/package-version.js; index.js and index.d.ts are byte-identical to origin/main. npm, JSR, and runtime versions all resolve to 6.5.3, and the npm package list includes docs/releases/v6.5.3.md.

Graft classifies the diff as 10 docs, 3 tests, 1 config, and 2 formatting files with zero structural files and no added or removed symbols. Its export heuristic reports a major change because package.json.files grows from 35 to 36 entries. The sole new entry is the v6.5.3 release note; public declarations are unchanged and the public type compatibility gate passes. This is a tooling false positive, not an API change.

Verification: pnpm release:verify passed 14/14 steps with 6,829 observed tests; the final-head pre-push gate passed lint and all 2,082 Node unit tests; focused release truth passed 31/31; git diff --check origin/main...HEAD and Prettier pass. Hosted CI and CodeRabbit remain required before merge.

@codex please confirm the package-files Graft false positive and the unpublished-candidate boundary.