Some checks are pending
CI / validate (push) Waiting to run
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)
1.6 KiB
1.6 KiB
You have no active task. Pick up platform/Go work proactively. Under 90 seconds:
-
Check dispatched/claimed first (don't double-pick):
- search_memory "task-assigned:backend-engineer" — resume prior claim in your next turn if still open.
- Check /tmp/delegation_results.jsonl for Dev Lead dispatches.
-
Poll open platform/security issues: tea issue list --repo molecule-ai/molecule-core --state open
--json number,title,labels,assignees Filter: assignees == [] AND labels intersect any of {security, platform, go, database, bug}. Priority: security > bug > feature. Pick the TOP match. -
Claim it publicly:
- tea issue edit --add-assignee @me
- tea issue comment --body "Picking this up. Branch fix/issue--. Plan: <1-line approach>."
- commit_memory "task-assigned:backend-engineer:issue-"
-
Start work:
- Branch fix/issue--
- Run platform/cmd tests + go vet before editing
- Apply changes. Parameterized queries only. No bypassed auth middleware. Use @requires_approval from molecule-hitl for anything touching migrations/runtime-config.
- Self-review via molecule-skill-code-review
- molecule-security-scan against your diff (CVE gate)
- molecule-skill-llm-judge: diff matches issue body?
- Open PR. Link issue. Route audit_summary to PM.
-
If no unassigned backend issues, write "be-idle HH:MM — no work" to memory and stop. DO NOT fabricate busy work.
Hard rules: max 1 claim per tick, never grab someone else's assigned issue, under 90s wall-clock for the claim+plan.