Rendered evidence for the two defects round-1 review caught in DecisionLineChip.tsx (label truncation, group-hover scoping) — both fixed, verified here against the REAL component render.
2026-08-27 · PR #6401 · branch fede/leasing-progress-canon
Methodology, disclosed. This worktree's .env.local has no SMOKE_PASSWORD (a documented pre-existing gap — see docs/planning/prod-cookie-auto-refresh.md), so an authenticated Live Preview screenshot of the real page wasn't available. Instead: the REAL ConversationThread component (same fixture shape as ConversationThread.decision-line-chip.test.tsx) was rendered via react-dom/client in jsdom, its output HTML (plus the real compiled Tailwind CSS the dev server serves) was loaded into a real Chromium via Playwright, and these are screenshots of that — production component code, production CSS, real hover, just not behind the login wall.
Using door: 'guard_caught' → "Safety check caught it", the longest of the four real door labels (22 chars) — the worst case for the truncation bug round 1 caught.
max-width:0. Nothing else on the row changes.Round 1's second finding: an unnamed group-hover: was matching ChatSurface's own relative group bubble wrapper, so hovering anywhere on a Clara message lit the chip's dot. Fixed via a named group/dlchip. This shot: mouse is over the BUBBLE, not the chip.
label max-width: 0px, dot background-color: rgba(0,0,0,0), while hovering the bubble.