feat(multi-account): global-default resume routing (Batch 2e)

buildResumeCommand now emits `command claude` (bypassing the accounts.sh
`claude` dispatcher) so a configured non-anchor global-default can't
re-route an anchor-account resume to the wrong account. Behavior is
unchanged when the default IS the anchor; a no-op for single-account
users (command claude == claude).

2e's shell + CLI side already shipped in 2a (`codev account default`
plus the dispatcher `*)` -> defaultAccount). Also documents the
2c <-> Batch 3 coupling (cross-account resume needs shared session data).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017kCK4t5JSVynVZxGcrTGGp

Author: grimmerk

CHANGELOG.md

@@ -2,9 +2,10 @@
 
 ## 1.0.77
 
-- Feat: multi-account Batch 2a — `codev account` CLI to manage the registry
+- Feat: multi-account Batch 2a + 2e — `codev account` CLI + configurable global-default
   - `codev account list | add <label> [--dir D] | default <label> | remove <label> | regenerate | show | install | uninstall`
   - One shared generator (`src/cli/account-manager.ts`) produces both `~/.config/codev/accounts.json` and `accounts.sh`, replacing Batch 1's hand-editing; run in dev via `yarn account <cmd>` (PATH install + Settings UI land in Batch 2b)
+  - Batch 2e (global-default): `codev account default <label>` + the shell dispatcher route bare `claude` to a chosen account; CodeV resume now uses `command claude` (bypasses the dispatcher) so a non-anchor global-default can't misroute an anchor-account resume
   - Adds Vitest + a generator test suite, and a real CI workflow (replacing the placeholder)
 
 ## 1.0.76

docs/multi-account-support-design.md

@@ -351,6 +351,11 @@ good. But the hook must be **registered** in each account's `settings.json`. Opt
 - New-session launch (Projects `⌘+Enter`): allow an account override, e.g. extend the
   planned `>` command mode (`> claude @work myrepo`) or an account segment in the
   expanded project row.
+- **Coupled with Batch 3 (§5).** Truly resuming/sharing a *transcript* across accounts
+  only works if the session data (and global config: CLAUDE.md/skills) is shareable
+  across config dirs — i.e. it depends on Batch 3's cross-account reuse. So design 2c
+  and Batch 3 **together**: without sharing, 2c is limited to "new session in this cwd
+  under account Y"; with sharing, genuine cross-account resume becomes possible.
 
 ### 6.H pyenv-style auto-switch by folder (requirement 6, nice-to-have, "reverse" priority)
 

src/claude-session-utility.ts

@@ -1075,16 +1075,22 @@ const getResumeConfigDirEnv = (sessionId: string): string | null => {
 };
 
 /**
- * Build `claude --resume <id>`, prefixed with CLAUDE_CONFIG_DIR when the session
- * belongs to a non-default account so it resumes under the right account.
+ * Build `command claude --resume <id>`, prefixed with CLAUDE_CONFIG_DIR when the
+ * session belongs to a non-default account so it resumes under the right account.
  */
 const buildResumeCommand = (sessionId: string): string => {
   const configDir = getResumeConfigDirEnv(sessionId);
   // Single-quote the value: some terminal injections (Ghostty `initial input`)
   // don't escape the command, so a double-quoted prefix would break their
   // AppleScript string. Single quotes are safe across all terminals + handle spaces.
   const prefix = configDir ? `CLAUDE_CONFIG_DIR='${configDir}' ` : '';
-  return `${prefix}claude --resume ${sessionId}`;
+  // `command claude` bypasses the accounts.sh `claude` dispatcher. CodeV has
+  // already resolved the exact account (the prefix, or none for the anchor), so
+  // the shell must NOT re-route a bare `claude` to a configured non-default
+  // global-default (§2e) — that would resume an anchor-account session under the
+  // wrong account. Every terminal here runs the string through a shell, so the
+  // `command` builtin is available.
+  return `${prefix}command claude --resume ${sessionId}`;
 };
 
 /**