MC-4926

SCOPE ADDITION (from group-2 implementation stop-rule): also retire /partials/board-panel route + templates/partials/board_panel.html + templates/partials/ticket_card.html — these v1 board partials survive only because legacy dashboard.html embeds the panel as its side panel. Delete together with dashboard.html. Passive ref in static/sw.js:223 (cache exclusion) — remove or leave, harmless.

PRE-APPROVED BY ELMAR (2026-06-10 14:40): execute this retirement Friday 2026-06-12 WITHOUT further sign-off, provided no Home-v2 complaints land before then. Snoozed to Fri 05:00 UTC; status todo so the board-manager dispatches it when the snooze lifts. Full scope = original description + the v1 board panel partials (board_panel.html, ticket_card.html, /partials/board-panel route, sw.js ref). Gates unchanged: settings extraction first, tests, canary battery, deploy-verify, no 'Legacy Home' strings in / HTML.

[visibility-only board-manager] Parked this Luci-owned retirement slice until Friday 2026-06-12 after the Home-v2 burn-in precondition. I did not route implementation now: if Home-v2 complaints appear before Friday, fix Home first and push this retirement out. No human-owned Inbox/backlog rows were touched.

[visibility-only board-manager] Parked this Luci-owned deferred slice back to `waiting` because its burn-in gate is still future-dated (`waiting_until_2026-06-12_home_v2_burn_in`). No worker was launched; this preserves visibility-only routing and prevents the Todo bucket from implying runnable work before Friday.

[follow-up] 0 min past expected check-in (2026-06-12T07:00:00+02:00 UTC).

Controller gate/landing complete for MC-4926 (visibility-only; no MC runtime/pickup/send/claim/harvest endpoints used). Evidence: - Verified isolated worktree branch `mc-4926-legacy-retire` was clean at exact commit `8dc70677b8ca09bffd4b83d5bd3b5f66ad33ffb9`, matching `origin/mc-4926-legacy-retire` and based on `origin/master`. - Focused isolated tests: `python3 -m pytest tests/test_board_v2.py tests/test_mc4322_settings_routing.py tests/test_mc4321_cockpit_fix.py` => 226 passed. - Static acceptance: deleted `templates/dashboard.html`, `templates/partials/board_panel.html`, `templates/partials/ticket_card.html`; `/legacy-home` and `/?ui=v1` redirect to `/`; `/partials/board-panel` route is absent/404; `/` has no visible `Legacy Home` or `Switch to v1`. - Landed by fast-forward push to `origin/master` (`5f1455c` -> `8dc7067`) and fast-forwarded live checkout to `8dc7067`, preserving existing unrelated live dirt (`templates/partials/board_v2_panel.html`, `.gstack/`, `design/`, `test-results/`, `tests/qa-evidence/`). - Reloaded live gunicorn master `2335814` with SIGHUP; workers rotated to `2809485,2809487` from cwd `/home/lucienne/workspace/mission-control`. - Live verification on `127.0.0.1:3001`: `/api/health`, `/`, `/board`, `/settings` all 200; `/legacy-home` 301 -> `/`; `/?ui=v1` 301 -> `/`; `/partials/board-panel` 404; `/` contains no `Legacy Home` / `Switch to v1`. - Board canary battery: `MC_URL=http://127.0.0.1:3001/ python3 tests/canary/run_board_battery.py` => 13 PASS, 0 FAIL, consoleErrors=0 (fixture MC-5010 created then cancelled). - `graphify update .` was attempted and still fails locally with `ModuleNotFoundError: No module named 'graphify'` (known non-blocking tool import issue from parent handoff).

Mobile visual gate evidence added after done-gate 422: captured 375px live `/` screenshot at `/tmp/mc4926/home-mobile-375.png`; vision check approved — no visible `Legacy Home` / `Switch to v1`, no obvious broken mobile layout in visible viewport.

[visibility-only board-manager] Burn-in gate reached for the pre-approved legacy Home/Cockpit retirement. Controller precheck found no human Home/Cockpit/legacy/v2 complaint comments since the 2026-06-10 pre-approval. Routed implementation outside MC via internal Kanban `mc-internal` card `t_1394b2f3` in isolated worktree `/home/lucienne/workspace/.mc-kanban/MC-4926-legacy-retire`. Initial `claudebuilder` run hit Anthropic extra-usage HTTP 400, so I reclaimed/reassigned the same card to `codexbuilder`; verified run 311 is live as PID 2788281 with cwd `/home/lucienne/workspace/.mc-kanban/MC-4926-legacy-retire`. No MC runtime/pickup/send/harvest endpoint was used.

[visibility-only board-manager] Controller gate rejected parent Kanban card `t_1394b2f3` as incomplete: its handoff said reconnaissance-only and the isolated worktree still had dirty WIP. Routed the same MC-4926 acceptance scope to continuation card `t_f0169592` on `mc-internal`, using the same isolated worktree `/home/lucienne/workspace/.mc-kanban/MC-4926-legacy-retire`. Verified Kanban run 312 is `running` as PID 2797426 with cwd `/home/lucienne/workspace/.mc-kanban/MC-4926-legacy-retire`. MC remains visibility-only/waiting on that external worker; no MC runtime/pickup/send/harvest endpoint was used.

[visibility-only board-manager] Follow-up sweep found MC-4926's previous Kanban continuation `t_f0169592` had completed with a review-required/landing handoff, not a fully landed live deploy. Routed the controller gate/landing/deploy step outside MC to internal Kanban `mc-internal` card `t_a502622c` (codexbuilder) in isolated workspace `/home/lucienne/workspace/.mc-kanban/MC-4926-legacy-retire`; verified run 313 is `running` as PID 2807154 with cwd `/home/lucienne/workspace/.mc-kanban/MC-4926-legacy-retire`. MC remains visibility-only/waiting on that external worker; no MC runtime/pickup/send/harvest endpoint was used.