feat(migrations): add atomic checkpoint storage operator - #95
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@coderabbitai review |
|
|
@coderabbitai review |
|
|
@coderabbitai review Please review exact current replacement head |
|
|
Linearized replacement for #80
This Draft replays the atomic checkpoint-migration operator onto the current audit predecessor #94 without rewriting #94 or discarding the later #60 durable-store DSN boundary.
RCA and replacement boundary
#80 targeted the superseded #79 branch. Current #94 is the linearized audit replacement on #92 and differs from the former #79 baseline only through the current predecessor chain plus the preserved checkpoint-DSN CHANGELOG entry. Before publication, every #80-modified path that overlaps #94 was checked against the former #79 result.
.github/workflows/ci.yml,AGENTS.md,ARCHITECTURE.md,CLAUDE.md,pg_llm_batch/__init__.py, andtests/test_checkpoint_audit_ci_contract.pywere byte-identical between old #79 and current #94; onlyCHANGELOG.mdhad the expected newer DSN entry.The replacement therefore reuses the exact #80 result blobs for all non-CHANGELOG paths and applies the same migration-operator CHANGELOG delta to #94's current CHANGELOG. No conflict-side selection, force-push, feature rewrite, migration rewrite, workflow weakening, release action, or evidence transfer is used.
Exact replacement evidence
cc7c862cff76521ead8696c7d6bfe1a2c4b31780.7ada507901cbba6497348812a8c015403a5f38aa.CHANGELOG.mdpreserves feat(audit): persist append-only checkpoint acceptance trail #94's current durable checkpoint DSN boundary while reproducing old feat(migrations): add atomic checkpoint storage operator #80's operator entry.31315453617: completed / success.31315453635: completed / success.Historical #80 checks, reviews, and approvals do not transfer. Successful staged CI/release-acceptance is not final protected-main security/review/policy evidence.
Dependency and merge boundary
Required order is
.github#790 -> pg-llm-batch#53 -> #57 -> #58 -> #59 -> #60 -> #92 -> #94 -> this replacement -> #96 -> #97.Keep Draft while earlier prerequisites remain unintegrated. After prerequisite integration, reconcile/retarget only when integration correctness requires it and regenerate every applicable exact-head/exact-base CI, live PostgreSQL rollback/concurrency, security, dependency, SBOM/provenance, packaging, automated-review, branch-protection, repository-policy, and Release Acceptance gate. Merge only after the unchanged final head has zero valid unresolved findings, all required repository/security/release gates terminal-success, branch policy satisfied, and a qualifying independent non-author formal
APPROVEDreview where required. Queued, pending, cancelled, skipped-required, absent, neutral-required, stale-head/base, predecessor, status-only, synthetic-only, author-only, rate-limited or failed evidence is not acceptance.