Second reproduction probe: tickets array of length 2, mixed actions (create + comment), real write. Both landed in one call — so the array path works from this harness at both lengths tested.
Reproduction probe for part 1 (capture with a tickets array, length 1, real write). Posted by the capture tool itself — if this comment exists, the array path worked from this harness.
Dispatched 2026-08-18 12:47 and again at 12:58 (status:redispatch). Both runs failed in ~3 seconds, before turn 1 — nothing to do with this issue's scope.
Root cause is dispatch-wide and now…
🤖 dispatch: executor claude failed: runner error: agent run ended in error (see stderr)
🤖 dispatch: routing: executor=claude (default — no executor: label) — starting headless run
🤖 dispatch: executor claude failed: runner error: agent run ended in error (see stderr)
🤖 dispatch: routing: executor=claude (default — no executor: label) — starting headless run
🤖 dispatch: executor claude failed: runner error: agent run ended in error (see stderr)
🤖 dispatch: routing: executor=claude (default — no executor: label) — starting headless run
Part 2 — decided: brain-mcp stays inside ingestion
ADR in the brain: wiki/hyperguild/decisions/brain-mcp-stays-in-ingestion-fix-discoverability-by-name.
First, a flag: your comment…
🤖 dispatch: executor claude failed: runner error: agent run ended in error (see stderr)
🤖 dispatch: routing: executor=claude (default — no executor: label) — starting headless run