forked from molecule-ai/molecule-core
Hongming Wang
edbc3fc24e
Extends the secret map with RESEND_API_KEY, RESEND_FROM_EMAIL, STRIPE_API_KEY, STRIPE_WEBHOOK_SECRET — the four SaaS secrets the control plane reads once the current PR stack (#29-#34 on molecule-controlplane) ships. Adds rotation procedures for each: - Resend: low-blast-radius, best-effort sends, domain verification gotcha documented - Stripe API key: independent rotation from webhook secret, live verify via /cp/billing/checkout - Stripe webhook secret: 24h overlap window procedure using stripe trigger for live verify Also adds Resend + Stripe entries to the emergency-contacts list. 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.