You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 2666bcd
Browse filesBrowse the repository at this point in the historyBrowse files
feat(coil): rename the app to T3 Coil, with its own bundle id and certificate (#71)
APP_BASE_NAME T3 Code -> T3 Coil (DesktopEnvironment.ts)
productName T3 Code (Alpha) -> T3 Coil (Alpha) (apps/desktop/package.json)
bundle id dev.curlycloud.coil -> dev.curlycloud.t3coil
signing certificate T3X Code Signing -> T3 Coil Code Signing
APP_BASE_NAME is the one that matters: displayName is derived from it, and that reaches
app.setName(), the About panel, every window title, the Linux .desktop entry, and — through
getAppBranding() — the web UI, which reads the injected value rather than hardcoding one. So
renaming one literal renames the app almost everywhere it is computed.
Almost. 31 upstream-owned files still say "T3 Code" in body copy ("T3 Code needs the relay
client..."). Renaming those means displacement edits on 31 more upstream files for prose, which is
a bad trade against the sync cost; left alone deliberately, not missed.
Three things that look like they should have moved and must not:
- legacyUserDataDirName stays "T3 Code (Alpha)". It names a directory that already exists on disk
and is a hardcoded literal, not derived from APP_BASE_NAME. That is why #85 moved nobody's
threads and why this does not either. DesktopAppIdentity.test.ts now asserts both spellings a
few lines apart, with a comment, because the pair looks like a typo and is not.
- branding.test.ts's injected-branding case keeps "T3 Code" fixtures. It asserts that injection
WINS over the module constant; matching the fixture to the constant would make it pass whether
injection works or not.
- resolveDesktopProductName's "T3 Code (Nightly)" is upstream's literal on a branch this fork
never reaches, since nothing here builds a -nightly.<d>.<d> version.
The bundle id and certificate each invalidate every macOS TCC grant, because the designated
requirement names both. Done together so the user pays one round of permission dialogs rather than
two. The certificate half is NOT complete in code alone: a new name means a new certificate, so
setup-mac-signing.sh --rotate has to run before this merges, and designated-requirement.txt has to
be re-recorded from it. What is committed here has the new identifier and the CURRENT leaf hash,
which is exactly right until the rotation happens and loudly wrong after it — the release compares
that file byte for byte.
Also renames the pnpm-lock.yaml importer for the relay directory move in the previous commit;
without it `pnpm install --frozen-lockfile` fails, which is how it was caught.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
0 commit comments