feat: add protocol compatibility diagnostics and historical readers
This commit is contained in:
@@ -126,6 +126,25 @@ The root instructions point agents to that entry. Automatic discovery still depe
|
||||
on the agent inspecting project instructions; a CLI cannot force an arbitrary model
|
||||
to inspect hidden folders or obey a protocol. Exported context includes the guide.
|
||||
|
||||
## Inspect compatibility before updating
|
||||
|
||||
```sh
|
||||
aie project compatibility --format json
|
||||
```
|
||||
|
||||
`status` includes a compatibility summary. The diagnostic separates the installed
|
||||
CLI release, protocol contract revision and actual storage formats, including record
|
||||
history. `CURRENT` and `LEGACY_COMPATIBLE` both mean readable; neither requires a
|
||||
migration. `UNSUPPORTED` and `INVALID` return exit 4 and identify affected files.
|
||||
Validation of references and evidence remains `aie project validate`.
|
||||
|
||||
Keep completed Works in their existing formats. Older supported files are interpreted
|
||||
in memory; reads and diagnostics never normalize them on disk. `aie onboard` updates
|
||||
only entry instructions and the manifest, with backups. It refuses to overwrite a
|
||||
newer unsupported contract. There is no required data migration in this release.
|
||||
See [compatibility and evolution](docs/compatibility.md) for the version policy and
|
||||
the contract for future migrations; no source-code inspection is needed by consumers.
|
||||
|
||||
## Discuss topics and answer surveys
|
||||
|
||||
Ideas remain Discussion entries, organized by Work-local topics. Existing discussion
|
||||
|
||||
Reference in New Issue
Block a user