validate-change-planlisted

# Validate Change Plan Use only the eight tools in the `core` profile. Do not present this workflow as equivalent to the full profile's PRD validator, security gates, or semantic-diff verifier. For Rust caller or impact questions, request `lsp: true` in `analyze_codebase` and make rust-analyzer available. Inspect `lsp_status.state`: `disabled` means static-only analysis; `failed` means analysis continued and may retain partial LSP results. Record the error and treat affected conclusions as unverified until source checks or a successful rerun support them. `completed` means the pass returned, not that every call resolved. Record unresolved sites and coverage gaps. If a full-profile workflow supplies a `check_security_gates` receipt, inspect both `gates_passed` and `report.assessment_complete`. A true pass with an incomplete assessment is not security clearance: report skipped checks, unresolved symbols and warnings. This core-profile workflow does not invoke that additional tool. ## Workflow 1. Break the plan into falsifiable claims: files exist, symbols exist, dependency directions are correct, named boundaries match communities or processes, and the stated blast radius is plausible. 2. Call `health_check`, then build or refresh the graph with `analyze_codebase`. Reuse the returned `graph_path`. 3. Resolve each named symbol with `search_codebase`, then verify it with `get_symbol` or `get_context`. Mark ambiguous or missing names as unverified instead of choosing a conven