31B regimes parsed (early persist bump L7-16, motor only terminal — E2B signature absent, matches E4B); exp4_regimes.py takes explicit out path / defaults next to input jbar (fix pushed to node before 26B stage)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

results/REGIMES.json

@@ -42,9 +42,9 @@
   "hidden": 5376,
   "workspace_band": null,
   "kv_share_start": "none found in config (no num_kv_shared_layers key printed \u2014 verify in scan; if truly absent, all entrances structurally live)",
-  "jbar": "pending (H100 pipeline v4)",
-  "scan": "pending",
-  "status": "probe passed; jbar scan running on H100 (2026-07-15 late)"
+  "jbar": "bucket:results-lens/jbar_31b.pt (256/256 prompts)",
+  "scan": "results/exp4_31b.log (regimes_31b.pt reconstructed via parse_regimes_log.py; scan's own save hit the results/-CWD bug)",
+  "status": "mapped 2026-07-16, PROVISIONAL: E2B-style mid-depth workspace signature ABSENT (like E4B). Persistence+content bump sits EARLY instead \u2014 L7-16 (persist 0.30-0.49 peak L14, content 0.76-0.97, sensor/motor ~0). Sensor is two-lobed: L26-40 (peak 0.17@L26) and L49-56 (~0.12). Motor essentially absent until the final layer (0.06-0.07 L50-56, 0.20@L59). Ignition cross-check (in-log): commitment pinned hard through L38, collapses to ~0 at L42-46, becomes write-responsive at L54-58 (sign flips with w>=0.5 on all three pairs). Early persist zone vs late write-responsiveness disagree \u2014 no single band supported yet; needs jbar-side analysis before any band is entered."
  },
  "google/gemma-4-26B-A4B-it": {
   "revision": "01e5b3ee840d3a9e0b0b493c593e85398a30ef75",