Observed
For a task that really only needed project_api (and maybe project-orchestrator), spawning affected the whole workspace. The extra repos sat untouched and then caused finish-time friction (see companion issue on finish + untouched repos).
Why this matters
Task scoping should default narrow, not broad. Broad scoping pollutes affected_repos, creates noisy audit surface, and forces manual cleanup to finish.
Suggested direction
- Stronger
--repos defaulting: if the user passes --repos, only those are affected. Don't auto-expand.
- Or:
mship narrow --repos <name,...> to prune affected_repos on an existing task.
- Or:
mship prune-untouched auto-detects repos with no branch diff vs. base and removes them.
Related: finish-with-untouched-repos (#).
Observed
For a task that really only needed
project_api(and maybeproject-orchestrator), spawning affected the whole workspace. The extra repos sat untouched and then caused finish-time friction (see companion issue on finish + untouched repos).Why this matters
Task scoping should default narrow, not broad. Broad scoping pollutes
affected_repos, creates noisy audit surface, and forces manual cleanup to finish.Suggested direction
--reposdefaulting: if the user passes--repos, only those are affected. Don't auto-expand.mship narrow --repos <name,...>to pruneaffected_reposon an existing task.mship prune-untouchedauto-detects repos with no branch diff vs. base and removes them.Related: finish-with-untouched-repos (#).