[zzylol]

Base: main. Unblocks the comparison run's quantile queries.

Why

The first comparison run showed the backend refusing every quantile query: at the pinned ASAPPlanner ecea897f, KLL and DDSketch had no accuracy guarantee when raw_data_retained=false. ASAPPlanner #780 fixes this, so the backend needs a new pin.

What

• Pin: both Planner crates move to ASAPPlanner 7565c47e. Compared with ecea897f, that adds:
  • [Deferred] test: validate accuracy evidence independently of candidate costs #777: rate, increase and irate of a declared counter become non-negative Count-Min weights;
  • fix(control-plane): give the snapshot schema version one owner #782: the SQL and MetricsQL frontends become optional cargo features;
  • fix(control-plane): reject cost evidence quoting another dataset #780: a gauge declared non-negative (SourceFacts::values_non_negative) lets a per-series quantile sketch's relative error carry through sum and avg, and a quantile estimate carries the sign of its samples.
• Frontends: asap-planner is now a dependency with default-features = false, features = ["promql"]. DataFusion and the SQL and MetricsQL frontends drop out of the build, and Cargo.lock shrinks by about 1,850 lines.
• Sync script: scripts/sync-asapplanner-main.sh now accepts a pin followed by other keys, such as features.
• Not in this PR: ASAPPlanner refactor: route precompute outputs on StoredOutputId, not a bare u64 #787 (StoredOutput.coverage and inputs replace pane; the plan's definition id) is not included. Adapting the SDS to it needs the plan's full selection in the summary-instance key, because outputs with the same definition but different label constraints share one definition id. That comes in the next PR.

How

The rev and the asap-planner features change in Cargo.toml, followed by cargo update -p asap-planner -p asap-executor. No backend source changes: the API the backend uses is the same at 7565c47e.

Before this PR

Pinned to ecea897f. Without raw data, quantile queries got no sketch guarantee and were refused, and the build included DataFusion.

After this PR

Pinned to 7565c47e, which includes the sign and non-negative-gauge fixes; PromQL frontend only.

A workload benefits from #780 only when it declares its gauges in data_workload.sources, with "metric_type": "gauge" and "values_non_negative": true. The harness workloads need that.

Verification

• cargo test --workspace --locked passes, including the e2e examples.
• python3 -m unittest discover -s scripts/ci: the sync-script tests pass, including the real-manifest test with the features key.
• Cargo.lock has no datafusion entry.