Always investigate and remediate Dependabot/security alerts in the getsentry/craft repository before implementing fixes

The user consistently directs dependency and security work in the getsentry/craft repo, including analyzing open Dependabot alerts and fetching GitHub security advisories/alerts to plan remediation. When the user mentions security reports, advisories, or Dependabot alerts without specifying a repo, assume getsentry/craft. Gather the current alert data (e.g. via gh api for security-advisories and dependabot/alerts), map vulnerable packages to required version bumps, and present a remediation plan prior to editing files or running upgrades.