feat(branding): apply fork identity across app surfaces

[nohat]

Goal

Give this fork a consistent personal identity across its user-facing app surfaces while keeping the fork straightforward to sync with upstream T3 Code.

Scope

• Establish one fork-owned source for the app display name/brand and the icon assets, with only narrow integration points in upstream-owned code.
• Apply the identity to the main window wordmark and other primary brand marks in the web client, including local/hosted web where applicable.
• Apply it to desktop OS-facing identity: packaged app name, Activity Monitor/Dock/launcher labels, app icon, and native About panel.
• Apply it to mobile app name, launcher icon, and About screen.
• Show the fork's own version in the About UI and native About panel, using the existing fork version pipeline.
• Use the existing icon draft in the local design kit as the source artwork and export the required platform assets.
• Keep the branding delta small and easy to preserve during upstream sync; avoid broad edits to unrelated product code or assets.

Explicit non-goal

Do not replace every occurrence of “T3 Code”/“T3Code” across the UI or codebase. Contextual product copy, provider references, settings descriptions, legal text, docs, and internal identifiers remain as they are unless changing a specific value is required for the app identity above.

Acceptance criteria

• The chosen name and wordmark are consistent across primary web, desktop, and mobile app entry points.
• The correct icon appears in packaged desktop and mobile apps, and in browser favicon/touch-icon surfaces where applicable.
• The operating system identifies the desktop app by the chosen name, including Activity Monitor and the native About panel.
• About screens show the fork's version rather than the upstream package version.
• Branding is configured from a fork-owned source with the smallest practical set of upstream integration changes, preserving the normal upstream sync workflow.
• Changes are reviewed on applicable client surfaces: web (local and hosted build), desktop, and mobile.