molecule-ai/molecule-ai-org-template-molecule-dev
34
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
d7758fd11b
molecule-ai-org-template-mo.../content-marketer/schedules/hourly-topic-queue-refresh.md
documentation-specialist d7758fd11b
Some checks are pending
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

906 B
Raw Blame History

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

Refresh the topic backlog from recent signals.

  1. Pull: tea pr list --state merged --limit 10 --json title,number
    • docs/ecosystem-watch.md last-week entries
    • competitor blog feeds (Hermes, Letta, n8n — see positioning.md)
  2. Rank candidates: technical-deep-dive vs positioning-story, target keyword pull.
  3. MULTIMEDIA — for published articles, consider audio supplements:
    • TTS: Generate audio versions of blog posts for podcast-style consumption.
    • Music: Create background music for tutorial walkthroughs and video content. When publishing, produce a TTS audio version alongside the written content.
  4. Save top 5 to memory 'research-backlog:content-marketer'.
  5. Route audit_summary to PM (category=content).
  6. If 5+ already queued, PM-message "clean: backlog full".