squad init --global creates files in wrong location (.squad/ instead of personal-squad/)

[diberry]

Problem

squad init --global creates the squad structure in the wrong location. Agents, casting, and skills end up at ~/.config/squad/.squad/ instead of ~/.config/squad/personal-squad/.

Expected behavior

Personal squad files should be at:

• ~/.config/squad/personal-squad/agents/
• ~/.config/squad/personal-squad/casting/
• ~/.config/squad/personal-squad/skills/

Actual behavior

Files end up at:

• ~/.config/squad/.squad/agents/ (WRONG - agents here)
• ~/.config/squad/personal-squad/agents/ (empty)
• ~/.config/squad/personal-squad/config.json (only file)

Root cause

In cli-entry.ts:274-275, dest is set to resolveGlobalSquadPath() which returns ~/.config/squad/ (the parent). The full init then creates .squad/ inside that parent. The personal-squad/ subdirectory is created separately by ensurePersonalSquadDir() but is nearly empty.

Fix: dest should point to the personal-squad/ subdirectory when --global is set, OR the init flow needs to use personal-squad/ as the teamRoot.

Files involved

File	Lines	Issue
packages/squad-cli/src/cli-entry.ts	274-275	dest points to parent, not personal-squad/
packages/squad-cli/src/cli/core/init.ts	156-310	Creates .squad/ at wrong level, then empty personal-squad/
packages/squad-sdk/src/resolution.ts	301-324	resolveGlobalSquadPath() returns parent

Impact

• Personal agents are not discoverable by the ambient discovery system
• Ghost Protocol routing fails because agents aren't where resolvePersonalSquadDir() looks
• Users who run squad init --global get a broken personal squad that doesn't work with project squads

Classification

Product bug (not docs). The docs correctly describe the intended structure but the code creates files in the wrong location.

[diberry]

PRD: Fix squad init --global file placement (Issue #53)

Problem

squad init --global creates the full squad scaffold at ~/.config/squad/.squad/ (agents, casting, etc.) instead of ~/.config/squad/personal-squad/. This breaks personal agent discovery because
esolvePersonalSquadDir() looks in personal-squad/, not .squad/.

Root Cause

In cli-entry.ts:274-275, dest is set to
esolveGlobalSquadPath() which returns the global config root (e.g. ~/.config/squad/). This dest is passed to
unInit(), which calls sdkInitSquad({ teamRoot: dest }). The SDK init always creates a .squad/ subdirectory inside eamRoot, resulting in files at ~/.config/squad/.squad/agents/ — the wrong location.

Meanwhile, �nsurePersonalSquadDir() (called at the end of init) correctly creates personal-squad/agents/ and config.json, but the main scaffold has already polluted the global root with an unwanted .squad/ directory.

Fix Approach

When isGlobal is true, the init flow should:

1. Skip the full sdkInitSquad scaffold (which creates .squad/ — designed for repo-level projects)
2. Instead, use �nsurePersonalSquadDir() to create the personal-squad/ directory with agents/, casting/, skills/, and config.json
3. Return early before any repo-specific operations (git detection, worktree guard, workflows, etc.)

Changes:

• packages/squad-cli/src/cli/core/init.ts: Add early return when isGlobal — call �nsurePersonalSquadDir() + create casting/ and skills/ subdirs
• packages/squad-cli/src/cli-entry.ts: Update dest to target personal-squad subdirectory for semantic clarity

Acceptance Criteria

1. squad init --global creates agents/casting/skills inside personal-squad/ directory
2. personal-squad/ is discoverable by
   esolvePersonalSquadDir()
3. No .squad/ directory created at the global path root level
4. Existing tests continue to pass
5. New tests verify the correct file structure

[diberry]

Retargeted to bradygaster/squad — work shipped upstream.