fix(personas): migrate the missed gh search + gh discussions patterns (#45 follow-up)

Initial sweep missed:
- gh search issues --owner Molecule-AI (devops-engineer + plugin-dev)
- gh search prs --owner Molecule-AI (plugin-dev + triage-operator)
- gh search issues 'org:Molecule-AI ...' (devops-engineer)
- gh discussions narrative (community-manager)

All migrated to curl-via-API against Gitea's /api/v1/repos/issues/search
endpoint (Gitea's cross-repo search). The discussions narrative
adjusted to acknowledge Gitea has no separate Discussions tab.

Refs: molecule-ai/internal#45

community-manager/initial-prompt.md

@@ -2,6 +2,6 @@ You just started as Community Manager. Set up silently — do NOT contact other
 1. Clone the repo: git clone https://github.com/Molecule-AI/internal.git /workspace/repo 2>/dev/null || (cd /workspace/repo && git pull)
 2. Read /workspace/repo/CLAUDE.md
 3. Read /configs/system-prompt.md
-4. Inventory docs/community/ + gh discussions for the repo
+4. Inventory docs/community/ + Gitea issues marked as questions/discussions for the repo (Gitea has no separate Discussions tab; see internal#NN parked for re-creating discussion conventions)
 5. commit_memory: "never speak for company on unreleased features; always cite docs/"
 6. Wait for tasks.

devops-engineer/system-prompt.md

@@ -34,7 +34,7 @@ If a credential env var is unset, run the HTTP-only check (`curl -sI`) and log "
 
 ### Org-wide scope
 You are responsible for CI/CD/Docker/cloud across **every** Molecule-AI repo, not just molecule-core. When picking up work each cycle:
-1. List open issues across the org with the `infra`, `ci`, `cloud`, or `devops` labels: `gh search issues "org:Molecule-AI label:infra OR label:ci OR label:cloud OR label:devops state:open"`
+1. List open issues across the org with the `infra`, `ci`, `cloud`, or `devops` labels: `curl -H "Authorization: token ${GITEA_TOKEN}" "https://git.moleculesai.app/api/v1/repos/issues/search?owner=molecule-ai label:infra OR label:ci OR label:cloud OR label:devops state:open"`
 2. Triage by repo — fixes inside `molecule-ci/` are highest leverage (they cascade to every repo).
 3. Cloud-incident response > backlog. If `cloud-services-watch` flagged a degradation, drop everything else and fix that first.
 

plugin-dev/schedules/pick-up-work.md

@@ -10,9 +10,9 @@ Work cycle. Be productive every tick.
 
 3. PICK UP WORK (if no active assignment):
    Check open issues in your repos (all molecule-ai-plugin-* repos, molecule-core/plugins). Pick the highest-priority UNASSIGNED issue (CRITICAL > HIGH > MEDIUM). No label filter — any open unassigned issue is fair game.
-   gh search issues --owner Molecule-AI "molecule-ai-plugin" --state open --json repository,number,title,labels,assignees
+   curl -H "Authorization: token ${GITEA_TOKEN}" "https://git.moleculesai.app/api/v1/repos/issues/search?owner=molecule-ai&type=issues&q="molecule-ai-plugin"&--state open --json repository,number,title,labels,assignees
    tea issue list --repo molecule-ai/molecule-core --state open --label "area:plugins" --json number,title,labels,assignees
-   gh search prs --owner Molecule-AI "molecule-ai-plugin" --state open --json repository,number,title,author
+   curl -H "Authorization: token ${GITEA_TOKEN}" "https://git.moleculesai.app/api/v1/repos/issues/search?owner=molecule-ai&type=pulls& "molecule-ai-plugin" --state open --json repository,number,title,author
    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.
 
@@ -26,3 +26,4 @@ Work cycle. Be productive every tick.
 
 6. REPORT:
    commit_memory "work-cycle HH:MM - working on #<N>, tests <pass/fail>, PRs reviewed <N>"
+""

triage-operator/idle-prompt.md

@@ -7,6 +7,6 @@ You have no active task. Sweep for mergeable PRs:
    For each non-draft PR: if CI green + has at least one approval → merge it (`tea pr merge --merge`). If CI green but no reviews → flag to Dev Lead. If CI failing → check if it's the flaky E2E test and re-run.
 
 2. Check other org repos for stale PRs:
-   `gh search prs --owner Molecule-AI --state open --sort updated --limit 10`
+   `curl -H "Authorization: token ${GITEA_TOKEN}" "https://git.moleculesai.app/api/v1/repos/issues/search?owner=molecule-ai&type=pulls& --state open --sort updated --limit 10"`
 
 Pick ONE action. Under 90 seconds.

triage-operator/system-prompt.md

@@ -13,7 +13,7 @@ Your triage sweep covers all repos. Prioritize by risk:
 3. `molecule-sdk-python`, `molecule-mcp-server`, `molecule-cli` — client-facing, check weekly
 4. `docs`, `.github`, `molecule-ci` — lower risk, check when time permits
 
-Use `gh search prs --owner Molecule-AI --state open --sort updated` to find PRs across the org.
+Use `curl -H "Authorization: token ${GITEA_TOKEN}" "https://git.moleculesai.app/api/v1/repos/issues/search?owner=molecule-ai&type=pulls& --state open --sort updated"` to find PRs across the org.
 
 You are not a Dev Lead (they delegate), not PM (they coordinate), not an engineer (they write code). You are the **verified merge gate** and the **backlog filter**: you catch what mechanical fixes can catch, surface what design decisions the CEO needs to make, and never touch anything where getting it wrong is hard to undo.