Prevent passing run verdicts after failed scheduled realizations
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0e76f-be98-7ae3-965d-e0b31290a4c4
This commit is contained in:
parent
3ce772466b
commit
e3aac44c59
3 changed files with 36 additions and 2 deletions
|
|
@ -164,3 +164,14 @@ all 31 final parity cases pass, including native pytest reporting in a subproces
|
|||
The related subset passed 93 tests. Full suite: **471 passed in 167.82 seconds**.
|
||||
`git diff --check` is clean. Decision: `c06c8752-80db-4458-9eaf-6321a0ca710c`.
|
||||
No new task/workplan; T05 remains waiting and this workplan remains blocked.
|
||||
|
||||
|
||||
**2026-09-28 final run-verdict follow-up — done (T04).** A failed scheduled
|
||||
realization now prevents a passing aggregate even when no claims follow it.
|
||||
RunResult and persisted run_verdict become INCONCLUSIVE; previously observed
|
||||
FAIL is preserved. Added two receipt-level regressions (one reproduced the false
|
||||
PASS before the fix; the prior-failure control already passed). Focused evidence
|
||||
suite: **62 passed**. Final full suite: **473 passed in 167.98 seconds**.
|
||||
`git diff --check` is clean. No new task/workplan; pilot T05 stays waiting and
|
||||
TD-WP-0004 stays blocked. The session closes with existing external prerequisites
|
||||
explicitly retained, not promoted to completion.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue