Drop SASI on capacity, then find the budget never had the disk in it

USER DECISION: drop the `sasi` profile. Not on bandwidth -- on capacity. A SASI
volume is 40 MB, and the 22.8 min of unique scene footage on the source Blu-ray
(streams 00000-00201, measured, not recalled) is 146 MiB at the LOWEST rate this
codec makes -- more than the machine's whole 4-unit SASI space. `scsi` is the
only profile now. FINDINGS 32.

Then the user asked whether we were drawing the wrong conclusions about PIO vs
DMA, and we were, more broadly than the question implied. Every CPU figure in
FINDINGS 24-34 is scored against the full 833,333 cycles/frame with nothing
subtracted for moving the bitstream off disk. Debiting the HD63450 cycle-steal
at the long-standing 8 clk/word ESTIMATE, "1 frame of 120 misses" becomes 84 of
120, median 112.4%. PIO at the span rate is 99.8% of the machine. Spans buy
cycles by spending bandwidth and the bandwidth returns as steal, so 31.6's "fits
completely" becomes a worst frame of 114.3%. 10 fps absorbs it: median 93.7%,
1/120. FINDINGS 35. `11_cpu_budget.py` takes --io dma|pio|none, defaults to dma,
and warns if asked for none.

Also landed:
- item 1 done: the cost model checked against the 68000 on a cost-aware
  container, -3.07% to +0.01%, whole-window mean -1.22%. FINDINGS 34.
- item 4 done: the container carries its own 4-byte record alignment (DLX2).
  94/120 record starts were on odd addresses -- an address error, not a slow
  read -- now 0/120 for 16 B/s. Re-encoding reproduces 31.1 exactly. FINDINGS 33.
- a `scsi` window does not fit the 2 MB machine the rig emulates (2.84 MB of
  stream past a 0x200000 ceiling). The gate now verifies 80 of 120 frames and
  SAYS so, and fails loudly when the pass does not complete, instead of
  reporting a phantom 49,005-pixel diff. FINDINGS 36.

Three near-misses this session had one shape: an unobservable run nearly
produced a false finding. stdbuf -oL on any MAME job that prints progress -- a
file is block-buffered too, and a run that is merely finishing looks exactly
like one that is wedged.

check.sh ALL GREEN.

Claude-Session: https://claude.ai/code/session_01194oWYW8DQXK1SZ2DnChW6

tools/encoder/ratectl.py

@@ -49,18 +49,25 @@ import vq_hybrid as H
 #     ~216% of the frame budget on a 68000 and even LZ4 is ~54%. See FINDINGS 17.
 #     The rates below are therefore RAW payload, no entropy coding.
 #
-# The two profiles are the SAME codec, decoder and bitstream -- only `lam` differs.
 # `lam` here is a FLOOR, not a setting: encode.py rate-controls by default and
 # bisects lam per frame in [lam, LAM_CLIFF] to keep under `kbps`. The floor is
 # what a quiet frame is allowed to spend, so rate control can only ever spend
 # less than session 5's fixed-lam encoder did. FINDINGS 27.
+#
+# THE `sasi` PROFILE IS GONE (session 9, USER DECISION). It was dropped on
+# CAPACITY, not bandwidth: a SASI volume on this machine tops out at 40 MB, and
+# the 22.8 minutes of unique scene footage on the source Blu-ray is 147 MB even
+# at the 110 KB/s the profile targeted -- more than the whole 4-unit SASI
+# address space, with nothing left for Human68k or the game. FINDINGS 32.
+#
+# That leaves ONE profile, which is also the end of the two-quality-mode
+# decision of session 2. The 110 KB/s RATE POINT may still return under another
+# name: a 1x SCSI CD-ROM sustains ~150 KB/s, below this profile, and CD-ROM is
+# the only period medium with the capacity for the span-heavy stream. That is
+# deferred to the blocked disk benchmark and the DMA-vs-PIO check (docs/
+# BENCHMARK.md, FINDINGS 29.5), because every bandwidth figure here is folklore
+# until one of them lands.
 PROFILES = {
-    "sasi": dict(kbps=110, lam=60.0, k1=256, k4=256,
-                 desc="stock 10MHz ACE/EXPERT, SASI",
-                 quality="36.9 dB on 00020 / 29.6 dB on 00146 / 27.2 dB on the "
-                         "Singe window at 109.5 KB/s (session 5's fixed lam "
-                         "gave 27.8 dB there, but at 137.4 KB/s)",
-                 util="~105 KB/s = 35% of the pessimistic 300 KB/s SASI figure"),
     "scsi": dict(kbps=280, lam=10.0, k1=256, k4=256,
                  desc="Super/XVI, or CZ-6BS1 board in a 10MHz machine",
                  quality="39.4 dB on 00020 / 32.3 dB on 00146 / 29.9 dB on the "
@@ -82,9 +89,9 @@ PROFILES = {
 LAM_CLIFF = 800.0
 
 # Ceiling on the CYCLE search. mu prices a cycle in the same units lam prices a
-# byte, so the scale that matters is set by their ratio: at the `sasi` floor of
-# lam=60, mu=0.2 makes a V1 block's 300 cycles cost what its 1 payload byte
-# costs. MU_CLIFF=100 is three decades past that: a V1 block priced at 30,000
+# byte, so the scale that matters is set by their ratio: at a lam floor of 60
+# (the retired `sasi` profile's, and the highest this codec has shipped),
+# mu=0.2 makes a V1 block's 300 cycles cost what its 1 payload byte costs. MU_CLIFF=100 is three decades past that: a V1 block priced at 30,000
 # distortion units.
 #
 # It does NOT freeze the picture, and that is the point. At MU_CLIFF a block