memtrace-preflight

## Overview Pre-flight check: the two minutes before an edit that prevent the bug. One `preflight_check` call composes the dependency graph, the bi-temporal change history, and the complexity metrics into an actionable radar for a single symbol. ## Quick Reference | Tool | Purpose | |------|---------| | `preflight_check` | Full radar for one symbol: blast radius + co-change + churn + checklist | | `get_impact` | Deeper blast-radius walk when the radar flags HIGH/CRITICAL | | `get_cochange_context` | Wider co-change window when partners look surprising | | `recall_decision` | Recorded choices, bans, and conventions for the symbol/subsystem/behavior | | `why_is_this_here` / `governing_contracts` | Symbol-scoped rationale and constraints when a symbol id is available | > **Parameter types:** MCP parameters are strictly typed. Numbers must be Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bundled at the memtrace-skills plugin root). > JSON numbers — not strings. ## Steps ### 1. Run the pre-flight check before touching the symbol `preflight_check` with: - `repo_id` — required - `symbol` — the function/method name you are about to modify ### 2. Read the checklist — it is generated from the graph, not boilerplate Each line names something concrete to verify: - *"N symbols depend on this"* → run `get_impact` again after your edit and compare `total_affected`; new dependents mean your change leaked wider than intended. - *"hotspot: N changes...