test: cover CCM anomaly v2, ai-evals drift, and schema sync regressions

[cursor]

Description

Adds regression tests for recently merged production changes that lacked focused coverage:

Risky behavior now covered

1. CCM cost anomaly v2 API (PR Anomaly tools - Drilldown and upgrade to v2 APIs #533)

   • anomalyListExtract maps v2 { data: [...] } array responses to { items, total } without envelope leakage
   • cost_anomaly list bodyBuilder defaults, explicit time range, ordering, and min_amount: 0 (!= null guard)
   • cost_anomaly_drilldown pathBuilder routes details vs time-series endpoints
   • Registry dispatch round-trips verify v2 paths and __skipCompact marker survival

2. AI Evals control-plane alignment (PR fix(ai-evals): correct toolset drift against control-plane API #529)

   • eval_metric create requires dimension
   • eval_annotation create/update expose thumbs_up
   • online_eval evaluate uses metric_set_id + judge_llm_connector_ref (not deprecated metric_ids)
   • Dispatch proves metric_set_id reaches the API body

3. DeployGoogleAgentRuntimeRevision schema sync (PR chore: auto-sync harness schemas #534) — already on branch

   • Bundle contract asserts step definitions in v0 pipeline/template
   • harness_schema resolves DeployGoogleAgentRuntimeRevisionStepNode

Test files added/updated

• tests/registry/ccm-anomaly.test.ts (new)
• tests/registry/ccm-extractors.test.ts
• tests/registry/ai-evals.test.ts
• tests/schemas/schema-bundle-contract.test.ts
• tests/tools/harness-schema-tool.test.ts

Why these tests materially reduce regression risk

• Anomaly v2 migration changes endpoint paths, request body shape, and response extraction — silent breakage would return empty lists or wrong drill-down URLs
• AI Evals schema drift would cause validation failures or wrong API payloads if metric_ids/dimension contracts regress
• Schema sync tests catch upstream step definition drops before agents generate invalid pipeline YAML

Type of Change

• Bug fix
• New feature
• Refactor
• Documentation
• Other (test coverage)

Checklist

• pnpm test passes (targeted suites)
• pnpm typecheck passes
• pnpm build passes
• pnpm standards:check passes
• pnpm docs:check passes

  

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ thisrohangupta
❌ cursoragent
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[thisrohangupta]

Closing: superseded by merged #533 (CCM anomaly v2), #530 (AI evals API fields), and #535 (schema sync) — all already on main.

Triaged as part of an open-PR cleanup pass. If this was mis-triaged, reopen and rebase onto current main.