slim(parent-template): extract dev tree → symlink to molecule-dev-department, delete 17 orphans (Phase 3d) #5

Merged
claude-ceo-assistant merged 1 commits from slim/extract-dev-into-symlink into main 2026-05-08 11:16:41 +00:00

1 Commits

Author SHA1 Message Date
claude-ceo-assistant
f331bebac1 slim(parent-template): delete 17 orphans + extract dev tree, wire dev-lead symlink to molecule-dev-department
All checks were successful
CI / validate (push) Successful in 56s
CI / validate (pull_request) Successful in 52s
Phase 3d of internal#77 (dev-department extraction).

What changed:

  Deletions:
  - 17 orphan workspace folders not reachable from any teams/*.yaml
    !include chain in this template (caught at extract time by
    validate-tree.py): backend-engineer{,-2,-3}, frontend-engineer{,-2,-3},
    qa-engineer{,-2,-3}, security-auditor{,-2}, platform-engineer,
    devops-engineer, sre-engineer, offensive-security-engineer,
    devrel-engineer, triage-operator-2, uiux-designer.
  - 27 dev-tree workspace folders extracted to molecule-ai/molecule-dev-department
    (history preserved via git filter-repo): dev-lead, core-{lead,be,fe,qa,
    security,uiux,devops,offsec}, cp-{lead,be,qa,security}, app-{lead,fe,qa},
    technical-writer, infra-{lead,sre,runtime-be}, sdk-{lead,dev}, plugin-dev,
    release-manager, integration-tester, fullstack-engineer,
    documentation-specialist, triage-operator.
  - 8 teams/<dev-tree>.yaml composition files (dev.yaml, core-platform.yaml,
    controlplane.yaml, app-docs.yaml, infra.yaml, sdk.yaml,
    documentation-specialist.yaml, triage-operator.yaml).

  Additions:
  - dev-lead → ../molecule-dev-department/dev-lead/ (symlink). Resolves
    correctly when both repos are cloned as siblings under operator's
    /org-templates/ (current convention: /org-templates/molecule-dev/
    + /org-templates/molecule-dev-department/). Platform's
    resolveYAMLIncludes follows the symlink at file-read while its
    security check (filepath.Abs/Rel) operates on path strings, so
    'dev-lead/workspace.yaml' counts as 'inside parent root' even though
    its content lives in the sibling repo. Contract pinned by
    molecule-core PR #102's tests.

  Edits:
  - org.yaml workspaces: gains '!include dev-lead/workspace.yaml' (third
    root after pm.yaml + marketing.yaml). The other two roots are
    unchanged.
  - teams/pm.yaml children: removed dev.yaml, documentation-specialist.yaml,
    triage-operator.yaml, triage-operator-2 (orphan). Comments document
    where each moved.
  - teams/marketing.yaml children: removed devrel-engineer (orphan).

This template is now ~50% smaller and contains only parent-only roles:
PM + Research (research-lead, market-analyst, technical-researcher,
competitive-intelligence) + Marketing (marketing-lead, content-marketer,
product-marketing-manager, community-manager, seo-growth-analyst,
social-media-brand). Engineering org tree is composed in via
the dev-lead symlink + dev-department repo.

Refs:
  internal#77 — extraction RFC
  molecule-ai/molecule-dev-department PRs #1, #2, #3 (scaffold + extract + atomize)
  molecule-core PR #102 — symlink-resolution contract test
  Hongming GO 2026-05-08 ("approved, keep going" + "dont wait for me, follow the plan")
  SOP Phase 3d — task #225
2026-05-08 04:15:51 -07:00