v0.8.0

Breaking Changes

• RFC and Clause legacy JSON write paths are no longer supported.
• RFC/Clause mutation and lifecycle operations now assume TOML as the canonical writable format.
• Repositories that still contain legacy JSON RFC or clause artifacts must run govctl migrate before using those commands.

This is why this release is 0.8.0 rather than a patch release: it introduces a public CLI capability expansion and a breaking change in legacy artifact handling.

Highlights

• Introduced the canonical path-first edit surface:
  • govctl <resource> edit <ID> <path> --set
  • govctl <resource> edit <ID> <path> --add
  • govctl <resource> edit <ID> <path> --remove
  • govctl <resource> edit <ID> <path> --tick
• Routed existing set / add / remove / tick verbs through the same canonical edit planning path.
• Generalized nested edit resolution so object and array paths work at arbitrary supported depth.
• Simplified command planning and hardened CLI help so help text is a more reliable agent-facing contract.
• Kept the canonical edit surface while rejecting the heavier ADR schema redesign; ADR-0038 supersedes ADR-0036.

Fixed

• Converted command paths now emit explicit DiagnosticCode values with stable formatting for automation.
• User-facing expected failures no longer fall back to temporary uncoded anyhow messages.
• Legacy JSON-only RFC/clause lifecycle commands now fail with a migrate-first diagnostic instead of a misleading not-found error.
• Concurrency and lock behavior for canonical edit paths were tightened and regression-tested.

Upgrade Notes

• If your repository is already on TOML-governed artifacts, no special migration step is needed.
• If you still have legacy JSON RFC or clause artifacts, run:

govctl migrate

before attempting RFC/clause edit or lifecycle operations.

Full Changelog: v0.7.7...v0.8.0