Conversation
…vation-20260905 Collect reproducible hosted release readiness evidence
Promote hosted release readiness observation to data
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 799a584d02
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
…ding-20260905 Bind readiness receipts to owned TLS and verified source execution
Promote verified readiness receipt source and transport binding
twoimo
changed the title
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
1 participant
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.
Promote bounded release-readiness observation and its provenance correction from data to main. The metadata-only query reports the current policy tuple, retention configuration, migration ledger summary and bounded catalog gaps without retaining user rows or raw approval/provider details.
Version-3 receipts use an isolated source-file launcher that verifies committed SQL/executor/CA/launcher blobs, compiles captured executor bytes directly, anchors Git lookup to the intended repository without environment or file-based alternate stores, and creates a fresh connection to the exact project endpoint with pinned Supabase CA. Non-idle transactions are rejected and read-only/repeatable-read state is verified. Legacy v1/v2 receipts remain insufficient and are not relabeled.
Validation: 17 targeted tests and 7 reconciliation tests pass, including real PostgreSQL stale-snapshot rejection, poisoned bytecode cache, and foreign Git repository/alternate-store controls. Actual committed launcher source verification passes. The correction passed 28 effective checks plus one skip into develop (#2871), then35 successful checks into data (#2872). This main promotion requires its own current checks and protected merge admission.
Transport success unit tests are mocked. No hosted v3 receipt, legal review, backup/PITR, production write, deployment or closure of the remaining external tasks is claimed. Production auto-deployment remains disabled for main; this is source promotion only.