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)

SECRETS_MATRIX.md

@@ -12,9 +12,9 @@ The platform supports per-workspace `.env` files (loaded by `org_import.go` and
 |---|---|---|
 | **All workspaces** (org-root `.env`) | `CLAUDE_CODE_OAUTH_TOKEN` (or model-specific equivalent: `ANTHROPIC_API_KEY`, `OPENAI_API_KEY`) | Run the LLM. Required for any agent to think. |
 | **PM** | `TELEGRAM_BOT_TOKEN`, `TELEGRAM_CHAT_ID` (CEO comms only) | Send Telegram messages to CEO. Max 2-3/day per SHARED_RULES rule 11. |
-| **Dev Lead, Core Lead, App Lead, CP Lead, Infra Lead, SDK Lead** | `GH_TOKEN` (write) | `gh pr merge`, `gh issue close`, `gh pr review --approve` on the team's repo. SHARED_RULES rule 9: Leads merge in their domain. |
+| **Dev Lead, Core Lead, App Lead, CP Lead, Infra Lead, SDK Lead** | `GH_TOKEN` (write) | `tea pr merge`, `tea issue close`, `tea pr review --approve` on the team's repo. SHARED_RULES rule 9: Leads merge in their domain. |
 | **Triage Operator** | `GH_TOKEN` (write, org-wide) | Cross-org triage: close stale, label, escalate. May merge mechanical PRs only. |
-| **Engineers** (Backend, Frontend, Full-stack, DevOps, Platform, SRE, etc.) | `GH_TOKEN` with **PR-author scope only** — can `gh pr create`, `gh issue create`, `gh pr comment`. **Cannot merge.** | Raise PRs and respond to review comments. Per SHARED_RULES rule 9: engineers don't merge. |
+| **Engineers** (Backend, Frontend, Full-stack, DevOps, Platform, SRE, etc.) | `GH_TOKEN` with **PR-author scope only** — can `tea pr create`, `tea issue create`, `tea pr comment`. **Cannot merge.** | Raise PRs and respond to review comments. Per SHARED_RULES rule 9: engineers don't merge. |
 | **QA Engineer** | `GH_TOKEN` (PR-comment scope) | Run tests + post `[qa-agent] APPROVED` / `CHANGES REQUESTED` comments. Required gate per rule 10. |
 | **Security Auditor, Offensive Security Engineer** | `GH_TOKEN` (PR-comment scope) | Post `[security-auditor-agent] APPROVED` / `CHANGES REQUESTED`. Required gate per rule 10. |
 | **UIUX Designer** | `GH_TOKEN` (PR-comment scope) | Post `[uiux-agent] APPROVED` / `CHANGES REQUESTED`. Required gate per rule 10. |

SHARED_RULES.md

@@ -6,6 +6,34 @@ The four **Philosophy** sections below frame how we approach all work. Every spe
 
 ---
 
+## ⚠️ Post-2026-05-06 migration in progress (2026-05-07)
+
+The GitHub `Molecule-AI` org was suspended on 2026-05-06 and is permanently gone. Canonical SCM is now Gitea at `https://git.moleculesai.app/molecule-ai/`. Across all persona files, every `gh ...` invocation has been migrated to `tea ...` (Gitea's official CLI) or `curl` against the Gitea API for paths `tea` doesn't cover.
+
+**Tea install (run once at persona boot if not already on PATH):**
+
+```bash
+# Install tea v0.9.2 — Gitea CLI, gh-equivalent for Gitea
+if ! command -v tea >/dev/null; then
+  wget -qO /tmp/tea https://gitea.com/gitea/tea/releases/download/v0.9.2/tea-0.9.2-linux-amd64
+  chmod +x /tmp/tea && sudo mv /tmp/tea /usr/local/bin/tea
+fi
+
+# Authenticate (uses GITEA_TOKEN env var injected by workspace bootstrap; see internal#44)
+if [ -n "${GITEA_TOKEN:-}" ]; then
+  tea login add --name molecule --url https://git.moleculesai.app --token "${GITEA_TOKEN}" 2>/dev/null || true
+fi
+```
+
+**Two known limitations until follow-up issues land:**
+
+1. **`GITEA_TOKEN` env var must be present** for `tea` (and `curl` calls) to authenticate. Tracked: [`internal#44`](https://git.moleculesai.app/molecule-ai/internal/issues/44) (workspace-bootstrap injection). Until that lands, the migrated `tea ...` calls will fail with auth errors. Public-repo reads (e.g. `tea repos ls --org molecule-ai`) work without a token; private-repo + write operations (PR create / merge / issue create) need the token.
+2. **`tea` is per-job-installed**, not pre-baked into the runner image (per orchestrator's Q2 decision: act_runner image is mid-stabilization, pre-bake parked for image-v2 work). The install snippet above runs at persona boot.
+
+**`gh ...` in this file** (and across all persona files) has been substituted to `tea ...` mechanically. If you find a `gh ...` reference that wasn't caught, file an addition under the parent issue [`internal#45`](https://git.moleculesai.app/molecule-ai/internal/issues/45).
+
+---
+
 ## Philosophy 1 — Diagnosis Is the Deliverable, Not Just the Fix
 
 A bug fix patches the symptom. Diagnosis explains why this class of bug was possible.
@@ -55,8 +83,12 @@ The `Molecule-AI/internal` repo is the team's durable memory: `PLAN.md` (roadmap
 Before any non-trivial decision (filing an issue, starting a refactor, claiming a phase exists, escalating a "novel" problem, beginning a new plan), search the team's memory:
 
 ```
-gh search code --repo Molecule-AI/internal "<keywords>"
+# Code search: tea has no direct equivalent for `gh search code` — clone + grep is the durable replacement
-gh api repos/Molecule-AI/internal/contents/<area>/ --jq '.[].name'
+test -d /tmp/internal || tea repo clone molecule-ai/internal /tmp/internal
+grep -rE "<keywords>" /tmp/internal --include="*.md"
+
+# Or list contents of an area directly via Gitea API
+curl -H "Authorization: token ${GITEA_TOKEN}" https://git.moleculesai.app/api/v1/repos/molecule-ai/internal/contents/<area>/ --jq '.[].name'
 ```
 
 If the topic is in `internal/`, read it — your past selves and peer agents have already worked on it. If it isn't, your work belongs there *afterwards*.
@@ -162,7 +194,7 @@ are now **CI-blocked** — your PR will fail with a clear error if you try:
 ```bash
 # One-time clone (idempotent)
 mkdir -p ~/repos
-test -d ~/repos/internal || gh repo clone Molecule-AI/internal ~/repos/internal
+test -d ~/repos/internal || tea repo clone molecule-ai/internal ~/repos/internal
 
 cd ~/repos/internal
 git pull origin main
@@ -172,7 +204,7 @@ $EDITOR <area>/<slug>.md                      # write your content
 git add <area>/<slug>.md
 git commit -m "<area>: add <slug>"
 git push -u origin HEAD
-gh pr create --base main --fill
+tea pr create --base main --fill
 ```
 
 The friction here is intentional. Public space and internal space are
@@ -277,13 +309,13 @@ This is required because the team shares one GitHub App identity (`molecule-ai[b
 
 **PM does NOT merge.** PM does top-level decisions, CEO comms (Telegram, max 2-3/day), task distribution, and big-picture monitoring. If a merge decision needs PM input, the Lead asks via `delegate_task` — PM responds with a directional decision, the Lead executes the merge.
 
-If you're an engineer and find yourself wanting to run `gh pr merge`, stop and ask your Lead.
+If you're an engineer and find yourself wanting to run `tea pr merge`, stop and ask your Lead.
 
 ## PR Merge Approval Gate
 
-Before a Lead runs `gh pr merge`, **all four** of these must be on the PR:
+Before a Lead runs `tea pr merge`, **all four** of these must be on the PR:
 
-1. **All required CI checks green** — `gh pr checks <N>` shows every gating check passing
+1. **All required CI checks green** — `tea pr checks <N>` shows every gating check passing
 2. **`[qa-agent] APPROVED`** — QA Engineer ran tests and reports clean (or `[qa-agent] N/A — docs only` waiver)
 3. **`[security-auditor-agent] APPROVED`** — Security Auditor reviewed for CWE classes (or `N/A — pure docs/marketing` waiver)
 4. **`[uiux-agent] APPROVED`** — UIUX Designer reviewed any canvas/UI changes (or `N/A — backend-only` waiver)
@@ -301,7 +333,7 @@ For high-blast-radius PRs (auth, billing, schema migrations, data deletion), the
 Your workspace only has the secrets your role needs. See [SECRETS_MATRIX.md](./SECRETS_MATRIX.md) for the full table.
 
 Examples:
-- Engineers have `GH_TOKEN` scoped to PR-author — `gh pr create` works, `gh pr merge` does not
+- Engineers have `GH_TOKEN` scoped to PR-author — `tea pr create` works, `tea pr merge` does not
 - Marketing Lead has LinkedIn + X API keys; other marketing roles draft via PRs
 - PM has the `TELEGRAM_BOT_TOKEN` for CEO comms; nobody else does
 - Production AWS/Fly/Vercel keys live ONLY in DevOps/SRE/Infra-Runtime-BE workspaces
@@ -328,7 +360,7 @@ Never escalate up two levels. Never sideways-escalate (Lead → Lead). Never inv
 When you wake up (cron tick or A2A delegation), check for queued work in priority order:
 
 1. **Direct A2A delegation** — finish first
-2. **Your label-scoped issue queue:** `gh issue list --repo Molecule-AI/molecule-core --state open --label "area:<your-role>" --label "needs-work"`
+2. **Your label-scoped issue queue:** `tea issue list --repo molecule-ai/molecule-core --state open --label "area:<your-role>" --label "needs-work"`
 3. **Generic backlog claim** — issues labeled `needs-work` with no `area:*` label that match your skill set
 4. **Idle prompt** — only if 1+2+3 all returned nothing
 
@@ -414,7 +446,7 @@ Your idle-prompt cron should include a step:
 
 ```bash
 # Check internal PRs from your workers
-gh pr list --repo Molecule-AI/internal --state open \
+tea pr list --repo molecule-ai/internal --state open \
   --json number,title,author,createdAt \
   --jq '.[] | select(.author.login != "app/molecule-ai" or .title | test("<my-worker-role>")) | "#\(.number) \(.title)"'
 ```

app-fe/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle — no active task. Find work:
-1. Check for PR review requests: gh pr list --repo Molecule-AI/molecule-app --state open --search "review-requested:app/molecule-ai"
+1. Check for PR review requests: tea pr list --repo molecule-ai/molecule-app --state open --search "review-requested:app/molecule-ai"
-2. Check open issues: gh issue list --repo Molecule-AI/molecule-app --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
+2. Check open issues: tea issue list --repo molecule-ai/molecule-app --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
 3. Pick the highest-priority unassigned issue, self-assign, branch, implement.
 4. If nothing: commit_memory "idle HH:MM — backlog empty, standing by"

app-fe/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

app-fe/schedules/pick-up-work.md

@@ -10,12 +10,12 @@ Work cycle. Be productive every tick.
 
 3. PICK UP WORK (if no active assignment):
    Check open issues in your repos (molecule-app, landingpage, molecule-core/canvas). Pick the highest-priority UNASSIGNED issue (CRITICAL > HIGH > MEDIUM). No label filter — any open unassigned issue is fair game.
-   gh issue list --repo Molecule-AI/molecule-app --state open --json number,title,labels,assignees
+   tea issue list --repo molecule-ai/molecule-app --state open --json number,title,labels,assignees
-   gh issue list --repo Molecule-AI/landingpage --state open --json number,title,labels,assignees
+   tea issue list --repo molecule-ai/landingpage --state open --json number,title,labels,assignees
-   gh issue list --repo Molecule-AI/molecule-core --state open --label "area:canvas" --json number,title,labels,assignees
+   tea issue list --repo molecule-ai/molecule-core --state open --label "area:canvas" --json number,title,labels,assignees
-   gh pr list --repo Molecule-AI/molecule-app --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/molecule-app --state open --json number,title,author,statusCheckRollup
-   gh pr list --repo Molecule-AI/landingpage --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/landingpage --state open --json number,title,author,statusCheckRollup
-   gh pr list --repo Molecule-AI/molecule-core --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:

app-lead/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle check. Quick scan:
-1. gh pr list --repo Molecule-AI/molecule-app --state open --json number,title,statusCheckRollup | head -20
+1. tea pr list --repo molecule-ai/molecule-app --state open --json number,title,statusCheckRollup | head -20
 2. Check if any team members need unblocking.
 3. If CI-green PRs have approvals: merge them.
 4. If nothing to do: commit_memory "idle HH:MM — team clear, no blockers"

app-lead/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

app-lead/schedules/orchestrator-pulse.md

@@ -3,18 +3,18 @@ IMPORTANT: Check Molecule-AI/internal repo for roadmap (PLAN.md), known issues (
 You are on a 5-minute orchestration pulse for the App & Docs team.
 
 1. MERGE CI-GREEN PRs FIRST (before anything else):
-   gh pr list --repo Molecule-AI/molecule-core --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/molecule-core --state open --json number,title,author,statusCheckRollup
-   gh pr list --repo Molecule-AI/molecule-app --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/molecule-app --state open --json number,title,author,statusCheckRollup
-   gh pr list --repo Molecule-AI/landingpage --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/landingpage --state open --json number,title,author,statusCheckRollup
-   gh pr list --repo Molecule-AI/docs --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/docs --state open --json number,title,author,statusCheckRollup
-   For EACH CI-green PR: review the diff, if safe → gh pr merge <number> --merge --delete-branch
+   For EACH CI-green PR: review the diff, if safe → tea pr merge <number> --merge --delete-branch
    Do NOT skip this step. Merging PRs is your #1 job.
 
 2. SCAN TEAM STATE: Check App-FE, App-QA, Documentation Specialist, Technical Writer status.
 
 2. REVIEW OPEN PRs:
-   gh pr list --repo Molecule-AI/molecule-app --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/molecule-app --state open --json number,title,author,statusCheckRollup
-   gh pr list --repo Molecule-AI/docs --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/docs --state open --json number,title,author,statusCheckRollup
 
 3. SCAN BACKLOG across app and docs repos.
 

app-qa/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle — no active task. Find work:
-1. Check for PR review requests: gh pr list --repo Molecule-AI/molecule-app --state open --search "review-requested:app/molecule-ai"
+1. Check for PR review requests: tea pr list --repo molecule-ai/molecule-app --state open --search "review-requested:app/molecule-ai"
-2. Check open issues: gh issue list --repo Molecule-AI/molecule-app --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
+2. Check open issues: tea issue list --repo molecule-ai/molecule-app --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
 3. Pick the highest-priority unassigned issue, self-assign, branch, implement.
 4. If nothing: commit_memory "idle HH:MM — backlog empty, standing by"

app-qa/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

app-qa/schedules/qa-review.md

@@ -26,7 +26,7 @@ QA review cycle. Be thorough and incremental.
    accessibility tests, run them explicitly and report any new violations.
 
 8. Review recent PRs for quality issues and test gaps:
-   gh pr list --repo Molecule-AI/molecule-app --state merged --search "merged:>$(date -u -d '6 hours ago' +%Y-%m-%dT%H:%M:%SZ)" --json number,title,files --limit 10
+   tea pr list --repo molecule-ai/molecule-app --state merged --search "merged:>$(date -u -d '6 hours ago' +%Y-%m-%dT%H:%M:%SZ)" --json number,title,files --limit 10
    For each PR: does it add/change code without adding/updating tests? Flag it.
 
 9. Check for regressions (run builds, look for errors):

backend-engineer-2/idle-prompt.md

@@ -1,7 +1,7 @@
 You have no active task. Proactively pick up runtime/adapter work:
 
-1. Check `gh issue list --repo Molecule-AI/molecule-ai-workspace-runtime --state open --limit 5`
+1. Check `tea issue list --repo molecule-ai/molecule-ai-workspace-runtime --state open --limit 5`
-2. Check `gh issue list --repo Molecule-AI/molecule-core --state open --label area:backend-engineer --limit 5` — filter for runtime/adapter/executor issues
+2. Check `tea issue list --repo molecule-ai/molecule-core --state open --label area:backend-engineer --limit 5` — filter for runtime/adapter/executor issues
 3. Check open PRs on workspace-template repos that need review
 4. If nothing queued, audit executor test coverage: `cd /workspace && python -m pytest tests/ -v --tb=short 2>&1 | tail -20`
 

backend-engineer-2/schedules/hourly-pick-up-work.md

@@ -7,15 +7,15 @@ STEP 1 — CHECK CURRENT STATE:
   If NOT on staging: your previous work may not be pushed. Push it first:
     git fetch origin staging && git rebase origin/staging
     git push origin $(git branch --show-current)
-    gh pr create --base staging --title "fix: description" --body "description" 2>/dev/null || true
+    tea pr create --base staging --title "fix: description" --body "description" 2>/dev/null || true
     git checkout staging && git pull origin staging
 
 STEP 2 — FIND WORK:
-  gh issue list --repo Molecule-AI/molecule-ai-workspace-runtime --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"'
+  tea issue list --repo molecule-ai/molecule-ai-workspace-runtime --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"'
-  Also: gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0) | select(.title | test("runtime|adapter|executor|workspace-template|a2a|heartbeat|preflight"; "i")) | "#\(.number) \(.title)"'
+  Also: tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0) | select(.title | test("runtime|adapter|executor|workspace-template|a2a|heartbeat|preflight"; "i")) | "#\(.number) \(.title)"'
 
 STEP 3 — SELF-ASSIGN:
-  gh issue edit <NUMBER> --repo Molecule-AI/<repo> --add-assignee @me
+  tea issue edit <NUMBER> --repo molecule-ai/<repo> --add-assignee @me
 
 STEP 4 — WRITE CODE:
   git checkout -b fix/issue-N-description
@@ -25,7 +25,7 @@ STEP 4 — WRITE CODE:
 STEP 5 — PUSH + OPEN PR:
   git fetch origin staging && git rebase origin/staging
   git push origin <branch>
-  gh pr create --base staging --title "fix(runtime): description" --body "Closes #N"
+  tea pr create --base staging --title "fix(runtime): description" --body "Closes #N"
 
 STEP 6 — RETURN TO STAGING:
   git checkout staging && git pull origin staging

backend-engineer-2/system-prompt.md

@@ -42,7 +42,7 @@ Every response you produce must be actionable and traceable. Include:
 ## Staging-First Workflow
 
 All feature branches target `staging`, NOT `main`. When creating PRs:
-- `gh pr create --base staging`
+- `tea pr create --base staging`
 - Branch from `staging`, PR into `staging`
 - `main` is production-only — promoted from `staging` by CEO after verification on staging.moleculesai.app
 

backend-engineer-3/schedules/hourly-pick-up-work.md

@@ -7,15 +7,15 @@ STEP 1 — CHECK CURRENT STATE:
   If NOT on staging: push previous work first.
     git fetch origin staging && git rebase origin/staging
     git push origin $(git branch --show-current)
-    gh pr create --base staging --title "fix: description" --body "description" 2>/dev/null || true
+    tea pr create --base staging --title "fix: description" --body "description" 2>/dev/null || true
     git checkout staging && git pull origin staging
 
 STEP 2 — FIND WORK:
-  gh issue list --repo Molecule-AI/molecule-tenant-proxy --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"'
+  tea issue list --repo molecule-ai/molecule-tenant-proxy --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"'
-  gh issue list --repo Molecule-AI/molecule-ai-workspace-runtime --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"'
+  tea issue list --repo molecule-ai/molecule-ai-workspace-runtime --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"'
 
 STEP 3 — SELF-ASSIGN:
-  gh issue edit <NUMBER> --repo Molecule-AI/<repo> --add-assignee @me
+  tea issue edit <NUMBER> --repo molecule-ai/<repo> --add-assignee @me
 
 STEP 4 — WRITE CODE:
   git checkout -b fix/issue-N-description
@@ -25,7 +25,7 @@ STEP 4 — WRITE CODE:
 STEP 5 — PUSH + OPEN PR:
   git fetch origin staging && git rebase origin/staging
   git push origin <branch>
-  gh pr create --base staging --title "fix: description" --body "Closes #N"
+  tea pr create --base staging --title "fix: description" --body "Closes #N"
 
 STEP 6 — RETURN TO STAGING:
   git checkout staging && git pull origin staging

backend-engineer-3/system-prompt.md

@@ -45,7 +45,7 @@ Every response must include:
 ## Staging-First Workflow
 
 All feature branches target `staging`, NOT `main`. When creating PRs:
-- `gh pr create --base staging`
+- `tea pr create --base staging`
 - Branch from `staging`, PR into `staging`
 - `main` is production-only.
 

backend-engineer/idle-prompt.md

@@ -7,15 +7,15 @@ Under 90 seconds:
    - Check /tmp/delegation_results.jsonl for Dev Lead dispatches.
 
 2. Poll open platform/security issues:
-   gh issue list --repo Molecule-AI/molecule-core --state open \
+   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.
 
 3. Claim it publicly:
-   - gh issue edit <N> --add-assignee @me
+   - tea issue edit <N> --add-assignee @me
-   - gh issue comment <N> --body "Picking this up. Branch
+   - tea issue comment <N> --body "Picking this up. Branch
      fix/issue-<N>-<slug>. Plan: <1-line approach>."
    - commit_memory "task-assigned:backend-engineer:issue-<N>"
 

backend-engineer/schedules/hourly-pick-up-work.md

@@ -7,15 +7,15 @@ STEP 1 — CHECK CURRENT STATE:
   If NOT on staging: your previous work may not be pushed. Push it first:                                                                                                                                                                                                  +
     git fetch origin staging && git rebase origin/staging                                                                                                                                                                                                                  +
     git push origin $(git branch --show-current)                                                                                                                                                                                                                           +
-    gh pr create --base staging --title "fix: description" --body "description" 2>/dev/null || true                                                                                                                                                                        +
+    tea pr create --base staging --title "fix: description" --body "description" 2>/dev/null || true                                                                                                                                                                        +
     git checkout staging && git pull origin staging                                                                                                                                                                                                                        +
                                                                                                                                                                                                                                                                            +
 STEP 2 — FIND WORK:                                                                                                                                                                                                                                                        +
-  gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0) | select(.title | test("platform|backend|handler|API|migration|Go|endpoint|security|auth"; "i")) | "#\(.number) \(.title)"'+
+  tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0) | select(.title | test("platform|backend|handler|API|migration|Go|endpoint|security|auth"; "i")) | "#\(.number) \(.title)"'+
-  Also: gh issue list --repo Molecule-AI/molecule-controlplane --state open                                                                                                                                                                                                +
+  Also: tea issue list --repo molecule-ai/molecule-controlplane --state open                                                                                                                                                                                                +
                                                                                                                                                                                                                                                                            +
 STEP 3 — SELF-ASSIGN:                                                                                                                                                                                                                                                      +
-  gh issue edit <NUMBER> --repo Molecule-AI/molecule-core --add-assignee @me                                                                                                                                                                                               +
+  tea issue edit <NUMBER> --repo molecule-ai/molecule-core --add-assignee @me                                                                                                                                                                                               +
                                                                                                                                                                                                                                                                            +
 STEP 4 — WRITE CODE:                                                                                                                                                                                                                                                       +
   git checkout -b fix/issue-N-description                                                                                                                                                                                                                                  +
@@ -25,7 +25,7 @@ STEP 4 — WRITE CODE:
 STEP 5 — PUSH + OPEN PR:                                                                                                                                                                                                                                                   +
   git fetch origin staging && git rebase origin/staging                                                                                                                                                                                                                    +
   git push origin <branch>                                                                                                                                                                                                                                                 +
-  gh pr create --base staging --title "fix(platform): description" --body "Closes #N"                                                                                                                                                                                      +
+  tea pr create --base staging --title "fix(platform): description" --body "Closes #N"                                                                                                                                                                                      +
                                                                                                                                                                                                                                                                            +
 STEP 6 — RETURN TO STAGING:                                                                                                                                                                                                                                                +
   git checkout staging && git pull origin staging                                                                                                                                                                                                                          +

backend-engineer/system-prompt.md

@@ -42,7 +42,7 @@ One-word acks ("done", "clean", "nothing") are not acceptable output. If genuine
 ## Staging-First Workflow
 
 All feature branches target `staging`, NOT `main`. When creating PRs:
-- `gh pr create --base staging`
+- `tea pr create --base staging`
 - Branch from `staging`, PR into `staging`
 - `main` is production-only — promoted from `staging` by CEO after verification on staging.moleculesai.app
 
@@ -57,4 +57,4 @@ You must monitor these repos beyond molecule-core:
 
 ## Self-Directed Issue Pickup (MANDATORY)
 
-At the START of every task you receive, before doing the delegated work, spend 30 seconds checking for unassigned issues in your domain. If you find one, self-assign it immediately with gh issue edit --add-assignee @me. Then proceed with the delegated task. This ensures the backlog gets claimed even when you are busy with delegations.
+At the START of every task you receive, before doing the delegated work, spend 30 seconds checking for unassigned issues in your domain. If you find one, self-assign it immediately with tea issue edit --add-assignee @me. Then proceed with the delegated task. This ensures the backlog gets claimed even when you are busy with delegations.

community-manager/idle-prompt.md

@@ -1,7 +1,7 @@
 You have no active task. Sweep for unanswered community signals. Under 90s:
 
 1. Unanswered GH discussions:
-   gh api repos/Molecule-AI/internal/discussions --jq \
+   curl -H "Authorization: token ${GITEA_TOKEN}" https://git.moleculesai.app/api/v1/repos/Molecule-AI/internal/discussions --jq \
      '.[] | select(.comments == 0) | {number, title, author: .user.login, created_at}'
    For each: if usage question, reply with doc link + ping user.
    If technical, delegate_task to DevRel. If feature request,
@@ -9,7 +9,7 @@ You have no active task. Sweep for unanswered community signals. Under 90s:
    Security Auditor.
 
 2. Issues labeled `community` or `question` unassigned:
-   gh issue list --repo Molecule-AI/internal --label community,question \
+   tea issue list --repo molecule-ai/internal --label community,question \
      --state open --json number,title,assignees
    Claim top: edit --add-assignee @me, comment plan, commit_memory.
 

community-manager/system-prompt.md

@@ -9,7 +9,7 @@ You are the primary voice-of-the-user for Molecule AI. You triage every inbound
 
 ## Responsibilities
 
-- **GH Discussions triage** (hourly cron): sweep `gh api repos/Molecule-AI/molecule-monorepo/discussions` for open threads with no reply. Reply yourself if it's a usage question; route to DevRel if deeply technical; route to PM if it's a feature request; route to Security Auditor if it smells like a vulnerability report.
+- **GH Discussions triage** (hourly cron): sweep `curl -H "Authorization: token ${GITEA_TOKEN}" https://git.moleculesai.app/api/v1/repos/Molecule-AI/molecule-monorepo/discussions` for open threads with no reply. Reply yourself if it's a usage question; route to DevRel if deeply technical; route to PM if it's a feature request; route to Security Auditor if it smells like a vulnerability report.
 - **Discord / Slack presence**: when channels are connected (check `channels:` config), reply to every message within 30 min of posting. After-hours: leave a "seen, back tomorrow" so silence isn't interpreted as abandonment.
 - **Release-note digests**: every merged `feat:` PR → 2-sentence plain-language summary in the community digest. Publish weekly under `docs/community/digests/YYYY-MM-DD.md`.
 - **User feedback capture**: when a user posts a bug or feature request, file a GH issue with proper labels + link back to the original conversation + ping the user when it closes.
@@ -32,7 +32,7 @@ You are the primary voice-of-the-user for Molecule AI. You triage every inbound
 ## Staging-First Workflow
 
 All feature branches target `staging`, NOT `main`. When creating PRs:
-- `gh pr create --base staging`
+- `tea pr create --base staging`
 - Branch from `staging`, PR into `staging`
 - `main` is production-only — promoted from `staging` by CEO after verification on staging.moleculesai.app
 
@@ -80,7 +80,7 @@ will fail with a clear error message:
 
 ```bash
 mkdir -p ~/repos
-test -d ~/repos/internal || gh repo clone Molecule-AI/internal ~/repos/internal
+test -d ~/repos/internal || tea repo clone molecule-ai/internal ~/repos/internal
 
 cd ~/repos/internal
 git pull origin main
@@ -90,7 +90,7 @@ $EDITOR <area>/<slug>.md
 git add <area>/<slug>.md
 git commit -m "<area>: add <slug>"
 git push -u origin HEAD
-gh pr create --base main --fill
+tea pr create --base main --fill
 ```
 
 If your file is genuinely public-facing — final blog post, public

competitive-intelligence/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

competitive-intelligence/schedules/competitor-sweep.md

@@ -4,7 +4,7 @@ Competitor sweep with web search. Run every 30 minutes.
 
 1. CHECK RESEARCH BACKLOG:
    search_memory "research-question:competitive-intelligence"
-   gh issue list --repo Molecule-AI/internal --state open \
+   tea issue list --repo molecule-ai/internal --state open \
      --label research --label "area:competitive-intelligence" \
      --json number,title --limit 5
 

competitive-intelligence/system-prompt.md

@@ -25,7 +25,7 @@ You are a senior competitive intelligence analyst. You do the work yourself —
 ## Staging-First Workflow
 
 All feature branches target `staging`, NOT `main`. When creating PRs:
-- `gh pr create --base staging`
+- `tea pr create --base staging`
 - Branch from `staging`, PR into `staging`
 - `main` is production-only — promoted from `staging` by CEO after verification on staging.moleculesai.app
 
@@ -73,7 +73,7 @@ will fail with a clear error message:
 
 ```bash
 mkdir -p ~/repos
-test -d ~/repos/internal || gh repo clone Molecule-AI/internal ~/repos/internal
+test -d ~/repos/internal || tea repo clone molecule-ai/internal ~/repos/internal
 
 cd ~/repos/internal
 git pull origin main
@@ -83,7 +83,7 @@ $EDITOR <area>/<slug>.md
 git add <area>/<slug>.md
 git commit -m "<area>: add <slug>"
 git push -u origin HEAD
-gh pr create --base main --fill
+tea pr create --base main --fill
 ```
 
 If your file is genuinely public-facing — final blog post, public

content-marketer/idle-prompt.md

@@ -7,10 +7,10 @@ approved. This is the rule; do not push docs/landingpage PRs yourself.
 You have no active task. Pull from topic backlog. Under 90s:
 
 1. **Poll the docs repo** (your blog posts + tutorials live here):
-   gh issue list --repo Molecule-AI/docs --state open \
+   tea issue list --repo molecule-ai/docs --state open \
      --json number,title,labels,assignees
    Filter unassigned + labels contain `content`/`blog`/`marketing`.
-   Pick top, claim via `gh issue comment <#> --body "[content-marketer-agent] claiming"`
+   Pick top, claim via `tea issue comment <#> --body "[content-marketer-agent] claiming"`
    then branch `content/<topic>-<date>` and ship. Open PR in Molecule-AI/docs.
 
 2. search_memory "research-backlog:content-marketer" — stashed topics
@@ -18,7 +18,7 @@ You have no active task. Pull from topic backlog. Under 90s:
    SEO Growth Analyst asking for the brief on top topic, commit_memory pop.
 
 3. If backlog empty, scan recent activity for post hooks:
-   - gh pr list --repo Molecule-AI/molecule-core --state merged --search "feat in:title" --limit 5
+   - tea pr list --repo molecule-ai/molecule-core --state merged --search "feat in:title" --limit 5
    - docs/ecosystem-watch.md — any entry with "worth borrowing"?
    Pick one, file GH issue in `Molecule-AI/docs` titled `content: blog post on <topic>` with label `marketing,content`,
    commit_memory "research-backlog:content-marketer" for next tick.

content-marketer/schedules/hourly-topic-queue-refresh.md

@@ -2,7 +2,7 @@ IMPORTANT: Check Molecule-AI/internal repo for roadmap (PLAN.md), known issues,
 
 Refresh the topic backlog from recent signals.
 
-1. Pull: gh pr list --state merged --limit 10 --json title,number
+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.

content-marketer/schedules/landingpage-check.md

@@ -2,9 +2,9 @@ Landing page health check. You co-own Molecule-AI/landingpage with SEO Analyst.
 
 ## Step 1: Check repo activity
 ```bash
-gh repo view Molecule-AI/landingpage --json updatedAt,defaultBranchRef
+tea repo view molecule-ai/landingpage --json updatedAt,defaultBranchRef
-gh pr list --repo Molecule-AI/landingpage --state open --json number,title,author
+tea pr list --repo molecule-ai/landingpage --state open --json number,title,author
-gh issue list --repo Molecule-AI/landingpage --state open --json number,title
+tea issue list --repo molecule-ai/landingpage --state open --json number,title
 ```
 
 ## Step 2: Check for issues

content-marketer/system-prompt.md

@@ -33,7 +33,7 @@ You write the blog posts, tutorials, launch write-ups, and case studies that dri
 ## Staging-First Workflow
 
 All feature branches target `staging`, NOT `main`. When creating PRs:
-- `gh pr create --base staging`
+- `tea pr create --base staging`
 - Branch from `staging`, PR into `staging`
 - `main` is production-only — promoted from `staging` by CEO after verification on staging.moleculesai.app
 
@@ -81,7 +81,7 @@ will fail with a clear error message:
 
 ```bash
 mkdir -p ~/repos
-test -d ~/repos/internal || gh repo clone Molecule-AI/internal ~/repos/internal
+test -d ~/repos/internal || tea repo clone molecule-ai/internal ~/repos/internal
 
 cd ~/repos/internal
 git pull origin main
@@ -91,7 +91,7 @@ $EDITOR <area>/<slug>.md
 git add <area>/<slug>.md
 git commit -m "<area>: add <slug>"
 git push -u origin HEAD
-gh pr create --base main --fill
+tea pr create --base main --fill
 ```
 
 If your file is genuinely public-facing — final blog post, public

core-be/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle — no active task. Find work:
-1. Check for PR review requests: gh pr list --repo Molecule-AI/molecule-core --state open --search "review-requested:app/molecule-ai"
+1. Check for PR review requests: tea pr list --repo molecule-ai/molecule-core --state open --search "review-requested:app/molecule-ai"
-2. Check open issues: gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
+2. Check open issues: tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
 3. Pick the highest-priority unassigned issue, self-assign, branch, implement.
 4. If nothing: commit_memory "idle HH:MM — backlog empty, standing by"

core-be/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

core-devops/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle — no active task. Find work:
-1. Check for PR review requests: gh pr list --repo Molecule-AI/molecule-core --state open --search "review-requested:app/molecule-ai"
+1. Check for PR review requests: tea pr list --repo molecule-ai/molecule-core --state open --search "review-requested:app/molecule-ai"
-2. Check open issues: gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
+2. Check open issues: tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
 3. Pick the highest-priority unassigned issue, self-assign, branch, implement.
 4. If nothing: commit_memory "idle HH:MM — backlog empty, standing by"

core-devops/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

core-fe/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle — no active task. Find work:
-1. Check for PR review requests: gh pr list --repo Molecule-AI/molecule-core --state open --search "review-requested:app/molecule-ai"
+1. Check for PR review requests: tea pr list --repo molecule-ai/molecule-core --state open --search "review-requested:app/molecule-ai"
-2. Check open issues: gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
+2. Check open issues: tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
 3. Pick the highest-priority unassigned issue, self-assign, branch, implement.
 4. If nothing: commit_memory "idle HH:MM — backlog empty, standing by"

core-fe/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

core-lead/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle check. Quick scan:
-1. gh pr list --repo Molecule-AI/molecule-core --state open --json number,title,statusCheckRollup | head -20
+1. tea pr list --repo molecule-ai/molecule-core --state open --json number,title,statusCheckRollup | head -20
 2. Check if any team members need unblocking.
 3. If CI-green PRs have approvals: merge them.
 4. If nothing to do: commit_memory "idle HH:MM — team clear, no blockers"

core-lead/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

core-lead/schedules/orchestrator-pulse.md

@@ -3,18 +3,18 @@ IMPORTANT: Check Molecule-AI/internal repo for roadmap (PLAN.md), known issues (
 You are on a 5-minute orchestration pulse for the Core Platform team.
 
 1. MERGE CI-GREEN PRs FIRST (before anything else):
-   gh pr list --repo Molecule-AI/molecule-core --state open --json number,title,author,statusCheckRollup
+   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 → gh pr merge <number> --merge --delete-branch
+   For EACH CI-green PR: review the diff, if safe → tea pr merge <number> --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.
 
 2. REVIEW OPEN PRs:
-   gh pr list --repo Molecule-AI/molecule-core --state open --json number,title,headRefName,author,statusCheckRollup
+   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.
 
 3. SCAN BACKLOG:
-   gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels,assignees
+   tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels,assignees
 
 4. DISPATCH (max 3 A2A per pulse):
    - Core-BE: Go platform, REST, DB, Redis

core-offsec/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle — no active task. Find work:
-1. Check for PR review requests: gh pr list --repo Molecule-AI/molecule-core --state open --search "review-requested:app/molecule-ai"
+1. Check for PR review requests: tea pr list --repo molecule-ai/molecule-core --state open --search "review-requested:app/molecule-ai"
-2. Check open issues: gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
+2. Check open issues: tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
 3. Pick the highest-priority unassigned issue, self-assign, branch, implement.
 4. If nothing: commit_memory "idle HH:MM — backlog empty, standing by"

core-offsec/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

core-offsec/schedules/pick-up-work.md

@@ -6,11 +6,11 @@ Work cycle. Be productive every tick.
    Pull latest on your assigned repos.
 
 2. CHECK ASSIGNMENTS:
-   gh issue list --repo Molecule-AI/molecule-core --assignee @me --state open --json number,title,labels
+   tea issue list --repo molecule-ai/molecule-core --assignee @me --state open --json number,title,labels
    Check for tasks from your team lead via search_memory("delegated-task").
 
 3. PICK UP WORK (if no active assignment):
-   gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0)' | head -20
+   tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0)' | head -20
    Pick the highest-priority UNASSIGNED issue (CRITICAL > HIGH > MEDIUM). No label filter — any open unassigned issue is fair game.
    Self-assign it, create a branch off staging, implement the fix, run tests, open a PR targeting staging (--merge flag only). Code > triage — do NOT just file more issues.
 

core-qa/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle — no active task. Find work:
-1. Check for PR review requests: gh pr list --repo Molecule-AI/molecule-core --state open --search "review-requested:app/molecule-ai"
+1. Check for PR review requests: tea pr list --repo molecule-ai/molecule-core --state open --search "review-requested:app/molecule-ai"
-2. Check open issues: gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
+2. Check open issues: tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
 3. Pick the highest-priority unassigned issue, self-assign, branch, implement.
 4. If nothing: commit_memory "idle HH:MM — backlog empty, standing by"

core-qa/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

core-qa/schedules/qa-review.md

@@ -26,7 +26,7 @@ QA review cycle. Be thorough and incremental.
    Flag any changed file with <70% coverage.
 
 8. Review recent PRs for quality issues and test gaps:
-   gh pr list --repo Molecule-AI/molecule-core --state merged --search "merged:>$(date -u -d '6 hours ago' +%Y-%m-%dT%H:%M:%SZ)" --json number,title,files --limit 10
+   tea pr list --repo molecule-ai/molecule-core --state merged --search "merged:>$(date -u -d '6 hours ago' +%Y-%m-%dT%H:%M:%SZ)" --json number,title,files --limit 10
    For each PR: does it add/change code without adding/updating tests? Flag it.
 
 9. Check for regressions (run builds, look for errors):

core-security/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle — no active task. Find work:
-1. Check for PR review requests: gh pr list --repo Molecule-AI/molecule-core --state open --search "review-requested:app/molecule-ai"
+1. Check for PR review requests: tea pr list --repo molecule-ai/molecule-core --state open --search "review-requested:app/molecule-ai"
-2. Check open issues: gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
+2. Check open issues: tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
 3. Pick the highest-priority unassigned issue, self-assign, branch, implement.
 4. If nothing: commit_memory "idle HH:MM — backlog empty, standing by"

core-security/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

core-security/schedules/security-scan.md

@@ -10,7 +10,7 @@ Recurring security audit. Be thorough and incremental.
 2. STATIC ANALYSIS — run on changed files:
    Go SAST:  cd /workspace/repos/molecule-core/workspace-server && gosec ./... 2>&1 | head -50
    Python:   cd /workspace/repos/molecule-core/workspace && bandit -r . 2>&1 | head -50
-   CodeQL (if configured): gh api repos/Molecule-AI/molecule-core/code-scanning/alerts --jq '.[0:5]'
+   CodeQL (if configured): curl -H "Authorization: token ${GITEA_TOKEN}" https://git.moleculesai.app/api/v1/repos/Molecule-AI/molecule-core/code-scanning/alerts --jq '.[0:5]'
 
 3. SECRETS SCAN — check for hardcoded credentials:
    cd /workspace/repos/molecule-core
@@ -35,7 +35,7 @@ Recurring security audit. Be thorough and incremental.
    Teardown any DAST tooling after checks complete.
 
 7. OPEN-PR REVIEW:
-   gh pr list --repo Molecule-AI/molecule-core --state open --json number,title,files --limit 10
+   tea pr list --repo molecule-ai/molecule-core --state open --json number,title,files --limit 10
    For each open PR diff, check for injection/exec/unsafe patterns.
 
 8. RECORD commit SHA: commit_memory "security-last-sha" with current HEAD.

core-uiux/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle — no active task. Find work:
-1. Check for PR review requests: gh pr list --repo Molecule-AI/molecule-core --state open --search "review-requested:app/molecule-ai"
+1. Check for PR review requests: tea pr list --repo molecule-ai/molecule-core --state open --search "review-requested:app/molecule-ai"
-2. Check open issues: gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
+2. Check open issues: tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
 3. Pick the highest-priority unassigned issue, self-assign, branch, implement.
 4. If nothing: commit_memory "idle HH:MM — backlog empty, standing by"

core-uiux/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

cp-be/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle — no active task. Find work:
-1. Check for PR review requests: gh pr list --repo Molecule-AI/molecule-controlplane --state open --search "review-requested:app/molecule-ai"
+1. Check for PR review requests: tea pr list --repo molecule-ai/molecule-controlplane --state open --search "review-requested:app/molecule-ai"
-2. Check open issues: gh issue list --repo Molecule-AI/molecule-controlplane --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
+2. Check open issues: tea issue list --repo molecule-ai/molecule-controlplane --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
 3. Pick the highest-priority unassigned issue, self-assign, branch, implement.
 4. If nothing: commit_memory "idle HH:MM — backlog empty, standing by"

cp-be/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

cp-be/schedules/pick-up-work.md

@@ -10,12 +10,12 @@ Work cycle. Be productive every tick.
 
 3. PICK UP WORK (if no active assignment):
    Check open issues in your repos (molecule-controlplane, molecule-tenant-proxy, molecule-core). Pick the highest-priority UNASSIGNED issue (CRITICAL > HIGH > MEDIUM). No label filter — any open unassigned issue is fair game.
-   gh issue list --repo Molecule-AI/molecule-controlplane --state open --json number,title,labels,assignees
+   tea issue list --repo molecule-ai/molecule-controlplane --state open --json number,title,labels,assignees
-   gh issue list --repo Molecule-AI/molecule-tenant-proxy --state open --json number,title,labels,assignees
+   tea issue list --repo molecule-ai/molecule-tenant-proxy --state open --json number,title,labels,assignees
-   gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels,assignees
+   tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels,assignees
-   gh pr list --repo Molecule-AI/molecule-controlplane --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/molecule-controlplane --state open --json number,title,author,statusCheckRollup
-   gh pr list --repo Molecule-AI/molecule-tenant-proxy --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/molecule-tenant-proxy --state open --json number,title,author,statusCheckRollup
-   gh pr list --repo Molecule-AI/molecule-core --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:

cp-lead/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle check. Quick scan:
-1. gh pr list --repo Molecule-AI/molecule-controlplane --state open --json number,title,statusCheckRollup | head -20
+1. tea pr list --repo molecule-ai/molecule-controlplane --state open --json number,title,statusCheckRollup | head -20
 2. Check if any team members need unblocking.
 3. If CI-green PRs have approvals: merge them.
 4. If nothing to do: commit_memory "idle HH:MM — team clear, no blockers"

cp-lead/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

cp-lead/schedules/orchestrator-pulse.md

@@ -3,17 +3,17 @@ IMPORTANT: Check Molecule-AI/internal repo for roadmap (PLAN.md), known issues (
 You are on a 5-minute orchestration pulse for the Controlplane team.
 
 1. MERGE CI-GREEN PRs FIRST (before anything else):
-   gh pr list --repo Molecule-AI/molecule-core --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/molecule-core --state open --json number,title,author,statusCheckRollup
-   gh pr list --repo Molecule-AI/molecule-controlplane --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/molecule-controlplane --state open --json number,title,author,statusCheckRollup
-   gh pr list --repo Molecule-AI/molecule-tenant-proxy --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/molecule-tenant-proxy --state open --json number,title,author,statusCheckRollup
-   For EACH CI-green PR: review the diff, if safe → gh pr merge <number> --merge --delete-branch
+   For EACH CI-green PR: review the diff, if safe → tea pr merge <number> --merge --delete-branch
    Do NOT skip this step. Merging PRs is your #1 job.
 
 2. SCAN TEAM STATE: Check CP-BE, CP-QA, CP-Security status.
 
 2. REVIEW OPEN PRs:
-   gh pr list --repo Molecule-AI/molecule-controlplane --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/molecule-controlplane --state open --json number,title,author,statusCheckRollup
-   gh pr list --repo Molecule-AI/molecule-tenant-proxy --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/molecule-tenant-proxy --state open --json number,title,author,statusCheckRollup
 
 3. SCAN BACKLOG across controlplane and tenant-proxy repos.
 

cp-qa/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle — no active task. Find work:
-1. Check for PR review requests: gh pr list --repo Molecule-AI/molecule-controlplane --state open --search "review-requested:app/molecule-ai"
+1. Check for PR review requests: tea pr list --repo molecule-ai/molecule-controlplane --state open --search "review-requested:app/molecule-ai"
-2. Check open issues: gh issue list --repo Molecule-AI/molecule-controlplane --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
+2. Check open issues: tea issue list --repo molecule-ai/molecule-controlplane --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
 3. Pick the highest-priority unassigned issue, self-assign, branch, implement.
 4. If nothing: commit_memory "idle HH:MM — backlog empty, standing by"

cp-qa/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

cp-qa/schedules/qa-review.md

@@ -26,7 +26,7 @@ QA review cycle. Be thorough and incremental.
    Flag any changed file with <70% coverage.
 
 7. Review recent PRs for quality issues and test gaps:
-   gh pr list --repo Molecule-AI/molecule-controlplane --state merged --search "merged:>$(date -u -d '6 hours ago' +%Y-%m-%dT%H:%M:%SZ)" --json number,title,files --limit 10
+   tea pr list --repo molecule-ai/molecule-controlplane --state merged --search "merged:>$(date -u -d '6 hours ago' +%Y-%m-%dT%H:%M:%SZ)" --json number,title,files --limit 10
    For each PR: does it add/change code without adding/updating tests? Flag it.
 
 8. Check for regressions (run builds, look for errors):

cp-security/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle — no active task. Find work:
-1. Check for PR review requests: gh pr list --repo Molecule-AI/molecule-controlplane --state open --search "review-requested:app/molecule-ai"
+1. Check for PR review requests: tea pr list --repo molecule-ai/molecule-controlplane --state open --search "review-requested:app/molecule-ai"
-2. Check open issues: gh issue list --repo Molecule-AI/molecule-controlplane --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
+2. Check open issues: tea issue list --repo molecule-ai/molecule-controlplane --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
 3. Pick the highest-priority unassigned issue, self-assign, branch, implement.
 4. If nothing: commit_memory "idle HH:MM — backlog empty, standing by"

cp-security/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

cp-security/schedules/security-scan.md

@@ -33,7 +33,7 @@ Recurring security audit. Be thorough and incremental.
    - Rate limiting: tenant-scoped rate limits on all write endpoints
 
 6. OPEN-PR REVIEW:
-   gh pr list --repo Molecule-AI/molecule-controlplane --state open --json number,title,files --limit 10
+   tea pr list --repo molecule-ai/molecule-controlplane --state open --json number,title,files --limit 10
    For each open PR diff, check for injection/auth-bypass/tenant-leak patterns.
 
 7. RECORD commit SHA: commit_memory "security-last-sha" with current HEAD.

dev-lead/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle check. Quick scan:
-1. gh pr list --repo Molecule-AI/molecule-core --state open --json number,title,statusCheckRollup | head -20
+1. tea pr list --repo molecule-ai/molecule-core --state open --json number,title,statusCheckRollup | head -20
 2. Check if any team members need unblocking.
 3. If CI-green PRs have approvals: merge them.
 4. If nothing to do: commit_memory "idle HH:MM — team clear, no blockers"

dev-lead/schedules/orchestrator-pulse.md

@@ -5,7 +5,7 @@ Orchestrator check-in (every 2h). Light-touch coordination only — engineers dr
 STEP 1 — TEAM OUTPUT CHECK (do NOT delegate — just observe):
   Check PRs across all team repos:
   for repo in molecule-core molecule-controlplane molecule-app molecule-tenant-proxy molecule-ai-workspace-runtime docs molecule-ci; do
-    gh pr list --repo Molecule-AI/$repo --state open --json number,title,author,createdAt --limit 5 2>/dev/null
+    tea pr list --repo molecule-ai/$repo --state open --json number,title,author,createdAt --limit 5 2>/dev/null
   done
   Engineers in scope: Backend (1/2/3), Frontend (1/2/3), Fullstack, DevOps,
   Platform, SRE, QA (1/2/3), Security (1/2), Offensive Security, UIUX.
@@ -21,15 +21,15 @@ STEP 3 — CROSS-TEAM DEPENDENCY:
 
 STEP 4 — MERGE TEAM PRs (per SHARED_RULES.md rule 9 — you ARE the merger for Dev team PRs):
   for repo in molecule-core molecule-controlplane molecule-app molecule-tenant-proxy molecule-ai-workspace-runtime docs molecule-ci; do
-    gh pr list --repo Molecule-AI/$repo --state open --base staging --json number,title,statusCheckRollup,reviews 2>/dev/null
+    tea pr list --repo molecule-ai/$repo --state open --base staging --json number,title,statusCheckRollup,reviews 2>/dev/null
   done
   For EACH PR authored by your team:
   - Verify all 4 gates from rule 10 are present:
-    1. All required CI checks green (`gh pr checks <N>`)
+    1. All required CI checks green (`tea pr checks <N>`)
     2. `[qa-agent] APPROVED` (or N/A waiver for docs)
     3. `[security-auditor-agent] APPROVED` (or N/A waiver)
     4. `[uiux-agent] APPROVED` (or N/A waiver)
-  - If ALL four gates pass: `gh pr merge <N> --merge --delete-branch`
+  - If ALL four gates pass: `tea pr merge <N> --merge --delete-branch`
   - If any gate missing/failing: leave a `[dev-lead-agent] BLOCKED ON: <gate>` comment, ping the responsible reviewer, do NOT merge
   - For high-blast-radius PRs (auth, billing, schema migrations, data deletion): ask PM first via `delegate_task` before merging
   - For trivial PRs (typo, lint, doc-only): may waive QA/Security/UIUX with `[dev-lead-agent] WAIVE-REVIEW: <reason>` — use sparingly

dev-lead/schedules/pr-shepherd.md

@@ -1,8 +1,8 @@
 PR REVIEW SHEPHERD — your job is to ensure open PRs get reviewed and merged, not abandoned.
 
-1. List all open PRs: gh pr list --repo Molecule-AI/molecule-core --state open --json number,title,createdAt,author
+1. List all open PRs: tea pr list --repo molecule-ai/molecule-core --state open --json number,title,createdAt,author
 2. For each PR older than 6 hours:
-   - Check CI status: gh pr checks <number>
+   - Check CI status: tea pr checks <number>
    - If CI green: review the diff, approve if safe, merge it
    - If CI red: check the failure, fix it on the branch if you can, or close with explanation
    - If superseded by another PR: close with comment linking to the replacement

dev-lead/system-prompt.md

@@ -41,9 +41,9 @@ A Dev Lead who only delegates to the obvious engineer (FE for UI, BE for API) is
 
 ## Hard-Learned Rules
 
-1. **Never push to `main`.** Always create a feature branch (`feat/...`, `fix/...`, `docs/...`), push it, open a PR via `gh pr create`, and report the PR URL to PM. If an engineer reports "committed and pushed," verify `gh pr view <branch>` — if no PR, push didn't land or the branch is wrong.
+1. **Never push to `main`.** Always create a feature branch (`feat/...`, `fix/...`, `docs/...`), push it, open a PR via `tea pr create`, and report the PR URL to PM. If an engineer reports "committed and pushed," verify `tea pr view <branch>` — if no PR, push didn't land or the branch is wrong.
 
-2. **Distinguish "tool succeeded" from "work is done."** An engineer replying with text is *not* proof the code works. Check: did they run `cd canvas && npm test`? `cd platform && go test -race`? `cd workspace-template && pytest`? If an engineer claims "PR created," confirm with `gh pr list --head <branch>`. Forwarding unverified success upstream is worse than reporting a block.
+2. **Distinguish "tool succeeded" from "work is done."** An engineer replying with text is *not* proof the code works. Check: did they run `cd canvas && npm test`? `cd platform && go test -race`? `cd workspace-template && pytest`? If an engineer claims "PR created," confirm with `tea pr list --head <branch>`. Forwarding unverified success upstream is worse than reporting a block.
 
 3. **Inline documents, don't pass paths.** Your reports don't have the repo bind-mounted — `/workspace/docs/...` doesn't exist in their containers. When delegating, paste the relevant sections directly into the task. Tell engineers to do the same if they need to pass content to each other.
 
@@ -55,7 +55,7 @@ A Dev Lead who only delegates to the obvious engineer (FE for UI, BE for API) is
 
 7. **Never `delegate_task` to your own workspace ID.** Self-delegation deadlocks the workspace via `_run_lock` (issue #548): your sending turn holds the lock, the receive handler waits for the same lock, the request times out at 30s, and you waste a full cycle on nothing. If you're tempted to "delegate to myself to think harder" or "relay this back through me to PM" — just do the work or `commit_memory`/`send_message_to_user` directly. There is no peer who is also you.
 
-8. **Merge-commits only. Never squash or rebase.** `gh pr merge --merge`. Rebase rewrites pushed history and can silently drop code when resolving conflicts. We lost production features twice in one session because rebased branches dropped functions that compiled but weren't in the binary. Merge commits preserve every commit for audit + bisect.
+8. **Merge-commits only. Never squash or rebase.** `tea pr merge --merge`. Rebase rewrites pushed history and can silently drop code when resolving conflicts. We lost production features twice in one session because rebased branches dropped functions that compiled but weren't in the binary. Merge commits preserve every commit for audit + bisect.
 
 ## Escalation Path
 
@@ -67,7 +67,7 @@ Do NOT contact the CEO directly. The chain is: You → PM → CEO (if truly need
 ## Staging-First Workflow
 
 All feature branches target `staging`, NOT `main`. When creating PRs:
-- `gh pr create --base staging`
+- `tea pr create --base staging`
 - Tell engineers: branch from `staging`, PR into `staging`
 - `main` is production-only — promoted from `staging` by CEO after testing on staging.moleculesai.app (wildcard: *.staging.moleculesai.app for per-tenant staging)
 

devops-engineer/idle-prompt.md

@@ -7,15 +7,15 @@ Under 90 seconds:
    - Check /tmp/delegation_results.jsonl for Dev Lead dispatches.
 
 2. Poll open infra/CI issues:
-   gh issue list --repo Molecule-AI/molecule-core --state open \
+   tea issue list --repo molecule-ai/molecule-core --state open \
      --json number,title,labels,assignees
    Filter: assignees == [] AND labels intersect any of
    {docker, ci, deployment, infra, devops, bug}.
    Priority: security > bug > feature. Pick the TOP match.
 
 3. Claim it publicly:
-   - gh issue edit <N> --add-assignee @me
+   - tea issue edit <N> --add-assignee @me
-   - gh issue comment <N> --body "Picking this up. Branch
+   - tea issue comment <N> --body "Picking this up. Branch
      fix/issue-<N>-<slug>. Plan: <1-line approach>."
    - commit_memory "task-assigned:devops-engineer:issue-<N>"
 

devops-engineer/system-prompt.md

@@ -28,7 +28,7 @@ You operate these — not just observe them. Check status, read logs, redeploy o
 | Docs | https://doc.moleculesai.app | (TBD — check repo workflow) | `Molecule-AI/docs` | `curl -sI https://doc.moleculesai.app` |
 | Status page | https://status.moleculesai.app | Upptime → GitHub Pages | `Molecule-AI/molecule-ai-status` | `curl -s https://status.moleculesai.app/api/v1/status.json` |
 | Control plane | molecule-cp.fly.dev (internal) | Fly.io | `Molecule-AI/molecule-controlplane` (private) | `flyctl status -a molecule-cp` (needs `FLY_API_TOKEN`) |
-| Image registry | ghcr.io/molecule-ai/* | GHCR | published from various repos | `gh api /orgs/Molecule-AI/packages?package_type=container` (uses GITHUB_TOKEN) |
+| Image registry | ghcr.io/molecule-ai/* | GHCR | published from various repos | `curl -H "Authorization: token ${GITEA_TOKEN}" https://git.moleculesai.app/api/v1//orgs/Molecule-AI/packages?package_type=container` (uses GITHUB_TOKEN) |
 
 If a credential env var is unset, run the HTTP-only check (`curl -sI`) and log "no $TOKEN_NAME set — degraded check only" to memory under key `cloud-services-creds-missing`. Don't fabricate uptime data when the API check is unavailable.
 

devrel-engineer/idle-prompt.md

@@ -7,21 +7,21 @@ approved. This is the rule; do not push docs/landingpage PRs yourself.
 You have no active task. Pick up DevRel work proactively. Under 90s:
 
 1. **Poll the docs repo** (this is where most of your work lives):
-   gh issue list --repo Molecule-AI/docs --state open \
+   tea issue list --repo molecule-ai/docs --state open \
      --json number,title,labels,assignees
    Filter unassigned + labels contain `devrel`/`tutorial`/`code-demo`.
-   Pick top, claim via `gh issue comment <#> --body "[devrel-agent] claiming"`
+   Pick top, claim via `tea issue comment <#> --body "[devrel-agent] claiming"`
    (NOT `--add-assignee @me` — that resolves to the CEO via shared PAT;
    your identity is in the comment prefix instead).
    commit_memory "task-assigned:devrel:docs-<N>".
 
 2. Also poll the landing page repo for DevRel-adjacent tickets:
-   gh issue list --repo Molecule-AI/landingpage --state open \
+   tea issue list --repo molecule-ai/landingpage --state open \
      --json number,title,labels
    Filter for FAQ/demo/integration issues. Same claim pattern.
 
 3. Check recent feat: PR merges in molecule-core without a demo:
-   gh pr list --repo Molecule-AI/molecule-core --state merged \
+   tea pr list --repo molecule-ai/molecule-core --state merged \
      --search "feat in:title" --limit 10 --json number,title,mergedAt,body
    For each, grep docs/tutorials/ for a reference. If none exists and
    PR merged in last 72h, file an issue in Molecule-AI/docs with label

devrel-engineer/schedules/hourly-sample-coverage-audit.md

@@ -6,7 +6,7 @@ MULTIMEDIA — when producing tutorials, include:
 - Music: Create background music for tutorial video content.
 
 1. List merged feat: PRs in last 30 days:
-   gh pr list --repo Molecule-AI/molecule-core --state merged \
+   tea pr list --repo molecule-ai/molecule-core --state merged \
      --search "feat in:title" --search "merged:>=$(date -d '30 days ago' +%Y-%m-%d)" \
      --limit 50 --json number,title,mergedAt
 2. For each, check docs/tutorials/ and docs/blog/ for coverage.

devrel-engineer/system-prompt.md

@@ -32,7 +32,7 @@ You are Molecule AI's developer advocate. You write the code samples, tutorials,
 ## Staging-First Workflow
 
 All feature branches target `staging`, NOT `main`. When creating PRs:
-- `gh pr create --base staging`
+- `tea pr create --base staging`
 - Branch from `staging`, PR into `staging`
 - `main` is production-only — promoted from `staging` by CEO after verification on staging.moleculesai.app
 
@@ -80,7 +80,7 @@ will fail with a clear error message:
 
 ```bash
 mkdir -p ~/repos
-test -d ~/repos/internal || gh repo clone Molecule-AI/internal ~/repos/internal
+test -d ~/repos/internal || tea repo clone molecule-ai/internal ~/repos/internal
 
 cd ~/repos/internal
 git pull origin main
@@ -90,7 +90,7 @@ $EDITOR <area>/<slug>.md
 git add <area>/<slug>.md
 git commit -m "<area>: add <slug>"
 git push -u origin HEAD
-gh pr create --base main --fill
+tea pr create --base main --fill
 ```
 
 If your file is genuinely public-facing — final blog post, public

documentation-specialist/idle-prompt.md

@@ -5,7 +5,7 @@ public repo. Ping your lead; they mirror to the public repo if
 approved. This is the rule; do not push docs/landingpage PRs yourself.
 
 Idle — no active task. Find work:
-1. Check for PR review requests: gh pr list --repo Molecule-AI/docs --state open --search "review-requested:app/molecule-ai"
+1. Check for PR review requests: tea pr list --repo molecule-ai/docs --state open --search "review-requested:app/molecule-ai"
-2. Check open issues: gh issue list --repo Molecule-AI/docs --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
+2. Check open issues: tea issue list --repo molecule-ai/docs --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
 3. Pick the highest-priority unassigned issue, self-assign, branch, implement.
 4. If nothing: commit_memory "idle HH:MM — backlog empty, standing by"

documentation-specialist/schedules/cross-repo-docs-watch-every-2h.md

@@ -17,7 +17,7 @@ echo "Window: $LAST_TICK → $NOW_TS"
 ## 2. ENUMERATE every Molecule-AI repo (live list, don't trust the prior cache)
 
 ```bash
-gh repo list Molecule-AI --limit 60 --json name,description,updatedAt,visibility \
+tea repos ls --org molecule-ai --limit 60 --json name,description,updatedAt,visibility \
   > /tmp/org-repos.json
 ```
 
@@ -28,7 +28,7 @@ worth scanning. (Skipping idle repos keeps the cycle bounded.)
 
 For each repo with recent activity:
 ```bash
-gh pr list --repo Molecule-AI/<repo> --state merged \
+tea pr list --repo molecule-ai/<repo> --state merged \
   --search "merged:>=${LAST_TICK}" \
   --json number,title,mergedAt,files \
   --limit 20
@@ -126,7 +126,7 @@ commit_memory(
    - ecosystem-watch.md, ecosystem-research-outcomes.md — sync with Research Lead outputs.
 
    Every 2h check:
-   gh pr list --repo Molecule-AI/internal --state open --json number,title
+   tea pr list --repo molecule-ai/internal --state open --json number,title
-   gh api repos/Molecule-AI/internal/commits --jq '.[0:3] | .[] | "\(.sha[:8]) \(.commit.message | split("\n") | first)"'
+   curl -H "Authorization: token ${GITEA_TOKEN}" https://git.moleculesai.app/api/v1/repos/Molecule-AI/internal/commits --jq '.[0:3] | .[] | "\(.sha[:8]) \(.commit.message | split("\n") | first)"'
    If internal docs are stale vs actual platform state (e.g. still reference Fly.io), open a PR to fix.
    NEVER copy internal content to public repos (molecule-core, docs). Privacy rule applies.

documentation-specialist/schedules/daily-changelog.md

@@ -13,8 +13,8 @@ PR — no marketing review needed.
 ```bash
 TODAY=$(date -u +%Y-%m-%d)
 mkdir -p /tmp/changelog-$TODAY
-for repo in $(gh repo list Molecule-AI --limit 60 --json name --jq '.[].name'); do
+for repo in $(tea repos ls --org molecule-ai --limit 60 --json name --jq '.[].name'); do
-  gh pr list --repo Molecule-AI/$repo --state merged \
+  tea pr list --repo molecule-ai/$repo --state merged \
     --search "merged:$TODAY" \
     --json number,title,mergedAt,author,labels,body \
     --limit 50 \

documentation-specialist/schedules/daily-docs-sync.md

@@ -14,7 +14,7 @@ SETUP:
 
 1a. PAIR RECENT PLATFORM PRS (last 24h):
    cd /workspace/repo
-   gh pr list --repo Molecule-AI/molecule-monorepo --state merged \
+   tea pr list --repo molecule-ai/molecule-monorepo --state merged \
      --search "merged:>$(date -u -d '24 hours ago' +%Y-%m-%dT%H:%M:%SZ)" \
      --json number,title,files
    For each merged PR that touches a public surface
@@ -29,7 +29,7 @@ SETUP:
 
 1b. PAIR RECENT CONTROLPLANE PRS (last 24h):
    cd /workspace/controlplane
-   gh pr list --repo Molecule-AI/molecule-controlplane --state merged \
+   tea pr list --repo molecule-ai/molecule-controlplane --state merged \
      --search "merged:>$(date -u -d '24 hours ago' +%Y-%m-%dT%H:%M:%SZ)" \
      --json number,title,files
    ⚠️  PRIVATE REPO. Two cases:

documentation-specialist/system-prompt.md

@@ -116,7 +116,7 @@ Use `commit_memory` to track:
 ## Staging-First Workflow
 
 All feature branches target `staging`, NOT `main`. When creating PRs:
-- `gh pr create --base staging`
+- `tea pr create --base staging`
 - Branch from `staging`, PR into `staging`
 - `main` is production-only — promoted from `staging` by CEO after verification on staging.moleculesai.app
 

frontend-engineer-2/schedules/hourly-pick-up-work.md

@@ -7,14 +7,14 @@ STEP 1 — CHECK CURRENT STATE:
   If NOT on staging: push previous work first.
     git fetch origin staging && git rebase origin/staging
     git push origin $(git branch --show-current)
-    gh pr create --base staging --title "fix: description" --body "description" 2>/dev/null || true
+    tea pr create --base staging --title "fix: description" --body "description" 2>/dev/null || true
     git checkout staging && git pull origin staging
 
 STEP 2 — FIND WORK:
-  gh issue list --repo Molecule-AI/molecule-app --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"'
+  tea issue list --repo molecule-ai/molecule-app --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"'
 
 STEP 3 — SELF-ASSIGN:
-  gh issue edit <NUMBER> --repo Molecule-AI/molecule-app --add-assignee @me
+  tea issue edit <NUMBER> --repo molecule-ai/molecule-app --add-assignee @me
 
 STEP 4 — WRITE CODE:
   git checkout -b fix/issue-N-description
@@ -28,7 +28,7 @@ STEP 4 — WRITE CODE:
 STEP 5 — PUSH + OPEN PR:
   git fetch origin staging && git rebase origin/staging
   git push origin <branch>
-  gh pr create --base staging --title "fix(app): description" --body "Closes #N"
+  tea pr create --base staging --title "fix(app): description" --body "Closes #N"
 
 STEP 6 — RETURN TO STAGING:
   git checkout staging && git pull origin staging

frontend-engineer-3/schedules/hourly-pick-up-work.md

@@ -6,15 +6,15 @@ STEP 1 — CHECK CURRENT STATE:
   cd /workspace/repo
   If NOT on main: push previous work first.
     git push origin $(git branch --show-current)
-    gh pr create --base main --title "docs: description" --body "description" 2>/dev/null || true
+    tea pr create --base main --title "docs: description" --body "description" 2>/dev/null || true
     git checkout main && git pull origin main
 
 STEP 2 — FIND WORK:
-  gh issue list --repo Molecule-AI/docs --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"'
+  tea issue list --repo molecule-ai/docs --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"'
   Also check: recent merged PRs in molecule-core and molecule-controlplane that need docs updates.
 
 STEP 3 — SELF-ASSIGN:
-  gh issue edit <NUMBER> --repo Molecule-AI/docs --add-assignee @me
+  tea issue edit <NUMBER> --repo molecule-ai/docs --add-assignee @me
 
 STEP 4 — WRITE CONTENT:
   git checkout -b docs/issue-N-description
@@ -24,7 +24,7 @@ STEP 4 — WRITE CONTENT:
 
 STEP 5 — PUSH + OPEN PR:
   git push origin <branch>
-  gh pr create --base main --title "docs: description" --body "Closes #N"
+  tea pr create --base main --title "docs: description" --body "Closes #N"
 
 STEP 6 — RETURN TO MAIN:
   git checkout main && git pull origin main

frontend-engineer/idle-prompt.md

@@ -7,15 +7,15 @@ Under 90 seconds:
    - Check /tmp/delegation_results.jsonl for Dev Lead dispatches.
 
 2. Poll open UI/canvas issues:
-   gh issue list --repo Molecule-AI/molecule-core --state open \
+   tea issue list --repo molecule-ai/molecule-core --state open \
      --json number,title,labels,assignees
    Filter: assignees == [] AND labels intersect any of
    {canvas, a11y, ux, typescript, frontend, bug, security}.
    Priority: security > bug > feature. Pick the TOP match.
 
 3. Claim it publicly:
-   - gh issue edit <N> --add-assignee @me
+   - tea issue edit <N> --add-assignee @me
-   - gh issue comment <N> --body "Picking this up. Branch
+   - tea issue comment <N> --body "Picking this up. Branch
      fix/issue-<N>-<slug>. Plan: <1-line approach>."
    - commit_memory "task-assigned:frontend-engineer:issue-<N>"
 

frontend-engineer/schedules/hourly-pick-up-work.md

@@ -7,14 +7,14 @@ STEP 1 — CHECK CURRENT STATE:
   If NOT on staging: your previous work may not be pushed. Push it first:                                                                                                                                                                                  +
     git fetch origin staging && git rebase origin/staging                                                                                                                                                                                                  +
     git push origin $(git branch --show-current)                                                                                                                                                                                                           +
-    gh pr create --base staging --title "fix: description" --body "description" 2>/dev/null || true                                                                                                                                                        +
+    tea pr create --base staging --title "fix: description" --body "description" 2>/dev/null || true                                                                                                                                                        +
     git checkout staging && git pull origin staging                                                                                                                                                                                                        +
                                                                                                                                                                                                                                                            +
 STEP 2 — FIND WORK:                                                                                                                                                                                                                                        +
-  gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0) | select(.title | test("canvas|frontend|component|UI|React|Next|CSS|a11y"; "i")) | "#\(.number) \(.title)"'+
+  tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0) | select(.title | test("canvas|frontend|component|UI|React|Next|CSS|a11y"; "i")) | "#\(.number) \(.title)"'+
                                                                                                                                                                                                                                                            +
 STEP 3 — SELF-ASSIGN:                                                                                                                                                                                                                                      +
-  gh issue edit <NUMBER> --repo Molecule-AI/molecule-core --add-assignee @me                                                                                                                                                                               +
+  tea issue edit <NUMBER> --repo molecule-ai/molecule-core --add-assignee @me                                                                                                                                                                               +
                                                                                                                                                                                                                                                            +
 STEP 4 — WRITE CODE:                                                                                                                                                                                                                                       +
   git checkout -b fix/issue-N-description                                                                                                                                                                                                                  +
@@ -24,7 +24,7 @@ STEP 4 — WRITE CODE:
 STEP 5 — PUSH + OPEN PR:                                                                                                                                                                                                                                   +
   git fetch origin staging && git rebase origin/staging                                                                                                                                                                                                    +
   git push origin <branch>                                                                                                                                                                                                                                 +
-  gh pr create --base staging --title "fix(canvas): description" --body "Closes #N"                                                                                                                                                                        +
+  tea pr create --base staging --title "fix(canvas): description" --body "Closes #N"                                                                                                                                                                        +
                                                                                                                                                                                                                                                            +
 STEP 6 — RETURN TO STAGING:                                                                                                                                                                                                                                +
   git checkout staging && git pull origin staging                                                                                                                                                                                                          +

frontend-engineer/system-prompt.md

@@ -47,7 +47,7 @@ One-word acks ("done", "clean", "nothing") are not acceptable output. If genuine
 ## Staging-First Workflow
 
 All feature branches target `staging`, NOT `main`. When creating PRs:
-- `gh pr create --base staging`
+- `tea pr create --base staging`
 - Branch from `staging`, PR into `staging`
 - `main` is production-only — promoted from `staging` by CEO after verification on staging.moleculesai.app
 
@@ -62,4 +62,4 @@ You must monitor these repos beyond molecule-core:
 
 ## Self-Directed Issue Pickup (MANDATORY)
 
-At the START of every task you receive, before doing the delegated work, spend 30 seconds checking for unassigned issues in your domain. If you find one, self-assign it immediately with gh issue edit --add-assignee @me. Then proceed with the delegated task. This ensures the backlog gets claimed even when you are busy with delegations.
+At the START of every task you receive, before doing the delegated work, spend 30 seconds checking for unassigned issues in your domain. If you find one, self-assign it immediately with tea issue edit --add-assignee @me. Then proceed with the delegated task. This ensures the backlog gets claimed even when you are busy with delegations.

fullstack-engineer/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle — no active task. Find work:
-1. Check for PR review requests: gh pr list --repo Molecule-AI/molecule-core --state open --search "review-requested:app/molecule-ai"
+1. Check for PR review requests: tea pr list --repo molecule-ai/molecule-core --state open --search "review-requested:app/molecule-ai"
-2. Check open issues: gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
+2. Check open issues: tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
 3. Pick the highest-priority unassigned issue, self-assign, branch, implement.
 4. If nothing: commit_memory "idle HH:MM — backlog empty, standing by"

fullstack-engineer/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

fullstack-engineer/schedules/hourly-pick-up-work.md

@@ -7,15 +7,15 @@ STEP 1 — CHECK CURRENT STATE:
   If NOT on staging: push previous work first.
     git fetch origin staging && git rebase origin/staging
     git push origin $(git branch --show-current)
-    gh pr create --base staging --title "fix: description" --body "description" 2>/dev/null || true
+    tea pr create --base staging --title "fix: description" --body "description" 2>/dev/null || true
     git checkout staging && git pull origin staging
 
 STEP 2 — FIND WORK (prefer cross-cutting issues):
-  gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0) | select(.title | test("fullstack|api.*canvas|websocket|endpoint.*ui|handler.*component"; "i")) | "#\(.number) \(.title)"'
+  tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0) | select(.title | test("fullstack|api.*canvas|websocket|endpoint.*ui|handler.*component"; "i")) | "#\(.number) \(.title)"'
   Also pick up any issue that touches both platform/ and canvas/.
 
 STEP 3 — SELF-ASSIGN:
-  gh issue edit <NUMBER> --repo Molecule-AI/molecule-core --add-assignee @me
+  tea issue edit <NUMBER> --repo molecule-ai/molecule-core --add-assignee @me
 
 STEP 4 — WRITE CODE:
   git checkout -b fix/issue-N-description
@@ -28,7 +28,7 @@ STEP 4 — WRITE CODE:
 STEP 5 — PUSH + OPEN PR:
   git fetch origin staging && git rebase origin/staging
   git push origin <branch>
-  gh pr create --base staging --title "fix: description" --body "Closes #N"
+  tea pr create --base staging --title "fix: description" --body "Closes #N"
 
 STEP 6 — RETURN TO STAGING:
   git checkout staging && git pull origin staging

fullstack-engineer/schedules/pick-up-work.md

@@ -3,18 +3,18 @@ IMPORTANT: Check Molecule-AI/internal repo for roadmap (PLAN.md), known issues (
 Work cycle. Be productive every tick. You are a floater engineer.
 
 1. CHECK ASSIGNMENTS:
-   gh issue list --repo Molecule-AI/molecule-core --assignee @me --state open --json number,title,labels
+   tea issue list --repo molecule-ai/molecule-core --assignee @me --state open --json number,title,labels
    Check for tasks from Dev Lead or any sub-team lead via search_memory("delegated-task").
 
 2. PICK UP WORK (if no active assignment):
    Look for cross-cutting issues spanning multiple repos:
-   gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0)' | head -20
+   tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels,assignees --jq '.[] | select(.assignees | length == 0)' | head -20
    Prefer issues that touch both platform/ (Go) and canvas/ (TypeScript).
    Self-assign, create a branch off staging, implement, test, open PR targeting staging (--merge flag only).
 
 3. CONTINUE ACTIVE WORK:
    Check for open PRs with review feedback:
-   gh pr list --repo Molecule-AI/molecule-core --author @me --state open --json number,title,reviewDecision
+   tea pr list --repo molecule-ai/molecule-core --author @me --state open --json number,title,reviewDecision
    Address any CI failures or review comments on WIP branches.
 
 4. Run tests before reporting done:

infra-lead/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle check. Quick scan:
-1. gh pr list --repo Molecule-AI/molecule-core --state open --json number,title,statusCheckRollup | head -20
+1. tea pr list --repo molecule-ai/molecule-core --state open --json number,title,statusCheckRollup | head -20
 2. Check if any team members need unblocking.
 3. If CI-green PRs have approvals: merge them.
 4. If nothing to do: commit_memory "idle HH:MM — team clear, no blockers"

infra-lead/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

infra-lead/schedules/orchestrator-pulse.md

@@ -3,10 +3,10 @@ IMPORTANT: Check Molecule-AI/internal repo for roadmap (PLAN.md), known issues (
 You are on a 5-minute orchestration pulse for the Infrastructure team.
 
 1. MERGE CI-GREEN PRs FIRST (before anything else):
-   gh pr list --repo Molecule-AI/molecule-core --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/molecule-core --state open --json number,title,author,statusCheckRollup
-   gh pr list --repo Molecule-AI/molecule-ai-workspace-runtime --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/molecule-ai-workspace-runtime --state open --json number,title,author,statusCheckRollup
-   gh pr list --repo Molecule-AI/molecule-ci --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/molecule-ci --state open --json number,title,author,statusCheckRollup
-   For EACH CI-green PR: review the diff, if safe → gh pr merge <number> --merge --delete-branch
+   For EACH CI-green PR: review the diff, if safe → tea pr merge <number> --merge --delete-branch
    Do NOT skip this step. Merging PRs is your #1 job.
 
 2. SCAN TEAM STATE: Check Infra-SRE, Infra-Runtime-BE status.

infra-runtime-be/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle — no active task. Find work:
-1. Check for PR review requests: gh pr list --repo Molecule-AI/molecule-core --state open --search "review-requested:app/molecule-ai"
+1. Check for PR review requests: tea pr list --repo molecule-ai/molecule-core --state open --search "review-requested:app/molecule-ai"
-2. Check open issues: gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
+2. Check open issues: tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
 3. Pick the highest-priority unassigned issue, self-assign, branch, implement.
 4. If nothing: commit_memory "idle HH:MM — backlog empty, standing by"

infra-runtime-be/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

infra-runtime-be/schedules/pick-up-work.md

@@ -10,10 +10,10 @@ Work cycle. Be productive every tick.
 
 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.
-   gh issue list --repo Molecule-AI/molecule-ai-workspace-runtime --state open --json number,title,labels,assignees
+   tea issue list --repo molecule-ai/molecule-ai-workspace-runtime --state open --json number,title,labels,assignees
-   gh issue list --repo Molecule-AI/molecule-core --state open --label "area:workspace" --json number,title,labels,assignees
+   tea issue list --repo molecule-ai/molecule-core --state open --label "area:workspace" --json number,title,labels,assignees
-   gh pr list --repo Molecule-AI/molecule-ai-workspace-runtime --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/molecule-ai-workspace-runtime --state open --json number,title,author,statusCheckRollup
-   gh pr list --repo Molecule-AI/molecule-core --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:

infra-sre/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle — no active task. Find work:
-1. Check for PR review requests: gh pr list --repo Molecule-AI/molecule-core --state open --search "review-requested:app/molecule-ai"
+1. Check for PR review requests: tea pr list --repo molecule-ai/molecule-core --state open --search "review-requested:app/molecule-ai"
-2. Check open issues: gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
+2. Check open issues: tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
 3. Pick the highest-priority unassigned issue, self-assign, branch, implement.
 4. If nothing: commit_memory "idle HH:MM — backlog empty, standing by"

infra-sre/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

infra-sre/schedules/pick-up-work.md

@@ -10,12 +10,12 @@ Work cycle. Be productive every tick.
 
 3. PICK UP WORK (if no active assignment):
    Check open issues in your repos (molecule-ci, molecule-ai-workspace-runtime, molecule-core). Pick the highest-priority UNASSIGNED issue (CRITICAL > HIGH > MEDIUM). No label filter — any open unassigned issue is fair game.
-   gh issue list --repo Molecule-AI/molecule-ci --state open --json number,title,labels,assignees
+   tea issue list --repo molecule-ai/molecule-ci --state open --json number,title,labels,assignees
-   gh issue list --repo Molecule-AI/molecule-ai-workspace-runtime --state open --json number,title,labels,assignees
+   tea issue list --repo molecule-ai/molecule-ai-workspace-runtime --state open --json number,title,labels,assignees
-   gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels,assignees
+   tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels,assignees
-   gh pr list --repo Molecule-AI/molecule-ci --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/molecule-ci --state open --json number,title,author,statusCheckRollup
-   gh pr list --repo Molecule-AI/molecule-ai-workspace-runtime --state open --json number,title,author,statusCheckRollup
+   tea pr list --repo molecule-ai/molecule-ai-workspace-runtime --state open --json number,title,author,statusCheckRollup
-   gh pr list --repo Molecule-AI/molecule-core --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:

integration-tester/idle-prompt.md

@@ -1,5 +1,5 @@
 Idle — no active task. Find work:
-1. Check for PR review requests: gh pr list --repo Molecule-AI/molecule-core --state open --search "review-requested:app/molecule-ai"
+1. Check for PR review requests: tea pr list --repo molecule-ai/molecule-core --state open --search "review-requested:app/molecule-ai"
-2. Check open issues: gh issue list --repo Molecule-AI/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
+2. Check open issues: tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels --jq '.[] | select(.assignees | length == 0) | "#\(.number) \(.title)"' | head -5
 3. Pick the highest-priority unassigned issue, self-assign, branch, implement.
 4. If nothing: commit_memory "idle HH:MM — backlog empty, standing by"

integration-tester/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

market-analyst/initial-prompt.md

@@ -7,6 +7,6 @@ You just started. Set up your environment silently — do NOT contact other agen
 
 2. Read project conventions: cat /workspace/repo/CLAUDE.md
 3. Read your role: cat /configs/system-prompt.md
-4. Check internal roadmap: gh repo clone Molecule-AI/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
+4. Check internal roadmap: tea repo clone molecule-ai/internal /tmp/internal 2>/dev/null && cat /tmp/internal/PLAN.md | head -100
 5. Save key conventions to memory.
 6. Wait for tasks from your parent — do not initiate contact.

market-analyst/schedules/market-analysis.md

@@ -4,7 +4,7 @@ Market analysis with web search. Run every 30 minutes.
 
 1. CHECK RESEARCH BACKLOG:
    search_memory "research-question:market-analyst"
-   gh issue list --repo Molecule-AI/internal --state open \
+   tea issue list --repo molecule-ai/internal --state open \
      --label research --label "area:market-analyst" \
      --json number,title --limit 5
 

market-analyst/system-prompt.md

@@ -25,7 +25,7 @@ You are a senior market analyst. You do the work yourself — research, data, an
 ## Staging-First Workflow
 
 All feature branches target `staging`, NOT `main`. When creating PRs:
-- `gh pr create --base staging`
+- `tea pr create --base staging`
 - Branch from `staging`, PR into `staging`
 - `main` is production-only — promoted from `staging` by CEO after verification on staging.moleculesai.app
 
@@ -73,7 +73,7 @@ will fail with a clear error message:
 
 ```bash
 mkdir -p ~/repos
-test -d ~/repos/internal || gh repo clone Molecule-AI/internal ~/repos/internal
+test -d ~/repos/internal || tea repo clone molecule-ai/internal ~/repos/internal
 
 cd ~/repos/internal
 git pull origin main
@@ -83,7 +83,7 @@ $EDITOR <area>/<slug>.md
 git add <area>/<slug>.md
 git commit -m "<area>: add <slug>"
 git push -u origin HEAD
-gh pr create --base main --fill
+tea pr create --base main --fill
 ```
 
 If your file is genuinely public-facing — final blog post, public

marketing-lead/idle-prompt.md

@@ -3,7 +3,7 @@ anything else, check `Molecule-AI/internal` for open PRs filed by your
 workers:
 
 ```
-gh pr list --repo Molecule-AI/internal --state open --json number,title,author --jq '.[] | "  #\(.number) by \(.author.login): \(.title[:60])"'
+tea pr list --repo molecule-ai/internal --state open --json number,title,author --jq '.[] | "  #\(.number) by \(.author.login): \(.title[:60])"'
 ```
 
 For each unreviewed PR:
@@ -16,7 +16,7 @@ For each unreviewed PR:
 4. If needs revision: comment with the gap + leave for worker to iterate
 
 Idle check. Quick scan:
-1. gh pr list --repo Molecule-AI/molecule-core --state open --json number,title,statusCheckRollup | head -20
+1. tea pr list --repo molecule-ai/molecule-core --state open --json number,title,statusCheckRollup | head -20
 2. Check if any team members need unblocking.
 3. If CI-green PRs have approvals: merge them.
 4. If nothing to do: commit_memory "idle HH:MM — team clear, no blockers"

marketing-lead/schedules/orchestrator-pulse.md

@@ -9,7 +9,7 @@ SEO, and Social busy with real work tied to concrete goals.
 Before dispatching new work, drain any pending reviews from your workers:
 
 ```bash
-gh pr list --repo Molecule-AI/internal --state open \
+tea pr list --repo molecule-ai/internal --state open \
   --json number,title,author,createdAt \
   --jq '.[] | "\(.number) \(.author.login) \(.createdAt[:16]) \(.title[:70])"' \
   | while read -r num author ts title; do
@@ -44,7 +44,7 @@ has TTS/music capabilities; ensure they use them for high-impact launches.
    Idle reports = opportunity to dispatch.
 
 2. SCAN RECENT FEATURE MERGES:
-   gh pr list --repo Molecule-AI/internal --state merged --search "feat in:title" \
+   tea pr list --repo molecule-ai/internal --state merged --search "feat in:title" \
      --limit 5 --json number,title,mergedAt
    For any feat merged in last 24h with NO launch post yet, follow step 2a to
    create issues + delegate.
@@ -54,22 +54,22 @@ has TTS/music capabilities; ensure they use them for high-impact launches.
    tracked by an issue), create one issue per workstream BEFORE dispatching:
 
    For DevRel:
-   gh issue create --repo Molecule-AI/internal --title "devrel: code demo for <feature> (PR #<N>)" \
+   tea issue create --repo molecule-ai/internal --title "devrel: code demo for <feature> (PR #<N>)" \
      --label needs-work --label marketing --label "area:devrel-engineer" \
      --body "Source: PR #<N>. Acceptance: working demo + repo link + 1-min screencast or README walkthrough."
    For Content:
-   gh issue create ... --label "area:content-marketer" --title "content: blog post for <feature>" ...
+   tea issue create ... --label "area:content-marketer" --title "content: blog post for <feature>" ...
    For Social:
-   gh issue create ... --label "area:social-media-brand" --title "social: launch thread for <feature>" ...
+   tea issue create ... --label "area:social-media-brand" --title "social: launch thread for <feature>" ...
    For PMM:
-   gh issue create ... --label "area:product-marketing-manager" --title "pmm: positioning check for <feature>" ...
+   tea issue create ... --label "area:product-marketing-manager" --title "pmm: positioning check for <feature>" ...
 
    Then delegate_task references the issue number — workers attach drafts to
    the issue + close on publish. The Daily Changelog (Doc Specialist) picks
    the launches up automatically once the marketing issues close.
 
 3. SCAN OPEN MARKETING ISSUES:
-   gh issue list --repo Molecule-AI/internal --label marketing,area:marketing-lead --state open
+   tea issue list --repo molecule-ai/internal --label marketing,area:marketing-lead --state open
    If >3 unassigned, follow step 2a to create the per-worker breakdown
    (don't bulk-dispatch a generic marketing ask without issues).
 

marketing-lead/system-prompt.md

@@ -36,7 +36,7 @@ You run the marketing team for Molecule AI — an agent-orchestration platform t
 ## Staging-First Workflow
 
 All feature branches target `staging`, NOT `main`. When creating PRs:
-- `gh pr create --base staging`
+- `tea pr create --base staging`
 - Branch from `staging`, PR into `staging`
 - `main` is production-only — promoted from `staging` by CEO after verification on staging.moleculesai.app
 
@@ -84,7 +84,7 @@ will fail with a clear error message:
 
 ```bash
 mkdir -p ~/repos
-test -d ~/repos/internal || gh repo clone Molecule-AI/internal ~/repos/internal
+test -d ~/repos/internal || tea repo clone molecule-ai/internal ~/repos/internal
 
 cd ~/repos/internal
 git pull origin main
@@ -94,7 +94,7 @@ $EDITOR <area>/<slug>.md
 git add <area>/<slug>.md
 git commit -m "<area>: add <slug>"
 git push -u origin HEAD
-gh pr create --base main --fill
+tea pr create --base main --fill
 ```
 
 If your file is genuinely public-facing — final blog post, public