v0.2.0 — automatic receipt capacity governance

Project Continuity v0.2.0

Features

• Explicit v2-to-v3 migration with source hash, revision CAS and no active lease.
• Automatic lossless receipt capacity governance at 80% of the 64 KiB limit;
  retain the newest 32 receipts after governance and preserve all business data.
• Compact managed rendering, full candidate budgeting, and read-only previews.
• Archived operation retries, integrity validation, recoverable commit ordering.
• Controlled export/verify handoff bundles and per-write manual capacity mode.

Compatibility

Existing v2 projects are not automatically migrated. v3 requires a receipt-aware
client; old clients reject v3. CURRENT remains the only editable current progress
source. Safe cross-machine continuation also requires the reachable receipt
archives. Use a verified handoff bundle, not a copy of CURRENT alone.

Verification

66 tests cover lifecycle, capacity growth, leases/CAS, Git drift, archived retries,
storage fault injection, security boundaries and clean extracted-package execution.
The release commit is tested on macOS/Linux/Windows × Python 3.11/3.12/3.13.
CI: https://github.com/seriousz158/project-continuity/actions/runs/34184645027

A private historical-snapshot rehearsal completed migration and cross-writer
handoff while retaining business records and custom Markdown. Pending business
patches were NOT applied and no live project cutover was performed.

Limitations and recovery

64 KiB is still a hard CURRENT limit; business growth may require explicit review.
Archive validation is linear in committed history, archives are never automatically
deleted, and locks are local rather than distributed. Status/validate diagnose
missing archives; restore them from verified backups rather than editing managed
state. See references/commands.md and references/protocol.md.

Disk installation, client discovery and actual model-session reload are different
verification levels. No active client restart, automatic project migration,
background watcher, DSH modification or live paid experiment is included.

Pinned CI actions currently emit a Node.js 20 deprecation warning while GitHub
runs them on Node.js 24; the warning is non-blocking and tracked as maintenance.

Remote clean clone, re-downloaded release archive (SHA-256 verified), and local
installed directory each passed 66 tests. Seven configured local entrypoints
were verified against the 29-file package; no active client was restarted.