feature: track managed artifact lifecycle and clean obsolete paths on upgrade

未關閉
#2,232 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
30/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
typescript
領域
cli, devtools

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

wave:1-next wave1:P2

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-run list 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.

主要語言
TypeScript
星號
3.4k
分支
516
平均合併
1 天 15 小時
30 天內合併 PR
116

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

github/squad 的其他 Issue

查看 github/squad 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。