Publish git-cas v6.2.0 CAS ownership APIs

[flyingrobots]

Parent: #50

Outcome

The completed application storage and cache boundary is documented, versioned, tagged, published to npm, and available to git-warp.

Required evidence

• All v6.2.0: Application CAS and cache ownership boundary #50 implementation slices merged.
• CHANGELOG, README, GUIDE, API docs, architecture, upgrade notes, and release notes updated.
• Public declaration and package-content verification.
• pnpm lint, unit tests, Node/Bun/Deno integration tests, and release verification pass.
• Self-review and Code Lawyer review are clean.
• v6.2.0 tag matches package.json.
• Release workflow publishes npm provenance and GitHub Release.
• npm registry reports @git-stunts/git-cas@6.2.0 before downstream work begins.

[coderabbitai]

🔗 Related PRs

#1 - feat(cas): M1 Bedrock — foundation hardening [merged]
#15 - chore: deterministic fuzz, DRY chunk verify, DRY KDF metadata [merged]
#27 - docs: publish benchmark baselines [merged]
#47 - Make GitHub issues the canonical tracker [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[flyingrobots]

Publication evidence is now durable on main through merged PR #68 (80059fa378bb6f89c3de10c15d680712137a2c3d). The witness records signed release identity, successful workflow jobs, npm integrity and SLSA provenance, the final GitHub Release, and the downstream registry gate. [cite: docs/design/0047-application-storage-cache-boundary/witness/release-publication.md#9-64@80059fa378bb6f89c3de10c15d680712137a2c3d] The documentation-contract test pins the critical release facts. [cite: test/unit/docs/release-state.test.js#16-30@80059fa378bb6f89c3de10c15d680712137a2c3d]

Closure is supported by source evidence.