Problem
In ce-code-review Stages 5–6, the report leaf subagent (seeded with references/finish-review.md) is told to write report.md into the run directory. On a Claude Code host, the harness refuses report-shaped Markdown writes from subagents ("Subagents should return findings as text"). On every run the leaf returned the report in-band with a note that the write failed, and the run directory has no report.md.
Seen on five consecutive runs (four ce-code-review, one ce-doc-review) with compound-engineering v3.28.2 on Claude Code.
Impact
The report is still emitted to the user, but the run-artifact list is incomplete. Anything that later reads report.md from the run dir (resume, audit, comparing rounds) finds nothing.
Suggestion
Have the dispatch context, which already receives the leaf's return verbatim, write report.md from that return. The leaf then only renders and never writes, which matches what the host allows.
Problem
In
ce-code-reviewStages 5–6, the report leaf subagent (seeded withreferences/finish-review.md) is told to writereport.mdinto the run directory. On a Claude Code host, the harness refuses report-shaped Markdown writes from subagents ("Subagents should return findings as text"). On every run the leaf returned the report in-band with a note that the write failed, and the run directory has noreport.md.Seen on five consecutive runs (four
ce-code-review, onece-doc-review) with compound-engineering v3.28.2 on Claude Code.Impact
The report is still emitted to the user, but the run-artifact list is incomplete. Anything that later reads
report.mdfrom the run dir (resume, audit, comparing rounds) finds nothing.Suggestion
Have the dispatch context, which already receives the leaf's return verbatim, write
report.mdfrom that return. The leaf then only renders and never writes, which matches what the host allows.