Documentation And Planning
The public documentation is organized around shipped behavior. Start with:
| Page | Purpose |
|---|---|
| Current features | What is implemented now. |
| Project status | Evidence-based done, partial, and not-started classification. |
| Planned features | Short product-level view of remaining work. |
| Technical overview | Runtime, API, MCP, CLI, configuration, and project structure. |
| Agent integration | MCP tools, resources, prompts, and client behavior. |
| Architecture | Implemented system and provider boundaries. |
Where Work Is Tracked
GitHub issues are the source of truth for unfinished implementation work. Use
the enhancement issue list
for active epics and child issues.
The repository still contains older plan and improvement Markdown files because some preserve useful design decisions, validation evidence, or compatibility history. They are no longer presented as the public navigation or treated as an authoritative backlog. Their unchecked boxes may be stale; use Project status and linked GitHub issues instead.
Documentation Rule
New product work should have a GitHub issue with acceptance criteria. Add a Markdown design record only when the design remains useful after the work is complete. User-facing docs should describe behavior that actually ships.