apply_jvm wrote instance.cfg and never restored it, so B5-B12a in run 1
ran on B4's last set (Shenandoah, 6 GB). Within-block verdicts hold
(same JVM on both sides); B7's no-shader baseline is re-run in run 2.
Also: B14 spawn-count automation (b14/: fresh seeded world per run,
offline-located biome sites, datapack entity counts, journaled config
variants) and RESULTS-proxy.md with run-1 verdicts.
- gen_shader_profiles.py + shader-profiles/: Iris per-pack option files
resolved from each pack's profile.* lines (Iris has no profile key)
- bench.py: flag rows shader_not_loaded when Iris falls back to vanilla
rendering (analyze.py treats it as invalid)
- matrix: shader_options session key, trial jar globs pinned to the
downloaded Modrinth builds, post-join settle 45 s (B0 v1 showed rep 1
still warming at 10 s)
- bench.py: gamescope-headless display (default, 1920x1080; ~2% cost vs
desktop for isolation from the shared Wayland desktop), --shader,
--dh, --disable-mods/--add-mods, --world-zip, crash-safe restore
journal, spectator mode in the plan (elevated cameras fell to the
sea floor and S4 measured underwater darkness)
- matrix.toml/matrix.py: declarative, resumable B0-B14 runner keyed on
mods hash (warns when B0 must be re-run)
- build.py: bench-only resource-pack variants (C1-fa, C1-fa-ext,
emf-lod*-fa, C1-bl); every bench variant pins resourcePacks so packs
don't leak between sessions; shipped tier output unchanged
- analyze.py: tagged labels use their own block's baseline
xdotool chat injection silently fails under KDE Wayland/Xwayland, so the
v1 harness recorded runs whose scene commands never executed. v2 drives
scenes from a generated world datapack, detects crashes, aligns MangoHud
CSVs by file birth time, flags vsync/backup/low-n windows, and records
full run metadata to JSONL; analyze.py applies the BENCH-MATRIX win rule.
logan