Evergreen deprecation workflow

Use Evergreen outputs as the source of truth. This workflow requires the Evergreen CLI or local MCP server and needs no account or API key. Prefer MCP tools when available; use the CLI mapping below when the host cannot connect to MCP. Keep detection, migration constraints, and verification logic in Evergreen rather than recreating them from these instructions.

Workflow

1. Discover. Run a fresh repository scan. Select an exact finding ID from the result. This step is complete when the target finding and its current repository path are known.
2. Explain. Fetch the full finding and inspect its rule, location, impact, and authoritative sources. This step is complete when the lifecycle evidence and migration scope are understood.
3. Migrate. Create migration context for that finding. Follow its constraints and ordered steps, preserve behavior at every listed usage, and account for each affected file. Inspect suggested commands before running them under the host's normal authorization rules.
4. Verify. Run relevant project checks, then perform a fresh Evergreen verification. With MCP, verify the finding in the same session that observed it. This step is complete when the finding is absent, required checks pass, and any scope beyond the packet is explained.

Tool mapping