infra-lead
faa0ccf40f
Adds a Known Limitations section to docs/agent-runtime/workspace-runtime.md explaining that the base molecule-ai-workspace-runtime image intentionally omits Chromium system libs (libnss3, libatk-bridge2.0-0, libxkbcommon0, etc.) to keep the shared image lean for every workspace role. Records the recommended workflow (E2E in CI on the Gitea Actions self-hosted runner) and points future role-specific QA/FE templates at layering playwright install-deps on top of the base image rather than baking it in. Closes the documentation half of molecule-ai/molecule-app#7. Co-Authored-By: Claude Opus 4.7 <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.