feat(audit): add bounded stable export pages - #96
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 |
|
|
|
SUPERSEDED by the current-main durable-checkpoint reconstruction in #181. Fresh topology shows this Draft still depends on closed-unmerged predecessor #95, while #92/#94/#95 are all closed unmerged and #181 now rebuilds the checkpoint-store line from exact protected main without transferring historical stack evidence. Preserve this branch as design/test provenance only; do not retarget or count its historical checks as protected-main acceptance. |
SUPERSEDED historical pagination stack — closed unmerged
This PR is retained as design/test provenance for bounded checkpoint-audit pagination, but its predecessor chain is no longer an integration path to protected
main.Fresh exact topology at closure
main:9640ab9765db427412f3d108a4fc9eadf4fa1d8c;4e7c68fa3e5da050d433395568ab5eb3465a4cbbonagent/bounded-checkpoint-audit-export-pages-v5;agent/checkpoint-migration-operator-v3at1d05184be9fe699ef1e3f62068597a26ab88afce;The pagination feature itself remains useful provenance: strict positive PostgreSQL BIGINT keyset cursors, bounded newest-first
<continuation with one-row lookahead, exact tenant/consumer/endpoint/batch revalidation, descending identity validation, concurrent-insert stability evidence, public API, and the explicit absence of a false multi-page snapshot claim.Current reconstruction boundary
Current-main durable checkpoint-store reconstruction is owned separately by Draft #181 (
feat/durable-checkpoint-store-current-main). This historical pagination branch must not be retargeted directly tomain, merged through a closed predecessor branch, or used to transfer old CI/review/approval evidence.After the prerequisite durable checkpoint/audit capabilities are integrated on protected main, reconstruct the pagination feature test-first from a freshly read protected head on a new explicit non-default branch, reusing historical code only as design/regression provenance. Reacquire exact live-base ancestry, realistic PostgreSQL pagination/concurrency evidence, Python 3.10/3.12/3.14, exact 100% owned production statement/branch and public-docstring coverage, package/container/security/SAST/SBOM/provenance, every live required organization workflow, Release Acceptance, zero valid unresolved findings, and then-current policy on one unchanged final head.
No historical, predecessor, synthetic, cancelled, queued, status-only, author-only, or stale evidence from #96 or #97 transfers to that future reconstruction.