You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ce326d5
Browse filesBrowse the repository at this point in the historyBrowse files
fix: prevent agent file collision in init, upgrade, and consult paths
All code paths that write squad.agent.md now check for an existing
exported coordinator (squad.md with generated marker) first. If one
exists, squad.agent.md is skipped — the exported file supersedes it.
Previously only the export direction was guarded (export renames legacy
to .bak). This closes the reverse vectors: init, upgrade, and consult
could blindly write squad.agent.md alongside an already-exported
squad.md, causing a collision.
Vectors fixed:
- squad init: skips squad.agent.md when exported coordinator present
- squad upgrade: skips refresh when exported coordinator present
- squad consult: skips agent file creation when exported coordinator present
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Prevent agent file collision: init, upgrade, and consult-mode now skip writing squad.agent.md when an exported coordinator (squad.md) already exists in .github/agents/
constexported='---\nname: Squad\n---\n\n# Big file\n\nLots of content...\n\n<!-- generated by squad export: do not edit by hand -->\n\nMore content.\n';
0 commit comments