Real-World Example Refutation Prompt

Your job is to REFUTE a change, not review it. Default to: this is broken, and prove it.

Requirement (verbatim):
- Human-typed user messages are never hidden because of how their text starts.
  Messages with images show their text. Real harness output (task
  notifications, tool results, slash-command wrappers, interrupt notices,
  system reminders) stays hidden.
- Both the normal JSON.parse path and the oversized-line (>100KB, head+tail
  truncated) path in message-reader.ts, plus the live SessionWatcher path,
  must agree.

Code: branch fix/image-messages, commit range a41c07d2..HEAD. Files mainly
transcript-filter.ts, message-reader.ts, session-watcher.ts.

Test command: npm run build && npx jest

Real data: Claude Code JSONL transcripts under ~/.claude/projects/*/ (many
versions, many entry shapes). Use them to find real entries that are now
shown but are harness output, or human messages still hidden. Compare
against the unfixed reader at `git show a41c07d2:...`.

A finding counts only with evidence: a failing jest test, or a command plus
its output, or a line-numbered path from input to wrong result. "Could not
break it" is valid if you list what you tried.

Rules: don't modify committed code except to add failing tests in a new file
you do NOT commit (name the path). Don't restart any services.

Report: each confirmed defect with severity (high/medium/low), its repro, and
whether it is inside the requirement above; then what you tried that held.