Coldkeep v1.13.3 — Read-Side Contract Cleanup #93
franchoy
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Coldkeep v1.13.3 — Read-Side Contract Cleanup
Coldkeep v1.13.3 stabilizes the read-side contract surface for
stats,inspect,snapshot show, andsnapshot diff.This release started as a read-side contract cleanup release and also includes release-gate blocker remediations discovered during the final
PRE_RELEASE_CHECKLIST.mdProfile A validation, including a production storage correctness fix for concurrent store convergence.Highlights
Documented the current read-side ownership and contract boundaries for:
statsinspectsnapshot showsnapshot diffAdded focused read-side taxonomy boundary tests.
Added public CLI preservation tests for read-side JSON and error behavior.
Reviewed backend compatibility and dependency-direction seams.
Added the v1.13.4 handoff plan:
v1.13.4 — Read-Side Dependency Direction and Result Ownership ReviewFixed PostgreSQL catalog contract test isolation uncovered during the release gate.
Fixed a real concurrent-store correctness issue in the storage layer where unsafe completed-chunk reuse could occur when packed/legacy companion mappings were incomplete or inconsistent.
Added regression coverage for invalid packed/legacy companion mappings.
Correctness and compatibility
This release preserves:
Validation
The final release gate completed successfully after blocker remediation.
Validation included:
PRE_RELEASE_CHECKLIST.mdProfile Ago vet ./...golangci-lint run ./...plainandaes-gcmThe local benchmark matrix recorded worker-4 variance on virtualized hardware according to checklist guidance; this was documented and not treated as a release blocker.
Notes for maintainers
v1.13.3 makes the current read-side contract safer to reason about without broad routing or API changes.
The main follow-up is intentionally deferred to:
v1.13.4 — Read-Side Dependency Direction and Result Ownership ReviewThat release should continue from the documented ownership seams around engine result ownership, direct observability paths, snapshot package coupling, renderer coupling, and CLI JSON assembly boundaries.
This discussion was created from the release Coldkeep v1.13.3 — Read-Side Contract Cleanup.
All reactions