[milindsrivastava1997]

Why

The private corpus (ASAPPlanner-private-corpus) #[path]-included crates/frontend-promql/tests/support.rs and kept its own Cargo.toml dependency list. Whenever support.rs started importing a new crate or feature-gated module, public CI stayed green and the private nightly broke the next morning. That happened twice in a week: asap-types test-support (private #4/#5), then logical-asap-optimization::test_support after #1108.

What

Moves the test runner into public; the private repo keeps only the queries.

• crates/frontend-metricsql/tests/external_corpus.rs: lowers and binds every query in every *.txt under $ASAP_EXTERNAL_CORPUS_DIR, checks that nothing panics, nothing that lowers fails to bind, and each file's lowered count stays at or above its # floor: N line. Prints failure causes by count. Skips when the env var is unset, so CI compiles it on every PR but needs no data.
• Includes support.rs (for logical_plan) via #[path] in the metricsql test binary, and adds asap-logical-asap-optimization (test-support) as a dev-dependency. A future support.rs import change now fails here, in the PR that makes it.

Run locally:

ASAP_EXTERNAL_CORPUS_DIR=<private-corpus>/data cargo test -p asap-frontend-metricsql --test metricsql external_corpus:: -- --nocapture

Testing

• With the env var unset: skips and passes.
• Against the private data: passes with the same floors as before.
• Raising one floor to 999: fails as expected.
• Workspace clippy --all-targets --all-features -D warnings: clean.

Companion PR in ASAPPlanner-private-corpus (chore/data-only); merge this one first, since that repo's CI runs against public main.

Note: the pre-commit cargo test failed once on two asap-devtools stage_pipeline tests ("MILP solver: execution-scope expansion exceeded the deadline"). They're timing-sensitive under full-suite load and pass in isolation; they're unrelated to this change.

🤖 Generated with Claude Code