[tianxingjian2406]

Fixes #335

What changed

• The copy button and the answer time under a finished reply fade in on hover only. Phones have no hover, so there was no visible way to copy an earlier reply. The row now carries pointer-coarse:opacity-100 and always shows on touch screens.
• With a mouse, the row still appears on hover and on keyboard focus.

Testing

• bun run typecheck, bun test components app lib, and bun run lint run clean (the known ghostty-web WASM baseline failure aside).
• Manual check from the issue: in touch emulation at 390px, the copy button and the time are visible under every finished reply. With a mouse, the row still appears on hover and on focus.

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.

An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[tianxingjian2406]

I have read the CLA Document and I hereby sign the CLA

[abhishekgahlot2]

Thanks for this. Before we can merge, please add a before/after screenshot or a short screen recording of the change working in the running app (the issue asks for one), plus a line on how you tested it.

[tianxingjian2406]

Screenshots at 390px with touch emulation (pointer: coarse, DevTools device mode), on /lab/session:

Before — the copy button and answer time stay hidden:

After — the copy button and answer time are visible:

How I tested it: I ran the app, enabled touch emulation at 390px, scrolled to a settled reply, and read getComputedStyle(row).opacity (0 before, 1 after). With a mouse the row still appears on hover or keyboard focus through the existing group-hover/turn and focus-within classes. The full suite passes (only the known ghostty-web baseline failure).

[abhishekgahlot2]

Merged, thanks @tianxingjian2406, good catch for phones.