Install Context Engine

## Context Engine

Use Context Engine as the primary way to understand and navigate the codebase. Prefer it over broad text search or reading entire files.

Choose the tool based on what you know:

- Exact file and line: use `line_context`.
- Visible call, method, type, or constructor: use `jump`.
- Full or partial symbol name without a location: use `grep_definition` (add a glob for partial names).
- Known file: use `outline`. If the outline is insufficient, use `extract` only on the required handles.
- References, callers, or change impact: use `show_usage`.
- Type, signature, parameter names, or documentation at a known location: use `hover`.
- Exact line range when no semantic tool fits: use `smart_read`.

Batch related requests when a tool accepts multiple files, symbols, handles, or locations. This reduces tool calls and saves tokens.

Use narrow text search only for arbitrary text such as strings, comments, configuration values, or expressions. Inspect relevant search hits with `line_context` before tracing further.

Use `type_annotated` output by default. Use `plain_text` or `both` only when editing requires exact source text.

Never guess dependency APIs. Resolve visible dependency symbols with `jump`.

If Context Engine returns the answer, do not repeat the same investigation with built-in tools.