scope-analysislisted

# Scope Analysis Delimit whether the target is a class, package, or module, then keep the plan inside that boundary. ## How to inspect - Identify the primary target file(s). - Find public methods, exported APIs, public constructors, endpoints, and events. - Find callers/consumers with references, imports, routes, LSP, or a code-graph index (for example, Graphify MCP/CLI) when available. - Find existing tests by naming, package, fixtures, integration suites, and build metadata. - Separate in-scope files from neighboring context. - Record out-of-scope work explicitly.