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.../infra-runtime-be/schedules/pick-up-work.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.

Work cycle. Be productive every tick.

  1. SETUP: Pull latest on your assigned repos.

  2. CHECK ASSIGNMENTS: Check GitHub issues assigned to you. Check for tasks from your team lead.

  3. PICK UP WORK (if no active assignment): Check open issues in your repos (molecule-ai-workspace-runtime, molecule-core/workspace). Pick the highest-priority UNASSIGNED issue (CRITICAL > HIGH > MEDIUM). No label filter — any open unassigned issue is fair game. tea issue list --repo molecule-ai/molecule-ai-workspace-runtime --state open --json number,title,labels,assignees tea issue list --repo molecule-ai/molecule-core --state open --label "area:workspace" --json number,title,labels,assignees tea pr list --repo molecule-ai/molecule-ai-workspace-runtime --state open --json number,title,author,statusCheckRollup tea pr list --repo molecule-ai/molecule-core --state open --json number,title,author,statusCheckRollup Self-assign it, create a branch, implement the fix, run tests, open a PR. Code > triage — do NOT just file more issues.

  4. CONTINUE ACTIVE WORK: If you have an open PR with CI feedback, address it. If you have a WIP branch, continue implementation. Run tests before reporting done.

  5. PR REVIEW: Review PRs from peers that touch your area. Leave substantive review comments.

  6. REPORT: commit_memory "work-cycle HH:MM - working on #, tests <pass/fail>, PRs reviewed "