molecule-ai/molecule-core
36
0
Fork 2
Code Issues 6 Pull Requests 1 Actions 2 Packages Projects Releases Wiki Activity
b97bda13e9
molecule-core/docs
History
Molecule AI Core-DevOps b5d9f13ab1
Some checks failed
sop-tier-check / tier-check (pull_request) Failing after 10s
Details
Secret scan / Scan diff for credential-shaped strings (pull_request) Successful in 10s
Details
docs(runbook): add admin-auth.md covering test-token route lockdown 
Issue #214: documents the MOLECULE_ENV=production requirement for
staging/prod tenants to lock the /admin/workspaces/:id/test-token route.
Also adds a startup INFO log in main.go when the route is enabled, so
operators can confirm the setting in boot logs without having to probe
the endpoint directly.

Ref: issue #214.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-10 02:20:30 +00:00
..
adapters
adr
agent-runtime
api-protocol tech-debt: rename molecule-monorepo-net -> molecule-core-net 2026-05-09 20:51:48 +00:00
architecture tech-debt: rename molecule-monorepo-net -> molecule-core-net 2026-05-09 20:51:48 +00:00
assets
blog
design-system docs(canvas-audit): record PR #205 test coverage addition 2026-05-10 00:45:47 +00:00
development tech-debt: rename molecule-monorepo-net -> molecule-core-net 2026-05-09 20:51:48 +00:00
devrel/demos/tool-trace-platform-instructions
engineering
frontend
guides
incidents
infra
integrations chore: sync main → staging (auto, 068c9682) 2026-05-08 01:17:12 +00:00
memory-plugins
pages/api
plugins
runbooks docs(runbook): add admin-auth.md covering test-token route lockdown 2026-05-10 02:20:30 +00:00
tutorials
.gitignore
api-reference.md
e2e-coverage.md
ecosystem-watch.md
glossary.md
index.md
internal-content-policy.md
quickstart.md
README.md
workspace-runtime-package.md

README.md

docs/

This directory serves two purposes:

  1. Markdown content — everything under architecture/, agent-runtime/, api-protocol/, development/, frontend/, plugins/, product/, etc. This is what agents and humans read.
  2. 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, and CLAUDE.md — otherwise agents can't find them (see .claude/ memory feedback_cross_reference_docs.md).
  • edit-history/YYYY-MM-DD.md is 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.