eb7cedb13e
One new data point on the in-mission freeze. The refuted resume-spin lead rested on refused resumes being normal -- thousands during gameplay, more in a healthy run than a frozen one. Today's freeze log contains zero of them across 1147 lines, and the mission still froze at about 267 s with a black screen, against 2447 in an older log. So the warning is not even necessary for a freeze, let alone sufficient, which closes the lead from the other side. Also refuted today, before this file was found: the burst of BaseHeap::Release failures at the end of the short log looks like a freeze signature and is not. In the longer log the same failures span lines 1044 to 5210 and the log continues for 2700 lines afterwards; they begin at mission load in both runs and are routine. The uncomfortable part is that both were already settled in mission-freeze-resume-spin.md, as was the 0xbdb59668 address that a previous iteration rediscovered independently. That is twice in one session that existing work was redone. The cause is mechanical rather than forgetfulness. docs/re/INDEX.md listed 20 of 43 notes and none of the recent ones, so searching the index for prior work on the freeze returned nothing -- the corpus was searched, but the search was blind. INDEX.md now carries a generated table of every note under docs/re/, 59 entries with title and status, and states outright that it should be searched before starting an investigation. Regenerating it is a few lines of Python and should be redone whenever notes are added.