feat: add protocol compatibility diagnostics and historical readers
This commit is contained in:
@@ -471,6 +471,18 @@ described in discussion/reference files, rather than copied into this workspace.
|
||||
`artifacts/outputs` is versionable for deliberately retained outputs; use ignored `runs/`
|
||||
for large temporary results. No command creates large output files by default.
|
||||
|
||||
## Compatibility and evolution
|
||||
|
||||
`project compatibility` inspects actual stored formats and revisions without writes.
|
||||
`protocol.json.schemaVersion` versions the manifest, while optional `protocolVersion`
|
||||
versions the engineering contract (absent means the supported legacy baseline 1).
|
||||
The diagnostic exposes the supported read/write format catalog separately from the
|
||||
executable release. Old compatible records remain valid and readable without
|
||||
normalization, including COMPLETED Works. `onboard` updates only entry instructions
|
||||
and the manifest; a newer unsupported contract is never silently overwritten.
|
||||
See [compatibility and evolution](compatibility.md) for public states, update guidance
|
||||
and requirements for future explicit conversions. No required migration exists today.
|
||||
|
||||
## Context and continuity
|
||||
|
||||
`work context --format markdown|json` loads only canonical project/Work files. It
|
||||
|
||||
Reference in New Issue
Block a user