docs(morning): fold in the real corpus number — 51+21 of 694 live/ tracks

The sweep landed after the brief was written. Replaces the placeholder with the
measured figure and, more importantly, with the right DENOMINATOR: study/ is
documentation prose, so 79+30 of 799 overstates it the same way the harness bug
did. Also surfaces the CRASH class to him directly, since those are the ones
worth his time and the ones I deliberately did not touch.

MORNING.md

@@ -124,9 +124,32 @@ Seven regression tests, mutation-checked — each fix reverted individually to
 prove the test actually fails without it. Full suite **229 passed**. The setlist
 stayed **13/13 green** throughout; none of this touched the gig path.
 
-A clean corpus-wide re-run was still going when I wrote this. The real count
-lands on **#112** rather than being guessed here — quoting an unmeasured number
-is how #112 got a wrong one in the first place.
+### The clean re-run landed. The real number is:
+
+**51 of your 694 `live/` tracks don't compile, and 21 more throw when queried.**
+Zero in the setlist. Full triage: `docs/2026-07-31-corpus-compile-failures.md`.
+
+Three figures have now been attached to this question and the first two were
+about the tool, not the music: #112's original 14, then a pre-fix 128 (~49 of
+them the harness artifact above), now 79+30 across all 799 files. But 799 is the
+wrong denominator too — 59 of those files are `study/`, i.e. Tidal documentation
+with inline examples that was never meant to compile as a track. Counting it
+inflates the figure the same way the bug did, just more quietly.
+
+The **CRASH** class is new and it's the one worth your time. These compile, then
+throw — invalid mini-notation *inside a string*, which is exactly why the type
+checker let them through:
+
+```
+"[d d] <d d d*2 d*4>]"        unbalanced bracket
+"~ ulgab?:1"                  ? before :
+"[0 .. 7 0]"                  a range with a trailing element
+"<0.75 .. 0.8 0.8 .. 0.65>"   a sequence on the left of ..
+```
+
+I didn't fix any of them. They're not in the set, and each needs a call about
+what you meant — `"[0 .. 7 0]"` has at least two readings and only you know
+which. Triage is the deliverable; the edits are yours.
 
 ---