Sweeps 51 persona initial-prompt.md files + org.yaml + 2 schedule files (55 substitutions across 50 files) plus a SHARED_RULES.md DOCUMENTATION_POLICY link migration. Per orchestrator's #37 A/B/C decision (Q1): - PUBLIC repos (docs, molecule-sdk-python) → anonymous clone: https://git.moleculesai.app/molecule-ai/<repo>.git - PRIVATE repos (internal, molecule-controlplane, molecule-core, molecule-app, landingpage, etc.) → GITEA_TOKEN-authed clone: https://oauth2:${GITEA_TOKEN}@git.moleculesai.app/molecule-ai/<repo>.git Private-repo clones DEPEND ON the workspace-bootstrap pipeline injecting GITEA_TOKEN — tracked at internal#44 (parked follow-up). Until that lands, persona boot steps that clone private repos WILL FAIL with a no-such-env-var error. LEFT UNTOUCHED in this PR: - gh CLI calls (gh repo clone, gh pr list, gh issue create, gh run list) — gh doesn't talk to Gitea. Migration to tea/curl/shim is tracked at internal#45 (parked follow-up). - Narrative `Molecule-AI/<repo>` mentions (e.g. "PR against Molecule-AI/molecule-core") — these are typically gh-CLI flag args; separate concern, see #45. - Historical issue/PR cross-refs (per Q3, leave-as-is for audit trail). SHARED_RULES.md adds a "Post-2026-05-06 migration in progress" callout at the top, naming both #44 (private-repo blocker) and #45 (gh CLI blocker), so persona authors hitting boot failures know what to look up. Refs: molecule-ai/internal#37, molecule-ai/internal#38, molecule-ai/internal#42, molecule-ai/internal#44, molecule-ai/internal#45
488 B
488 B
You just started as Community Manager. Set up silently — do NOT contact other agents.
- Clone the repo: git clone https://oauth2:${GITEA_TOKEN}@git.moleculesai.app/molecule-ai/internal.git /workspace/repo 2>/dev/null || (cd /workspace/repo && git pull)
- Read /workspace/repo/CLAUDE.md
- Read /configs/system-prompt.md
- Inventory docs/community/ + gh discussions for the repo
- commit_memory: "never speak for company on unreleased features; always cite docs/"
- Wait for tasks.