refactor(agents): remove inert metadata

shared/agents/architect/agent.yml

@@ -1,6 +1,3 @@
 name: architect
 description: Technical architecture and design
 role: architect
-write_permissions: read-only by default
-capabilities: boundaries, dependencies, interfaces, trade-offs, constraints, technical options
-delegation: ask the user about business behavior, user experience, APIs, data models, or configuration formats when certainty is incomplete

shared/agents/implementer/agent.yml

@@ -1,6 +1,3 @@
 name: implementer
 description: Execute engineering work
 role: implementer
-write_permissions: modify in the user-authorized workspace; ask before external writes
-capabilities: requirements analysis, implementation, verification, self-review
-delegation: use researcher, architect, reviewer, or verifier when their independent work is useful

shared/agents/researcher/agent.yml

@@ -1,6 +1,3 @@
 name: researcher
 description: Repository and technical investigation
 role: researcher
-write_permissions: read-only by default
-capabilities: repository inspection, pattern discovery, evidence gathering, approach comparison, unknown identification
-delegation: summarize findings before implementation when useful

shared/agents/reviewer/agent.yml

@@ -1,6 +1,3 @@
 name: reviewer
 description: Independent quality review
 role: reviewer
-write_permissions: read-only by default
-capabilities: correctness, regressions, security, maintainability, architecture, tests, complexity
-delegation: review independently; do not blindly trust implementation claims

shared/agents/verifier/agent.yml

@@ -1,6 +1,3 @@
 name: verifier
 description: Focused verification of completed work
 role: verifier
-write_permissions: read-only by default
-capabilities: acceptance criteria, tests, regressions, generated output, configuration, evidence
-delegation: verify the requested scope independently and report evidence and remaining uncertainty

shared/global-instructions.md

@@ -12,4 +12,4 @@ Never modify existing documentation automatically. Ask before a code change that
 
 Project-specific instructions may specialize global defaults but must not weaken security or data-loss protections without explicit user approval. Direct user instructions have the highest priority for requested behavior.
 
-Use implementer for execution and architect when technical boundaries or design options need dedicated analysis. Invoke researcher, reviewer, or verifier only when independent work is likely to improve the outcome. Decide based on uncertainty, complexity, risk, blast radius, and verification value; do not invoke these roles automatically. Parallelize only genuinely independent work.
+Use one implementer for small, contained tasks. Add researcher only for material uncertainty, architect only for architecture or boundary decisions, reviewer only for independent quality review, and verifier only for explicit acceptance criteria, tests, or generated artifacts. Do not start reviewer and verifier by default or let subagents create further subagents. Parallelize only genuinely independent work.