chore(template): add Documentation Specialist as 3rd PM direct report

[HongmingWang-Rabbit]

Summary

Adds a 13th workspace to the molecule-dev template — Documentation Specialist — owning end-to-end documentation across all Molecule AI surfaces. Pairs with the new Molecule-AI/docs repo (Fumadocs + Next.js 15) that will be deployed to doc.moleculesai.app.

Context

CEO directive 2026-04-15: deploy a document specialist for documenting everything including what's in our repository and in our customer facing page doc.moleculesai.app.

I just shipped:

1. Molecule-AI/docs — new public repo, scaffolded with Fumadocs (open-source MIT, Next.js 15 App Router native, Tailwind v4, MDX). Three hand-written pages (index, quickstart, concepts) + 9 stub pages with the agent's TODO marker.
2. This PR — wires the agent into the molecule-dev template.

Framework choice rationale

Framework	Verdict	Why
Fumadocs ✅ chosen	MIT open source; built on Next.js 15 App Router; matches our existing canvas stack; flexible enough to grow into custom doc components for our agent canvas flows; ships search/dark-mode/Shiki out of the box
Mintlify	Rejected	Paid SaaS subscription — vendor lock-in conflicts with self-hosting on doc.moleculesai.app
Nextra	Rejected	More opinionated than Fumadocs; less room to grow into custom MDX components
Docusaurus	Rejected	Not Next.js-native; would split our React build pipeline in two

Where it sits in the org

Third PM direct report, parallel to Research Lead and Dev Lead. Docs is its own swim lane that spans engineering (docs follow code) and research/product (concepts and terminology).

PM
├── Research Lead
├── Dev Lead
└── Documentation Specialist   ← new (13th workspace)

Schedules added (2)

Cron	When	Job
0 9 * * *	Daily 09:00 UTC	Pair every merged platform PR (last 24h) with a docs PR; backfill one stub page on the docs site; crawl live site for broken links/dead anchors; delegate_task to PM with audit_summary{category=docs}
0 11 * * 1	Weekly Monday 11:00 UTC	Stale page detection (>30 days untouched on fast-moving surfaces); terminology consistency check (one canonical name per concept); link-rot scan; same audit_summary contract

Both schedules end with the structured audit_summary routing per #75 (category: docs) so PM fans out via the platform-level category_routing.

Routing

Adds docs: [Documentation Specialist] to category_routing in the defaults block. Any agent that emits an audit_summary with category=docs is auto-routed here.

Plugins

Inherits the 9 universal defaults (#71 union semantics). Adds browser-automation for crawling the live docs site (visual regressions, broken links, dead anchors).

• molecule-skill-update-docs (already in defaults) handles the cross-repo docs sync skill.
• molecule-careful-bash, molecule-prompt-watchdog, molecule-audit-trail (defaults) provide guardrails on this agent's git operations.

Initial prompt — clones BOTH repos

The agent's initial_prompt clones both:

• /workspace/repo — the platform monorepo (read recent commits, identify public surfaces)
• /workspace/docs — Molecule-AI/docs (write-side, where it opens PRs)

This is the first workspace in the template that needs cross-repo access. Tracking as a follow-up: the platform's workspace_dir field currently only mounts ONE host directory; we need a way to mount multiple. For now the agent does git clones in the initial_prompt which works but doesn't get bind-mount caching benefits.

What this PR does NOT do

• It does not create the workspace immediately on the running platform — that needs an org/import (currently failing on a pre-existing PM workspace_dir env-var issue, orthogonal). I'll sync the new workspace into the running DB manually after merge.
• It does not configure the deployment to doc.moleculesai.app — that's a separate Vercel/DNS step the agent itself can later automate.
• It does not write the actual content for the 9 stub pages — that's the agent's primary job once it boots.

Test plan

• YAML valid (python -c "import yaml; yaml.safe_load(open(...))").
• Tree-walk shows Documentation Specialist as 3rd PM child.
• Total schedules count = 9 (was 7, added 2).
• category_routing.docs = [Documentation Specialist].
• After merge + provision: agent boots, clones both repos, opens its first docs sync PR within 24h.
• First daily cron fires Tuesday 09:00 UTC.
• First weekly cron fires next Monday 11:00 UTC.

Related

• NEW: Molecule-AI/docs — the customer-facing site this agent owns
• fix(org): per-workspace plugins UNION with defaults; '!' prefix opts out (#68) #71 — plugin union semantics (this PR uses plugins: [browser-automation] add-only form)
• feat(platform): generic category_routing replaces hardcoded audit dispatch (#51) #75 — category_routing + audit_summary schema this agent consumes
• fix(org): DB-authoritative schedules; org/import is additive on template rows (#24) #76 — DB-authoritative schedules (so the new schedules stick on re-import)
• chore(template): add 4 evolution crons — ecosystem / plugins / template / channels #87 — evolution crons (this is in the same spirit — adds an evolution lane for docs)

🤖 Generated with Claude Code

[HongmingWang-Rabbit]

Updated 2026-04-15 per CEO directive: Documentation Specialist now watches all THREE repos.

Added: Molecule-AI/molecule-controlplane (PRIVATE)

The SaaS controlplane (Go/Fly.io tenant provisioner) is now in scope. With a strict public/private split — privacy rule repeated 3× in the prompt:

Bucket	Where docs live	Examples
Internal-only (default)	Inside molecule-controlplane (README.md, PLAN.md, docs/internal/)	handler changes, schema migrations, fly.toml updates, billing logic, provisioner internals
Customer-facing (sanitized)	Public docs site Molecule-AI/docs	new tier, new region, new SLA, signup flow change, pricing change

When unsure → default to internal-only and ask PM before publishing.

Changes in this push (commit 41e39c2)

• role description extended to cover all 3 repos with the privacy split
• initial_prompt clones controlplane in step 1, reads README+PLAN in step 5, scans recent commits in step 8, lists 4 owned surfaces with public/private labels in step 10
• Daily cron adds step 1b 'PAIR RECENT CONTROLPLANE PRS' with branching (internal vs customer-facing)
• SETUP block adds cd /workspace/controlplane && git pull

What this means in practice

• Daily 09:00 UTC tick scans merged PRs across BOTH molecule-monorepo AND molecule-controlplane
• Internal controlplane changes get documented inside their own repo
• Customer-facing controlplane changes get sanitized + opened as PRs against Molecule-AI/docs
• Public docs never leak controlplane source code, file paths, internal endpoints, or schemas

Token: the agent will need read access to molecule-controlplane via its GitHub token. Add to follow-ups: ensure the workspace's GH credentials have access to the private repo before first cron tick.