feat: add protocol compatibility diagnostics and historical readers
This commit is contained in:
@@ -216,6 +216,21 @@ receipts from their input key, allowing reuse after interrupted publication.
|
||||
Reconciliation derives state from files; no mutable in-memory index is authoritative.
|
||||
Details and explicit reopening/reauthorization rules are in [epics.md](epics.md).
|
||||
|
||||
## Compatibility inspection
|
||||
|
||||
The project module owns the protocol contract revision independently of the CLI
|
||||
release and manifest schema. Filesystem owns the supported storage-format catalog;
|
||||
existing typed readers continue interpreting older representations in memory.
|
||||
Verification's compatibility service inspects actual metadata and typed content,
|
||||
including record revisions and system completion receipts. The CLI exposes a full
|
||||
read-only report through `project compatibility` and a summary in `status`.
|
||||
|
||||
This adds no automatic conversion or blanket normalization. Onboarding refreshes
|
||||
entry instructions with backups and refuses to overwrite an unsupported contract.
|
||||
Frozen prior-release fixtures protect historical approvals, completion provenance,
|
||||
scope hashes and bytes. See [compatibility](compatibility.md) for the public contract
|
||||
and requirements before a future incompatible writer or migration is introduced.
|
||||
|
||||
## Earlier framework review and migration
|
||||
|
||||
Both implementations were inspected read-only:
|
||||
|
||||
Reference in New Issue
Block a user