Coldkeep v1.13.11 — Safety and Backend Compatibility Gate Closure

[franchoy]

Coldkeep v1.13.11 — Safety and Backend Compatibility Gate Closure

scope: authorized exact-head release PR for v1.13.11

Summary

This PR proposes Coldkeep v1.13.11 from the immutable corrected exact-head candidate 22b2ea787f4c444af8c046c739de7af414e799c4. Phases 0–20 are complete.

• Closes the bounded safety and backend-compatibility phase train: selected SQLite/PostgreSQL parity; schema/bootstrap/migration contracts; catalog/read/mutation/transaction semantics; repository coordination; container range/header consistency; bounded decompression; exact JSON integer fidelity; and fail-closed SQL mutation cardinality.
• Preserves native coordination proof on Linux, macOS, and Windows, with Linux independent-process contention, killed-holder release, live-GC exclusion, and PostgreSQL dedicated advisory-session ownership.
• Includes the bounded benchmark-baseline workflow trust-boundary correction: calibration is fail-closed to the trusted main SHA, trusted checkouts disable persisted credentials and caching, and artifact provenance must match that SHA.
• Reconciles release validation/evidence. The corrected exact-head Phase 20 Profile A gate passed against this candidate.

Key Invariants

• Snapshot immutability is preserved
• Snapshot rows are treated as GC roots
• Retention model remains explicit and consistent
• Recovery remains conservative and metadata-consistent

Additional preserved boundaries: selected contracts do not claim broad SQLite/PostgreSQL equivalence; cross-host/distributed coordination is not claimed; network-filesystem safety is not guaranteed; and macOS/Windows independent-process subprocess semantics are not separately proven. FreeBSD native runtime remains compile-only/unsupported as documented.

Lifecycle Semantics Impact (Required)

This release preserves current-state removal versus snapshot-retained content semantics. GC eligibility remains governed by explicit reachability roots, and recovery continues to conservatively resynchronize quarantined metadata with on-disk state. Operator/CLI behavior remains within the documented local-filesystem coordination and PostgreSQL compatibility boundaries; this PR does not broaden those contracts.

Validation Evidence

• Unit/package tests: pinned golangci-lint v2.6.2: 0 issues; module, format, shell, vet, build, SQLite, PostgreSQL contracts, and release/repository audits: PASS.
• Integration tests: complete restarted Profile A correctness, stress, long-run, legacy compatibility, snapshot, and required storage/recovery selectors in plain and AES-GCM: PASS.
• Adversarial tests: complete plain/AES-GCM adversarial suites plus Linux independent-process, killed-holder, and live-GC selectors: PASS without required skips.
• Smoke/manual lifecycle gate: plain/AES-GCM smoke and native Linux coordination: PASS.
• Local storage remediation: stale ignored repository-local storage/containers was left unchanged; all affected gate commands used explicit writable storage under /tmp.
• Release checklist steps executed locally: complete corrected exact-head Profile A gate: PASS; four hard benchmark-integrity profiles: 4/4 PASS with verified checksums; four timing-advisory profiles: evaluator-verified exit 0 for all 4. External evidence: /tmp/coldkeep-v1.13.11-phase20/.

Exact-head hosted evidence for 22b2ea787f4c444af8c046c739de7af414e799c4:

• Push CI: https://github.com/franchoy/coldkeep/actions/runs/32123966105 — SUCCESS
• CI Required Gate: job 95676195431 — SUCCESS
• Push CodeQL: https://github.com/franchoy/coldkeep/actions/runs/32123966095 — SUCCESS
• CodeQL Aggregate: job 95670634577 — SUCCESS
• PR-context CodeQL: https://github.com/franchoy/coldkeep/actions/runs/32123971732 — SUCCESS
• GitHub security check: job 95670468944 — PASS
• Code-scanning alerts 6 and 7: FIXED, not dismissed; open actions/cache-poisoning/poisonable-step findings in .github/workflows/benchmark-baseline.yml: 0.

Reviewer Notes

Benchmark integrity is hard required and passed 4/4. Timing advisory returned four evaluator-verified classification-0 observations; hard timing-regression enforcement remains deferred to controlled infrastructure. BKC-016 remains Deferred — documented. Codacy currently reports action_required with a summary of 379 new issues but no supplied severity/details; repository policy treats Codacy as advisory.

Merge authorization applies only to exact candidate 22b2ea787f4c444af8c046c739de7af414e799c4 while PR #106 remains pointed at that SHA. Merge is authorized but was not executed by the Phase 20 gate task. Tag creation, GitHub release publication, and release-branch deletion remain not authorized.

[codacy-production]

Not up to standards ⛔

🔴 Issues 9 high · 89 medium · 2 minor

Alerts:
⚠ 100 issues (≤ 0 issues of at least minor severity)

Results:
100 new issues

Category	Results
Documentation	2 minor
ErrorProne	4 high
Security	5 high
Complexity	89 medium

View in Codacy

🟢 Metrics 4690 complexity · 263 duplication

Metric	Results
Complexity	4690
Duplication	263

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}