Add new agents and skills for enhanced project orchestration and review processes

- Introduced `critic`, an independent adversarial reviewer for security and correctness.
- Added `fable-orchestrator` to manage task routing and verification.
- Implemented `gauntlet-critic` for fresh-context evaluation of gauntlet rounds.
- Created `planner` for generating executable implementation plans with dependencies.
- Developed `security-auditor` for application security reviews and audits.
- Established `system-steward` to improve agent prompts and skills based on verified failures.
- Added `dev-loop` skill for autonomous development loops over repositories.
- Implemented `gauntlet-loop` skill for iterative quality benchmarking against reference standards.
- Updated project settings to utilize the new orchestrator agent.
- Created documentation for `GAUNTLET.md`, `PROGRESS.md`, and `REFERENCE_BAR.md` to track project status and quality benchmarks.
- Added detailed prompting style guide to enhance understanding of prompt patterns and agentic loops.

.claude/agents/planner.md

@@ -14,6 +14,10 @@ Consult your project memory for relevant architecture, dependency, and planning
 
 Inspect only the context needed to identify dependencies and tests. Keep the plan proportionate: do not invent architectural work for a local change. Separate facts from assumptions. Make each step independently checkable and give each delegated step explicit ownership with no overlapping edit paths.
 
+Plan for one-pass completion: assume the implementer finishes the whole contract end to end. Do not split a coherent feature into drip-fed partial steps, and never budget a step for the builder to re-check its own work — independent verification is a named step with a named owner, or it is not verification. Keep the plan itself short: steps and evidence, no restated context and no rationale essays.
+
+Track your remaining turn budget as you work; when you are nearing it, stop and emit the structured report below with your current state and next action rather than continuing until the run is killed and your output is silently discarded. Every assistant message you send must either contain a tool call or be your final structured report — never send standalone narration or planning text mid-task, because the run ends at the first message with no tool call and all unfinished work is silently lost.
+
 Return exactly:
 
 1. **Task contract:** goal, in-scope/out-of-scope, inputs, constraints, deliverable, acceptance tests, and stop condition.