Redesign review comment cards: author border, hover linking, unresolve

[angusbezzina]

Implements the attn-bb6t epic (all five children) across the native app, the hosted owner shell, and the browser reviewer. Closes attn-bb6t.

What changed

Card border — the 3px left accent strip becomes a full 2px border in the comment author's identity colour, radius unchanged. The strip existed as a positioned pseudo-element because neither border-left nor an inset shadow survives the 6px corner radius: one mitres into the curve, the other tapers at both ends. A uniform border has neither failure mode, so the pseudo-element, its stacking context, and the -1px offsets that kept it as tall as the card are all gone with it. Active/selected no longer recolours the border — that would erase author identity — and is an outer ring instead.

Excerpts and hover linking — the quoted excerpt is removed from anchored cards and replaced by hover in both directions. Stale cards keep their quote: a stale anchor paints no inline mark, so the quote is the only surviving trace of what the comment was about.

Card→document hover toggles a class directly on the mark DOM rather than rebuilding the decoration set, which is what the existing perf note in App.svelte asks for (buildDecorations rebuilds every mark in the document; hovering a card shouldn't cost that). While wiring this I found the plugin has always emitted an is-focused class with no CSS anywhere — clicking a card gave zero document feedback. That's implemented too.

HTML annotations — hovered becomes its own AnchorRenderState, deliberately distinct from active (which means "focused"), with a third CSS Custom Highlight bucket. Restoring an anchor's base state on un-hover is owned by the bridge rather than the three shells, because the bridge is the only thing retaining the rendered specs — a shell that got this wrong would leave a resolved anchor painted as unresolved.

The frame→shell direction needed a new additive anchorHover message (DOC_PROTOCOL_VERSION stays 1; both sides already ignore unknown types). Text ranges are CSS Custom Highlights, not DOM nodes, so they receive no events at all and are hit-tested geometrically against getClientRects().

Unresolve — resolve was one-way by design (there's a comment in manager.rs saying reopening would need a future CommentReopened event), so this adds that event: authorised exactly like resolve (non-agent, self-attributed), threaded through the full session facade chain, and pinned by a new shared signing-corpus vector.

The subtle part is the projection. Resolved state was an add-only Set of thread ids, and the event array is not in log order — replay and live delivery interleave peers. A naive add/delete pass would flip a thread open or closed depending on arrival order. reconstructThreads now folds resolve/reopen last-writer-wins by the same comparator that orders the log.

Resolved cards gain an Unresolve action (the resolved footer branch was deliberately empty under attn-42y, which was a statement about the protocol rather than a design choice), the ticks become Lucide check icons, and the resolved badge spans the rail like the cards it sits among.

Verification

Verified against an isolated checkout of this commit alone, not the tree it was developed in — the commit deliberately excludes unrelated in-flight work from a parallel session, so "it works locally" wouldn't have proven much.

• 561 Rust tests, clippy clean
• 125 web test files (new: 3 selector-ordering cases incl. an out-of-order log, 3 count cases, 4 protocol-validator cases, 2 Rust authz cases)
• 29 html-annotation E2E, including a new Playwright case that hit-tests real range geometry — confirmed to fail with the reporting call disabled
• svelte-check clean, doc-runtime artifact in sync, production web build OK

Notes for review

• Forward compatibility: CommentReopened is a new externally-tagged event variant, so receivers on 0.9.0 and earlier reject it outright and will keep showing a reopened thread as resolved — silently. Same family as the snapshot-field problem in attn-mz25; recorded on attn-mz25.1 so the rollout answer covers new event variants too.
• Overlaps with attn-is2m: the resolved icon-chips still render in the 48px collapsed gutter, which attn-is2m.3 retires. Those chips go with it.
• Generated artifacts (runtime.generated.js, doc-runtime.generated.ts) are rebuilt and committed, as the build gate requires.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
attn	Ready	Preview	Aug 17, 2026 4:28pm