Coldkeep v1.13.1 — Explicit Deferred-Contract Boundaries

[franchoy]

Coldkeep v1.13.1 — Explicit Deferred-Contract Boundaries

Coldkeep v1.13.1 is a boundary-hardening release in the v1.13 engine-stabilization train.

This release makes deferred, unsupported, candidate-only, partial, and transitional CLI/domain-owned boundaries explicit and test-protected before later v1.13.x releases continue engine contract cleanup, error taxonomy work, catalog expansion, and CLI thin-wrapper proof.

This release does not implement missing engine/catalog functionality and does not migrate additional operations into the engine.

Release Type

Boundary-hardening / tests-comments-docs.

No runtime behavior changed.
No unsupported operation was implemented.
No broad engine routing was added.
CLI behavior is unchanged.
JSON output is unchanged.
Exit codes are unchanged.
Schema and migrations are unchanged.
Storage and repository formats are unchanged.
Default backend behavior is unchanged.
PostgreSQL compatibility is preserved.

What Changed

Boundary target matrix

Added the v1.13.1 deferred-boundary target matrix.

The matrix inventories 37 explicit boundary targets across:

• explicit ErrNotImplemented paths
• candidate-only engine operations
• direct CLI bypasses
• partial engine routing
• field/option narrowing
• fallback behavior
• catalog deferred methods
• request/result support surfaces that could imply more support than currently exists

Engine unsupported modes

Added focused engine tests proving unsupported active engine modes fail explicitly with ErrNotImplemented and do not mutate state.

Covered:

• recursive Engine.Store
• stored-path Engine.Restore
• stored-path Engine.Remove
• stored-paths batch Engine.Remove

Catalog deferred methods

Strengthened deferred catalog-boundary tests.

Covered:

• snapshot graph
• chunk placement
• restore-plan metadata
• GC-plan metadata

The tests verify:

• errors.Is(err, catalog.ErrNotImplemented)
• returned value is nil
• no obvious catalog mutation occurs
• existing backend-contract parity remains covered through the current harness

Candidate-only engine contracts

Clarified candidate-only request/result types so their presence does not imply active engine ownership.

Covered:

• snapshot create
• snapshot delete
• snapshot restore
• repair
• recover

Added guardrail tests proving these candidate-only operations remain outside the active engine.Engine interface.

Partial routing boundaries

Added comments and tests documenting mixed/partial routing seams.

Covered:

• inspect
• snapshot show
• snapshot diff
• restore by-ID vs stored-path split
• remove by-ID vs stored-path/stored-paths split

No routing was changed.

Request/result support-surface clarity

Clarified provisional or limited request/result surfaces, including:

• VerifyResult
• SnapshotQuery
• StoreRequest
• RestoreRequest
• RemoveRequest
• SnapshotListRequest
• SnapshotListResult
• SnapshotShowResult
• SnapshotDiffRequest
• SnapshotDiffResult

Added focused tests around current seam behavior and provisional result shape.

CLI transitional ownership

Added focused CLI-boundary preservation tests and comments showing that several paths remain intentionally CLI/domain-owned in v1.13.1.

Covered:

• stored-path restore
• stored-path remove
• stored-paths batch remove
• snapshot create
• snapshot delete
• snapshot restore
• repair
• doctor/recovery

No CLI behavior was changed.

Documentation

Added or updated the v1.13.1 release documentation under:

docs/release/v1.13/

<hr /><em>This discussion was created from the release <a href='https://github.com/franchoy/coldkeep/releases/tag/v1.13.1'>Coldkeep v1.13.1 — Explicit Deferred-Contract Boundaries</a>.</em>