feat(asapquery-profile): cover the complete ASAPQuery PromQL acceleration matrix

[zzylol]

Summary

Raise the backend-local asapquery profile from its four-case MVP matrix to the complete accelerated PromQL surface documented and tested by current ASAPQuery.

Current gap

The backend profile's executable matrix currently proves only rate, increase, sum_over_time, and quantile_over_time for instant/range queries. ASAPQuery additionally accelerates:

• temporal count_over_time, avg_over_time, min_over_time, max_over_time;
• spatial sum, count, avg, min, max, quantile, and topk, with optional by(...);
• the six safe temporal/spatial compositions currently recognized by ASAPQuery: sum(sum_over_time), sum(count_over_time), min(min_over_time), max(max_over_time), topk(sum_over_time), and topk(count_over_time);
• arithmetic trees over acceleratable leaves using + - * / ^ %, including scalar/vector arms;
• both instant and range evaluation, including sliding-window composition and a query lookback wider than the materialized pane/window.

ASAPQuery's README intentionally excludes label selectors from this accelerated profile, and vector-matching modifiers are explicitly out of scope in its arithmetic design; those are not requested here.

Scope

• Add every listed shape to backend-local planning, physical compilation, precompute, QueryPlan execution, and readiness coverage.
• Preserve Prometheus labels, timestamps, range steps, counter reset/extrapolation semantics, Top-K ordering/labels, and arithmetic behavior.
• Use the canonical ASAPPlanner IR and selected summary plan; do not restore the historical ASAPQuery planner.
• Fail closed to exact Prometheus fallback whenever any leaf/operator cannot be accelerated safely.
• Version and document the expanded compatibility level.

Acceptance criteria

• A table-driven conformance suite runs every family through both /api/v1/query and /api/v1/query_range, comparing against Prometheus and asserting data_source: warm.
• Arithmetic covers all six operators, nested trees, scalar-vector/vector-scalar/vector-vector, divide-by-zero/NaN behavior, and whole-query fallback on an unsupported arm.
• Sliding and wider-lookback cases cover aligned and misaligned steps without double-counting panes.
• Existing focused gaps remain linked rather than duplicated: Exact TopK (accuracy: Exact) has no warm-tier materialization -- always falls to archive #432 (exact Top-K), SummaryExecutor: permanent self-exclusions + upstream composition gaps leave some PromQL shapes always on the legacy/archive path #436 (composition/SummaryExecutor exclusions), PromQL range warm path ignores step_ms and differential E2E does not detect it #487 (range step handling), and Small-sample quantile_over_time p99 diverges from Prometheus interpolation semantics #492 (small-sample quantile semantics).

[zzylol]

ASAPQuery PromQL PR audit → executable matrix

Audited all ASAPQuery PRs and excluded SQL/Elasticsearch. The matrix is grouped by behavior rather than duplicating every literal metric name.

Warm rows already proved by the backend process E2E

• rate(m[w]), increase(m[w]) — Small-sample quantile_over_time p99 diverges from Prometheus interpolation semantics #492, fix(clickhouse): preserve nulls in query results #657, Add canonical versioned label population keys #663, Preserve Planner aggregate semantics through maintenance and serving #700, Add offline cluster data exporter tool #704
• sum_over_time(m[w]), quantile_over_time(phi,m[w]) — test(e2e): controller → backend streaming-config round-trip + grouping plumb #247, Preserve Planner aggregate semantics through maintenance and serving #700
• topk(k,sum_over_time(m[w])), topk by(labels)(k,count_over_time(m[w])) with explicit value/count heap modes — feat(promql): support topk over sum_over_time/count_over_time (ASAPQuery #706 parity) #502 / ASAPQuery Lookback vs PromQL range selector: redundant window concepts (+ /query_range readout bug) #706/[Refactor] Centralize planner and backend accuracy formulas #707, implemented by PR fix(promql): bind temporal TopK update semantics on the shared workload plan #505
• every warm row is exercised through instant and range endpoints

Rows that compile but still need process-level parity promotion

• temporal: count_over_time, min_over_time, max_over_time
• spatial: sum, sum by, min, max, quantile
• safe compositions from ASAPQuery Unify workload selection for startup and distributed publication #518/Preserve Planner aggregate semantics through maintenance and serving #700: sum(sum_over_time), sum(count_over_time), min(min_over_time), max(max_over_time)
• TopK k representatives 1/3/5/10 from Preserve Planner aggregate semantics through maintenance and serving #700

These remain in this umbrella until they are added to the canonical startup snapshot and asserted warm against Prometheus.

Executed fallback rows and owners

PR #506 now sends these through the production binary and asserts atomic fallback:

• avg_over_time, spatial count, spatial avg → feat(promql): compile and execute count/avg aggregation families from the ASAPQuery matrix #503
• raw-value topk(k,m) / exact TopK → Exact TopK (accuracy: Exact) has no warm-tier materialization -- always falls to archive #432
• arithmetic leaf op leaf, leaf op scalar, all + - * / % ^, nesting and labels → feat(promql): execute binary arithmetic over warm summary readouts #504 + feat(promql): retain summary leaves under binary arithmetic plans ASAPPlanner#343; derived from ASAPQuery fix(query): dispatch Vector vs Matrix in asap_tier_result_to_query_result #256/Type physical plan references as summary definitions #572/feat: compose ClickHouse exact subtrees with summaries #577/Make completed summary windows immutable after durable flush #644
• wider lookback over materialized panes → feat(control-plane): realize Planner window candidates and feed back costs #473; derived from feat(control-plane): require complete plan publication #466/chore(parser): pin backend PromQL parser revision #603/fix: propagate DDSketch delta admission errors #621/Rotate retired physical series on catalog reactivation #640

Independent correctness gates (existing issues)

• range step/output timestamps: PromQL range warm path ignores step_ms and differential E2E does not detect it #487 (Execute external exact work through QueryPlan DAG edges #582/Evaluate 27 ClickHouse SQL queries on current main #595/chore(parser): pin backend PromQL parser revision #603/test(clickhouse): measure automatically selected SUM and MAX plans #629/fix(erp): validate readouts against existing state evidence #635)
• small-sample quantile interpolation: Small-sample quantile_over_time p99 diverges from Prometheus interpolation semantics #492
• exact/summary composition: SummaryExecutor: permanent self-exclusions + upstream composition gaps leave some PromQL shapes always on the legacy/archive path #436 + Compose exact operators with summary plans across explicit update/readout boundaries ASAPPlanner#171
• millisecond window precision: covered by the window-realization work in feat(control-plane): realize Planner window candidates and feed back costs #473 (ASAPQuery backend-plan: construct BackendPlan from BackendStageConfig (Phase 1) #437/fix(control-plane): preserve query semantics through physical planning #449)

Selectors and vector-matching modifiers remain out of the ASAPQuery accelerated contract; Elasticsearch is intentionally excluded per scope.