Confirm cap7 is a single-object recording (not a mission with terrain)

payload_scan_mid.py scans a mid-mission frame (snapfull1, cmd 19,889): identical
9 coordinates as cmd 735 (65.5/72/181/236, all x[66,236]). So cap7 redraws the
same static surface patch every frame across its whole length -- no terrain, no
battle, ever. Corrects the earlier "mid-mission frames have battle scenes" guess:
a full battle scene lives in a different capture entirely. Readout last-mile
updated. The decode + array render fully account for cap7's content.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

emulator/firmware-decomp/render-readout.html

@@ -396,8 +396,8 @@
           <li>The array's <b>computational model</b> runs and matches the reference — the piece left is executing the board's own <b>compiled micro-code</b></li>
           <li>The per-region <b>DMA command lists decode cleanly</b> (§02) — SEND / SENDE / TXDN / TILE / GOTO, tile-relative</li>
           <li>The SEND payloads carry <b>real float coefficients</b> in a regular bit-serial sweep — recoverable, not opaque</li>
-          <li>Coefficients <b>verified to 0.2%</b> against the geometry; for this death-cam frame, the object <b>is</b> the geometry (§05)</li>
-          <li>Wider battle scenes with terrain live in mid-mission frames — a separate capture, since this death-cam view holds one object</li>
+          <li>Coefficients <b>verified to 0.2%</b> against the geometry; for this frame, the object <b>is</b> the geometry (§05)</li>
+          <li>cap7 redraws <b>this one object every frame</b> — confirmed identical at cmd 735 and cmd 19,889, same 9 coordinates. A battle scene with terrain is a different capture entirely</li>
         </ul>
       </div>
     </div>