Desktop Material implementation UI inventory

Date: 2026-07-20
Worktree: desktop-material-ui-audit-20260720
Scope: static implementation inventory for comparison with the supplied Material Design UI Recreation (1).zip
Companion reference contract: docs/verification/ui-design-audit-2026-07-20/reference-inventory.md

This document inventories the implementation surfaces that a full visual audit must exercise and records the static remediations made for this audit. It does not claim pixel parity or runtime success: final findings belong in the post-fix headless evidence and remediation report. Reference IDs below are the stable IDs defined by the companion reference inventory.

Method and counting rules

The inventory was produced by:

1. Enumerating every file below app/src/ui, then grouping the 474 React .tsx modules by top-level feature directory.
2. Treating the central state and route registries as canonical: SelectionType, RepositorySectionTab, FoldoutType, PopupType, PreferencesTab, RepositorySettingsTab, and CloneRepositoryTab (app/src/lib/app-state.ts:82-99,517-558; app/src/models/popup.ts:57-177; app/src/models/preferences.ts:1-13; app/src/ui/repository-settings/repository-settings.tsx:74-91; app/src/models/clone-repository-tab.ts:1-6).
3. Verifying those registries against their render switches and the static completeness test (app/src/ui/app.tsx:2461-4488,6175-6283; app/src/ui/repository.tsx:1064-1148; app/src/ui/preferences/preferences.tsx:433-541,628-884; app/test/unit/feature-registration-completeness-test.ts:24-81).
4. Enumerating native desktop menu events, the command-palette catalog, React context-menu call sites, shared control primitives, search/bulk registries, theme/language models, appearance models, SCSS viewport rules, and UI tests.
5. Comparing static implementation evidence to the reference contract. A static match means the expected structure or token exists in source; it is not a pixel or behavior pass. Extension means reachable product UI is not designed in the zip and must be regression-tested without forcing it into an unrelated prototype screen. Preliminary gap means source evidence is strong enough to nominate remediation before capture. Runtime required means source alone cannot decide.

Counts are declarations or registered logical surfaces, not a claim that all conditional states render simultaneously. Feature flags, selected repository/account/provider, authentication, remote API state, Git state, first-run state, and viewport determine reachability. Test-file counts use filenames/path membership; language-aware counts use explicit LanguageModeChangedEvent, translate, LocalizedText, or translation-helper references and therefore measure integration signals rather than translated-string completeness.

Quantitative ledger

Selector and entry-point conventions

No data-testid or data-test attributes were found in production UI. The audit driver should prefer, in order:

1. Native roles plus accessible names (button, tab, textbox, dialog titles, aria-label).
2. Stable IDs and product classes such as #changes-tab, #history-tab, #actions-tab, #releases-tab, #issues-tab, #github-api-tab, #triage-tab, #repository-tools-tab (app/src/ui/repository.tsx:397-463), .repository-tab-strip, and .repository-tab-search (app/src/ui/repository-tabs/repository-tab-strip.tsx:135-331,636-728).
3. Registry attributes such as data-search-surface-id, data-toolbar-item-id, and data-customization-surface (app/src/lib/collection-surface-registry.ts:13-378; app/src/ui/app.tsx:1708-1777).
4. Text only when the active language is explicitly fixed. Bilingual mode intentionally joins both strings and will invalidate English-only text locators (app/src/lib/i18n.ts:99-174).

Every automated interaction must resolve the current element after a rerender. Dialogs are stacked and can be raised, repository content changes on tab/account/repository selection, virtualized lists recycle rows, and responsive layout can move controls.

Application reachability map

startup
├─ initialization/recovery/error UI
├─ welcome → sign-in/configure Git/first-run checklist
├─ no repositories → tutorial/clone/create/add existing
└─ selected item
   ├─ cloning progress
   ├─ missing repository
   └─ repository workspace
      ├─ tab strip + app toolbar + banners + navigation rail
      ├─ Changes | History | Actions | Releases | Issues | Triage | GitHub API | Repository Tools
      ├─ repository | branch | app-menu | push/pull | worktree foldout
      ├─ notification right sheet + anchored appearance editors
      └─ stack of 119 popup routes (only Installing Update is modal)

The root discriminated union is at app/src/lib/app-state.ts:82-99; root rendering is at app/src/ui/app.tsx:6175-6283. The assembled repository shell renders update progress, tabs, toolbar, banner, submodule context, repository, build panel, notification center, appearance editor, popups, and drag/drop overlay at app/src/ui/app.tsx:5334-5385.

Shell, onboarding, and global surfaces

Repository workspace sections

getRepositorySections conditionally includes Actions, Releases, Issues, and GitHub API, while Triage and Repository Tools are always present (app/src/ui/repository-sections.ts:3-25). Rendering is centralized at app/src/ui/repository.tsx:1064-1148, so each row below is a real root workspace route rather than merely a popup.

Preferences and settings surfaces

Application Preferences: 11 pages

The left navigation and content switch are exhaustive for the PreferencesTab enum (app/src/models/preferences.ts:1-13; app/src/ui/preferences/preferences.tsx:433-541,628-884). Preferences is one of the stacked non-modal popups.

Repository Settings: 9 pages

Tab controls and rendering are at app/src/ui/repository-settings/repository-settings.tsx:315-500. ForkSettings is conditional; the preceding eight pages remain contiguous so enum values equal visible tab positions (:74-90).

The stale 2026-07-17 responsive JSON ledger still names repository-settings.Appearance (docs/verification/responsive-surface-matrix-2026-07-17.json:32709) and does not reflect the current Subtrees topology. Regeneration must use the current enum/render switch, not copy the old ledger.

Clone: 4 top-level pages and batch states

Foldouts, sheets, popovers, and anchored editors

Popup registry: all 119 registered dialog routes

PopupType is the canonical complete registered route list (app/src/models/popup.ts:57-177). renderPopup handles each type in app/src/ui/app.tsx:2461-4199, and the exact-set test fails if a type lacks a case (app/test/unit/feature-registration-completeness-test.ts:24-36). The stack renderer is at app/src/ui/app.tsx:4442-4488. Registration proves render support, not that every route is reachable in the Windows production menu: developer Test*, state-gated, legacy, and non-Windows-only paths require an explicit applicability disposition.

Only InstallingUpdate is in ModalPopupTypes (app/src/ui/app.tsx:424). All other routes are non-modal stacked dialogs: they can be dragged, clamped to the viewport, and raised on interaction by the shared Dialog (app/src/ui/dialog/dialog.tsx:17-60,82-180,860-923). This is more general than the package, where Settings is non-modal but ambiguously non-draggable and only Clone/Regex/Catalog explicitly drag (REF-PROTO-004, REF-RESP-002). Audit z-order, focus, drag bounds, Escape/dismiss, destructive confirmation, busy-state dismissal, and minimum viewport for each dialog family.

Complete enum order (the numbering is an audit index, not a priority):

1. RenameBranch
2. DeleteBranch
3. DeleteRemoteBranch
4. ConfirmDiscardChanges
5. Preferences
6. SettingsHistory
7. NotificationHistory
8. NotificationAutomations
9. LogHistory
10. FileHistory
11. CreateGitHubIssue
12. CreateGitHubPullRequest
13. GitHubPullRequestLifecycle
14. BranchRules
15. SparseCheckout
16. RepositorySettings
17. AddSubmodule
18. CloneableSubmodules
19. SubmoduleManager
20. SubmoduleConfig
21. SubtreeManager
22. AddSubtree
23. AddRepository
24. CreateRepository
25. CloneRepository
26. CreateBranch
27. SignIn
28. About
29. InstallGit
30. PublishRepository
31. Acknowledgements
32. UntrustedCertificate
33. RemoveRepository
34. TermsAndConditions
35. PushBranchCommits
36. CLIInstalled
37. GenericGitAuthentication
38. ExternalEditorFailed
39. OpenWithExternalEditor
40. OpenShellFailed
41. InitializeLFS
42. LFSAttributeMismatch
43. UpstreamAlreadyExists
44. ReleaseNotes
45. DeletePullRequest
46. OversizedFiles
47. CommitConflictsWarning
48. PushNeedsPull
49. ConfirmForcePush
50. StashAndSwitchBranch
51. ConfirmDiscardStash
52. ConfirmCheckoutCommit
53. ConfirmDeletePushedTag
54. CreateTutorialRepository
55. ConfirmExitTutorial
56. PushRejectedDueToMissingWorkflowScope
57. SAMLReauthRequired
58. CreateFork
59. CreateTag
60. DeleteTag
61. LocalChangesOverwritten
62. ChooseForkSettings
63. ConfirmDiscardSelection
64. MoveToApplicationsFolder
65. ChangeRepositoryAlias
66. ChangeRepositoryGroupName
67. ThankYou
68. CommitMessage
69. MultiCommitOperation
70. WarnLocalChangesBeforeUndo
71. WarnUndoPushedCommit
72. WarningBeforeReset
73. WarnResetToPushedCommit
74. InvalidatedToken
75. InsufficientOAuthScopes
76. CommandPalette
77. AddSSHHost
78. SSHKeyPassphrase
79. SSHUserPassword
80. PullRequestChecksFailed
81. CICheckRunRerun
82. WarnForcePush
83. DiscardChangesRetry
84. PullRequestReview
85. UnreachableCommits
86. StartPullRequest
87. Error
88. InstallingUpdate
89. TestNotifications
90. PullRequestComment
91. UnknownAuthors
92. TestIcons
93. ConfirmCommitFilteredChanges
94. TestAbout
95. TestCLIAction
96. PushProtectionError
97. BypassPushProtection
98. GenerateCommitMessageOverrideWarning
99. GenerateCommitMessageDisclaimer
100. CopilotConflictResolutionDisclaimer
101. HookFailed
102. CommitProgress
103. AddWorktree
104. RenameWorktree
105. DeleteWorktree
106. EditCopilotBYOKProvider
107. EditCopilotBYOKModel
108. ConfirmDeleteCopilotBYOKProvider
109. CopilotConflictResolutionAlwaysNudge
110. DeleteWorktreeFailed
111. BatchCloneProgress
112. ExportRepositoryList
113. ImportRepositoryList
114. ExportTabSession
115. ImportTabSession
116. MergeAll
117. PullAllRepositories
118. CommitAndPushAll
119. OpencodeFix

The four Test* routes are developer/test surfaces but remain registered and renderable; they must be either excluded explicitly from production acceptance or audited as reachable diagnostics. MoveToApplicationsFolder is not applicable to the repository's Windows-only product boundary and should be marked N/A rather than driven. Sign-in has a five-value store enum (Endpoint Entry, Existing Account Warning, Authentication, Two-Factor Authentication, Success), while the current UI switch directly renders four paths and has no distinct two-factor branch (app/src/lib/stores/sign-in-store.ts:25-45; app/src/ui/sign-in/sign-in.tsx:86-104,200-219). Treat two-factor as a static reachability question for product owners, not as a design-zip gap.

Menus, context menus, command palette, and keyboard surfaces

Shared controls and universal visual states

These primitives are reused across hundreds of surfaces. A defect here has broad blast radius, so the runtime audit should test the primitive matrix before diagnosing each consumer independently.

Search and bulk-action audit registry

The 40 registered search IDs are: accounts, actions-runs, actions-caches, actions-job-log, actions-workflow-catalog, actions-workflows, branches, fork-network-repositories, fork-network-branches, pull-requests, changes, clone-repositories, add-submodule-repositories, add-subtree-repositories, command-palette, diff, github-api-rest, github-api-graphql, github-issues, github-releases-search, history-commits, copilot-models, ollama-models, material-context-menu, notification-automations, notifications, repositories, repository-tools, provider-triage, cheap-lfs, git-ignore-templates, submodules, arrange-tabs, close-tabs-containing, tab-search, tab-style-font, subtrees, tag-lifecycle-inventory, version-history, and worktrees (app/src/lib/collection-surface-registry.ts:13-255).

The 12 registered bulk-action IDs are Actions runs, Actions caches, branches, clone repositories, notifications, repositories, releases, tags, submodules, subtrees, stashes, and worktrees (app/src/lib/collection-surface-registry.ts:273-378).

The completeness test discovers production search inputs and regex builders and compares exact IDs (app/test/unit/collection-surface-registry-test.ts:70-213), then validates bulk surfaces and required Actions/Release commands (:233-255). This is strong static coverage for registered search grammar, but it does not demonstrate the zip’s exact seven default search contexts or their fixture results (REF-SEARCH-*). Each runtime comparison still needs plain, regex-valid, regex-invalid, filter-chip, builder, clear, and zero-result states.

Theme, typography, iconography, motion, and appearance

Language and copy

The implementation defines exactly the project-policy modes English, playful Hong Kong-style Cantonese, and bilingual (app/src/models/language-mode.ts:1-15). It persists English by default without consulting OS locale (app/src/lib/language-preference.ts:1-57). Translation behavior and bilingual English · 廣東話 composition are centralized at app/src/lib/i18n.ts:11-174; the resource union contains 806 keys in app/src/lib/i18n-resources.ts.

The design package is English-only and cannot establish alternate-language layout (REF-I18N-001). Runtime design parity should therefore use English for exact reference copy, then separately validate Cantonese and bilingual at desktop, minimum, narrow, and 200-percent scale.

Preliminary coverage gap: only 39 of 474 UI TSX modules contain an explicit language-integration signal. This does not prove the remaining 435 expose hard-coded user-visible copy, but static inspection found many literal English labels in reachable surface modules. The current tests (28 language-aware files) prove infrastructure and selected consumers, not every user-facing surface. A complete remediation needs a visible-string extraction/audit, translation-key adoption across all reachable menus/pages/dialogs/sheets/errors, fallback tests, and bilingual wrapping/truncation checks. Owners are cross-cutting feature modules, app/src/lib/i18n-resources.ts, app/src/lib/i18n.ts, the desktop menu builder, and language-mode UI/E2E tests.

Responsive and scaling behavior

The implementation has real responsive reflow: 107 viewport media declarations across 59 SCSS files. Main shell breakpoints occur at approximately 1100, 760 (and height 420), 620 (and height 520), and 420×320 (app/styles/_material-shell.scss:611-849). Dialogs, Actions, preferences, Repository Tools, notifications, welcome, tabs, diff/history, and other features add local breakpoints.

The registered viewport matrix includes desktop 1000×687, minimum 640×480, narrow 480×640, short 960×420, wide 1600×900, 125/150 percent zoom, and minimum-window 200 percent zoom. The responsive catalog test loads and validates the catalog and enum relationships (app/test/unit/responsive-surface-catalog-test.ts:61-102,226-233).

This deliberately differs from REF-RESP-001: the prototype fixes a minimum 1240×700 shell and scales the whole root instead of reflowing. Acceptance needs two tracks:

• At the reference baseline, compare exact shell geometry, fixed panels, dialogs, and UI scale behavior.
• At implementation-supported narrow/minimum sizes, assess usability as an extension; do not flag useful reflow solely because the prototype clips.

The catalog is now statically current at 86 logical rows: 66 grouped surfaces and 20 nested surfaces, comprising 85 product rows plus one deterministic paused/interrupted clone-recovery row. The grouped set now includes Cheap LFS, and the nested set includes Preferences → Git → Global ignore, account switcher, workflow manager, workflow catalog, and workflow dispatch. The prior 79-row 2026-07-17 evidence remains historical and must not be reused as a post-fix runtime receipt.

The responsive driver now accepts reviewed --theme light|dark and --language-mode english|cantonese|bilingual values while preserving English/light defaults. Schema-v2 receipts fail closed on requested, persisted, body/document-observed, and Appearance-UI state; every evidence row carries the appearance receipt. It also requires contained loopback provider readiness, safely hydrates the synthetic account/repository/Actions state without exposing the token, rejects provider mutations, and gates every settled viewport on bundled-font readiness. These are harness capabilities, not evidence that the final matrix has run.

Existing automated evidence and its limits

There is no exhaustive screenshot baseline spanning all routes/states. The single E2E file and one filename-classified visual test cannot support a claim that every element matches the zip.

UI beyond the prototype

The following reachable implementation areas have no direct design in the zip and must be treated as product extensions, not silently omitted from the audit:

• Releases, Issues, provider Triage, GitHub API, and the 30-entry Repository Tools hub.
• Worktrees; Submodule/Subtree managers and configuration; Cheap LFS; tag lifecycle; sparse checkout; branch rules; fork network/settings.
• GitHub notification source, notification automations/history, bulk notifications.
• Build & Run, command palette, repository/tab/session import-export, account/provider/auth/scopes/security failures.
• Copilot BYOK/Ollama model/provider management, generated-message disclaimers, conflict assistance, OpenCode fix.
• Accessibility and Agent Access preferences; prompts; owner-scoped appearance, app identity, repository logos, multiple palettes/surface/elevation/density modes.
• Rich Actions caches/artifacts/attempts/bulk operations; rich release asset lifecycle; issue comments/editing; API response tooling.
• Crash recovery, update installer, real Git/GitHub failure/retry/progress paths, welcome/tutorial/first-run and missing-repository states.

For these extensions, audit consistency with implementation design tokens/primitives and project requirements rather than inventing pixel targets from unrelated prototype screens.

Static remediation and remaining gap matrix

These are source-backed dispositions for the parent audit. A static fix is not a runtime pass; the companion static-findings.md separates fixed, approved, and pending-runtime work.

Runtime audit matrix derived from this inventory

At minimum, the parent headless audit should pair the reference acceptance summary with these implementation dimensions:

• Root states: welcome, no repository, cloning, missing, normal repository, startup/repository/dialog error.
• Shell: light and dark at baseline; title/menu/window buttons; tabs default/active/rename/format/overflow; toolbar every sync state; rail active entries; banners; account switcher.
• Reference workspaces: Changes filters closed/open/plain/regex invalid, all/partial/none inclusion, add/modify/delete diff, commit disabled/focus/warning/busy/undo/no-change; History search/chips/tag/unpushed/detail; Actions success/failure/running/manager/catalog/dispatch/log.
• Reference overlays: repository and branch sheets; Settings reference pages; Clone list/filter/selection/progress/done/empty; Notification all/unread/empty; Settings history HEAD/undo/redo; Regex Build/Guide/valid/invalid/apply.
• Implementation extensions: one representative normal, empty, loading, error, destructive confirmation, progress, and result state for each additional workspace/manager family.
• Cross-cutting: English exact-copy comparison, then Cantonese and bilingual; Material default appearance before custom variants; Light/Dark/System; OS and user reduced motion; keyboard-only focus; 100/125/150/200 percent scale; desktop/minimum/narrow/short/wide viewports.

Appendix: .tsx feature distribution

This distribution is included so future audits can detect implementation areas omitted from a route manifest. Counts are React .tsx files below each immediate app/src/ui child; root means files directly in app/src/ui.

root 20; about 2; accessibility 1; account-switcher 1; acknowledgements 1;
actions 15; add-repository 3; app-menu 5; appearance 4; autocompletion 5;
banners 16; branch-rules 1; branches 16; build-run 3;
change-repository-alias 1; change-repository-group-name 1; changes 15;
check-runs 9; checkout 1; choose-fork-settings 1; cli-action 1;
cli-installed 1; clone-repository 8; command-palette 1; commit-message 1;
commit-progress 1; commit-push-all 1; copilot 5; create-branch 1;
create-github-issue 1; create-github-pull-request 1; create-tag 1;
delete-branch 3; delete-tag 1; dialog 9; diff 22; discard-changes 3;
drag-elements 1; editor 1; file-history 1; forks 1;
generate-commit-message 1; generic-git-auth 1; github-api-explorer 1;
github-issues 1; github-projects 1; github-pull-request-lifecycle 1;
github-releases 1; history 12; hook-failed 1; install-git 1;
installing-update 1; insufficient-scopes 1; invalidated-token 1;
keyboard-shortcut 1; lfs 2; lib 78; local-changes-overwritten 1;
log-history 1; merge-all 1; merge-conflicts 1; multi-commit-operation 21;
no-repositories 2; notifications 10; octicons 2; open-pull-request 4;
open-with-external-editor 1; preferences 16; publish-repository 2;
pull-all 1; push-needs-pull 1; rebase 1; release-notes 1;
remove-repository 1; rename-branch 1; repositories-list 2;
repository-list-transfer 2; repository-logo 2; repository-rules 3;
repository-settings 13; repository-tabs 6; repository-tools 12; reset 2;
resizable 1; saml 1; secret-scanning 3; settings-history 1; shell 1;
sign-in 1; sparse-checkout 1; ssh 3; stash-changes 1; stashing 4;
submodules 3; subtrees 2; suggested-actions 4; tab-session-transfer 2;
tag 2; terms 1; test-notifications 1; thank-you 1; toolbar 11;
tutorial 5; undo 2; unknown-authors 1; untrusted-certificate 1;
upstream 1; version-history 1; welcome 5; window 5;
workflow-push-rejected 1; worktrees 7.

The distribution totals 474. It is an ownership map, not a severity metric: a single root switch can expose 119 routes, while a large utility directory may contain no independently reachable page.