BEFORE — ticket detail as it renders today (§TD3), for every viewer alike.
This is an HTML reconstruction, not a capture of the live app: `pipeliner.omdev.tech` is session-walled and no local dev server was running. Anatomy taken verbatim from `TicketHero.tsx`, `TicketFacts.tsx` and `TaskDetailPane.tsx`.
Status is read-only for everyone. There is no Move Forward, no Change Status, no Assign control and no assignee anywhere on the screen — including for the CTO and the developer actually doing the work.
#1527 Spec ✦ Feature

# Ticket panel: Move Forward and a role-correct Change Status control

RARequested by Redmine Admin Updated 2 hours ago Complexity 7/10 ✳ ✎ Edit ⏸ Pause

## ◎Context

First half of the frontend. A designer-agent section is appended to the design system first, then `TaskDetailPane.tsx` gains a Move Forward action and a Change Status control, both rendered strictly from the server-provided capabilities.

### At a glance

Reference
  #1527
Stage
  Spec
Type
  Feature
Complexity
  7/10
Criteria
  14

No “Assigned to” row exists today, for any viewer.