Repository navigation
[External State] squad internalize copies back without external-dir cleanup #1401
Description
Summary
squad internalize copies state from external dir back to local .squad but does not clean external dir afterwards.
Evidence
- Copy loop in internalize:
packages/squad-cli/src/cli/commands/externalize.ts:152-168
- No delete/cleanup of external source entries after copy.
- Delete calls in file are used in other contexts (externalize move + config cleanup), not external-dir cleanup in internalize.
Expected
If semantics are “move back”, external source should be cleaned; otherwise behavior/docs should explicitly define copy-back semantics.
Actual
Behavior is copy-back without external cleanup.
Activity
docs: align external-state page with actual externalize/internalize b…
chore: promote dev -> main (v0.12.0) (#1698)
bradygaster commentedon Sep 24, 2026
Keeping this open as a product-semantics decision, not folding it into the completed #1402 integration tracker. Current behavior is copy-back and was documented in merged PR #1466. Before implementation, decide explicitly whether
internalizemeans move (clean external state) or copy (retain it), then align acceptance criteria, safety behavior, and docs.