GeezerVison

Phase 2 of #2442. Every charter in .squad/agents/ (built-ins included)
becomes a managed .claude/agents/<id>.md. Charter model, reasoning effort and
the X-squad-host-claude extension (Tools, Isolation) map onto the subagent
frontmatter; config reasoning effort outranks the charter.

- managed files can carry an ownership marker: user-authored files at the same
  path are skipped (new `skipped` apply action) and never removed
- new `obsolete` projection entry removes generated files of members whose
  charter is gone, on upgrade and on rollback
- the Claude dispatch section routes to named members and applies per-spawn
  model precedence via the Agent tool's per-call model
- squad cast refreshes member files when claude is configured (local mode)
- model-selection.claude flips to supported in the host feature matrix
- spec 7.1/7.3/13 document the member files and the extension

Co-Authored-By: Claude Opus 5.5 <[email protected]>

Phase 4 of #2442. Squad's template skills are projected into
.claude/skills/<name>/SKILL.md (a team skill of the same name in
.squad/skills/ keeps precedence, so its template is not projected), with the
same ownership-marker rules as member subagents.

The Claude coordinator digest replaces core-protocol items 0 (Init Mode),
9 (Ralph), 15 (Ceremonies), 18 (Issues) and 19 (PRD) with stubs that keep each
trigger and its pre-load rules; the full item text moves verbatim into
generated squad-coordinator-* skills. Other hosts' digests and
.github/agents/squad.agent.md are unchanged. The parity tests check the Claude
digest plus its skills.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…ockouts

With "claudeHooks": "advisory" in .squad/config.json, the Claude projection
adds Squad hook handlers to .claude/settings.json (SessionStart,
SubagentStart, PreToolUse, PostToolUse, Stop). They run
`squad hook claude <Event>` and only add context or warnings; none returns a
permissionDecision. User settings and hooks are preserved; turning hooks off
or rolling back restores them byte for byte.

`squad lockout` records governance-review §6 lockout state in
.squad/governance/lockouts.json, which the PreToolUse hook reads to warn a
locked-out member editing a covered path. Paths resolve through symlinks so
the hook matches on macOS temp and symlinked checkouts.

Part of #2442.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

`--agent-preset claude` (or `watch.agentPreset: "claude"`) runs each round as
`claude -p <prompt> --agent squad --mcp-config .mcp.json --output-format
stream-json --verbose`. Preflight requires the projected coordinator and the
claude CLI; an error `result` event counts as a failed round. Execute mode
defaults to `--permission-mode bypassPermissions` (the counterpart of
Copilot's --yolo); `--claude-flags` overrides it. The default Copilot runner,
--agent-cmd precedence and Copilot-only fleet dispatch are unchanged.

Flips ralph-cli-triage-watch.claude to supported in the host feature matrix.

Refs #2442

Co-Authored-By: Claude Opus 5.5 <[email protected]>

The design and the Sonnet 5.5 calibration results now live in
#2449, so the proposal file is no longer needed.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…s table

Co-Authored-By: Claude Opus 5.5 <[email protected]>

Bump the Claude Code projection once, to v2 (CLAUDE_PROJECTION_VERSION),
for member subagents, skills and the opt-in settings.json hooks. Every
generated Claude Markdown file states the version in its generated-file
note; the v1 wording stays a prefix so v1 files are still recognised as
Squad-owned and upgraded in place.

Rollback tests (harness-adapters §15.7) snapshot the whole tree and
require identical bytes after install, upgrade and rollback, including
user content in every shared file and user-authored files at generated
paths. They found that marker-block rollback (CLAUDE.md, AGENTS.md,
GEMINI.md) added or dropped a newline when the file ended without one or
with a blank line; upsertBlock and removeBlock now round-trip exactly.

Also fixes regressions from earlier phases: `squad hook` leaves the main
help (Claude Code invokes it), `lockout` fits in 80 columns, the help
budget allows it, and the Init Mode scenario tests read Claude's
coordinator together with the skills it loads.

Refs #2442

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…text

- docs lint (cspell) rejected "recognises" in harness-adapters §5.
- PostToolUse no longer reflects the Agent call's free-text description
  into the coordinator's context; the handoff envelope keeps only
  structured fields (review feedback on #2450).
- Document why claudeHookLaunch has no command allowlist: the launcher is
  resolved by the CLI from its own install, never from repo content, and
  is already projected as the squad_state MCP server.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

Copilot AI left a comment

Security:
- watch Claude preset no longer passes the repository's .mcp.json (which
  bypassed Claude Code's approval for every server in it); it writes a
  private squad_state-only config resolved by the CLI from its own install.
- Charters, routing.md and template SKILL.md files that resolve outside the
  team directory through a symlink are no longer copied into .claude/.
- The lockout store refuses a governance/ path that resolves outside the
  team directory, and replaces (never writes through) a lockouts.json link.

Correctness:
- squad lockout reads, transitions and writes under an interprocess lock,
  so concurrent commands keep every transition.
- `squad lockout status --json` no longer treats --json as the subject.
- Rai and Fact Checker are not offered as revision authors.
- Monitor, retro and decision-hygiene Claude runs fail on an error result
  event, like execute.
- A no-op settings.json update keeps the user's bytes (`{}` is no longer
  deleted when hooks are off).
- PostToolUse reports a background Agent launch as an acknowledgement,
  not a result.
- Individually backticked member Tools (`Read`, `Grep`) are accepted.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

Lockout fields come from a repository file and from free text typed with
`squad lockout`. Before they reach the coordinator (SessionStart,
SubagentStart, PreToolUse, PostToolUse) they are flattened to one line,
stripped of markup and code delimiters, bounded, and the reason is quoted as
a JSON string; member IDs that are not a-z0-9- are dropped (code scanning
review on #2450).

Co-Authored-By: Claude Opus 5.5 <[email protected]>

`.squad/config.json` belongs to the repository, so `watch.claudeFlags` from
that file could add `--mcp-config .mcp.json` (or settings, plugins, extra
directories, another agent) and undo the Claude preset's squad_state-only
MCP config during unattended runs. The file may now set only
--permission-mode, --model, --fallback-model, --effort, --max-turns and the
allowed/disallowed tool lists, with validated values; anything else fails
config loading with a clear error. --claude-flags on the command line is
the user's own and stays unrestricted (code scanning review on #2450).

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…s data

SessionStart context included routing.md work types, charter roles and the
Ralph circuit breaker's model names verbatim; all are repository text. They
now go through the same inert() handling as lockout fields: work types and
model names are quoted, roles flattened, and routes name only roster
members. Charters are read with the team-directory containment guard
(code scanning review on #2450).

Co-Authored-By: Claude Opus 5.5 <[email protected]>

Tool-list flags (--allowedTools, --disallowedTools and their dashed forms)
can widen what Claude Code may run, so watch.claudeFlags in
.squad/config.json may no longer set them; they must come from
--claude-flags on the command line (code scanning review on #2450).

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…gine

The cell stays n/a (the workflows run in GitHub Actions, so the local host
is irrelevant), but the mechanism no longer implies Copilot is the only
engine: gh-aw ships `engine: claude`, Squad does not ship a workflow for it
yet, and the notes record what one would need (`engine.args` with
`--agent squad`, `bare: false`) with a link to the #2438 research.

Refs #2442

Co-Authored-By: Claude Opus 5.5 <[email protected]>

Directory names under .squad/agents/ reached SessionStart context as-is;
names outside a-z0-9- are now ignored, matching member IDs elsewhere
(code scanning review on #2450).

Co-Authored-By: Claude Opus 5.5 <[email protected]>