Reproduction
On current main (ea544d88405590eb91b5132eb73ef28546b6b0f3):
skills/manifest.json lists vs-product-qa/references/delegation.md.skills/vs-product-qa/SKILL.md links to that file in three places.- The file is not present in the Git tree, so installed source-tree skills have a broken delegation reference.
- On an LF checkout,
npm run generate:embedded-skills also changes the embedded vs-product-qa and vs-shared entries, showing that the checked-in bundle is stale relative to its source files.
The missing file was removed while the product-QA reference tree was reorganized in #45; its callers and manifest entry remained. I also searched all-state issues, PR titles/bodies, and repository history and found no existing report or pending fix.
Expected behavior
Every manifest-listed reference should exist, and regenerating embedded skills from a clean checkout should produce no diff. Restoring the delegation matrix and regenerating the bundle would keep both source-tree and packaged installs coherent.
Reproduction
On current
main(ea544d88405590eb91b5132eb73ef28546b6b0f3):skills/manifest.jsonlistsvs-product-qa/references/delegation.md.skills/vs-product-qa/SKILL.mdlinks to that file in three places.npm run generate:embedded-skillsalso changes the embeddedvs-product-qaandvs-sharedentries, showing that the checked-in bundle is stale relative to its source files.The missing file was removed while the product-QA reference tree was reorganized in #45; its callers and manifest entry remained. I also searched all-state issues, PR titles/bodies, and repository history and found no existing report or pending fix.
Expected behavior
Every manifest-listed reference should exist, and regenerating embedded skills from a clean checkout should produce no diff. Restoring the delegation matrix and regenerating the bundle would keep both source-tree and packaged installs coherent.