Repository navigation
fix: seal and retain qualified Flow 10 release evidence - #204
Merged
Merged
Conversation
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. |
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.
Public JavaScript expressions and embedded installation TypeScript were rejected as secret assignments, blocking an already passed Flow 10 qualification. Parse source in the schema-defined program fields while keeping ordinary evidence data strict. Static credentials, malformed programs and source maps still fail closed. A full token-trivia pass covers comments beside punctuation while preserving literal and template boundaries. Initial hashbang text receives the same strict privacy checks.
Retain the complete OpenAI-only matrix and exact-artifact canary. The matrix is VERIFIED with 71 of 72 attempts passing; the retained miss is within its unchanged 90% case threshold. The canary passes all six checks. The qualified package remains byte-identical (
f505b101…). No paid runs were repeated for this verifier fix.Validation:
This PR prepares the release evidence. Tagging and publication remain separate gates.