fix: sync restart QA DAG assertion into v0.9.10 - #3160
Merged
Conversation
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.
What changed
devintorelease/v0.9.10Why
The Linux Docker DAG completed correctly across forced restarts, but the test harness rejected a valid
changes_requested, changes_requested, passhistory. This sync fixes that false negative without weakening protection against spurious or reordered QA histories.Validation
pnpm exec vitest run tests/backend/ci/workflow-health.test.ts tests/backend/scripts/mockup-sprint-pentest-runner.test.ts— 46 passedpnpm run lint— passedpnpm run check:docs-web— passedpnpm run build— passedRisk and rollback
Risk is limited to the mock sprint pentest assertion layer. Roll back commit
1339a09b9if the stricter causal matching rejects a newly discovered valid recovery history.