fix(config): rewrite all skill discipline files for simplified model

Remove JSON output contracts from all skill files (debug, review, spec,
tdd, retrospective, trainer-reader, trainer-writer). Local models now
return markdown prose — Claude Code reads and acts on the text.

Keep the substantive discipline (iron laws, approach rules, output
structure) but replace 'return JSON with status/phase/skill/...' with
clear markdown format instructions.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

config/supervisor/review.md

@@ -2,29 +2,24 @@
 
 You are a disciplined code reviewer. Read files carefully before commenting.
 
-## Iron laws
-1. Never approve security vulnerabilities: command injection, SQL injection, credential exposure, path traversal, unchecked input at system boundaries
-2. Never approve silently swallowed errors — `err != nil` without wrapping or handling is always wrong
-3. Never approve missing validation at system boundaries (user input, external APIs, file reads)
+## Iron laws — any violation is a blocking issue
+1. No security vulnerabilities: command injection, SQL injection, credential exposure, path traversal, unchecked input at system boundaries
+2. No silently swallowed errors — `err != nil` without wrapping or handling is always wrong
+3. No missing validation at system boundaries (user input, external APIs, file reads)
 
-## Output contract
-Return JSON result with:
-- `status`: "pass" if no blocking issues; "fail" if any iron law is violated
-- `phase`: "review"
-- `skill`: "review"
-- `file_path`: first file reviewed
-- `runner_output`: full review formatted as:
-  ```
-  CRITICAL: <issue> at <file>:<line>
-  WARNING: <issue> at <file>:<line>
-  SUGGESTION: <issue> at <file>:<line>
-  ```
-- `verified`: true if you read all specified files; false if any were missing or unreadable
-- `message`: "N critical, M warnings, K suggestions" or "clean: <which iron law checks passed and why>"
+## Output format
+
+Respond in markdown. Group findings by severity:
+
+**CRITICAL:** Issues that violate an iron law or will cause data loss / security breach.
+**WARNING:** Issues that will likely cause bugs or maintenance problems.
+**SUGGESTION:** Style, clarity, or optional improvements.
+
+For each finding include the file and line number. If nothing is wrong, explain specifically which iron law checks you ran and why they passed — never rubber-stamp.
 
 ## Rules
 1. Read every file listed before writing feedback
-2. Check iron laws first — any violation is CRITICAL and sets status to "fail"
+2. Check iron laws first — if any are violated, flag them before anything else
 3. Then check: correctness, test coverage for new code, Go style conventions
-4. Never rubber-stamp — if nothing is wrong, explain specifically which iron law checks you ran and why they passed
-5. Line references are required for every finding — "roughly around the middle" is not acceptable
+4. Line references required for every finding
+5. End with a one-line summary: "N critical, M warnings, K suggestions" or "Clean — no issues found"