chore: rename project to Coord - #7
Conversation
Unifies every surface under a single name: the product name (Condominium), npm packages (@teambridge/* -> @coord/*), CLI command, COORD_* env vars, coord:// MCP URI scheme, the .coord/ state directory, and the coord/<track>/<name> participant branch prefix. Supabase identifiers are deliberately left as-is because they address already-deployed data: the tc_ table prefix, the teambridge_private schema, the teambridge-checkpoints storage bucket, and the applied migration 001_teambridge_relay.sql. The [tb ...] vault annotation tag is also unchanged since it is persisted inside existing vault markdown. Existing local state must be migrated with `mv .teambridge .coord` plus a rewrite of teambridge/ branch prefixes in participants.branch. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Important Review skippedToo many files! This PR contains 128 files, which is 28 over the limit of 100. To get a review, narrow the scope: Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (128)
You can disable this status message by setting the ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Renames the project from Condominium / teambridge to Coord across every surface, so the product name, package names, CLI command, and on-disk identifiers all agree.
Renamed:
teambridgecoord@teambridge/*@coord/*teambridge <cmd>coord <cmd>pnpm teambridgepnpm coordTEAMBRIDGE_*,VITE_TEAMBRIDGE_*COORD_*,VITE_COORD_*teambridge://workspacecoord://workspace.teambridge/.coord/teambridge/<track>/<name>coord/<track>/<name>teambridgeClient.tscoordClient.tsTeambridgeConfig,TeambridgeError,buildTeambridgeUrl, …CoordConfig,CoordError,buildCoordUrl, …Deliberately NOT renamed
These address already-deployed data, so renaming them would orphan it:
tc_Supabase table prefixteambridge_privatePostgres schemateambridge-checkpointsstorage bucketsupabase/migrations/001_teambridge_relay.sql(applied migration — left byte-for-byte untouched)[tb color= assign=]vault annotation tag (persisted inside existing vault markdown)Migration required for existing local state
This is a breaking change for anyone with an existing
.teambridge/directory. After pulling, the daemon looks for.coord/and will otherwise start from empty state:Any pre-existing git worktrees on
teambridge/<track>/<name>branches will no longer resolve as "the current track" (publish,vault *,ask,inbox,conflictsinfer the track from the branch name), so those branches need renaming or the track needs re-joining.Rename
TEAMBRIDGE_*keys toCOORD_*in any local.env.Test plan
pnpm buildclean across all 6 packagespnpm test:integration— all 9 end-to-end suites pass, including the CLI worktree flow, MCP stdio server, inbox/conflicts, and relay reconnect/checkpoint bootstrapcoord daemon listening on http://127.0.0.1:9473coord statusreads migrated state (3 projects, 11 tracks, 33 participants) withcoord/<track>/<name>branches<title>Coord</title>and renders migrated projectsteambridgereferences outside the intentional keep-listMade with Cursor