devql-explore-first

# DevQL Explore First <VERY_IMPORTANT> For code understanding and exploration, DevQL is the primary discovery tool, not a one-time preflight. Use `bitloops devql query ...` whenever locating symbols, files, tests, implementations, callers/usages, or the next source region to inspect. </VERY_IMPORTANT> Do not use `sed`, `rg`, `grep`, `find`, `wc`, directory crawling, or broad source-file reads to discover task-relevant code while DevQL can answer the lookup. Use traditional tools only to: - read bounded ranges returned by DevQL - inspect files you are editing after DevQL selected them - run tests or git/status commands - fall back when DevQL fails, is empty, or contradicts the task Do not run `bitloops devql --help` or `bitloops devql query --help`. Choose the most specific selector: - known `symbolFqn`: use `symbolFqn` - known file or file range: use `path`, optionally with `lines` - single concrete identifier, method name, literal, error code, path-like string, or copied snippet: use `searchMode: LEXICAL` - architecture role terms such as API endpoint, command handler, repository, adapter, or boundary: use `searchMode: ARCHITECTURE` - multiple related terms, behavior, concept, or task keywords without one exact anchor: omit `searchMode` and use default `AUTO` Fuzzy symbol-name lookup is included in the lexical lane; do not use a separate fuzzy selector. Use compact exploration queries. If the prompt has no concrete anchor, start with the default `AUTO` query: ...