bmad-run-inspector

# BMAD Run Inspector Verified against [bmad-loop 0.11.1](https://github.com/bmad-code-org/bmad-loop/releases/tag/v0.11.1). The bundled scripts run on Python 3.9+. `bmad-loop` itself needs 3.11+, but it often lives in an isolated environment while the host's `python3` is still stock macOS 3.9. A run leaves a directory of evidence. This skill is about reading it honestly: saying what it proves, and refusing to say what it doesn't. ## The one thing to get right **The `.log` file is a terminal redraw capture, not a transcript.** The coding CLI paints a live TUI into a tmux or psmux pane. The capture records every repaint. One adapter differs. `opencode-http` writes a real transcript instead. Read `references/log-forensics.md` before applying any of this to it. Three consequences: - Each logical line appears hundreds of times, growing character by character. `tail -50` returns fragments of one frame, not the last 50 things that happened. - Whitespace is dropped unpredictably. `Done(10tooluses·99.2ktokens·1m0s)` is one real line. - **Long tool output is collapsed into `… +N lines (ctrl+o to expand)` and never painted.** Those lines do not exist in the file. The third one decides what you may claim. Test summaries sit inside collapsed blocks. Your test runner's pass/fail line is long output, so the TUI hides it. One measured 4.35 MB log had 58 collapse markers hiding roughly 2,463 lines. Its largest single block was 484 lines. So **never report that tests passed or fail...