- 已装运
- 2026年8月31日 01:43 UTC
- 作者
- Kamo
- 提交
- 19fcddd
A dispatch composed the operator's instruction and the bug description with the separator between them. The title was never in it, so the session opening the message read the paragraphs about what happened without the one line saying what the report is about. It now heads the second half, above the description: the first half is the instruction to the AI, the second is the report, and the title belongs to the report. Absent from the request it falls back to the bug's stored title, so an unattended dispatch and a console tab predating the field both still land instead of losing a written prompt to a 400. An operator who sharpens a vague title has corrected the REPORT, so the edited title is written back onto the bug — the one field in that dialog that does. It is applied beside the audit row and before the network call: the correction was true whether or not the dev machine answers, and a report should not go back to being badly titled because a hand-off timed out. The description still never writes back; restating a bug for an AI is not rewriting what the member filed.