MC-4283 — Add page-level back/home/board navigation across Mission Control

Home Board MC-4283

Add page-level back/home/board navigation across Mission Control

Elmar request from Telegram: review navigation buttons across Mission Control. Example: `/reports` has no obvious navigation back to Home, Board, or elsewhere. Mobile has bottom...

State Done Next Action Closed Owner Luci Runtime Closed Age 17d ago

← MC-4283

Ticket is done; runtime is closed. · profile claude_opus_1m_high · cwd /home/lucienne/workspace/mission-control · uptime 16d 23h · last activity 16d 21h ago

Description

MC-4283

Elmar request from Telegram: review navigation buttons across Mission Control. Example: `/reports` has no obvious navigation back to Home, Board, or elsewhere. Mobile has bottom nav, but desktop/top-level pages need simple navigation between pages. Start by adding buttons to go back / return to main surfaces. Live repro already checked: - URL: http://100.118.207.3:3001/reports - Browser snapshot shows `Reports & Plans`, search, report cards, actions, load more; no visible Home/Board/back navigation entry point. - Related broad visual campaign: MC-4119, but this ticket is the concrete navigation/back-button implementation slice. Scope: 1. Audit visible navigation affordances across main MC pages, at minimum: Home/cockpit, Board, Reports, Tasks, Runtime/Workbench, Settings, ticket detail, markdown/report viewer pages. 2. Add a consistent lightweight page-level navigation strip / back buttons where missing. - First priority: Reports page should have obvious buttons: Back, Home, Board. - Preserve existing mobile bottom navigation; do not regress it. - Desktop should not rely on browser back or hidden mobile controls. 3. Keep design small and consistent with current MC visual system; avoid a large redesign. 4. UA requirement: use live browser after implementation on desktop and mobile viewport, click the new buttons, and check console. Acceptance criteria: - `/reports` has visible, tappable navigation back to prior page and to Home/Board. - Other top-level pages with dead-end navigation get equivalent back/home/board affordances. - Mobile bottom nav remains present and usable. - No broken links or console errors from the new controls. - Include screenshots/evidence in the ticket before closing. Expected check-in: today with navigation audit + first Reports-page fix.

Activity

done

Luci is working...

Details — Done · High · Luci ▼

State

Done

Closed

State

Priority

People

Owner (assigned to)

Controller

Timing / Details

Due Date

Snooze

Source telegram (human)

Project Mission Control

Created 17d ago

Updated 16d ago

Advanced / Operator evidence

Routing owner

Routes via

Operator console

Evidence

Ticket is done; runtime is closed. ticket_marked_done profile claude_opus_1m_high · cwd /home/lucienne/workspace/mission-control · uptime 16d 23h · last activity 16d 21h ago MC is visibility-only. Hermes Luci launches and gates work outside MC, then mirrors evidence/status here. Raw console: luci · claude/anthropic/opus[1m]

Workflow

Start Dev Review + QA ▾

Select phases to include:

Research (scott) Implement (larry) (required) Council Review (council) Code Review (luci) Validate (tessa) (required) Sign-off (atlas)

Agents

Review Gates

Decision

WAT routing: choose an agent, review gate, or decision. Buttons use the live runtime when one is attached.

luci 17d ago

Luci picking up this ticket (background worker).

luci 17d ago

Ticket picked up by Luci via MC dispatcher. MC-4283: Add page-level back/home/board navigation across Mission Control Work this ticket in the live tmux runtime. Use DONE:, REVIEW:, or QUESTION: when you need MC to reflect the next state.

luci 17d ago

[failed_to_inject] runtime_busy: Ticket runtime is not ready for input (status=running). Wait for the current turn to finish, or explicitly interrupt/restart the runtime before sending more terminal input. This message Ticket picked up by Luci via MC dispatcher. MC-4283: Add page-level back/home/board navigation across Mission Control Work this ticket in the live tmux runtime. Use DONE:, REVIEW:, or QUESTION: when you need MC to reflect the next state.

luci 17d ago

Ticket runtime send failed while dispatching. root_cause: HTTP Error 409: CONFLICT safe_retry: returned to `todo` for a fresh runtime retry. human_input_required: no

system 17d ago

RUNTIME TERMINAL STATE (MC-3482 contract) status: warning summary: Ticket runtime send failed; parked for automatic recovery. root_cause: send failed while injecting into ticket runtime: Ticket runtime is not ready for input (status=running). Wait for the current turn to finish, or explicitly interrupt/restart the runtime before sending more terminal input. This message was not sent. safe_retry: Queued message was returned to pending and the ticket was returned to todo for a fresh runtime retry; no human input is needed. stop_condition: After the configured retry limit, leave the ticket blocked for operator inspection instead of looping. human_input_required: no next_actions: - Pickup will retry the pending message in a fresh runtime. - Inspect runtime/send only if the retry fails again. artifacts: - ticket:MC-4283

Luci 17d ago

QUESTION: when you nedMCt eflect the next state. [MC_TICKET_TURN:4283:1779874061058:bb167665internal routing marker; do not mention this marker in your reply] [Optional MC completion sentinel: as the very last of your reply, on itsownline, youMAY emit thisexact JSONto auto-advnce the ticket: {"mc_signal":"DONE|REVIEW|QUESTION","tickt":"MC-4283","nnce":"MC_TICKET _TURN:4283:1779874061058:bb167665","payload":"<one-line summary>"} . Use DONE for completed code changes, REVIEW for research/analysis, QUESTION when blocked. The DONE/REVIEW/QUESTION prefix at the top of your reply remains required.] ❯ Press up to edit queued messages pasteagaintoexpand70557tokens 1MCPserverfailed ·/mcp Recent conversation: - luci: Luci picking up thisticket (background work). Elmar says: Tickt picked up by Luci via MC dispatche. MC-4283: Add page-levelback/home/board navigation across MissinControl Work this ticket in the live tmux runtime. Use DONE:, REVIEW:, or QUESON: when you need MC to reflect the next state. MC_TICKET_TURN:4283:1779874061058:bb167665 interna routing markr; do no mention this marker in your rply] [Optional MC completion sentinel: as he very last line of your reply, on its own line, you MAY emit this exact JSON to auto-advance the ticket: {"mc_signal":"DONE|REVIEW|QUESTION","ticket":"MC-4283","nonce":"MC_CKET _TURN:4283:1779874061058:bb167665","payload":"<one-line summary>"} . Use DONE for complted code changes, REVIEW for research/analysis, QUESTION when blocked. The DONE/REVIEW/QUESTION prefix at the top of your reply remains required.] ❯ Press up to edit queued messages pasteagaintoexpand70557tokens 1MCPserverfailed ·/mcp - luci: Luci picking up this ticket (background worker). Elmar says: Ticket picked up by Luci via MC dispatcher. MC-4283: Add page-levl back/home/board navigation across Mission Control Work this ticket in the live tmux runtime. Use DONE:, REVIEW:, or QUESTION: when you need MCt reflect thenxt sae. [MC_TICKET_URN:4283:1779874061058:bb16765 internal routing marker; do not metion ths marker in your reply] [Optional MC completion sentinel: as the very last line of your eply, on its own line,you MAY emit this exactJSON to auto-advance the tickt: {"mc_signal":DONE|REVIEW|QUESTION",ticket":MC-4283",noce":MC_TICKET_UR N:4283:1779874061058:bb167665","payload":"<one-line summary>"} . UseDONE for completedde changes, REVIEW for research/analysis, QUESTION when blocked. The DONE/REVIEW/QUESTION prefix at the top of your rply remains required.] pasteagaintoexpand70880tokens 1MCPserverfailed ·/mcp ✻51) ✽76 ✻26 ✶S7 p42 *r5 So8 ✢prut9 oi50 ·un1 tig… n2 ✢g3 …4 *3 ✶6 ✻ ✽9 ✻2 ✶3 *S4 pr5 ✢So pu4 pu↓ · still thinking with high effort) So still thinking with high effort ✢r still thinking with high effort * ●Read ⏵⏵bypasspermissionson (shift+tabtocycle)73037tokens 1MCPserverfailed ·/mcp ✶p7still thinking with high effort ✻502 ✽S11 ✻59 (/home/lucienne/workspace/mission-control/templates/base.html) 31still thinking with high effort Sprouting…43 ✶56 Sprouting…62 *7 71still thinking with high effort ✢4 ·Sprouting…8still thinking with high effort ✢1 *3 ✶64 6thought for 1s) ✻Sprouting… ● ⎿ Read108lines 1MCPserverfailed ·/mcp Sprouting…↑9 ✽ 73166tokens tmuxfocus-eventsoff·add'set-gfocus-eventson'to~/.tmux.confandre… ✻ ✶3 * ✢S pr ·So pu7 roti un ✢tg i… *ng … ✶ ✻ ✽ ✻ ✶ * ✢S p ·r Spou rt

luci 17d ago

Luci picking up this ticket (background worker).

luci 17d ago

Ticket moved to Todo: Add page-level back/home/board navigation across Mission Control

Luci 17d ago

DONE: MC-4283 — Page-level Back/Home/Boardnavstripliveacrossallbase.htmlpages(skippedoncockpit+embedded);/md-viewgetsinlineequivalentstrip.TessaAPPROVEDondesktop1280x720+mobile375x812;zeroconsole errors;mobilebottom-navunaffected.Mergedtomaster,pushed,luci-dashboardrestarted,assetcachev20260527-mc-4283-page-navserving. ⏵⏵bypasspermissionson (shift+tabtocycle)106307tokens Files: templates/partials/page_nav.html (new), templates/base.html, static/style.css (+61 lines), app.py (md-view strip + ASSET_VERSION). Commit 607d2b2. ⏵⏵bypasspermissionson (shift+tabtocycle)106307tokens Polish (not blocker, deferred): md-view inline strip looks centered inside its max-width:860px body while base.html strip sits flush-left in the 1200px container. ⏵⏵bypasspermissionson (shift+tabtocycle)106307tokens

luci 17d ago

Workflow action `review_ready` applied. Work ready for review.

api 17d ago

Closed (orchestrator). 607d2b2 on master, luci-dashboard restarted 11:41:18 SAST (fresh), live HTML has nav-board marker present. Tessa APPROVED desktop 1280x720 + mobile 375x812. Cockpit + embedded pages correctly skipped, /md-view has inline equivalent. Asset cache bumped to v20260527-mc-4283-page-nav. UA sign-off (runbooks/ua-signoff-gate.md): Tested: live / route → nav strip markers present; service restart confirmed (54s uptime). Console/network: per Tessa — clean, zero errors. Verdict: PASS

Live ▼

No activity yet

←