Run Lathe's own Connect service at lathe.codes #71

Lathe builds use upstream's public T3 Connect configuration. release-fork.yml reads the Clerk publishable key, JWT template, CLI OAuth client id and T3CODE_RELAY_URL from .env.example, and DEFAULT_HOSTED_APP_URL in packages/shared/src/connectAuth.ts is https://app.t3.codes. So any Lathe user on Connect goes through upstream's relay, Clerk instance and hosted web app.

Lathe should run its own Connect service at lathe.codes (domain registered 2026-10-16).

Scope

• Relay deployment for Lathe, with its own RELAY_URL.
• Hosted web app for pairing and /connect on a lathe.codes origin.
• A Lathe Clerk instance (publishable key, JWT template, CLI OAuth client id).
• Fork release builds read these values instead of upstream's.

Why it matters for the source rename

The planned t3 to Lathe source rename keeps every name on the Connect path byte-identical (the "wire-peer" class), because upstream-run services talk to Lathe servers. Once Lathe owns its Connect service, those names can move to the "persisted" class: write the Lathe name, still accept the old one, and warn.

Not in scope

The source rename itself.