[jayleaton]

JJ approved renaming the GitHub repository from jayleaton/t3code to jayleaton/ada. This PR points everything at the new name. Merge right after the rename. Until then GitHub redirects the old name, so CI runs either way.

Summary

• Every jayleaton/t3code becomes jayleaton/ada (104 references in 46 files):
  • CLI_RELEASE_REPOSITORY, and so every derived URL (release pages, API index, install scripts, license);
  • the literals that don't derive from it: the web download, desktop update, star prompt and boot-error links, the marketing site, the Linux metainfo and GNOME extension, desktop packaging, install.sh/install.ps1, t3-headless-update;
  • the workflows, docs, README and tests.
• Clone instructions say cd ada.
• MCP write allowlist: the default is now ${CLI_RELEASE_REPOSITORY},jayleaton/t3code. The gateway checks a project's git remote, and existing clones keep jayleaton/t3code as their remote until someone updates it. Both names are the same repository. A new test shows the old name is still allowed; it fails without the extra entry.
• Fork guard re-pinned: apps/server/src/cli/update.test.ts "authenticates each release page until the requested channel is found" (fix: switching from T3 Code to T3 Agents keeps data, pairing and updates working #207) changed only in the repository URL it expects, so it still guards the same fix.

Unchanged

• pingdotgg/t3code (upstream sync, the model manifest, upstream-only guards).
• App and bundle IDs (com.jayleaton.t3agents, com.jayleaton.t3code*), t3code URL schemes, profile directory names and package names.

After the rename

1. Rename the repository on GitHub, then merge this PR.
2. Run git remote set-url origin https://github.com/jayleaton/ada.git in local checkouts. The redirect keeps old remotes working in the meantime.
3. The first nightly after the merge publishes from the new name. Existing installs keep finding updates through the redirect, then through the new URLs once they update.

Checks

• vp run check:changed → pass: format, lint, knip, typecheck (41 packages), test (17 files, 338 passed), react compiler.

Merge Danger

Door: two-way. It's a string change, and GitHub redirects the old name.

Blast Radius: platform. Every update check, installer and release link points at the new name. Merged before the rename, they would 404. Merged after it, everything works directly, and old clients keep working through the redirect.

Model and harness: Claude Opus 5.5 in Claude Code (T3 Code).

🤖 Generated with Claude Code

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	5.0 KiB	5.0 KiB	0 B (0.0%)	6.8 KiB	✅
Codex	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Codex	Live turn WebSocket wire	1.2 KiB	1.2 KiB	0 B (0.0%)	2.0 KiB	✅
Codex	Live turn WebSocket decoded	21.5 KiB	21.5 KiB	0 B (0.0%)	24.4 KiB	✅
Codex	Live turn messages	1	1	0 (0.0%)	8	✅
Claude	Total thread wire	5.0 KiB	5.0 KiB	0 B (0.0%)	6.8 KiB	✅
Claude	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Claude	Live turn WebSocket wire	1.2 KiB	1.2 KiB	0 B (0.0%)	2.0 KiB	✅
Claude	Live turn WebSocket decoded	21.9 KiB	21.9 KiB	0 B (0.0%)	24.4 KiB	✅
Claude	Live turn messages	1	1	0 (0.0%)	8	✅

Baseline: e2d428d · PR result: bd03f39 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 108.5 KiB
• Claude decoded thread snapshot: 108.8 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.