migrate-directory doesn't replace .ai-team/ references inside file content #134

Description

The squad upgrade --migrate-directory command renames .ai-team/ to .squad/ and scrubs email addresses from file content, but it does not replace .ai-team/ path references inside the migrated files themselves.

Example

After running --migrate-directory, .squad/skills/squad-conventions/SKILL.md still contains:

`markdown

File Structure

• .ai-team/ — Team state (user-owned, never overwritten by upgrades)
• .ai-team-templates/ — Template files copied from templates/
• .ai-team/skills/ — Team skills in SKILL.md format
• .ai-team/decisions/inbox/ — Drop-box for parallel decision writes
  `

And in the code example:

javascript console.log(GREEN + '✓' + RESET + ' .ai-team/ceremonies.md');

The upstream template (templates/skills/squad-conventions/SKILL.md) has already been updated to use .squad/ paths, but the migration command doesn't propagate those content changes to existing user files.

Affected files

Any user-owned file inside .squad/ that contains .ai-team/ string references. The squad-conventions SKILL.md is one example, but decisions.md, history.md files, and log entries may also contain stale references.

Suggested fix

Add a content replacement pass to the --migrate-directory flow (after the rename, alongside the email scrub) that replaces .ai-team/ → .squad/ and .ai-team-templates/ → .squad-templates/ in all .md and .json files within the migrated directory.

Additional context

• Also hit EPERM on Windows during the fs.renameSync call (VS Code file watchers holding handles on the directory). A copy+delete fallback for Windows would make the migration more robust.
• Squad version: v0.5.2
• OS: Windows 11