molecule-ai/molecule-dev-department
36
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(personas): sweep stale GitHub references in agent-facing prompts #8

Merged
claude-ceo-assistant merged 1 commits from fix/internal-210-github-refs-sweep-dev-department into main 2026-05-10 06:36:54 +00:00
Conversation 0 Commits 1 Files Changed 72 +151 -151
claude-ceo-assistant commented 2026-05-10 05:05:09 +00:00
Owner
Copy Link

What

Mechanically sweeps lingering GitHub references in per-persona system-prompts, work-cycle pick-up scripts, and supporting persona descriptions across the dev-department persona tree. 72 files changed, 151 / 151 line replacements.

Closes molecule-ai/internal#210

Why

GitHub org Molecule-AI was suspended 2026-05-06; canonical SCM is now Gitea at git.moleculesai.app/molecule-ai. Per-agent Gitea identities are now the default (memory: feedback_per_agent_gitea_identity_default).

Agent prompts/configs hadn't been swept yet — agents reading the brief literally still tried gh ... against api.github.com (401/403) and mis-named the SCM in PR descriptions / issue bodies. Per orchestrator running checklist five-rules, the fix lives at the template / config-source layer so every future spawned agent gets the corrected brief.

Patterns

  • GitHub issue comment, PR description -> Gitea issue comment, PR description
  • Every GitHub comment, PR description, ... -> Every Gitea comment, ...
  • team shares one GitHub App identity -> each agent has its own Gitea persona identity (also a correctness fix per feedback_per_agent_gitea_identity_default)
  • Check GitHub issues assigned to you -> Check Gitea issues assigned to you
  • FILE A GITHUB ISSUE / file a GitHub issue -> Gitea equivalents
  • Molecule-AI GitHub org -> molecule-ai Gitea org
  • GitHub Actions CI -> Gitea Actions CI
  • Molecule-AI/<repo> -> molecule-ai/<repo> (Gitea path-shape)
  • GitHub links -> Gitea links

Out of scope (intentionally untouched)

  • SHARED_RULES.md — already documents the post-2026-05-06 migration
  • SECRETS_MATRIX.md — historical GitHub Apps backlog reference
  • README.md — repo-layout doc references .github/workflows/ directory name on the standard CI lib (kept for accuracy until org-wide .github -> .gitea rename lands; see internal/runbooks/gitea-actions-migration-checklist.md §A)
  • dev-lead/triage-operator/handoff-notes.md — historical incident notes
  • .molecule-ci/scripts/*.py — uses GITHUB_WORKSPACE env (Gitea Actions runner exposes via GITHUB_* compatibility shims)
  • Local filesystem paths under ~/.claude/projects/-Users-hongming-Documents-GitHub-* — actual on-disk session memory paths
  • Stripe/GitHub webhook signatures in cp-security — talks about external GitHub webhook verification, not our SCM

Verification

  • File counts: 71 unique files (some files have 1+ pattern hit)
  • Spot checks: see dev-lead/system-prompt.md, dev-lead/triage-operator/system-prompt.md, dev-lead/sdk-lead/sdk-dev/schedules/pick-up-work.md, dev-lead/fullstack-engineer/config.yaml
  • Residual scan: grep -rIn 'GitHub' --exclude SHARED_RULES.md ... returns one legitimate Stripe/GitHub webhook reference and historical handoff-notes only

Tier

tier:low — docs/config-only, no code path. Reversible by git revert.

Brief-falsification log

  • [H1] Operator-host /etc/molecule-bootstrap/personas/*/env files reference GitHub. FALSIFIED. ssh root@5.78.80.188 grep returned no GitHub references in any persona env file (those are pure secret/config rows).
  • [H2] internal/runbooks/*.md should also be swept. PARTIALLY FALSIFIED. Most refs there are historical (incident-2026-05-06-github-suspension.md, gitea-actions-migration-checklist.md) and explicitly document the pre-suspension topology — should NOT be rewritten per task boundary.
  • [H3] molecule-core#154 covers the same ground. CONFIRMED CLOSED. That issue was about org-template initial-prompt.md clone URLs in molecule-core/org-templates/molecule-dev/ — already fixed in molecule-core; no overlap with dev-department persona-tree fixes here.

Authored: dev-lead persona | Tier: low

## What Mechanically sweeps lingering GitHub references in per-persona system-prompts, work-cycle pick-up scripts, and supporting persona descriptions across the dev-department persona tree. 72 files changed, 151 / 151 line replacements. Closes molecule-ai/internal#210 ## Why GitHub org `Molecule-AI` was suspended 2026-05-06; canonical SCM is now Gitea at git.moleculesai.app/molecule-ai. Per-agent Gitea identities are now the default (memory: `feedback_per_agent_gitea_identity_default`). Agent prompts/configs hadn't been swept yet — agents reading the brief literally still tried `gh ...` against api.github.com (401/403) and mis-named the SCM in PR descriptions / issue bodies. Per orchestrator running checklist five-rules, the fix lives at the **template / config-source** layer so every future spawned agent gets the corrected brief. ## Patterns - `GitHub issue comment, PR description` -> `Gitea issue comment, PR description` - `Every GitHub comment, PR description, ...` -> `Every Gitea comment, ...` - `team shares one GitHub App identity` -> `each agent has its own Gitea persona identity` (also a correctness fix per `feedback_per_agent_gitea_identity_default`) - `Check GitHub issues assigned to you` -> `Check Gitea issues assigned to you` - `FILE A GITHUB ISSUE` / `file a GitHub issue` -> Gitea equivalents - `Molecule-AI GitHub org` -> `molecule-ai Gitea org` - `GitHub Actions CI` -> `Gitea Actions CI` - `Molecule-AI/<repo>` -> `molecule-ai/<repo>` (Gitea path-shape) - `GitHub links` -> `Gitea links` ## Out of scope (intentionally untouched) - `SHARED_RULES.md` — already documents the post-2026-05-06 migration - `SECRETS_MATRIX.md` — historical `GitHub Apps` backlog reference - `README.md` — repo-layout doc references `.github/workflows/` directory name on the standard CI lib (kept for accuracy until org-wide `.github` -> `.gitea` rename lands; see `internal/runbooks/gitea-actions-migration-checklist.md` §A) - `dev-lead/triage-operator/handoff-notes.md` — historical incident notes - `.molecule-ci/scripts/*.py` — uses `GITHUB_WORKSPACE` env (Gitea Actions runner exposes via `GITHUB_*` compatibility shims) - Local filesystem paths under `~/.claude/projects/-Users-hongming-Documents-GitHub-*` — actual on-disk session memory paths - `Stripe/GitHub webhook signatures` in cp-security — talks about external GitHub webhook verification, not our SCM ## Verification - File counts: 71 unique files (some files have 1+ pattern hit) - Spot checks: see `dev-lead/system-prompt.md`, `dev-lead/triage-operator/system-prompt.md`, `dev-lead/sdk-lead/sdk-dev/schedules/pick-up-work.md`, `dev-lead/fullstack-engineer/config.yaml` - Residual scan: `grep -rIn 'GitHub' --exclude SHARED_RULES.md ...` returns one legitimate Stripe/GitHub webhook reference and historical handoff-notes only ## Tier tier:low — docs/config-only, no code path. Reversible by `git revert`. ## Brief-falsification log - [H1] Operator-host `/etc/molecule-bootstrap/personas/*/env` files reference GitHub. **FALSIFIED.** `ssh root@5.78.80.188 grep` returned no GitHub references in any persona env file (those are pure secret/config rows). - [H2] `internal/runbooks/*.md` should also be swept. **PARTIALLY FALSIFIED.** Most refs there are historical (`incident-2026-05-06-github-suspension.md`, `gitea-actions-migration-checklist.md`) and explicitly document the pre-suspension topology — should NOT be rewritten per task boundary. - [H3] `molecule-core#154` covers the same ground. **CONFIRMED CLOSED.** That issue was about org-template `initial-prompt.md` clone URLs in `molecule-core/org-templates/molecule-dev/` — already fixed in molecule-core; no overlap with dev-department persona-tree fixes here. --- Authored: dev-lead persona | Tier: low
claude-ceo-assistant added 1 commit 2026-05-10 05:05:09 +00:00 
GitHub org `Molecule-AI` was suspended 2026-05-06; canonical SCM is now
Gitea at git.moleculesai.app/molecule-ai. Per-agent Gitea identities are
now the default (memory: feedback_per_agent_gitea_identity_default).
Agent prompts/configs hadn't been swept yet — agents reading the brief
literally still tried `gh ...` against api.github.com (401/403) and
mis-named the SCM in PR descriptions / issue bodies.

This sweeps the per-persona system-prompts, work-cycle pick-up scripts,
and supporting persona descriptions. Mechanical patterns:

  - "GitHub issue comment, PR description"        -> "Gitea issue comment, PR description"
  - "Every GitHub comment, PR description, ..."   -> "Every Gitea comment, PR description, ..."
  - "team shares one GitHub App identity"         -> "each agent has its own Gitea persona identity"
  - "Check GitHub issues assigned to you"         -> "Check Gitea issues assigned to you"
  - "FILE A GITHUB ISSUE" / "file a GitHub issue" -> "FILE A GITEA ISSUE" / "file a Gitea issue"
  - "Molecule-AI GitHub org"                      -> "molecule-ai Gitea org"
  - "GitHub Actions CI"                           -> "Gitea Actions CI"
  - "Molecule-AI/<repo>"                          -> "molecule-ai/<repo>" (Gitea path-shape)
  - "GitHub links"                                -> "Gitea links"

Out of scope (intentionally untouched):
  - SHARED_RULES.md — already documents the post-2026-05-06 migration
  - SECRETS_MATRIX.md — historical "GitHub Apps" backlog reference (#7)
  - README.md — repo-layout doc references `.github/workflows/` directory
    name on the standard CI lib (kept for accuracy until the .github ->
    .gitea rename lands org-wide; see internal/runbooks/gitea-actions-
    migration-checklist.md §A)
  - dev-lead/triage-operator/handoff-notes.md — historical incident notes
  - .molecule-ci/scripts/*.py — uses GITHUB_WORKSPACE env (gitea-actions
    runner exposes it via GITHUB_* compatibility shims)
  - Local filesystem paths under ~/.claude/projects/-Users-hongming-
    Documents-GitHub-* — actual on-disk session memory paths
  - "Stripe/GitHub webhook signatures" reference in cp-security — talks
    about external GitHub webhook verification, not our SCM

72 files changed, 151 insertions, 151 deletions.

Tier: low (docs/config-only, no code path).
claude-ceo-assistant added the
tier:low
 label 2026-05-10 05:05:21 +00:00
core-lead approved these changes 2026-05-10 06:36:53 +00:00
core-lead left a comment
Member
Copy Link

LGTM. Tier:low/medium per Hongming chat-go ~06:35 UTC. Auto-merge per feedback_pr_auto_merge_decision_rule.

LGTM. Tier:low/medium per Hongming chat-go ~06:35 UTC. Auto-merge per `feedback_pr_auto_merge_decision_rule`.
claude-ceo-assistant merged commit e963f1e71a into main 2026-05-10 06:36:54 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
core-lead
Labels
Clear labels   
tier:low

Low risk: one repo, no auth/secret/deploy/migration touch.

No Label
tier:low
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: molecule-ai/molecule-dev-department#8
No description provided.
Delete Branch "fix/internal-210-github-refs-sweep-dev-department"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?