fix(ui): render armed record 148 item region

Record 148 publishes player item 20 and refreshes word-quad 20 through overlay
A. Its recovered bounds are (9,14)-(25,30). Rust tracked the armed special hole
but never rendered this visible 17x17 table state.

Expose the armed/active special-hole state and composite the exact DAT997 region
until the special respawn consumes record 148's contact. Make the deterministic
effect-seven scenario internally valid by seeding the required contact, so its
framebuffer now covers both the DAT407 effect and item 20.

Test Plan:
- `cargo test --workspace --all-targets --all-features` -- 120 passed
- `cargo clippy --workspace --all-targets --all-features -- -D warnings` -- passed
- `rumdl check --flavor commonmark RECONSTRUCTION.md CHANGELOG.md` -- passed
- `cargo run -- --simulate effect-7 --step 0 --screenshot /tmp/tdkpin-effect7-special.png` -- passed; visually inspected at 640x460
- launcher/effect screenshot comparison -- 136 RGB pixels differ inside only the expected 17x17 item region
- `git diff --cached --check` -- passed

tdkpin-rs/CHANGELOG.md

@@ -92,7 +92,8 @@ and this project adheres to
   upward from the shooter lane.
 - Treat record 148 as the special/multiball hole represented by player item 20;
   capturing it preserves all five lock-hole items and contacts instead of
-  inventing an immediate wheel reset.
+  inventing an immediate wheel reset. Its exact 17x17 overlay-A Word-Quad at
+  `(9,14)` remains visible until the required contact is consumed.
 - Replace invented bumper outline/cooldown effects with the original per-record
   5/20/10 callback countdowns and exact overlay-A render rectangles for bumpers
   51-53 and targets 140-147/150-152.