b2d7d6c7 · zzmq.dev@gmail.com/zz
Commit
b2d7d6c79ab61dc1a9f605bced543e5dbe1225f8
Block completing a "work" ask with files embedded in the payload Observed directly (qwen3.8-27b on Groq): a contributor sometimes shortcuts the protocol by stuffing its proposed file changes straight into the "work" ask's own completion payload instead of posting a submit_changeset ask. ask_answer still succeeds and the ask reports "complete" -- but nothing ever gets committed, since no coordinator-scope ask exists for anyone to pick up. This was a silent failure: the run looked successful end to end. Enforce this structurally in answer() itself rather than hoping every model follows the system prompt's prose instructions -- the same pattern already used for the coordinator-RBAC check right above it.
Troy Howard <thoward37@gmail.com> -- 2026-10-11T08:20:53.000Z