feat(checkpoint): rebuild durable result store on protected main - #181
Conversation
|
Warning Review limit reached
Next review available in: 87 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (16)
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 |
Durable PostgreSQL checkpoint store — current protected topology
This PR reconstructs the durable result-checkpoint store on the current protected baseline without transferring historical #60 checks, reviews, approvals, or generated-merge evidence.
Exact current identities
main:6f367d97e5f5011bddb9c718f71a9a14e008f025;d21a29926081a7bfdd495da0a61c378de00bb04c;No protected-main source/documentation mutation, force-push, destructive rebase, conflict-side selection, or gate weakening occurred.
Test-first evidence
The durable public API, deployable-image installation path, validation confidentiality, live tenant/RLS behavior, rollback safety, concurrent first-writer behavior, CAS advancement, stale-writer refusal, and caller-owned transaction coupling were all developed through observable RED states followed by narrow GREEN changes.
Notable preserved evidence includes:
ff5d7c2241ce28ec860abe74f6ccf5d0f44720a0: public durable-store symbols absent;d6c213ff25963f6988e7e3d4db47d8c01db9f3b4: narrow public export implementation;32329f0c8e97e2a707c813ca0d598be77d423f94: deployable PostgreSQL image omitted migration0007;91f0139e4967ec6ca67fa8779a1c887e5f6ed001: installs the existing checkpoint migration into/docker-entrypoint-initdb.d;f009f942c71398315083957b240db475a4beda5c: auditable cleanup restoring the pre-existingARG PG_MAJOR=16default after the preceding implementation accidentally removed it;The store provides durable tenant-qualified checkpoint CAS and optional same-PostgreSQL-transaction coupling. It deliberately does not claim distributed exactly-once delivery.
Exact-head validation
For unchanged head
d21a29926081a7bfdd495da0a61c378de00bb04cagainst base6f367d97e5f5011bddb9c718f71a9a14e008f025:branch = trueandfail_under = 100, and the exact-head quality job is terminal success;One conditional Strix child check (
publish-manual-pr-evidence-status) isskipped; it is not treated as success and is not a live required workflow/gate. The required Strix workflow itself completed successfully.CodeRabbit attempted a current-head review after the PR became Ready but reported its organization/developer review limit exhausted. That rate-limited attempt is not counted as approval or exact-head success. There are no CodeRabbit current-head findings to resolve, and CodeRabbit is not a live required ruleset workflow.
Documentation and promotion boundary
This PR carries its bounded ADR (
0007) and doctoring evidence. Broad README/architecture/CHANGELOG/canonical-document reconstruction is owned by active Draft #93 and must not be raced from this source branch. The current protected-main README/architecture do not claim this checkpoint store is already implemented; after merge, #93 must describe the protected-main state accurately before its own promotion.Merge only while this exact contributor head and exact live base remain unchanged, all required workflows remain terminal-success, mergeability remains true, and no new valid review/security finding appears.