Add LLM tooling feature request

FEATURE_REQUESTS.md

@@ -57,3 +57,19 @@
 ## Notes
 - Treat these as separate features to schedule independently.
 - Likely Sprint 6/7, after core library-aware flow is stable.
+
+## LLM Tooling & MCP Bridge
+
+**Goal:** Make the agent API easy for LLMs to use and optionally expose it via MCP.
+
+**Concept:**
+- Document JSON-RPC API with schemas and examples.
+- Generate synthetic interaction traces for fine-tuning / tool-use evaluation.
+- Add an MCP server wrapper that exposes current agent methods as MCP tools/resources.
+
+**Candidate Deliverables:**
+- `docs/AGENT_API.md` with request/response schemas
+- Example flows: read AST ? mutate ? verify
+- MCP bridge module (optional): maps JSON-RPC to MCP tools
+
+---

PROGRESS.md

@@ -482,3 +482,4 @@ Sprint 5 in progress. Step 135 (library-aware completion) done. Next: Step 136 (
 | 2026-02-09 | Codex | Step 134: PrimitivesRegistry aggregating builtins, imports, and in-scope symbols. 6/6 tests pass. |
 | 2026-02-09 | Codex | Step 135: Library-aware completion ordering with auto-import hints for non-primitive symbols. 5/5 tests pass. |
 | 2026-02-09 | Codex | Added FEATURE_REQUESTS.md to track security vulnerability awareness and semantic library annotations for future sprints. |
+| 2026-02-09 | Codex | Added LLM tooling + MCP bridge feature request to FEATURE_REQUESTS.md. |