Align instructions with Claude Code agent teams API

[harrymunro]

Summary

• New file: tool-mapping.md — Reference table mapping Nelson operations (form squadron, spawn captain, message, broadcast, shutdown, etc.) to exact Claude Code tool calls (Agent, TeamCreate, TaskCreate, SendMessage, etc.) with mode annotations
• Fix all Task() references — Replaced Task() and "Task tool" with correct Agent tool calls in crew-briefing.md and SKILL.md, making the two-step spawn-then-assign pattern explicit for agent-team mode
• Quarterdeck rhythm improvements — Added TaskList, SendMessage, and tool-mapping.md references to Step 4; replaced wall-clock cadence ("every 15-30 minutes") with event-driven checkpoints ("every 2-3 task completions, on blocker, or on idle")
• Plan mode for Station 2+ — Added guidance to spawn Station 2/3 captains with mode: "plan" and approve via SendMessage(type="plan_approval_response")
• Read-only agent damage reports — Documented that Explore subagent types (NO, COX, Recce Marines) report hull integrity via SendMessage to their captain
• Worktree isolation — Added section to squadron-composition.md documenting isolation: "worktree" as an alternative to file-ownership boundaries
• Plugin settings — New settings.json ships CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 so plugin installs enable agent teams automatically
• Expanded agents/nelson.md — Added skills frontmatter field binding the nelson skill
• Hook documentation — Added TeammateIdle and TaskCompleted hook examples as opt-in advanced configuration
• Updated file trees in README and CLAUDE.md

Implements all 11 items from docs/prd-agent-teams-alignment.md.

Test plan

• Install plugin locally and invoke /nelson — verify SKILL.md loads without errors
• Run a subagents-mode mission — verify crew briefing template renders with Agent tool references
• Run an agent-team-mode mission — verify TeamCreate, TaskCreate, TaskUpdate, SendMessage are used correctly
• Verify settings.json is picked up by plugin install (agent teams enabled without manual config)
• Spot-check that no Task() or "Task tool" references remain in any skill file