Skip to content

chore(collections): rename security-planning collection to security #792

@katriendg

Description

@katriendg

Summary

Rename the security-planning collection to security to broaden the scope from planning-only to the full security domain (review, planning, incident response, risk assessment, vulnerability analysis).

This is a pre-condition for all other MVP security reviewer work. Breaking change — acceptable per copilot-instructions.md.

Acceptance Criteria

  • collections/security-planning.collection.yml renamed to collections/security.collection.yml
    • id: security, name: Security, updated description and tags
    • All path: entries updated from security-planning/ to security/
    • Collection level maturity set to experimental
  • collections/security-planning.collection.md renamed to collections/security.collection.md
    • Content updated to reflect broader security domain scope
    • Includes [!CAUTION] disclaimer about AI-generated security artifacts
  • .github/agents/security-planning/ moved to .github/agents/security/
    • security-plan-creator.agent.md preserved at new path
  • .github/prompts/security-planning/ moved to .github/prompts/security/
    • incident-response.prompt.md and risk-register.prompt.md preserved at new paths
  • collections/hve-core-all.collection.yml updated (all paths from security-planning/ to security/)
  • extension/package.security-planning.json renamed to extension/package.security.json
    • name updated to hve-security, displayName updated to HVE Core - Security
  • extension/README.security-planning.md renamed to extension/README.security.md (if exists)
  • Old plugins/security-planning/ directory removed
  • npm run plugin:generate produces plugins/security/ successfully
  • npm run plugin:validate passes
  • npm run lint:all passes with no regressions
  • No references to security-planning remain in the codebase (search verification)

Context

Discussion #480 consensus: collection scope broadens from "planning" to full security domain. All active participants (katriendg, obrocki, JasonTheDeveloper) agreed. Related to #643 (collection-based directory reorg, mostly implemented) — not a prerequisite but coordinate timing.

Files to Change

Action Path
Rename collections/security-planning.collection.ymlcollections/security.collection.yml
Rename collections/security-planning.collection.mdcollections/security.collection.md
Move .github/agents/security-planning/.github/agents/security/
Move .github/prompts/security-planning/.github/prompts/security/
Update collections/hve-core-all.collection.yml (path references)
Rename extension/package.security-planning.jsonextension/package.security.json
Rename extension/README.security-planning.mdextension/README.security.md
Regenerate plugins/security/ (via npm run plugin:generate)
Delete plugins/security-planning/

Related Issues

Complete this issue before starting the following MVP security reviewer work:

Metadata

Metadata

Assignees

Labels

breaking-changeBreaking change requiring major version bumpmaintenanceMaintenance work, no version bumpsecuritySecurity-related changes or concerns

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions