- Two-Axis Model sources table: replace mutable `github://owner/repo` row with
pinned-tag and pinned-SHA rows; clarify these are now the only valid forms
- Installing a Plugin: update GitHub example to use `#v1.0.0`; add Callout
warning that bare refs return HTTP 422 with link to Supply Chain Security section
- Install Safeguards: add `PLUGIN_ALLOW_UNPINNED` env var row (dev escape hatch)
- New "Supply Chain Security" section: explains pinned-ref enforcement (SAFE-T1102),
shows valid vs invalid ref forms, SHA-256 content integrity option with hash
computation recipe, and PLUGIN_ALLOW_UNPINNED escape hatch
Pairs with monorepo PR #775 (fix(security): plugin supply chain hardening).
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Pre-draft docs for the google-adk workspace adapter (issue #542, PR #550).
Covers installation, secrets, config reference, A2A compatibility, plugin
support, and troubleshooting. Also adds google-adk to the runtimes table
in architecture.mdx and the runtime list in concepts.mdx.
Closes#542
Co-authored-by: Molecule AI Documentation Specialist <documentation-specialist@agents.moleculesai.app>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Adds standard credential gitignore (.env / *.pem / .secrets/ / .auth_token).
Per-CEO directive 2026-04-16: every plugin and template repo should
gitignore credentials so self-hosters can't accidentally commit real
tokens to public repos.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Customer-facing documentation site for Molecule AI. Built with Fumadocs
(open-source MIT, Next.js 15 App Router native, Tailwind v4, MDX) so we
own the deployment and aesthetic and can grow into custom doc components
for our agent-canvas flows.
## Why Fumadocs (over Mintlify, Nextra, Docusaurus)
- Open source, no vendor lock-in (vs Mintlify SaaS subscription)
- Built on Next.js 15 App Router — matches our existing canvas stack
- Less opinionated than Nextra; can grow into custom doc components
- React/Tailwind first; team already on this stack
- Ships search, dark mode, Shiki highlighting, MDX out of the box
## Initial structure
- app/ — Next.js App Router (home + docs + search route)
- content/docs/ — MDX source (3 hand-written + 9 stub pages)
- lib/source.ts — Fumadocs loader bound to the MDX content
- mdx-components.tsx — default + future custom MDX renderers
- source.config.ts — MDX compile config
## Hand-written launch content
- index.mdx — landing / what you can build / how it works
- quickstart.mdx — clone repo → docker compose → import template → talk to PM
- concepts.mdx — the five primitives: workspaces / plugins / channels / schedules / canvas
## Stub pages (Documentation Specialist agent fills these in on cron)
- org-template, plugins, channels, schedules
- architecture, api-reference, self-hosting
- observability, troubleshooting
## Ownership
The Documentation Specialist agent in the molecule-dev org template will
own this repo end-to-end:
- Watches PRs landing in the platform monorepo
- Auto-opens docs PRs when public APIs / templates / plugins / channels change
- Runs daily cron to backfill stubs and refresh stale pages
Manual edits welcome. Agent picks up on next cron tick.
