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>

rules/02-responses.md

@@ -1,6 +0,0 @@
-# Responses & Explanations
-
-- Be concise — lead with the action or answer, not the preamble
-- Include just enough reasoning to explain *why* a decision was made, not a full walkthrough
-- Skip trailing summaries ("Here's what I did...") — the diff speaks for itself
-- No emojis unless explicitly asked

rules/04-tools.md

@@ -20,14 +20,3 @@
 - Commonly run development workflows MUST be wired into `just` recipes as the user-facing entrypoints
 - Temporary artifacts created during work MUST be cleaned up before completion unless the user explicitly asked to keep them
 
-# Parallelism
-
-- Always parallelize independent work — tool calls, file reads, searches
-- When a task has components that don't depend on each other, run them concurrently by default
-- Sequential execution is allowed only when required by dependencies or operational constraints (tool/runtime limits, contention, staged validation)
-
-# Context Management
-
-- Use subagents for exploratory reads and investigations to keep the main context clean
-- Use scoped file reads (offset/limit) over reading entire large files
-- When a task is complete or the topic shifts significantly, suggest clearing context or starting a new session

rules/05-verification.md

@@ -1,6 +1,5 @@
 # Verification
 
-- After making changes, run relevant tests or build commands to verify correctness before reporting success
 - If no tests exist for the changed code, say so rather than silently assuming it works
 - Run single targeted tests by default; run the full suite when requested or when targeted coverage is insufficient