Repository navigation
Spec and Ticket cards for the thread's Build item #80
Description
Part of #78. That Spec's Design (Spec card, Ticket card, Mobile) is the contract.
Scope
- Spec and Ticket hover cards on the header segment, following
PullRequestLinkPreview.tsx: the same delays, and fetching only while open. - The card detail read: Tickets by parent with counts by status, holds, waits with
required, attempts and last failure, acceptance, andgovernedByDecisions from ci: use blob:none to reduce checkout data pingdotgg/t3code#2485. While a card is open, it is re-read once a minute. - The footer shows the lead or worker activity and the updated time. Lead and worker thread links on Build cards #82 turns it into a thread link; until then it is plain text.
- Mobile: tapping the header subtitle opens the card as a sheet.
Classification
UI: new card components.
Acceptance
#78 acceptance 2 in full (seed:hq data: summary, Ticket counts, five Tickets and "+N more", hold note, blocker banner with the right "Starts when…"), the detail part of 5, and 7, on web and mobile.
Activity
feat: Spec and Ticket cards for a thread's Build item (#80)
pechhe commentedon Oct 16, 2026
Landed in t3peach 68730ed: hovering the web header's Build segment shows the Spec or Ticket card (summary, Tickets by status, holds, blockers with 'Starts when…', delivery, lead or worker, updated time), and tapping the mobile subtitle opens it as a sheet. The server reads a card only while it is open: each opening reads at once, re-reads are once a minute, and the last card is kept when HQ fails. Web rendered-verified against Development HQ; the mobile sheet is for Henry's phone check.