You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e9bde73
Browse filesBrowse the repository at this point in the historyBrowse files
fix(harness): second-wave review fixes — completion detector and run accounting hardening
- `termination.ts`: a fence-looking line with trailing info-string text
(e.g. ```` ```not-a-closer ````) was treated as a valid closer for an
already-open code fence; only a run of the same/longer marker followed by
nothing but whitespace may close a fence now, matching CommonMark, so a
still-open fence's interior `DONE` can no longer terminate a run.
- `run-accounting.ts` / `run.ts`: the idle-done confirm-DONE challenge's two
abort/finish suppression flags could both still be "fresh" once the
challenge reply itself was sent (the interrupted prompt's abort may
surface via only one of the two channels), letting a genuine failure of
the challenge reply be silently forgiven. `onIdleDoneChallengeReplySent()`
now marks the reply as in flight so a later abnormal signal is scored as
a real failure, not absorbed by suppression meant for the earlier abort.
Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_017KXpxBn4zteNfXTwv8cf93
0 commit comments