Description
PR #980 (ff351aad) renamed the security-planning collection to security. Subsequently, PR #979 (06f826ca) incorrectly re-created security-planning as a separate collection to house SSSC Planner artifacts, instead of adding those artifacts to the existing security collection.
This results in duplicate collection manifests and a security-planning extension in the marketplace that should not exist.
Expected Behavior
All security-related artifacts (Security Planner, SSSC Planner, RAI Planner, and their prompts/instructions) should be in the security collection. There should be no security-planning collection.
Required Changes
- Move all files from
.github/{agents,prompts,instructions}/security-planning/ and .github/instructions/sssc-planning/ to .github/{agents,prompts,instructions}/security/
- Update all path references in collection YAMLs, agent files, and documentation
- Delete
security-planning collection manifests and plugin outputs
- Remove
security-planning entry from marketplace.json
- Regenerate plugins
Description
PR #980 (
ff351aad) renamed thesecurity-planningcollection tosecurity. Subsequently, PR #979 (06f826ca) incorrectly re-createdsecurity-planningas a separate collection to house SSSC Planner artifacts, instead of adding those artifacts to the existingsecuritycollection.This results in duplicate collection manifests and a
security-planningextension in the marketplace that should not exist.Expected Behavior
All security-related artifacts (Security Planner, SSSC Planner, RAI Planner, and their prompts/instructions) should be in the
securitycollection. There should be nosecurity-planningcollection.Required Changes
.github/{agents,prompts,instructions}/security-planning/and.github/instructions/sssc-planning/to.github/{agents,prompts,instructions}/security/security-planningcollection manifests and plugin outputssecurity-planningentry from marketplace.json