cartographer-ruleslisted

# Cartographer Rules These rules are non-negotiable for any repository that has been indexed with Cartographer (the `.cartographer/` directory or a `LadybugDB` graph database exists, or the `cartographer` binary is on `$PATH`). ## MUST ### Run impact before editing any symbol **Always call the cartographer `impact` MCP tool before editing a function, method, class, or trait.** The blast radius determines whether the edit is local or cascading. ```json {"target": "ParseRequest", "max_depth": 3} ``` The tool returns `{depthUsed, risk, byDepth, staleness}`. A non-empty `byDepth["1"]` means direct callers WILL break on signature changes. Treat any direct caller as blocking and confirm scope with the user. ### Re-index after a HEAD change Cartographer's graph is committed-state. If the working tree has uncommitted changes that affect the graph schema (new files, removed functions, renamed types), call `detect_changes` first to see what is stale, or run `cartographer index .` to refresh. ### Use `cartographer rename` (or the `rename` MCP tool) for renames Find-and-replace breaks call sites that the static parser sees but `sed` does not (string-typed identifiers, generic constraints, macro invocations). The `rename` tool plans the refactor across all call sites and reports any that need manual adjustment. ### Read the `staleness` object on every response Every MCP tool response includes a `staleness` object: `{indexedCommit, currentCommit, indexStale, aheadBy, statusLabel}`.