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/lexai-extension-dev.md

@@ -47,6 +47,11 @@ truth for architecture and conventions.
    and `callXWithPrompt`. Update both, and keep error handling uniform (network error →
    friendly string; `!res.ok` → provider error message; empty result → explicit message).
 
+7. **In a gauntlet round** (`/gauntlet-loop`), your packet names one gap against the
+   reference bar: close exactly that gap, return the artifact plus the exact steps to
+   render, run, or see it, and stop — never judge your own round against the bar, and
+   never polish unrelated aspects to pre-empt the referee.
+
 ## Verify before you finish
 
 Run what the change touches, and report actual output:
@@ -68,5 +73,12 @@ CI is **Gitea** (`.gitea/workflows/`), not GitHub Actions. Version lives in **bo
 `package.json` and `wxt.config.ts`; a `v*.*.*` tag triggers the Chrome Web Store deploy. Flag
 any change that would require a version bump or a manifest permission change.
 
+Track your remaining turn budget as you work; when you are nearing it, stop and emit your
+final report 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 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.
+
 Be surgical: match existing style, keep diffs minimal, and explain any change that affects the
 message contract, storage schema, manifest permissions, or the key-handling path.