Attach To Intake

STAGE a screenshot or document against a bug report. Writes NO turn.

Reached by the paperclip, a paste, or a drop onto the composer in design/Issues.dc.html's chat -- three UI paths that all end up here with the same FormData shape. A reporter who can show the error does not have to describe pixels in prose, and Frederick's flow has Rooster collecting "screenshots whatever is needed" before he fixes anything. ALLOWED_ATTACHMENT_TYPES also covers plain text, CSV, JSON, PDF and common office documents, so this is not always a picture.

A paste used to write a fake "(screenshot attached)" turn the instant the file landed -- BEFORE there was anything to say about it, and before the reporter had typed a word. Frederick: "the screenshot shows up in the thread before you even submit the form... I told you to duplicate the same message box function that you have in Claude Code." One thought became four turns: an upload turn, Rooster answering it, a text turn, Rooster answering that too. This route now only stores the bytes and hands back their ids -- POST /intake/converse (intake_service.say) is the one place a turn is ever written, words and attachments together, the moment Send is actually pressed. The composer holds these as a removable tray of thumbnails in the meantime (IssueIntakeChat.tsx's attached state); nothing here is shown "in the thread" until that happens.

Attaching with no conversation yet opens a blank one (intake_service.open_conversation), so a person can drop a file in first and type afterwards -- opening it is not the same as speaking in it: no turn is written either way.