Repository navigation
Update Harness to Attune Verify 0.6.1 - #374
Merged
Merged
Conversation
Patrick Roebuck (silversurfer562)
force-pushed
the
deps/verify-0.6.1
branch
from
November 21, 2026 18:01
65f205e to
16f9072
Compare
Patrick Roebuck (silversurfer562)
marked this pull request as ready for review
November 21, 2026 19:06
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. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 16f9072686
ℹ️ 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 (@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 (@codex) address that feedback".
Pin Verify 0.6.1 and keep older accepted task evidence inspectable without allowing resume, replay, or recovery mutations on the previous profile. Preserve exact Windows saved-store controller identity and cover the historical evidence path with regression tests. Co-Authored-By: Codex (GPT-6) <codex@openai.com>
Patrick Roebuck (silversurfer562)
force-pushed
the
deps/verify-0.6.1
branch
from
November 21, 2026 20:27
16f9072 to
aeaf967
Compare
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.
Scope
Update the exact Verify dependency pin, runtime version gate, and active constraints together. Keep Forms and RAG unchanged. This is a candidate only; published Harness 1.8.1 is unchanged.
Preserve read-only task status across the Verify upgrade
The Codex P2 finding identified a regression in ordinary task
status, separate from review inspection. The fix allows read-only inspection of saved Verify 0.6.0 task evidence under 0.6.1 only when all other profile fields match. It does not rewrite records or permit execution or control operations on the mismatched runtime.Independent review and qualification
aeaf9677bd60dfe2f357666afcd262e100446750, based on2408c1e; exact independently tested tree1feedf20be0ea9a94859d67187a7ab9131a93014.status. The current runtime refused resume, cancel, transfer and reconcile; every saved file stayed byte-identical during candidate checks. The original runtime could still resume the paused record and replay the completed record. No provider calls.Compatibility before release
Verify 0.6.0 review records remain inspectable. Ordinary task
statuscan also display qualifying prior task records without rewriting them. Resuming or replaying these records requires the original runtime. Document the distinction in the release guidance before publishing. Published Harness 1.8.1 pins are unchanged.Patrick explicitly authorized merging PR #374 after its checks and review requirements pass. Package publication remains a separate decision.