refactor: relocate workspace/cli concerns out of orchestrator (isolation 2/7)#117
Merged
Conversation
Module-isolation migration PR 2 (docs/design/module-isolation-2026-06.md): - ProjectEntry moves to workspace/workspace.ts — it is the joint product of discovery + config loading, not a graph concern. graph/task-graph.ts keeps a type re-export so importers don't churn. - nested-dirs.ts and fingerprint.ts move to workspace/ — project geometry and workspace-file hashing are workspace products; their old home forced workspace logic to import from graph. - plan-format.ts moves to cli/ — pure presentation; the orchestrator keeps the RunPlan data types (cli → orchestrator edge is allowed). Mechanical relocation, zero behavior change. Boundary test still green; docs module-path references updated.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Migration PR 2 of the module-isolation series (
docs/design/module-isolation-2026-06.md). Mechanical moves, zero behavior change, history-following renames:orchestrator/nested-dirs.ts→workspace/nested-dirs.ts— project-boundary geometry is a workspace concern; it only fed the orchestrator by accident of history.orchestrator/fingerprint.ts→workspace/fingerprint.ts— workspace-file hashing, byte-identical move.orchestrator/plan-format.ts→cli/plan-format.ts— plan rendering (text/JSON/DOT) is presentation; orchestrator keeps theRunPlandata types. Consistent withcli/format.tsowningformatBytes.ProjectEntrymoved fromgraph/task-graph.tstoworkspace/workspace.ts(it's "discovered project + loaded config" — a workspace product); graph re-exports it so importers don't churn in this PR.Docs/module pages + layout trees updated to match. The boundary-law test from #116 passes — every new edge (graph → workspace, cli → orchestrator) is in the ALLOWED matrix.
Test plan
🤖 Generated with Claude Code