release: v0.30.1 — TP-196 segment-engine hardening + TP-197 dashboard segment indicators

[HenryLach]

Patch release. Bundles two segment-related task packets + three post-merge folds caught during operator polyrepo testing.

What ships

TP-196 — Multi-segment engine hardening

Closes #462, #502, #503, #508 in one coherent hardening pass:

• Segment scope mode should be a single enum gating all segment signals #502 SegmentScopeMode promoted to first-class type; gates env vars, tool registration, and execution branches on one flag (was scattered conditions)
• Harden .DONE authority for multi-segment tasks — monitor, resume, and discovery guards #462 Three defense-in-depth .DONE guards: monitor (resolveTaskMonitorState), resume (collectDoneTaskIdsForResume), discovery (sanity warning) — prevent premature task completion in non-final-segment edge cases
• Lane-runner should check segment completion before spawning next iteration #508 Early-exit optimization: lane-runner pre-spawn segment-completion check skips wasted iteration when checkboxes are already done
• Add regression tests for SegmentScopeMode prompt injection #503 855-LOC regression test file locks down SegmentScopeMode prompt-injection (FULL_TASK / SEGMENT_SCOPED / single-segment polyrepo / legacy fallback)

TP-197 — Dashboard segment-level progress indicators

Closes #464:

• Per-segment status pills (✅ done / ⏳ active / ⬚ pending) in lane rows
• Segment-aware progress bar reflects current segment progress
• Single-segment / single-repo tasks render IDENTICALLY to pre-TP-197

3 post-merge folds caught during operator polyrepo testing

1. CSS grid-layout opt-in via .has-segments class — sage caught that the in-batch implementation changed .task-row to a 3-row grid unconditionally, adding 8px phantom row-gap for non-segmented tasks
2. Wave-chip lane parallelization across all waves — user observed the | (parallel) / → (serial) separators flickering as active wave changed. Fix derives from batch.tasks[].laneNumber (persisted) with sentinel-0 handling for pending tasks
3. Merge-agents panel cleanup — removed dead SESSION ID + DETAILS columns (always —) and bumped header contrast from --text-faint to --text-muted

Validation

Gate	Result
npm run typecheck	exit 0
npm run lint	exit 0 / 286 warnings / 671 infos
npm run format:check	exit 0
npm run test:fast	3703 passing / 1 skipped / 0 failed (+76 from v0.30.0 baseline 3627)
Second release under post-TP-194 hard gates	✅ All four gates required at PR time, all green

Polyrepo verification

Operator ran live polyrepo tests during PR review and caught all three folds via the actual dashboard. This is the testing pattern paying compounding dividends — code-quality gates catch the static-analysis class of bugs; polyrepo testing catches the rendering/UX/state class of bugs that unit tests can't fully exercise.

Issues closed

• Harden .DONE authority for multi-segment tasks — monitor, resume, and discovery guards #462 — Harden .DONE authority for multi-segment tasks
• Dashboard: segment-level progress indicators for multi-segment tasks #464 — Dashboard segment-level progress indicators
• Segment scope mode should be a single enum gating all segment signals #502 — SegmentScopeMode single enum gating all signals
• Add regression tests for SegmentScopeMode prompt injection #503 — Regression tests for SegmentScopeMode prompt injection
• Lane-runner should check segment completion before spawning next iteration #508 — Lane-runner segment completion check before respawn

Tag

v0.30.1 will be pushed AFTER this PR merges. --merge mode preserves the version-bump commit so the tag references it correctly.