[omartelo]

A maintainability pass over frontend/, no user-facing change — hence no CHANGELOG.md entry. Seven commits, each one finding on its own.

The one worth reading first

vitest.config.ts claimed the .tsx components stayed out of the coverage denominator. They did not: include only decides which unloaded files join the report, so anything a test imports was measured regardless — components pulled in transitively, the React hooks no node-environment test can render, and the OS/framework boundaries invariant #1 exempts.

The number reaching review was 61% against an 80% bar, for a suite whose actual subject sits at 95%. a074fd7 excludes what the suite cannot reach so the summary means what invariant #1 says it means. Same tests, same assertions — only the denominator moved.

Duplication removed

• ae8ffab — five hooks each rebuilt the same sequence-guarded fetch, and the copies had drifted: the diff hook skipped the focus refetch, the checkouts hook swallowed its error, only the list blanked its rows when the request behind them changed. useRemoteResource owns the skeleton and each of those becomes a named option instead of an omission. useDiffEditor/useFileEditor were the same file twice; the view lifecycle moves to useCodeMirrorView and both stay as thin wrappers with their distinct selection contracts.
• 1592ccc — eight sites hand-rolled the same localStorage read, each with its own idea of what a bad stored value means. lib/prefs.ts splits it the way parsePullsSort already did: pure parsing the suite owns, a two-line boundary it does not. localStorage is no longer touched anywhere else. usePanelVisible covers both collapsible navigators, keeping the stored encoding so no install loses its choice.
• faa1b88 — one SkeletonLines behind the three loading skeletons; one FooterButton behind the status strip's five. That also clears the last template-literal classNames outside components/ui, so cn() is now genuinely the only class-merging helper.

Files that had grown past their job

• 3e51c8b — Pulls.tsx held six components in 732 lines. The screen (which pull request is in view, what an action there means for the checkout it lives in) and the view (header plus four tabs) have separate jobs and no seam between them. Each moves to a file named after it: 732 → 255, nothing in the folder above 330.
• e0f854c — the worktree keep/remove/force question was five functions and two useStates interleaved with the sidebar's layout and resize wiring; it becomes useWorktreeClose and the sidebar keeps only the two dialogs. SessionGroup was forwarding three callbacks it never read plus a projectName already derivable from the projectPath beside it. SessionSidebar 327 → 253; SessionGroup 14 props → 11.

Behaviour changes

Two, both deliberate:

• A boolean pref holding something writePref never emitted now reads as its default instead of as on.
• f1511b5 fixes a real screen-reader bug: the notifications badge announced its count through an aria-label on a bare span element, which carries no role — so nothing announced it. The count moves into the trigger's own accessible name and the dot goes aria-hidden. The review button in the footer also gained a label it never had, via FooterButton. Biome a11y warnings 13 → 12; the rest of that documented backlog stays.

Same commit also makes THEMES/TERMINAL_THEMES actually drive the Appearance picker (it redeclared both lists, so a mismatch was silent — a missing label is now a type error), gives AppUpdateGate the dependency array it was missing, and moves the store setting keys to lib/project-settings.ts, since the contract they mirror is internal/store/settings.go's and not a settings pane's.

Verification

Local gate green: gofmt/go vet/go test, biome check, tsc, vite build, 491 frontend tests.

The suite cannot render components, so the render path was driven for real — the binary built and served to a headless Chromium:

• sidebar → group → card with branch and diff stat, live PTY, footer segments with correct labels and aria-pressed;
• the Review dock mounting CodeMirror over an actual diff, gutter and line decorations intact;
• Settings → Appearance, and a theme click landing in both html.dark and the stored pref;
• the split Pulls screen rendering its list column, skeleton and error branches.

No page errors. What this did not reach: the happy path of PullRequestView and PullsEmptyState both need gh and a live PR, so they are worth a pass in task dev before merging.