feature: track managed artifact lifecycle and clean obsolete paths on upgrade
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 30/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 3.4k
- Forks
- 516
- Merge medio
- 1 d 15 h
- PR fusionados (30 d)
- 116
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de github/squad
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
Todos los issues de github/squad
Issues similares
-
bot:ai-assisted component:platform-js status:untriaged
Dificultad 1/5 Menos de una hora Aptitud para principiantes 74/100
midnightntwrk/platform-js#38 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
ranxianglei/billion-context#7068 ·
Los mantenedores suelen responder en 1 día
-
vendor: bump whisper.cpp past 6a8addd — the current pin aborts the app on a failed Metal initAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
mybigday/whisper.rn#348 ·
-
enhancement severity:low
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Battle-Cattle/BCUK-Bot-4#1075 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
ilan-pinto/roaring-lions#1552 ·
Los mantenedores suelen responder en 1 día