feat(audit): persist append-only checkpoint acceptance trail - #79
feat(audit): persist append-only checkpoint acceptance trail#79seonghobae wants to merge 3 commits into
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 |
|
Superseded by #94. Fresh comparison shows #94 is the linearized replacement on current predecessor #92, with the same 19 changed paths and the same aggregate 2,294 additions / 16 deletions while preserving #60's later DSN boundary on the predecessor. No checks, reviews, approvals, or old-base evidence transfer to #94; final acceptance must be reacquired there. |
Linearized replacement for #62
This Draft replays the exact checkpoint-audit feature delta onto replacement predecessor #78 exact head
64eea7edb28e391634a5d13c83495d20c6388c81without force-pushing or conflict-side selection.RCA and replacement boundary
Old observability PR #61 diverged after its predecessor moved and was replaced by #78. Before replay, every #62-modified file that also exists in the predecessor (
.github/workflows/ci.yml,AGENTS.md,ARCHITECTURE.md,CHANGELOG.md,CLAUDE.md,docker/postgres/Dockerfile,pg_llm_batch/__init__.py, andtests/test_dependency_refresh_contract.py) was verified byte-identical between old #62 based23fc6eade6959fa19e22b39337c14dc65b21ab5and replacement predecessor64eea7edb28e391634a5d13c83495d20c6388c81.Replacement head
e99c99b081cd5d85f67faf1a0f46944110efbef3is exactly one commit ahead and zero behind exact predecessor #78 and changes exactly the same 19 audit feature files as old #62: tenant-isolated accepted-save evidence, append-only PostgreSQL audit storage, same-transaction persistence, least-privilege live-role tests, migration/rollback protections, bounded reads, public API/export contracts, and authoritative docs.Old #62 is closed unmerged as superseded. No predecessor-head check, review, or approval transfers.
Current staged evidence
e99c99b081cd5d85f67faf1a0f46944110efbef3.64eea7edb28e391634a5d13c83495d20c6388c81(feat(observability): instrument durable checkpoint operations #78).31285817835: completed / success on the exact replacement source head.31285817861: completed / success on the exact replacement source head.This is current stacked-stage evidence only. Default-branch-only organization/security/review gates are not inferred as passing while this PR is stacked.
Merge boundary
Required order remains
.github#790 -> pg-llm-batch#53 -> #55 -> #56 -> #57 -> #58 -> #59 -> #60 -> #78 -> this PR -> #80.Keep Draft while earlier prerequisites remain unintegrated. After every prerequisite safely reaches protected
main, reconcile or retarget this slice onto the actual integrated base and regenerate all required exact-head/exact-base CI, live PostgreSQL, migration/rollback, security, dependency, SBOM/provenance, packaging, automated-review, branch-protection, repository-policy, and Release Acceptance gates. Merge only with zero unresolved valid findings and a qualifying independent non-author GitHubAPPROVEDreview on the unchanged final head. Queued, pending, failed, cancelled, skipped-required, neutral-required, absent, stale-head/base, predecessor, status-only, author-only, or synthetic-only evidence is never acceptance.