feat(audit): persist append-only checkpoint acceptance trail - #94
feat(audit): persist append-only checkpoint acceptance trail#94seonghobae wants to merge 2 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 |
|
@coderabbitai review |
|
|
@coderabbitai review |
|
@coderabbitai review Please review exact current replacement head |
|
|
Current stack purpose
This Draft carries the append-only checkpoint acceptance-audit slice after durable checkpoint storage and checkpoint observability. The audit behavior remains staged only; it is not protected-main behavior.
Repaired stack boundary — 2026-08-13
Fresh refs immediately before the repair were:
b9fa4f35772ae3259885cfbdaa3a6701964fe1abonagent/checkpoint-opentelemetry-observability-v3.cc7c862cff76521ead8696c7d6bfe1a2c4b31780.2235ec3eec2f73cb7ea3117c7b881d3bd1f0bdb7.The prior #94 head had diverged: its audit commit was one commit ahead of the historical merge base but seven predecessor commits behind the current #92 head. The predecessor advancement added exact-source CI governance on
.github/workflows/ci.yml,tests/test_workflow_contracts.py,docs/doctoring/exact-source-ci-evidence.md, andCHANGELOG.md, while the audit slice also changed the CI workflow and changelog.The branch was repaired non-destructively. Current exact #94 head is
22f9c6111d7f03a60cd5a6da845c9e16b5e60356, a two-parent merge commit whose first parent is the prior #94 audit head and whose second parent is exact current #92 head. GitHub comparison from #92 now reports ahead by 2, behind by 0, merge base exactly #92 head. No force-push, destructive rebase, conflict-side history selection, protected-main write, or predecessor evidence transfer was used.Integration RED -> fix
A read-only synthetic merge exposed one deterministic integration defect before the branch move: the newly added
checkpoint-audit-integrationjob still used an ordinary checkout, while #92's currenttests/test_workflow_contracts.pyrequires every CI checkout to bindref: ${{ github.event.pull_request.head.sha || github.sha }}and immediately verify the checked-out source SHA.The real merge tree therefore preserves both predecessor and audit results while adding that same exact-source checkout and verification contract to the audit integration job. Fresh exact-head inspection confirms all four CI checkout sites now carry
persist-credentials: false, the exact contributor-headref, and an immediateVerify exact source headstep. The audit job remains Python 3.14 PostgreSQL integration with the existing pinned PostgreSQL image and live audit test command.Current exact evidence
b9fa4f35772ae3259885cfbdaa3a6701964fe1ab.22f9c6111d7f03a60cd5a6da845c9e16b5e60356.Feature scope retained from the audit slice
The intended audit delta remains: tenant-isolated accepted-save evidence, append-only PostgreSQL audit storage, same-transaction persistence, least-privilege audit-role hardening,
clock_timestamp()semantics, package/container migration identity, bounded reads, public API, tests, ADR/operator/doctoring guidance, and release/CI contracts. These claims are ACTIVE-PR scope only until integrated through protected governance.Dependency and merge boundary
Current dependency order remains
#60 -> #92 -> #94 -> #95 -> #96 -> #97, subject to fresh protected-main reconciliation of earlier prerequisites. #95 is now stale against this repaired #94 head and must be reconciled only after this boundary's exact result is validated; later stack evidence does not transfer backward.Keep Draft until every then-current repository/organization CI, security, dependency, coverage, package, provenance, live PostgreSQL, automated-review, and Release Acceptance gate is terminal-success on one unchanged exact head and every live policy requirement is satisfied. Queued, pending, cancelled, skipped-required, absent, neutral-required, stale-head/base, predecessor, status-only, synthetic-only, author-only, rate-limited, infrastructure-only, or failed evidence is not acceptance.