MC-4201

auto-triage: assigned to **tessa** (confidence 0.95); moved to `todo` for pickup -- skill: `QA testing, UX verification` > The ticket requires a human-style QA tester to verify UI rendering and role-gating on a mobile web app, which aligns perfectly with Tessa's expertise.

TESSA FINDINGS — MC-4201 Mobile ticket primary actions VERDICT: BY DESIGN (not a regression), but with a discoverability problem worth fixing. --- What I tested --- - MC-4199 (in_progress) and MC-4200 (needs_input) on mobile 390x844 - No role switching was possible at the view layer — ticket_detail route passes NO identity context to the template; the same HTML serves to all roles/tokens --- Role gating: NONE --- The ticket.html template has zero role-based conditionals. Done/Cancel/Todo/WAT buttons render identically regardless of who is viewing. The MC-4126 walkthrough (which ran as Luci) saw the same page as Elmar would see. Role gating is not the cause. --- Real cause: sidebar is hidden inside a closed <details> accordion on mobile --- On mobile (390x844), the sidebar collapses into a 'Details' accordion that is CLOSED by default. The accordion sits at y~700 on the page — visible without scrolling, but not opened. Primary actions are distributed as follows: 1. Header sticky row (always visible, top of page): - checkmark button (Mark Done) — visible at y~481 - reset button (Reopen/Todo) — visible at y~481 2. Sidebar actions inside closed Details accordion (NOT visible by default): - btn-todo (↺ Todo) — at y=790, just 54px below fold - btn-done (✓ Done) — at y=790 - btn-cancel (✗ Cancel) — at y=790 These become visible with a tiny scroll AFTER opening the accordion. 3. WAT workflow buttons (Send to Larry, Code review, Request Elmar sign-off, Close, Approve) — at y=1954-2147, deep below fold, only accessible via significant scrolling inside the expanded accordion. --- What the MC-4126 walkthrough missed --- The walkthrough used a text probe (document.body.innerText) — the sidebar's button text IS in the DOM, but inside a closed <details> element. The buttons render as display:flex in computed style (they ARE in the DOM and technically 'visible') but are positioned off-screen at top > viewport height when the accordion is closed. The Send button (comment box) was found because the comment form lives in the main column, not the sidebar. --- Screenshots --- /tmp/tessa-mc4199-desktop.png — desktop: sidebar fully visible with Done/Cancel/Todo /tmp/tessa-mc4199-mobile-anon.png — mobile initial view: only header buttons visible /tmp/tessa-mc4199-mobile-state-actions.png — mobile after opening Details + scrolling: Done/Cancel visible /tmp/tessa-mc4200-mobile-initial.png — MC-4200 mobile initial state --- Severity: Minor --- The Done and Reset buttons ARE in the sticky header (always visible). The full sidebar actions require expanding the Details accordion — discoverable but not obvious. The WAT workflow actions (Request Elmar sign-off, Close) require significant scrolling and accordion expansion — higher friction. No code change needed to unblock core flow. Discoverability improvement (e.g. show State action buttons outside the accordion, or open accordion by default) would be a Polish-level improvement.

Closed (orchestrator). Tessa verdict: BY DESIGN, no regression. Core flow intact — Mark Done + Reset live in sticky header (always visible on mobile). Sidebar State buttons (Todo/Done/Cancel) + WAT actions sit inside collapsed Details accordion (discoverable, not obvious). Walkthrough miss was text-probe artifact (DOM had them, but in closed <details>). Role gating: NONE — same HTML serves all roles. No code change required. Discoverability polish (surface State actions outside accordion / open accordion by default) deferred — minor improvement, would be a separate ticket if Elmar wants it.