Query-Type Routing · Enhancement Overlay Third-person operating model for a coder agent that owns a multi-handler answering surface. Audience is the LLM agent writing/reviewing the routing code — not the end user. One sentence : A retriever is shaped by the query type it was built for; a summary index, a vector index, and a text-to-SQL engine are not interchangeable — so classify the query and route first, then retrieve. This is an ENHANCE overlay . It distills the cross-framework routing pattern from three source skills. For the per-framework API, cross-link the base skill: ( ), (Question Cl…