refactor(monorepo): remove legacy root runtime ownership

This commit is contained in:
2026-03-20 13:47:53 +08:00
parent 388c25b1b0
commit d00b2a30ee
99 changed files with 144 additions and 17619 deletions
+12 -12
View File
@@ -101,9 +101,9 @@ Current implementation status:
- `Milestone 7: Council Review` is complete
- `Milestone 8: Web Product Phase 1 Skeleton` is complete
- `Milestone 9: Web Product Phase 2 Read-Only Operator UI` is complete for the initial operator surface
- `Milestone 10: Skill Workspace Monorepo Migration` is in progress
- `Milestone 10: Skill Workspace Monorepo Migration` is complete
The council review v1 surface is complete, the first web-product skeleton now exists as a separate monorepo workspace plus read-only HTTP backend slice, the first real operator-facing Phase 2 read-only web views now exist on top of the internal Cadence UI component library, and the repository has now started the actual migration into a true skill workspace monorepo.
The council review v1 surface is complete, the first web-product skeleton now exists as a separate monorepo workspace plus read-only HTTP backend slice, the first real operator-facing Phase 2 read-only web views now exist on top of the internal Cadence UI component library, and the repository has now completed the migration into a package-owned skill workspace monorepo for the current runtime set.
### Milestone 1: Go Skeleton
@@ -487,7 +487,7 @@ Definition of done:
Status:
- in progress
- completed
Completed so far:
@@ -513,24 +513,24 @@ Completed so far:
- `packages/repo-memory-runtime/cmd/briefdb` plus its package-local `internal/brief` and `internal/store` now provide a package-owned repo-memory runtime and pass `go test ./...`
- `skills/repo-memory/` now exists with `SKILL.md`, `agents/openai.yaml`, and a bundled `assets/briefdb` binary produced by the declarative packaging flow
- `docs/tests/repo-memory-skill/` now exists with a README plus an initial forward-test case covering search-before-add and durable entry retrieval through the bundled skill
- root `cmd/inbox`, `cmd/orch`, and `cmd/orchd` now act as compatibility shims that invoke package-owned runtimes instead of root-owned runtime implementations
- legacy root runtime implementation directories under `internal/` have been removed now that package-owned runtimes and package-backed skill bundles are in place
Remaining:
- remove or reduce the remaining legacy root runtime ownership under `cmd/` and `internal/`
- decide whether the external `../tmp/briefdb` prototype should be archived, documented as superseded, or deleted after the package import is considered stable
- none for the current migration slice
- optional follow-up: archive or delete the external `../tmp/briefdb` prototype once the imported runtime is treated as the sole maintained source
## Immediate Next Task
If a new agent is taking over now, the next concrete step should be:
1. treat `Milestone 9: Web Product Phase 2 Read-Only Operator UI` as complete for the initial operator surface and do not expand web feature scope further until the workspace split is decided package-by-package
2. treat the Phase 1 workspace bootstrap for `Milestone 10` as complete and keep the new `go.work`, `packages/`, and declarative bundle metadata as the baseline for all further migration steps
3. treat the shared coordination kernel extraction into `packages/coord-core` as complete and move `inbox` plus `orch` into package-owned runtimes next
4. treat `coord-core`, `inbox-runtime`, `orch-runtime`, `orchd-runtime`, and `repo-memory-runtime` as the package-owned runtime baseline and start Phase 6 by removing or shrinking the remaining root-owned runtime paths
5. keep the authored skill forward-test plans under `docs/tests/*-skill/` synchronized as runtime ownership moves from root paths to package paths
6. decide how to retire or archive the external `../tmp/briefdb` prototype once the imported runtime is stable enough to be the sole source of truth
1. treat `Milestone 10: Skill Workspace Monorepo Migration` as complete for the current runtime set and keep new runtime work inside `packages/` plus `skills/` rather than recreating root-owned implementations
2. resume product-facing work on top of the new workspace, beginning with the next highest-priority feature slice rather than more repository reshuffling
3. keep the authored skill forward-test plans under `docs/tests/*-skill/` synchronized as new skills or runtime-backed bundles are added
4. optionally archive or delete the external `../tmp/briefdb` prototype after confirming no remaining workflow depends on it
The inbox implementation and its human-readable test-plan set are already in place, `orch` supports the main scheduler loop plus the complete council start/wait/tally/report workflow, the web product now has its first real operator-facing read surfaces, and the repository has completed the workspace bootstrap plus the shared coordination, inbox, orch, orchd, and repo-memory package-runtime extraction phases of the skill monorepo migration, so the next step should be removing legacy root ownership and finalizing source-of-truth boundaries rather than continuing to accrete new root-owned runtime paths.
The inbox implementation and its human-readable test-plan set are already in place, `orch` supports the main scheduler loop plus the complete council start/wait/tally/report workflow, the web product now has its first real operator-facing read surfaces, and the repository now uses package-owned runtimes plus agent-facing skill bundles as its primary structure, so the next step should be feature work and incremental new skill additions on top of that workspace rather than further structural churn.
## Recommended Driver Choices
@@ -2,7 +2,7 @@
## Status
- `in_progress`
- `completed`
## Owner
@@ -30,11 +30,11 @@
- [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
- [x] Phase 6: remove root runtime ownership and normalize package-based packaging
## Files
- `docs/roadmaps/active/skill-workspace-monorepo-migration.md`
- `docs/roadmaps/archive/skill-workspace-monorepo-migration.md`
- `docs/skill-workspace-monorepo.md`
- `docs/implementation-roadmap.md`
- `go.work`
@@ -54,4 +54,12 @@
## 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
- resume product work on top of the package-owned runtime workspace, starting with whichever user-facing feature slice has priority next
## Completion Summary
- bootstrapped the repository as a multi-package workspace with `go.work`, expanded JS workspace discovery, and declarative skill bundle metadata
- extracted the shared coordination kernel into `packages/coord-core`
- extracted package-owned runtimes for `inbox`, `orch`, `orchd`, and `repo-memory`
- switched the root skill packaging flow to build from package entrypoints, including the new `repo-memory` bundle
- removed the legacy root runtime implementation directories under `internal/`, leaving root `cmd/*` as compatibility shims while package-owned runtimes remain the source of truth