Returns: project name, file/LOC/symbol counts, detected package manager,
config files, entry points, test setup, notable frameworks, and a per-top-level
-package size map (files/LOC/classes/functions).

Do NOT use for finding a specific symbol or file — use find_symbol or
get_file_outline for that.

Returns each definition's kind, qualified name, and 'path:line'. With
include_body=True, also returns the full source of each match. If nothing
matches you get 'did you mean' suggestions.

Do NOT use to find usages/call sites — use find_references. Do NOT use for
free-text search — use search_code.

Resolution is scope/import-aware name matching, not full type inference — very
accurate for module-level functions/classes; methods may include same-named
calls on unrelated types. Use find_symbol to see where it is defined instead.

Returns an indented tree of qualified names with 'path:line'. Recursion and the
depth limit are marked inline. Shares the name-resolution precision tradeoff of
find_references.

Returns two indented trees with 'path:line'. External bases (e.g. pydantic
BaseModel) appear as leaves marked external/unresolved.

Returns file:line plus the matching line (lexical) or matched symbol (semantic).
Use this when you do NOT know the exact symbol name. Prefer find_symbol /
find_references when you DO — they are structural and far more precise.

Provide start_line/end_line to get blame for a specific region. Requires the
repo to be a git checkout.

If 'target' is a test file path, returns the modules/symbols it pulls in.
Otherwise treats it as a symbol name and returns the test files + test_*
functions that reference it. Use before changing code to know what to run.