cce-routing

# CCE Routing `cursor_context_engine` automatically inherits the persistent CCE model and reasoning-effort default configured through `cursor_model`. Do not change or reset that default unless the user explicitly asks; if selection cannot be confirmed, report the pre-send failure instead of retrying with Auto. Route project-understanding questions to the cheapest evidence surface that can answer them without guessing. ## Choose CCE for project semantics Call `cursor_context_engine` when one or more of these are true: - The implementation location is unknown and finding it locally would require guessing directories or repeating broad searches. - The question asks where or how a project behavior is implemented, what owns a state or responsibility, or why a flow behaves as it does. - The answer requires tracing callers and callees, producer-consumer flow, configuration and registration, interface implementations, data ownership, or relationships across modules. - An unfamiliar indexed project needs semantic context before a safe edit or review can begin. Prefer one CCE investigation over starting an Explore subagent merely to locate or understand project code. Let Cursor choose focused or extended depth from what it discovers. When these semantic conditions match, make CCE the first project-discovery surface. Do not establish the answer through generic context-mode, grep, or blind local exploration before trying CCE. If Claude Code denies an initial context-mode collectio...