Add Console Lanes and Stages pages

[JacobStephens2]

Summary

status --all --json observations
├── Lanes: stages scaled to 3.5 / 12 / 24 hours, with full time text
└── Stages: live Runs first → finished Runs newest first
    └── repository Usual ranges → exact Run peek

Keep child Runs with their Command, retain repeated stages, and distinguish unknown historical times from stages not reached. Keys 2 and 3 open the pages; both fit 390 px. Stage intervals have one owner shared with Usual range sampling.

Closes #826

Evidence

• Before: cargo test --test console time_pages_pair_with_all_status_stages_and_repository_usual_ranges failed because the time pages were absent.
  After: all 14 Console integration tests pass, including CLI parity for stage times, Usual ranges and each window.
• Before: the Spec review's ordering reproduction put ended acme/a Runs before live zz/z; its history reproduction labelled missing stage metadata “Not reached.” Both exact commands failed before fixes.
  After: both retained commands pass:

  python3 console/reproductions/time-grid.py target/debug/thirdshift ordering
  python3 console/reproductions/time-grid.py target/debug/thirdshift history

• All 13 Console Playwright tests pass, including bar scale and position in every window, cross-repository live ordering, historical unknown times, child Run peeks, page keys and 390 px layouts.
• cargo fmt --check, cargo clippy --all-targets -- -D warnings, and cargo test --locked pass. The focused run_health tests also pass after sharing stage timing.

Test seams

• Binary HTTP pages paired with thirdshift status --all --json, using retained Command-record fixtures.
• Console navigation, scaled timeline geometry, stage-column peek selection, and 390 px layout through Playwright.

Review coverage

Independent Standards and Spec reviews used remote issue-776 at 5af85a50c62c4bd7e24e9e4ba64166177c6177f6 as the fixed point; the local branch ref was stale. Follow-ups reviewed the fixes at 3a0d284.

Standards: one P3 maintenance finding, resolved by sharing stage intervals. Spec: two P2 behavior findings, independently reproduced and fixed with retained tests. Both axes read all 15 changed files. Changed files left unread: none. Generated-output exclusions: none.

Unaddressed findings

Standards

None.

Spec

None.

Merge Danger

Door: two-way

No persisted format changes; revert restores the previous pages and timing calculation.

Blast Radius: Observations

Console rendering and stage intervals used by Usual range sampling; existing health behavior remains covered by the Rust suite.

Built with codex · gpt-6.1-sol · high