refactor(monorepo): remove legacy root runtime ownership

2026-03-20 13:47:53 +08:00
parent 388c25b1b0
commit d00b2a30ee
99 changed files with 144 additions and 17619 deletions
@@ -1,57 +0,0 @@
-# Skill Workspace Monorepo Migration
-
-## Status
-
- `in_progress`
-
-## Owner
-
- Codex
-
-## Started At
-
- `2026-03-20`
-
-## Goal
-
- Execute `Milestone 10: Skill Workspace Monorepo Migration` by moving the repository toward a true multi-package monorepo whose primary deliverables are skills and skill runtimes.
-
-## Scope
-
- bootstrap the shared workspace structure described in `docs/skill-workspace-monorepo.md`
- complete migration phases incrementally, committing after each completed phase
- keep packaging, roadmap, and validation flows synchronized as the migration proceeds
-
-## Checklist
-
- [x] create or adopt an active execution roadmap for the migration workstream
- [x] Phase 1: bootstrap `go.work`, expanded workspace manifests, package roots, and declarative skill bundle metadata
- [x] Phase 2: extract shared coordination code into `packages/coord-core`
- [x] Phase 3: extract `inbox-runtime` and `orch-runtime`
- [x] Phase 4: extract `orchd-runtime`
- [x] Phase 5: import `repo-memory-runtime` and add `skills/repo-memory`
- [ ] Phase 6: remove root runtime ownership and normalize package-based packaging
-
-## Files
-
- `docs/roadmaps/active/skill-workspace-monorepo-migration.md`
- `docs/skill-workspace-monorepo.md`
- `docs/implementation-roadmap.md`
- `go.work`
- `pnpm-workspace.yaml`
- `package.json`
- `packages/`
- `scripts/`
-
-## Decisions
-
- keep one long-lived active roadmap for the full migration rather than opening a new execution trace for every individual phase
- complete and commit one migration phase at a time so the workspace remains bisectable
-
-## Blockers
-
- none
-
-## Next Step
-
- start Phase 6 by removing or reducing legacy root runtime ownership now that `coord-core`, `inbox-runtime`, `orch-runtime`, `orchd-runtime`, and `repo-memory-runtime` all exist as package-owned runtimes