Org-aware account identity, removal, and rotation priority (#6, #7)

[MagicalTux]

Closes #6, closes #7.

Problem

One Anthropic account (same email / accountUuid) can hold multiple subscriptions across different organizations — e.g. a corporate Pro org and a personal Max org. Identity was keyed only on accountUuid (with name as fallback), so connecting the second org overwrote the first (#6), and --name didn't help because the UUID check won (#7).

Approach

Identity is now accountUuid + organization. This was re-implemented and reviewed line-by-line against master rather than cherry-picked from the closed fork PRs (#15/#17) — per maintainer policy, and because the repo has already been targeted by a malicious soft-fork (#9), external diffs are treated as untrusted.

Changes

• src/identity.js (new) — orgKey / sameIdentity / matchAccounts / emailOf. sameIdentity treats an unknown org on either side as a match, so a freshly-profiled login backfills a legacy entry instead of duplicating it; once both orgs are known, a different org is a distinct account.
• fetchProfile extracts organization.uuid; accounts persist orgUuid/orgName.
• All ~14 dedup/sync/find match sites converted to sameIdentity. syncAccountsFromDisk uses a greedy 1:1 claim so multiple same-person/different-org entries pair correctly instead of all matching the first. The accounts command dedups by (accountUuid, org) and backfills org identity from the profile.
• Name disambiguation — single org → email; multiple → email (Org), renaming the existing collider too. Names stay unique because they're the user-facing key for remove/api/selection.
• Org-aware remove + api — resolve by name or email; --org <name|uuid> disambiguates; ambiguous queries list the candidates.
• Rotation priority — priority field (lower = preferred, default 0) is the primary sort key in _selectNext, with the existing weekly-reset heuristic as the tiebreaker (default 0 everywhere ⇒ unchanged behavior). New teamclaude priority <name> <n> command (--first/--last). Session-reset switching won't demote to a worse priority.

Tests

npm test — 22 passing. New test/identity.test.js (sameIdentity incl. legacy-backfill + two-orgs migration; matchAccounts/email/--org routing) and test/rotation-priority.test.js (priority ordering, tiebreak, default-0 parity). Lint clean (one pre-existing unrelated warning).

Backward compatibility

Existing single-account configs (no orgUuid) run unchanged; an entry is backfilled with its org after one accounts/profile fetch.

Out of scope (future PRs, from the #18 stack)

• Headless mode, management/reload API, and background quota prober #14 headless mode + reload API + background prober
• Quota: error recovery, probe-on-add, and usage-endpoint quota #16 usage-endpoint quota + error-state recovery
• Fail over to next account on 429 instead of blocking #13 429 account-failover — not taken: the throttle is IP-based, so the merged Bound 429 retries and handle listen errors gracefully #25 back-off is the correct behavior.

🤖 Generated with Claude Code