🧊 Coldkeep v1.10.11 — Stabilization and Regression Burn-down

v1.10.11 — Stabilization and Regression Burn-down

Summary

v1.10.11 closes the Coldkeep v1.10 stabilization train with a behavior-preserving release-control pass.

This release does not introduce product features, runtime behavior changes, engine extraction, catalog abstraction, CI workflow changes, script changes, or dependency changes. Its purpose is to consolidate evidence, verify the local release-candidate state, preserve known-issues visibility, and prepare v1.10 behavior for the next roadmap steps.

What changed

v1.10.11 adds release-control evidence for the final v1.10 stabilization pass:

• finalized stale v1.10.10 release evidence;
• created the v1.10.11 stabilization scope and review contract;
• refreshed the remaining S0/S1 inventory;
• assigned explicit dispositions to remaining S0/S1 needs-review rows;
• defined the v1.10.11 regression matrix;
• executed and recorded local validation results;
• audited flaky-test and CI stability risk;
• created the known-issues-after-v1.10 handoff;
• completed the local release-candidate gate;
• recorded PR/CI/Codacy/merge/release evidence as part of the Phase 9 flow.

Validation

Local v1.10.11 validation passed before release flow:

18 required regression matrix rows passed
0 failed
0 blocked
0 required rows skipped
0 unresolved S0/S1 items
0 release blockers
0 flaky candidates

The validation set included baseline repository tests, race validation, vet, restore, GC, verify, snapshot, recovery, path safety, adversarial validation, integration validation, coverage/report evidence, and release-control checks.

Risk and known-issues handling

v1.10.11 intentionally keeps accepted, deferred, suppressed, observed, and CI-pending items visible instead of hiding them.

The known-issues handoff records:

accepted_risk: 2
deferred_risk: 12
suppressed_finding: 1
ci_pending_evidence: 3
accepted_observation: 3

These items are documented for future v1.10.12 / v1.11+ planning and do not block v1.10.11 release readiness.

Compatibility

v1.10.11 is behavior-preserving.

It does not change:

• repository format;
• container format;
• CLI behavior;
• JSON contracts;
• restore semantics;
• GC semantics;
• snapshot semantics;
• database backend behavior;
• scripts;
• CI workflow configuration;
• dependencies.

Release boundary

v1.10.11 does not include engine extraction or catalog abstraction.

Those remain future roadmap work after the v1.10 stabilization train.

Notes for users

This release is primarily a stabilization, audit, and release-readiness milestone. Existing Coldkeep behavior should remain unchanged from v1.10.10, with the project now carrying clearer evidence for risk disposition, validation coverage, CI boundaries, and known issues before moving toward the next architecture-preparation phase.