feat: add governed audit evidence review boundary - #102
Draft
seonghobae wants to merge 32 commits into
Draft
Conversation
|
Warning Review limit reachedNext included review available in 53 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (15)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 Generate unit tests (beta)
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 |
seonghobae
marked this pull request as ready for review
August 23, 2026 19:04
seonghobae
marked this pull request as draft
August 23, 2026 20:06
seonghobae
marked this pull request as ready for review
August 23, 2026 20:59
seonghobae
marked this pull request as draft
August 24, 2026 15:40
seonghobae
marked this pull request as ready for review
August 24, 2026 15:40
Contributor
Author
|
@opencode-agent Please review the current unchanged head against protected |
seonghobae
marked this pull request as draft
September 6, 2026 00:09
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Current authority — 2026-09-06
Current exact head is
5344d77a9bd1058fee9fcecb7c6aaebc39ced995. Protected truth isdevelop@eb9757f8649aaad026a9865508d9aad50c1a7a4f; this branch still retains the olderdevelop@9e3e4847510e1e612b48474ba42b177b8ed824dfsnapshot. Live state is open · Draft. The audit-evidence-review delta remains valid and is not a Close candidate.The previous PR prose stopped at predecessor
67b84464dedc21c8414e1830826816144eda44df. Intervening ordinary successor5344d77a9bd1058fee9fcecb7c6aaebc39ced995is a real production+test trust-boundary repair.read_audit_evidence(...)now gives the authorization callback and store callback independent snapshots rather than the authoritative in-process query object. The added regressions prove a hostile authority callback cannot rewrite tenant/date/limit before the store read and a hostile reader callback cannot rewrite query reference/date/limit before returned-page checks. The authoritative query remains unchanged across both callbacks. This successor is adopted as current branch truth rather than treated as race/noise.Exact-head historical evidence on
5344d77...is strong for the Orgmetra-owned surface: Audit Evidence Review Quality, Foundation, Recovery, SAST, Security Scan, coverage source/evidence, Dependency Review, PostgreSQL restore rehearsal, and applicable PostgreSQL integrity contracts completed successfully; the dedicated audit-evidence review contract reports 100% coverage. The same old-base exact head has terminal failures in OpenCode, Noema, and Strix, so it is not merge-passing and no successful local result is promoted over those required review gates.Before Ready, non-force adopt current protected
develop, preserve #161 repository-workflow consolidation and the complete audit-evidence callback-isolation delta, resolve semantic/provenance conflicts rather than selecting one tree wholesale, reseal deterministic artifacts from the final resolved bytes, then reacquire exact-head owned quality/100% coverage/PostgreSQL plus every then-current central security/review gate, resolved conversations, and a qualifying independent approval. Do not self-approve, use administrator bypass, force-push, create no-op retriggers, weaken gates, or copy foreign-owner source.