#23 - feat(run): Ports.FinalGuard — nudge an announce-then-stop run to deliver its stranded artifact - executus

Conversation 0 Commits 2 Files Changed 6

+517 -18

2 Commits

Author SHA1 Message Date

Author	SHA1	Message	Date
steveandClaude Fable 5	7a074d8fa2	fix(run): the FinalGuard nudge round can never replace a non-blank answer executus CI / test (pull_request) Successful in 49s Details Live regression (mort run d5ec39f4, 2026-07-15): a research run's page-cache file false-positived the guard, and the nudge round's meta closer ("my answer above stands as-is") REPLACED the real answer — hosts deliver Output text plus separately-drained attachments, so the user received the closer and never saw the answer. New merge policy: the nudge round exists to make tool calls (queue the delivery); its final text is discarded and recorded as a final_nudge_result audit event, so a round that declined to queue stays observable without reaching the user. The only exception is a blank original stop turn, where the nudge round's text is the only answer there is. Messages/Usage still merge (audit, PostRun, checkpoint continuity). Additive on top of `007b753` (mort main pins that commit as a pseudo-version; this branch must never be rewritten). Co-Authored-By: Claude Fable 5 <[email protected]>	2026-07-15 10:15:44 -04:00
steveandClaude Fable 5	007b7539c2	feat(run): Ports.FinalGuard — host seam that nudges an announce-then-stop run to deliver its artifact Gadfly review (reusable) / review (pull_request) Successful in 29s Details Adversarial Review (Gadfly) / review (pull_request) Successful in 28s Details executus CI / test (pull_request) Successful in 3m1s Details A run can render an artifact into host storage, end on a text-only stop turn claiming "Done — sent you the file", and never call the host's delivery tool — the artifact strands while the user is told it shipped (mort general run e9e7bf40 2026-07-14, gifsmith run 29170c93 2026-07-12). The loop has no seam for the host to intervene at the stop turn. Add Ports.FinalGuard: consulted once when a single-loop run is about to finalize successfully. A non-empty nudge is appended to the SAME conversation as the next user turn and the agent runs ONE bounded extra round (same toolbox/observers, capped at finalNudgeMaxSteps=6) — enough to deliver the stranded file or correct the final text, not enough to start a new work spree. Guard panics and nudge-round failures are isolated: the original successful result always survives. The nudge is recorded as a final_nudge audit event and appended to the durable checkpoint transcript. stageInputFiles now also returns the staged file ids, surfaced to the guard via FinalState.StagedFileIDs — staged inputs live under run scope but are the user's attachments, not run-produced artifacts, so an undelivered-artifact check must exclude them. FinalState.ToolNames lets a host skip runs that have no delivery tool at all. Co-Authored-By: Claude Fable 5 <[email protected]>	2026-07-14 23:14:09 -04:00

steveandClaude Fable 5

7a074d8fa2

fix(run): the FinalGuard nudge round can never replace a non-blank answer

executus CI / test (pull_request) Successful in 49s

Details

Live regression (mort run d5ec39f4, 2026-07-15): a research run's page-cache
file false-positived the guard, and the nudge round's meta closer ("my
answer above stands as-is") REPLACED the real answer — hosts deliver
Output text plus separately-drained attachments, so the user received the
closer and never saw the answer.

New merge policy: the nudge round exists to make tool calls (queue the
delivery); its final text is discarded and recorded as a final_nudge_result
audit event, so a round that declined to queue stays observable without
reaching the user. The only exception is a blank original stop turn, where
the nudge round's text is the only answer there is. Messages/Usage still
merge (audit, PostRun, checkpoint continuity).

Additive on top of 007b753 (mort main pins that commit as a pseudo-version;
this branch must never be rewritten).

Co-Authored-By: Claude Fable 5 <[email protected]>

2026-07-15 10:15:44 -04:00

steveandClaude Fable 5

007b7539c2

feat(run): Ports.FinalGuard — host seam that nudges an announce-then-stop run to deliver its artifact

Gadfly review (reusable) / review (pull_request) Successful in 29s

Details

Adversarial Review (Gadfly) / review (pull_request) Successful in 28s

Details

executus CI / test (pull_request) Successful in 3m1s

Details

A run can render an artifact into host storage, end on a text-only stop
turn claiming "Done — sent you the file", and never call the host's
delivery tool — the artifact strands while the user is told it shipped
(mort general run e9e7bf40 2026-07-14, gifsmith run 29170c93 2026-07-12).
The loop has no seam for the host to intervene at the stop turn.

Add Ports.FinalGuard: consulted once when a single-loop run is about to
finalize successfully. A non-empty nudge is appended to the SAME
conversation as the next user turn and the agent runs ONE bounded extra
round (same toolbox/observers, capped at finalNudgeMaxSteps=6) — enough
to deliver the stranded file or correct the final text, not enough to
start a new work spree. Guard panics and nudge-round failures are
isolated: the original successful result always survives. The nudge is
recorded as a final_nudge audit event and appended to the durable
checkpoint transcript.

stageInputFiles now also returns the staged file ids, surfaced to the
guard via FinalState.StagedFileIDs — staged inputs live under run scope
but are the user's attachments, not run-produced artifacts, so an
undelivered-artifact check must exclude them. FinalState.ToolNames lets
a host skip runs that have no delivery tool at all.

Co-Authored-By: Claude Fable 5 <[email protected]>

2026-07-14 23:14:09 -04:00

feat(run): Ports.FinalGuard — nudge an announce-then-stop run to deliver its stranded artifact #23