dependency-checklisted

# Dependency Vulnerability Resolution When invoked, follow this four-phase workflow to identify and clear dependency CVE vulnerabilities for the current repository branch. ## Phase 1: Assess Gather repository context and fetch the vulnerability report with inline upgrade advice. 1. Determine the `repositoryName` and `branchName`: **`repositoryName`** — the repository name in `owner/repo-name` format (e.g., `organisation/my-project`). The server is case-insensitive and handles `.git` suffixes automatically. **`analysisName`** *(optional)* — if the repository is a mono-repo with multiple analysis projects, provide the analysis project name to disambiguate. Case-insensitive. Leave empty for single-project repositories. **`branchName`** — run this shell command: ```bash git branch --show-current ``` This returns the `branchName`. 2. Call `get_dependency_vulnerabilities` with `repositoryName`, `branchName`, and optionally `analysisName`. The response includes inline upgrade advice for each dependency: `NextSafeVersion`, `LatestVersion`, `UpgradeRisk`, and `CurrentVersionIsDeprecated`. 3. If the result contains zero vulnerabilities, report that no dependency vulnerabilities were found and stop. 4. Present a brief summary to the user: total vulnerable dependencies, highest risk score, count by ecosystem, and how many have an available safe upgrade. ## Phase 2: Locate Manifests Search the workspace for dependency manifest files so upgrades can be applied. Look for these