forked from molecule-ai/molecule-core
Hongming Wang
fd2c3fbfc4
Subagent used old CLAUDE.md baselines instead of measuring actuals. Verified counts via pytest --collect-only and go test -v: - Go platform: 536 → 695 (+159 off) - Python workspace-template: 1084 → 1140 (+56 off) - SDK python: 121 → 132 (+11 off) - Canvas vitest: 357 (already correct) - MCP jest: 97 (already correct) Files updated: - CLAUDE.md (Unit Tests block) - PLAN.md (Test Coverage table + totals: 2,295 → 2,421) - docs/development/local-development.md - docs/edit-history/2026-04-13.md (session test-count table + explanatory note about why the Python and SDK counts didn't change today) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
docs/
This directory serves two purposes:
- Markdown content — everything under
architecture/,agent-runtime/,api-protocol/,development/,frontend/,plugins/,product/, etc. This is what agents and humans read. - VitePress site —
.vitepress/config.ts,package.json,package-lock.json. These drive the rendered documentation site.
Local preview
cd docs
npm install
npm run dev # preview on http://localhost:5173
npm run build # static build to docs/.vitepress/dist/
Conventions
- New top-level docs must be linked from
PLAN.md,README.md, andCLAUDE.md— otherwise agents can't find them (see.claude/memoryfeedback_cross_reference_docs.md). edit-history/YYYY-MM-DD.mdis append-only log of significant changes; don't rewrite history.archive/holds one-shot analyses and retired docs — kept for context but not maintained.
Why site tooling lives here (not in docs-site/)
VitePress expects its config at <root>/.vitepress/config.ts where <root> is also the content directory. Splitting tooling into a sibling docs-site/ would require a non-trivial srcDir shim and break relative links in .vitepress/config.ts. Keeping both together is the pragmatic choice; this README is the tradeoff ledger.