Problem

Cluster 1 of the #2502 CSS class drift audit: the v2026.3.22 upstream sync (commit 0667aa5596, PR #2400) replaced the config-sidebar + config-nav + config-search__tag-* family with a new .config-top-tabs layout. The fork's ui/src/ui/views/config.ts still renders the old vocabulary, so the settings view ships with an unstyled left-rail sidebar and broken tag picker.

This is the same class of regression documented in remoteclaw/hq#57 (definition-site sync without paired call-site update), same as #2501 but in a different cluster.

Orphaned class references (21)

All at ui/src/ui/views/config.ts:

Scope

• In: ui/src/ui/views/config.ts — migrate all 21 orphan references to the upstream dashboard-v2 config-top-tabs vocabulary. Where the upstream redesign removed a concept entirely (e.g. the sidebar footer), fork may need to add a fork-owned CSS file (as fix(ui): restore nav-section/topbar class names after v2026.3.13-1 sync — paired call-site update missed #2501 did with topbar-brand.css) to preserve fork-specific UI. Investigate each case before deciding rename vs fork-owned restore.
• Out: Other drift clusters — audit(ui): one-shot CSS class drift audit — surface fork-side references with no CSS definition #2502 filed separate follow-ups per cluster.

Acceptance criteria

• config.ts emits only classes defined in the ui/src/styles.css import graph
• Re-run node scripts/audit-css-class-drift.mjs — cluster 1 (0667aa5) shows 0 orphans
• Settings view renders correctly in pnpm dev: sidebar/tabs, search with tag picker, subnav

References

• Parent audit: audit(ui): one-shot CSS class drift audit — surface fork-side references with no CSS definition #2502
• Sync commit: 0667aa5596 (sync: upstream to v2026.3.22 (2522 commits) #2400)
• Pattern post-mortem: remoteclaw/hq#57
• Similar fix: fix(ui): restore nav-section/topbar class names after v2026.3.13-1 sync — paired call-site update missed #2501 (cluster 2 of the same audit)