You're offline — showing cached data

MC-4604

Ticket pages: fix formatting issues and simplify advanced runtime UI
2026-06-13 08:47:08 SAST
Home Board MC-4604

Ticket pages: fix formatting issues and simplify advanced runtime UI

Elmar reported that the ticket detail sidebar exposes old/internal workflow controls: Runtime, Open raw console, Open workbench, WAT/agents/review gates/decisions. Review and si...
State Done Next Action Closed Owner Luci Runtime Closed Age 11d ago
MC-4604
Ticket is done; runtime is closed. · profile claude_opus_1m_high · cwd /home/lucienne/workspace/mission-control/.claude/worktrees/pool-2 · uptime 10d 14h · last activity 10d 11h ago

Description

MC-4604
Elmar reported that the ticket detail sidebar exposes old/internal workflow controls: Runtime, Open raw console, Open workbench, WAT/agents/review gates/decisions. Review and simplify the ticket interface so human-facing ticket detail does not expose obsolete or controller-only controls. Controller decision: - Runtime backend/session ledger/tmux work is still used by Luci workers and pickup. Do NOT remove runtime_sessions, ticket_runtime.py, tmux dispatch, or Workbench route. - Runtime Console / Workbench remains an advanced internal operator surface for Luci debugging/recovery/evidence. - Human-facing ticket detail should hide or collapse advanced runtime/WAT controls by default. Normal users should see plain state/owner/timing/source and a clear next action. - Show runtime info only as concise status when useful: e.g. "Luci is working", "No live runtime", "Advanced console" behind an Advanced disclosure or admin-only affordance. - WAT routing buttons (Larry/Tessa/Council/Luci review/Approve/Close) are controller tools, not default ticket UI. Keep if still needed internally, but move behind Advanced/Controller tools. Required work: 1. Audit ticket.html and related partials/scripts for all runtime/workbench/WAT controls. 2. Define normal vs advanced ticket-detail IA. 3. Implement default-hidden/collapsed advanced controls without breaking controller operations. 4. Preserve API/runtime functionality and links for Luci/operator access. 5. Add regression tests that the default ticket page does not expose "Open workbench", "Open raw console", WAT agent buttons, or runtime switching controls unless advanced mode is explicitly opened/enabled. 6. Browser-smoke live ticket page desktop + 375px mobile. Capture screenshots. Acceptance: - Default ticket detail page is simple and human-facing. - Runtime backend still works; /runtime-workbench remains reachable directly. - Advanced/controller controls are available only behind an explicit Advanced/Controller surface. - Tests pass and live screenshots show no runtime/WAT clutter by default. Expected check-in: 2026-06-02T17:32:30+02:00 Update from Elmar (2026-06-02): lots of formatting issues remain on ticket pages. Expand scope beyond runtime/WAT cleanup into a full ticket-page visual formatting pass. Additional acceptance: - Audit ticket detail pages on desktop and mobile. - Fix spacing, wrapping, overflow, button alignment, panel hierarchy, and visual clutter. - Preserve Settings runtime controls for luci-persistent; only reduce clutter on ticket pages. - Capture before/after screenshots for representative ticket states. - Add regression coverage where feasible for key layout affordances.

Activity

done
Luci is working...
Live
No activity yet
Help