molecule-ai-org-template-molecule-dev/daily-docs-sync.md at d7758fd11b5a459f73be2f0224e4a41ecb277086

molecule-ai/molecule-ai-org-template-molecule-dev

CI / validate (push) Waiting to run

Details

fix(personas): migrate gh CLI → tea (Gitea CLI) + curl-via-API (#45 )

Mass-sed across all 58 persona dirs in molecule-ai-org-template-molecule-dev.

Total: 158 files / 396 substitutions
- 389 gh → tea mappings (gh pr/issue/repo/run/auth → tea pr/issue/repo/action/login)
- 7 gh api → curl-via-API mappings
- All Molecule-AI/<repo> → molecule-ai/<repo> in --repo flags (Gitea slug case-sensitive)

Plus SHARED_RULES.md migration callout block + tea install snippet:
- Tea v0.9.2 install via wget (Q2 = B per orchestrator: per-job, not pre-baked into runner image)
- Authenticate using GITEA_TOKEN env var (gating on internal#44 workspace-bootstrap injection)
- Two known limitations called out:
  1. GITEA_TOKEN required for tea/curl auth (internal#44 pending)
  2. tea is per-job-installed; pre-bake parked for image-v2 work
- Cross-link to internal#45 for additions

Two manual edge cases:
- gh search code (no tea equivalent) → curl + tea repo clone + grep recipe
- URL with mixed-case Molecule-AI → lowercase molecule-ai (Gitea case-sensitive)

3 narrative GH_TOKEN references in SHARED_RULES.md intentionally preserved
(describe an env var name, not commands).

Q1=A (mega-PR) per orchestrator dispatch 2026-05-07T09:50:08.

Refs: molecule-ai/internal#45, molecule-ai/internal#44 (GITEA_TOKEN dep)

2026-05-07 02:54:35 -07:00

3.7 KiB

Raw Blame History

IMPORTANT: Check Molecule-AI/internal repo for roadmap (PLAN.md), known issues, runbooks before starting work.

MULTIMEDIA — when publishing docs, consider audio supplements:

TTS: Generate audio versions of key documentation pages for accessibility.

Daily documentation maintenance. Two parallel objectives: (1) keep the public docs site current with the platform repo, (2) backfill stub pages on the docs site one at a time.

SETUP: cd /workspace/repo && git pull 2>/dev/null || true cd /workspace/docs && git pull 2>/dev/null || true cd /workspace/controlplane && git pull 2>/dev/null || true

1a. PAIR RECENT PLATFORM PRS (last 24h): cd /workspace/repo tea pr list --repo molecule-ai/molecule-monorepo --state merged
--search "merged:>$(date -u -d '24 hours ago' +%Y-%m-%dT%H:%M:%SZ)"
--json number,title,files For each merged PR that touches a public surface (platform/internal/handlers/, plugins/, org-templates/, docs/architecture.md, README.md, workspace-template/adapters/*):

Identify which docs page(s) on the public site cover that surface.
If a docs page exists but is stale → update it with examples from the PR diff. Open a PR to Molecule-AI/docs with the change.
If NO docs page exists for the new surface → propose one (add to content/docs/meta.json + new .mdx file). Open a PR.
Always close PRs with Closes platform PR #N so the link is durable.

1b. PAIR RECENT CONTROLPLANE PRS (last 24h): cd /workspace/controlplane tea pr list --repo molecule-ai/molecule-controlplane --state merged
--search "merged:>$(date -u -d '24 hours ago' +%Y-%m-%dT%H:%M:%SZ)"
--json number,title,files ⚠️ PRIVATE REPO. Two cases: (i) Internal-only change (handler, schema, infra, fly.toml, billing logic): update README.md + PLAN.md + any docs/internal/*.md inside molecule-controlplane itself. Open the PR against Molecule-AI/molecule-controlplane. NEVER mention these changes in /workspace/docs. (ii) Customer-facing change (new tier, new region, new SLA, pricing change, signup flow change): write a sanitized description for the PUBLIC docs site (e.g. "We now offer EU-region tenants" — NOT "controlplane reads FLY_REGION from env and passes it to provisioner.go:142"). Open a PR against Molecule-AI/docs. When unsure which category a change falls into: default to INTERNAL-only and ask PM for explicit approval before publishing.

BACKFILL ONE STUB PAGE: cd /workspace/docs grep -l "Coming soon" content/docs/*.mdx | head -1 Pick the highest-priority stub (one of: org-template, plugins, channels, schedules, architecture, api-reference, self-hosting, observability, troubleshooting). Write 300-800 words of hand-crafted, example-rich content based on:
- The actual code in /workspace/repo/platform/internal/handlers/
- The actual templates in /workspace/repo/org-templates/
- The actual plugin manifests in /workspace/repo/plugins/ Cite file paths so readers can follow the source. Open a PR.
LINK + ANCHOR CHECK: Use the browser-automation plugin to crawl https://doc.moleculesai.app (or the local dev server if the site isn't deployed yet — cd /workspace/docs && npm install && npm run build && npm run start). Report broken links and missing anchors back to PM.
ROUTING: delegate_task to PM with audit_summary metadata:
- category: docs
- severity: info
- issues: [list of PR numbers opened to Molecule-AI/docs]
- top_recommendation: one-line summary If nothing to do today, PM-message a one-line "clean".
MEMORY: Save key 'docs-sync-latest' with timestamp + list of stub pages still pending + count of paired PRs this cycle.

3.7 KiB Raw Blame History

3.7 KiB

Raw Blame History