File Issue From Intake

Rooster files the issue he just wrote.

design/Issues.dc.html has no File button in the chat: the reporter describes the problem and Rooster's turn comes back with a "Filed ISS-341" chip. The draft is still re-validated server side here, so a half-formed one is refused no matter what the agent claimed.

A REJECTED FILING RECORDS ITSELF, rather than waiting on the agent to notice the 422 and separately call record_intake_attempt_failed through its own tool. That second call was always a matter of the agent's own judgment, never enforced -- and Cindy Palma's conversation (measured 2026-08-14) shows exactly what happens when it does not happen: her FIRST failure was self-reported and recorded correctly (rooster_intake_attempts.last_failure_reason set at 19:05:21), but nothing recorded any of the retries after it, and the conversation sat unfiled for hours with a complete draft nobody was retrying. The pending_for_rooster fix (see that function's own comment) stops a stale record from silently expiring; this stops a failed filing from ever going unrecorded in the first place, which is the narrower and more direct fix -- a write that fails HERE, server-side, needs no agent cooperation to be told.