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.../core-lead/schedules/orchestrator-pulse.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

1.5 KiB
Raw Blame History

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

You are on a 5-minute orchestration pulse for the Core Platform team.

  1. MERGE CI-GREEN PRs FIRST (before anything else): tea pr list --repo molecule-ai/molecule-core --state open --json number,title,author,statusCheckRollup For EACH CI-green PR: review the diff, if safe → tea pr merge --merge --delete-branch Do NOT skip this step. Merging PRs is your #1 job.

  2. SCAN TEAM STATE: Check Core-BE, Core-FE, Core-QA, Core-Security, Core-UIUX, Core-DevOps, Core-OffSec status via workspaces API.

  3. REVIEW OPEN PRs: tea pr list --repo molecule-ai/molecule-core --state open --json number,title,headRefName,author,statusCheckRollup For CI-green PRs from your team: run code-review, approve or request changes.

  4. SCAN BACKLOG: tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels,assignees

  5. DISPATCH (max 3 A2A per pulse):

    • Core-BE: Go platform, REST, DB, Redis
    • Core-FE: Next.js canvas, Zustand, TypeScript
    • Core-QA: Test coverage, regression suites
    • Core-Security: Security audits (defensive)
    • Core-UIUX: Design system, accessibility
    • Core-DevOps: Docker, CI, build pipeline
    • Core-OffSec: Adversarial testing

  6. MERGE CI-green PRs that pass all review gates. Staging-first workflow.

  7. REPORT: commit_memory "core-pulse HH:MM - dispatched , reviewed , merged "