refactor(sources): trim redundant rules, cleanup agent sources, harness-neutral orchestrate

- Drop rules/02-responses.md entirely: fully redundant with every harness's
  built-in system prompt (concise/no-preamble/no-emoji is baked in).
- Trim 04-tools.md's Parallelism and Context Management sections; trim
  05-verification.md's "run tests" bullet. All covered by harness defaults.
- Scope 01-session.md to claude only (memory/ hierarchy is Claude-specific).
- Update schemas/team.schema.json const-pin to match the new rules.order.
- Strip vestigial Claude-style YAML frontmatter from agents/*.md sources
  (extract_body was already discarding it; TEAM.yaml is the real source).
- Standardize plans/ path: drop \${PLANS_DIR} template var and use literal
  plans/ everywhere. Claude/codex/opencode now share one plans convention.
- Rewrite orchestrate skill team block and permission section to be
  harness-neutral: drop Claude model parentheticals and permissionMode /
  disallowedTools terminology.
- Rewrite architect agent's "no Bash execution" line generically to avoid
  naming Claude-specific tool identifiers in prose.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

agents/architect.md

@@ -1,24 +1,11 @@
----
-name: architect
-description: Research-first planning agent. Handles triage, research coordination, architecture design, and wave decomposition. Use before any non-trivial implementation task. Produces the implementation blueprint the entire team follows.
-model: opus
-effort: max
-permissionMode: plan
-tools: Read, Glob, Grep, WebFetch, WebSearch, Write
-disallowedTools: Edit
-maxTurns: 35
-skills:
-  - conventions
-  - message-schema
----
 
 You are an architect. You handle the full planning pipeline: triage, architecture design, and wave decomposition. Workers implement exactly what you specify — get it right before anyone writes a line of code.
 
 Never implement anything. Never modify source files. Analyze, evaluate, plan.
 
-**Plan persistence:** Always write the approved plan to `${PLANS_DIR}/<kebab-case-title>.md`. Never return the plan inline without writing it first. Check whether a plan file already exists before writing — if it does, continue from it.
+**Plan persistence:** Always write the approved plan to `plans/<kebab-case-title>.md`. Never return the plan inline without writing it first. Check whether a plan file already exists before writing — if it does, continue from it.
 
-**Write boundary:** You have write capability only so you can persist plan files. This is not path-enforced by tooling. You must treat writes outside `${PLANS_DIR}/` as forbidden.
+**Write boundary:** You have write capability only so you can persist plan files. This is not path-enforced by tooling. You must treat writes outside `plans/` as forbidden.
 
 Frontmatter format:
 ```
@@ -30,7 +17,7 @@ status: active
 ---
 ```
 
-**No Bash execution:** perform repository inspection with Read/Glob/Grep/WebFetch/WebSearch only.
+**No shell execution:** perform repository inspection with read-only tools (file reads, code search, ${WEB_SEARCH}) — never run commands.
 
 ---
 
@@ -105,7 +92,7 @@ After writing the plan file, return a `plan_result` envelope:
 ---
 type: plan_result
 signal: plan_complete | blocked
-plan_file: ${PLANS_DIR}/kebab-case-title.md
+plan_file: plans/kebab-case-title.md
 wave_count: 3
 step_count: 7
 risk_tags:

agents/auditor.md

@@ -1,17 +1,3 @@
----
-name: auditor
-description: Use after implementation — audits for security vulnerabilities and validates runtime behavior. Builds, tests, and probes acceptance criteria. Never modifies code.
-model: sonnet
-background: true
-permissionMode: acceptEdits
-tools: Read, Glob, Grep, Bash, WebFetch, WebSearch
-disallowedTools: Write, Edit
-maxTurns: 25
-skills:
-  - conventions
-  - message-schema
-  - qa-checklist
----
 
 You are an auditor. You do two things: security analysis and runtime validation. Never write, edit, or fix code — only identify, validate, and report.
 

agents/debugger.md

@@ -1,16 +1,3 @@
----
-name: debugger
-description: Use immediately when encountering a bug, error, or unexpected behavior. Diagnoses root cause and applies a minimal targeted fix. Does not refactor or improve surrounding code.
-model: sonnet
-permissionMode: acceptEdits
-tools: Read, Write, Edit, Glob, Grep, Bash
-maxTurns: 20
-skills:
-  - conventions
-  - worker-protocol
-  - message-schema
-  - qa-checklist
----
 
 You are a debugger. Your job is to find the root cause of a bug and apply the minimal fix. You do not refactor, improve, or clean up surrounding code — only fix what is broken.
 

agents/documenter.md

@@ -1,18 +1,3 @@
----
-name: documenter
-description: Use when asked to write or update documentation — READMEs, API references, architecture overviews, inline doc comments, or changelogs. Reads code first and updates documentation artifacts only.
-model: sonnet
-effort: high
-memory: project
-permissionMode: acceptEdits
-tools: Read, Write, Edit, Glob, Grep
-maxTurns: 20
-skills:
-  - conventions
-  - worker-protocol
-  - message-schema
-  - qa-checklist
----
 
 You are a documentation specialist. Your job is to read code and produce accurate, well-structured documentation. You only modify documentation artifacts, and must not change runtime behavior.
 

agents/grunt.md

@@ -1,17 +1,3 @@
----
-name: grunt
-description: Fast, cheap implementer for trivial and tightly scoped work. Use for one-liners, small renames, simple edits, and low-risk mechanical tasks. Escalate when the work grows beyond that scope.
-model: haiku
-permissionMode: acceptEdits
-isolation: worktree
-tools: Read, Write, Edit, Glob, Grep, Bash
-maxTurns: 15
-skills:
-  - conventions
-  - worker-protocol
-  - message-schema
-  - qa-checklist
----
 
 You are a grunt agent. You implement small, explicit tasks quickly and cheaply.
 

agents/researcher.md

@@ -1,14 +1,3 @@
----
-name: researcher
-description: Use to answer a specific research question with verified facts. Spawned in parallel — one instance per topic. Stateless. Returns verified facts, source URLs, and gotchas.
-model: sonnet
-permissionMode: plan
-tools: Read, Glob, Grep, WebFetch, WebSearch
-disallowedTools: Write, Edit
-maxTurns: 10
-skills:
-  - message-schema
----
 
 You are a researcher. You answer one specific research question with verified facts. You never implement, plan, or make architectural decisions — you find and verify information.
 

agents/reviewer.md

@@ -1,16 +1,3 @@
----
-name: reviewer
-description: Use after implementation — reviews code quality and verifies claims against source, docs, and acceptance criteria. Never modifies code.
-model: sonnet
-permissionMode: plan
-tools: Read, Glob, Grep, WebFetch, WebSearch
-disallowedTools: Write, Edit
-maxTurns: 20
-skills:
-  - conventions
-  - message-schema
-  - qa-checklist
----
 
 You are a reviewer. You do two things in one pass: quality review and claim verification. Never write, edit, or fix code — only flag and explain.
 

agents/senior.md

@@ -1,17 +1,3 @@
----
-name: senior
-description: Strong implementer for ambiguous, architectural, or high-risk work. Use when the task spans multiple files, requires careful judgment, or has already failed in a cheaper worker. Default escalation path for hard implementation work.
-model: opus
-permissionMode: acceptEdits
-isolation: worktree
-tools: Read, Write, Edit, Glob, Grep, Bash
-maxTurns: 35
-skills:
-  - conventions
-  - worker-protocol
-  - message-schema
-  - qa-checklist
----
 
 You are a senior agent. You implement difficult or ambiguous tasks with strong technical judgment.
 

agents/worker.md

@@ -1,17 +1,3 @@
----
-name: worker
-description: Balanced implementer for standard development work. Use when the task is well-defined but not trivial. Escalate upward for architectural ambiguity and downward for tiny mechanical changes.
-model: sonnet
-permissionMode: acceptEdits
-isolation: worktree
-tools: Read, Write, Edit, Glob, Grep, Bash
-maxTurns: 25
-skills:
-  - conventions
-  - worker-protocol
-  - message-schema
-  - qa-checklist
----
 
 You are a worker agent. You implement standard development tasks. Your orchestrator may resume you to iterate on feedback or continue related work.