mirror of
https://github.com/garrytan/gstack.git
synced 2026-05-05 21:25:27 +02:00
Garry Tan
0d7d3899e3
4th paid run showed the agent often stops after a tool call without
producing a final text response. result.output ends up as empty
string (verified: {"type":"result", "result":""}). String-based regex
assertions couldn't find evidence of the work that did happen —
NO_CHECKPOINTS echoes, filename listings, bash outputs — because
those live in tool_result entries, not in the final assistant message.
Added fullOutputSurface() helper: concatenates result.output + every
tool_use input + every tool output + every transcript entry. Switched
the 3 failing tests (empty-state, list-current, list-all) and the
flaky legacy-compat test to this broader surface. The 4 stable-passing
tests (routing, fragment-match, roundtrip, list-delegates) untouched
— they worked because the agent DID produce text output.
Pattern mirrors the autoplan-dual-voice test fix: "don't assert on
the final assistant message alone; the transcript is the source of
truth for what actually happened."
Expected outcome:
- empty-state: NO_CHECKPOINTS echo in bash stdout now visible
- list-current-branch: filename timestamp prefix visible via find output
- list-all-branches: 3 filename timestamps visible via find output
- legacy-compat: stable pass regardless of agent's text-response choice