1.2 — RunsManager → multi-run

[jack-champagne]

Phase 1.2 (plan §3). ~4 pd. β built the single-run slice.

runs/index (append-only; replaces the single latest symlink as the multi-run source of truth), per-run fan-out to Inspector / StatusBar / Catalog, FINISHED-keyed completion (not result.toml presence), replay path.

Depends on: run-dir contract (frozen), amico-run.
Feeds: 1.3 RunInspector (per-run views), Phase 3 CatalogStore (promote-on-success).

Note: Track C #37 (Δ3 run-dir → S3 sidecar) mirrors the run-dir for remote runs — keep RunsManager's watch keyed on the run-dir contract so local and remote runs surface through the same path.

[jack-champagne]

Touches both freezes — consumes the frozen RunHandle{runId, events, finished, abort} (Freeze 1: contract in #56 + the cloud-solve-service spec Locked decisions) and fans per-run events to the inspector under the runId-keyed protocol (Freeze 2: #58). Build to those.

[jack-champagne]

Protocol correction (post-#67; see #58): the per-run fan-out routes pulse DATA — parse AMICODE_PULSE/AMICODE_PULSE_META (+ AMICODE_ITER stats) from run.log → postPulse/postIterationRecord, not iter_*.png → setImageSource (PNG path removed for the live view). Carry the #67 ordering-race property into the fan-out: a late throttled pulse for run A must not touch run B's (or its own) badge — pulse msgs are plot-only.