Governance layer has no awareness of personal squad paths

[jsturtevant]

Problem

The personal squad path resolution (resolveGlobalSquadPath() → platform-specific dirs like ~/.config/squad/) lives entirely in SDK code. The governance layer — squad.agent.md, charter templates, and skills — has zero awareness of personal squads.

What's missing

1. squad.agent.md (coordinator instructions)

• Init Mode references --global but doesn't explain where it resolves to
• No guidance for agents operating in consult mode against a personal squad
• The TEAM_ROOT concept works, but nothing tells the coordinator that a personal squad has different semantics (shared across projects, skills are portable, etc.)

2. Charter templates (.squad/templates/charter.md)

• No personal-squad-aware patterns
• When casting a personal squad, charters should reflect that skills/knowledge are project-agnostic
• No guidance on "this agent lives in a personal squad and will be used across multiple repos"

3. Skills and templates

• All .squad/skills/ and .squad/templates/ reference .squad/ as project-relative only
• No skill for "how to behave when spawned from a personal squad" or "how consult mode changes agent behavior"

Impact

• Agents spawned via consult mode don't know they're backed by a personal squad
• The coordinator can't give agents context about personal vs project squads
• Personal squad casting has no template support (related: CLI casting bypasses CastingEngine template system #342)
• Skills earned in one project via a personal squad have no guidance on portability

Expected Behavior

The governance layer should:

1. Define personal squad semantics in squad.agent.md (how consult mode works, what TEAM_ROOT means when pointing to a personal squad)
2. Provide charter template variants for personal squad agents (project-agnostic framing)
3. Include a skill or template for consult-mode behavior (what's different when the squad is personal)

Related

• CLI casting bypasses CastingEngine template system #342 — CLI casting bypasses CastingEngine template system
• Personal squad docs reference ~/.squad/ instead of platform-specific paths #343 — Personal squad docs reference ~/.squad/ instead of platform-specific paths

[jsturtevant]

Additional gap: config.json → teamRoot resolution missing from coordinator

The coordinator's team root resolution in squad.agent.md (Worktree Awareness section) only describes worktree-based discovery:

1. git rev-parse --show-toplevel → check for .squad/
2. Fall back to main working tree

But there's a third path that's completely missing: config-directed resolution. When config.json has a teamRoot field (e.g., "teamRoot": "C:\\src\\squad-pr"), the SDK's resolveSquadPaths() follows it to load team identity from an external location. The coordinator has no instructions to read config.json for this field, so:

• The coordinator won't discover the remote team root
• Agents get a TEAM_ROOT that doesn't match the SDK's actual resolution
• Remote/consult mode is effectively broken at the governance layer

Fix needed in squad.agent.md: Add a step to the team root resolution:

3. Check .squad/config.json for a \teamRoot\ field.
   - If present → team identity (charters, skills, casting) lives at that path.
   - Pass both TEAM_ROOT (identity) and PROJECT_ROOT (local .squad/) to agents.

This is the same dual-root problem described in the personal squad proposal's open design question — the governance layer needs to mirror what the SDK already does in resolveSquadPaths().