Repository navigation
fix: complete V3 runtime isolation and acceptance evidence - #327
Open
EvanProgramming wants to merge 164 commits into
Open
EvanProgramming wants to merge 164 commits into
EvanProgramming wants to merge 164 commits into
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
EvanProgramming
marked this pull request as ready for review
November 7, 2026 11:24
Codex Review Summary: ✅ CompletedThis 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 branch has not been deployed
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.
V3 could still lose cancellation/persistence evidence, trust worker-provided execution authority, or let edited benchmark source influence the final oracle. This candidate preserves task/result identities and lifecycle state, keeps actual permissions and one-use execution tickets in a privileged parent, and executes frozen fixture assertions outside edited source processes. It also retains legacy full-output retrieval and keeps public installers on published v2.0.8 while V3 is unreleased.
The signed head is
0109494a87448ce345dc69751b314b0aeab88ef0. This consolidates the existing V3 candidate stack and subsequent hardening for review against main; merging remains blocked until the formal release evidence is complete. The intended integration is a non-forced fast-forward to the same verified SHA.Validation on this exact head:
Not ready to merge or publish: R260 still needs the complete bounded native SQLite/VFS causal evidence review; the fixed180-cell matched DeepSeek evaluation,54-cell routing experiment and independent outcome/workflow review have not run. Historical settled plus held DeepSeek exposure was re-audited as CNY0.582914960007; no new paid calls were made. The cumulative cap remains CNY15, including smoke/retry/unknown usage, with CNY2.032768 reserved before each request. No statistical threshold or original acceptance is waived.
Evidence, signed artifact checksums, the266-row requirement index and unpublished release-note preparation are retained outside the checkout. No passing17-gate manifest, main advance, tag, draft/public Release, package upload or preview-publisher execution is claimed or performed.