Coldkeep v1.13.2 — Engine Error Taxonomy Baseline

Coldkeep v1.13.2 — Engine Error Taxonomy Baseline

Coldkeep v1.13.2 establishes the first engine/catalog error taxonomy baseline for the v1.13 release train.

This release introduces narrow, code-backed taxonomy primitives for the stable surfaces that exist today, documents the broader taxonomy language, and protects public CLI behavior from accidental taxonomy leakage.

Highlights

• Added narrow engine unsupported classification:

  • engine.IsUnsupported(err error) bool
  • backed by errors.Is(err, engine.ErrNotImplemented)

• Added narrow catalog deferred classification:

  • catalog.IsDeferred(err error) bool
  • backed by errors.Is(err, catalog.ErrNotImplemented)

• Preserved engine/catalog sentinel separation:

  • engine unsupported errors and catalog deferred errors remain distinct
  • wrapped sentinel compatibility is protected by tests

• Added focused boundary tests for:

  • unsupported engine modes
  • malformed request validation
  • validation vs unsupported separation
  • per-item execution failures
  • catalog deferred method behavior
  • CLI translation preservation
  • JSON error-envelope stability
  • exit-code stability

• Added v1.13.2 release documentation:

  • scope
  • phase list
  • validation checklist
  • current error-surface inventory
  • formal error taxonomy
  • domain/invariant/runtime classification map
  • taxonomy summary and v1.13.3 handoff
  • final release gate

Public behavior

No public behavior changes.

This release does not change:

• CLI behavior
• human output contract
• JSON output shape
• exit codes
• command routing
• engine routing
• schema or migrations
• storage format
• repository format
• backend defaults
• PostgreSQL compatibility

Explicit non-goals

This release does not implement:

• a broad error framework
• unified validation/domain/invariant/runtime helpers
• recursive store
• stored-path restore/remove in the engine
• snapshot create/delete/restore in the engine
• repair/recovery engine ownership
• deferred catalog graph/placement/restore-plan/GC-plan behavior
• v2 work

Validation

The v1.13.2 release gate passed and was marked ready before PR review.

Validation included:

• full PR CI
• green CI on main after merge
• PRE_RELEASE_CHECKLIST.md Profile A
• Docker/PostgreSQL release-gate validation
• snapshot release gate
• CI enforcement audit
• legacy compatibility check
• local cross-platform approximation
• plain-codec CI-matrix local equivalent
• AES-GCM CI-matrix local equivalent
• benchmark matrix with focused reruns for initial noisy failures
• go test -count=1 ./...
• go test -race -count=1 ./...
• go vet ./...
• golangci-lint run ./...

Handoff

v1.13.3 should focus on read-side contract cleanup for:

• stats
• inspect
• snapshot show
• snapshot diff

That work should use the v1.13.2 taxonomy baseline while continuing to preserve public CLI behavior, JSON output, exit codes, and routing unless explicitly scoped otherwise.