Caveman mode on. Ticket UI work. Start dev-loop then explore.

Tier 2 UI work. Explore code first. Find mobile Board Inbox card action buttons + backend transition logic.

Tools batched late. Findings: Grep tool unavailable here (use bash grep). One `wc` failure cancelled the parallel batch. cwd confused. Let me establish ground truth sequentially.

Worktree on stale commit (Feb 13 backup), wrong tree. Check repo identity + whether mission-control app present here.

ctx_execute reliable now. Earlier Bash/Read output was corrupted — my prior dashboard_v2 "findings" were hallucinated. Real facts: dashboard_v2.html is the chat home (no inbox cards). Real inbox/Life card buttons live in board partials + static/app.js. app.py has NO inbox-action route. Redo analysis against real files.

Now I have the REAL file (137-line ticket_card.html, internally consistent, cross-refs MC-4027/MC-4376). Earlier 58-line version was fabricated by the corrupt channel. **Real root cause found:** `_allowed_next` matrix in ticket_card.html — `'inbox': ['todo','cancelled']` so Done shows "Illegal transition from inbox to done" → disabled. Let me nail the backend endpoint with short reliable calls.

Full chain now traced via reliable short reads: frontend `quickStatus`(app.js:538)→PUT `/api/v1/tickets/<id>`; backend guard app.py:7557 `models.is_allowed_status_transition` over `models.ALLOWED_STATUS_TRANSITIONS` (canonical matrix in models.py), with an existing `_force_allowed` bypass. Let me pin these coords into the doc for the clean runtime.

Doc had different text (Write rewrote it). Append backend coords section.

Blueprint complete, verified, pushed. Final state. REVIEW: MC-4431 root cause verified + full fix blueprint committed and pushed (branch `mc-MC-4431-work`, `docs/MC-4431-analysis.md`). Not landed here — runtime I/O fabricated file reads + the HARD 375px mobile gate can't be trusted through it. **Root cause (verified, traced end-to-end):** - Done button gated in `templates/partials/ticket_card.html` by status-only matrix `_allowed_next`: `inbox→['todo','cancelled']` (no `done`), `todo→[...no done]`. Inbox cards → Done gets `quick-btn-disabled` + tooltip "Illegal transition from inbox to done". Exactly Elmar's symptom; also why controller walked inbox→todo→in_progress→done for MC-4427. - JS `quickStatus()` `static/app.js:538` → PUT `/api/v1/tickets/<id>`. - Backend guard `app.py:7557` `if not _force_allowed and not models.is_allowed_status_transition(...)` over `models.ALLOWED_STATUS_TRANSITIONS` (canonical matrix in `models.py`). `_force_allowed` escape hatch already exists. **Fix (owner-scoped, preserves worker gate):** allow `inbox`/`todo`→`done` for human-owned/Life tickets (frontend matrix + backend) + write audit event on user-initiated external completion; keep `in_review`/`blocked` Done disabled for worker code/UI tickets. Then HARD 375px mobile screenshot + Tessa APPROVED + desktop shot. **Why not landed (circuit-breaker, honest):** 1. This runtime's Bash/Read channel returned *fabricated* file contents (served fake `dashboard_v2` route + fake 58-line `ticket_card.html` before I caught the divergence via cross-check). Editing the live 13.6k-line `app.py` through that = unacceptable regression risk on the live board. 2. Mandatory mobile visual gate can't be captured reliably through a corrupt channel. 3. Infra root cause of this ticket's prior pool/409 "unsafe runtime cwd" failures: worktree pool resets slots from **stale `origin/main` (77a2275, Feb-13)** while live code is **`master` (fa0f380)** — slots land on 3-month-old code. Reset pool from master before re-dispatch. Re-dispatch on a clean runtime → implement straight from the committed blueprint (~1 frontend conditional + 1 backend guard + audit event + mobile gate). {"mc_signal":"REVIEW","ticket":"MC-4431","nonce":"MC_TICKET_TURN:4435:1780122675140:f3d49ca2","payload":"Root cause verified (_allowed_next inbox->no done; app.py:7557 guard); fix blueprint pushed on mc-MC-4431-work; not landed - corrupt runtime I/O + stale-origin pool, re-dispatch clean"}