v1.12.0 — Engine/Catalog Boundary Migration Baseline

[franchoy]

Coldkeep v1.12.0 — Engine/Catalog Boundary Migration Baseline

Coldkeep v1.12.0, Engine/Catalog Boundary Migration Baseline, completes the scoped v1.12 engine/catalog migration release train.

This release moves several core operations behind the engine boundary, introduces the first catalog metadata facade, strengthens SQLite/PostgreSQL compatibility coverage, and adds an invariant matrix proving that routed operations preserve correctness-first behavior.

No storage format change, schema change, repository format change, default backend change, or intended CLI/JSON/exit-code behavior change is included.

Highlights

• Introduced the v1.12 release train documentation, risk register, coupling inventory, and invariant matrix.
• Fixed engine dependency ownership so routed engine operations use injected dependencies instead of reopening global DB/config state.
• Expanded engine operation contracts so future migrations can preserve behavior before routing.
• Added internal/catalog as a metadata facade skeleton.
• Added SQLite/PostgreSQL catalog compatibility contract tests.
• Routed read-side snapshot operations through the engine:
  • snapshot list
  • snapshot show
  • snapshot stats
  • snapshot diff
• Routed scoped GC behavior through the engine.
• Routed restore-by-ID live and dry-run paths through the engine.
• Routed single-file store through the engine.
• Routed remove-by-ID live and dry-run paths through the engine.
• Routed verify command execution through an engine seam.
• Added parity and invariant coverage for routed operations.
• Strengthened dependency guardrails, including preventing direct CLI-to-catalog coupling.

Engine/catalog boundary

v1.12 moves Coldkeep closer to the intended architecture:

CLI -> engine -> catalog/storage/domain packages

<hr /><em>This discussion was created from the release <a href='https://github.com/franchoy/coldkeep/releases/tag/v1.12.0'>v1.12.0 — Engine/Catalog Boundary Migration Baseline</a>.</em>