feature: track managed artifact lifecycle and clean obsolete paths on upgrade
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Facilidade para iniciantes
- 30/100
- Tipo de issue
- Funcionalidade
- Clareza
- Razoavelmente clara
- Status de atividade
- Ativa
- Stack de tecnologia
- typescript
Direção de pesquisa
Start by reading the existing squad upgrade migration and TEMPLATE_MANIFEST, then inspect the versioned layout manifest proposal in #670 and the related migration issues #2047 and #1126. Map how managed artifacts are identified, migrated, and tested before choosing an implementation approach. Done means versioned fixtures cover safe migration, preservation and reporting of unknown files, dry-run output, verification before removal, and idempotent repeated upgrades.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Problem
An upgraded Squad repository can retain artifacts from older layouts that a fresh squad init no longer creates. Stale skills or instructions can still be discovered and influence agent behavior, while the repository remains structurally different from a fresh install.
In one observed upgrade, the existing repository retained 21 folders and 24 tracked files under .copilot/skills, while a fresh init had no .copilot/skills directory. The installed upgrade migration only moves legacy skill names listed in TEMPLATE_MANIFEST; other entries are intentionally left behind to avoid deleting user content. This protects unknown files, but leaves old Squad artifacts and user-added skills indistinguishable in a deprecated location.
Expected behavior
Squad should track the lifecycle of artifacts it manages, rather than relying on filesystem comparisons or broad deletion. A machine-readable manifest could record each artifact's ownership, introduced version, canonical location, migration target, and retirement policy.
During squad upgrade, Squad should:
- Identify known Squad-managed artifacts that are obsolete, moved, or need refresh.
- Migrate managed content to the canonical location, verify the destination, then remove the old managed copy.
- Preserve unknown or user-owned content and report conflicts instead of guessing.
- Make
--dry-runlist planned moves, updates, and removals, with the reason for each. - Converge idempotently, so repeated upgrades do not leave managed artifacts drifting between layouts.
Acceptance criteria
- A legacy-install fixture with versioned managed files upgrades to the current canonical layout without leaving obsolete managed copies.
- A fixture with unknown or user-owned files at a deprecated path preserves them and reports the unresolved content.
- A dry run reports every planned artifact action without changing files.
- Upgrade verifies successful migration before removing a managed source file.
- Re-running upgrade produces no further changes.
This is distinct from #2047, which covers stale .squad/templates/skills and workflow snapshots, and builds on the versioned layout manifest proposal in #670. #1126 covers a prior skills-path migration, but not lifecycle tracking and safe retirement of artifacts from older layouts.
- Linguagem predominante
- TypeScript
- Estrelas
- 3.4k
- Forks
- 516
- Merge médio
- 1d 15h
- PRs com merge (30d)
- 116
Preparar o ambiente
- Inclui um Dockerfile ou arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de github/squad
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 84/100
Mantenedores costumam responder em até 1 dia
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 77/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
Mantenedores costumam responder em até 1 dia
Todas as issues de github/squad
Issues semelhantes
-
area: batch
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
inabagumi/shinju-date#7294 ·
Mantenedores costumam responder em até 1 dia
-
documentation
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
streaming-video-technology-alliance/common-media-library#700 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
vercel-labs/ui#809 ·
Mantenedores costumam responder em até 1 dia
-
enhancement
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 67/100
KrisCris/village-in-the-shade-guide#75 ·
Mantenedores costumam responder em até 1 dia
-
bot:ai-assisted component:platform-js status:untriaged
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 74/100
midnightntwrk/platform-js#38 ·