Deterministic flaky failure

Failed commit and CI evidence

• Placebo case flaky-timer-race: The assertion races a delayed state transition. Progressive triage reproduces a mixed result and stops.
• Failing command: vitest run
• Error excerpt: AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false  ❯ case.test.js:12:17  10| void delay(losesRace ? 30 : 0).then(() => { ready = true; });  11| await delay(10);  12| expect(ready).toBe(true);  | ^  13| });  14| ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯ [ELIFECYCLE] Test failed. See above for more details.
• Repository local/fixture · run local-fixture · runtime node
• Recorded workflow run

Nano diagnosis and confidence

Failure class

test-assertion

Confidence

49%

Signals

• AssertionError
• expected false to be true
• mechanical:test-assertion
• signature:\bexpected\b[^\n]*\b(?:to|but)\b[^\n]*\b(?:received|be|equal|match)\b
• llm-command-mismatch
• llm-excerpt-ungrounded

Clean audit branch and Ultra verdict

Not run. No candidate survived for adversarial audit.

Final outcome

Flaky, no patch Recorded live result

Sutura never merges a generated repair. A flaky, no patch result still needs human review.

Check a patch this page did not produce

This run did not record an exact failing commit and policy commit, so both are shown as placeholders. Verification is always tied to exact commits. A patch cannot ask for a more permissive policy by carrying one, and no green log is accepted in place of execution.

sutura verify \
  --case-dir <checkout> \
  --source-sha <failing commit> \
  --policy-base-sha <trusted policy commit> \
  --candidate-diff <patch file> \
  --failing-command diagnosed \
  --format json

The same route runs as a GitHub Action and needs no repository write access. Uploading a patch stays a command-line and Action route; this page never runs one.