perf-code-paths

Identify likely implementation paths for a performance scenario.

Follow docs/perf-requirements.md as the canonical contract.

Required Steps

• Use repo-map if available; otherwise use grep for entrypoints and handlers.

• List top candidate files/symbols tied to the scenario.

• Include imports/exports or call chains when relevant.

Output Format

keywords: <comma-separated list> paths:

• file: <path> symbols: [<symbol1>, <symbol2>] evidence: <short reason>

Constraints

• Focus only on supported languages (Rust, Java, JS/TS, Go, Python).

• Keep to the most relevant 10-15 files.