molecule-ai/molecule-dev-department
36
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
21 Commits 6 Branches 1 Tag 565 KiB
daafb1dfbf
Commit Graph

2 Commits

Author SHA1 Message Date
dev-lead
daafb1dfbf fix(personas): sweep stale GitHub references in agent-facing prompts (Closes molecule-ai/internal#210) 
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).
 2026-05-09 22:04:35 -07:00
claude-ceo-assistant
1dd614a4f1 atomize(dev-tree): nest sub-teams + leaf workspaces under dev-lead/, dissolve teams/ 
Phase 3c-3 of internal#77 (dev-department extraction).

Atomization completes the structural goal of the RFC (Hongming Q3+Q5):
each workspace is a self-contained folder; no cross-tree '..' refs;
the validator can enforce orphans-impossible-by-construction in --strict mode.

What changed:

  Folder moves (history preserved via git mv):
  - core-be, core-fe, core-qa, core-security, core-uiux, core-devops,
    core-offsec → core-lead/<self>/
  - cp-be, cp-qa, cp-security → cp-lead/<self>/
  - app-fe, app-qa, technical-writer, documentation-specialist
    → app-lead/<self>/
  - infra-sre, infra-runtime-be → infra-lead/<self>/
  - sdk-dev, plugin-dev → sdk-lead/<self>/
  - core-lead, cp-lead, app-lead, infra-lead, sdk-lead,
    release-manager, integration-tester, fullstack-engineer,
    triage-operator → dev-lead/<self>/

  Workspace.yaml content:
  - dev-lead/workspace.yaml: lifted from teams/dev.yaml. children: paths
    rewritten from team-yaml-style ('!include core-platform.yaml') and
    floater-style ('!include ../release-manager/workspace.yaml') to
    canonical './<child>/workspace.yaml'.
  - dev-lead/<sub-team>-lead/workspace.yaml: lifted from teams/<sub-team>.yaml.
    children: paths rewritten from '../<child>/workspace.yaml' to
    './<child>/workspace.yaml'.
  - dev-lead/app-lead/documentation-specialist/workspace.yaml: lifted from
    teams/documentation-specialist.yaml (Q1 placement).
  - dev-lead/triage-operator/workspace.yaml: lifted from
    teams/triage-operator.yaml (Q2 placement).
  - All files_dir: paths updated to full path-from-org-root
    (e.g. 'core-be' → 'dev-lead/core-lead/core-be',
     'core-lead' → 'dev-lead/core-lead', etc.). When parent template
    imports via the 'dev-lead' symlink (Phase 3d), files_dir resolves
    correctly relative to parent's org-root.

  Manifest:
  - dev-department.yaml roots: changed from '!include teams/dev.yaml'
    to '!include ./dev-lead/workspace.yaml'.

  Composition layer:
  - teams/ entirely deleted (8 yaml files removed). The composition is
    now expressed structurally via the folder tree.

  CI gate:
  - .github/workflows/validate.yml runs validate-tree.py --strict.
    Cross-tree '..' refs now hard-fail.

Validator state on this commit (--strict):
  filesystem workspace folders : 28
  reachable from manifest      : 28
  orphans                      : 0
  cross-tree '..' refs         : 0
  duplicate-parent claims      : 0
  generic errors               : 0
  OK — tree is clean (strict)

Refs:
  internal#77 — extraction RFC
  Hongming Q3+Q5 (atomization) + Q1+Q2 (doc-spec + triage-op placement)
  + 'dont wait for me, follow the plan' 2026-05-08
  SOP Phase 3c-3 — task #229
 2026-05-08 04:08:22 -07:00