Module mode_detection 

Request-shape validation for the having-range query, and the versioned (select, group_by, having, order_by, limit) → DocumentHavingMode resolution — including the operator → inclusive-bounds translation that turns a HAVING <agg> <op> <value> clause into an AxisRangeBounds.

Pure functions on the request shape — no Drive, no contract, no indexes. Available under server and verify for the same reason as super::super::drive_document_ranked_query::mode_detection: both sides must agree on which requests are well-formed and on the exact bounds a well-formed one resolves to, because the verifier rebuilds the bounded traversal from those bounds and re-executes the proof against it.

Versioned through platform_version.drive.methods.document.query.detect_having_mode — the accepted grammar is a consensus-adjacent contract on the query surface, so relaxing it later (multi-clause HAVING, IN, a pagination cursor) lands behind a method-version bump.

Functions

detect_having_mode

Versioned entry point. Routes through platform_version.drive.methods.document.query.detect_having_mode; today only 0 is defined and maps to detect_having_mode_v0 verbatim.

detect_having_mode_v0

v0 of the having-range request grammar.