test: skip Voxtral integration tests in CI

[tsavo-at-pieces]

Summary

• Skip Voxtral integration tests when running under CI/Cloud Run to avoid metadata.google.internal ADC lookup failures.
• Uses group(..., skip: reason) so tests are still discovered (CI does not fail with "No tests found").

Test plan

• CI=true dart test

[cursor]

PR Summary

Low Risk
Test-only change that conditionally skips integration tests based on environment variables; no production code paths or data handling are affected.

Overview
Voxtral integration tests are now skipped automatically in CI/Cloud Run environments by detecting CI/GCP runtime env vars via Platform.environment.

The tests are wrapped with group(..., skip: reason) so they remain discoverable while avoiding ADC/VPN-dependent failures in automated environments.

^{Written by Cursor Bugbot for commit 8da59bf. Configure here.}

[Copilot]

Pull request overview

Skips the Voxtral integration test group when running in CI/Cloud Run-like environments to avoid failures caused by ADC/metadata lookups.

Changes:

• Add _isCiOrCloudRun() helper to detect CI/Cloud Run via environment variables.
• Apply group(..., skip: reason) so Voxtral integration tests are discovered but skipped in CI.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

_isCiOrCloudRun() treats the mere presence of PROJECT_ID / GCP_PROJECT_ID as “CI/Cloud Run”. Those env vars are not Cloud Run–specific and can be set in local dev shells, which would cause these integration tests to be skipped unexpectedly. Consider narrowing the Cloud Run detection to Cloud Run–specific vars (e.g. K_SERVICE) and/or renaming the helper to match the broader condition.

Suggested change

	env.containsKey('K_SERVICE') || // Cloud Run
	env.containsKey('PROJECT_ID') ||
	env.containsKey('GCP_PROJECT_ID');
	env.containsKey('K_SERVICE'); // Cloud Run

[Copilot]

CI detection currently only skips when CI is exactly 'true' (case-insensitive). Some environments set CI=1 or other truthy values, which would still run these tests in CI and reintroduce the ADC/metadata failures this PR is addressing. Consider treating any non-empty CI value as CI, or explicitly allowing '1'/'yes' as well.

Suggested change

	final ciValue = env['CI']?.toLowerCase();
	return ciValue == 'true' ||
	final ciValue = env['CI']?.toLowerCase() ?? '';
	final isCi = ciValue.isNotEmpty && ciValue != 'false' && ciValue != '0';
	return isCi ||

[tsavo-at-pieces]

Addressed the review notes: removed / from detection (can be set locally), and treat as truthy (//etc) + / for Cloud Run. Implemented in commit 9a3451a.

[tsavo-at-pieces]

Follow-up (previous comment ate backticks):

• Removed PROJECT_ID/GCP_PROJECT_ID from detection (can be set locally).
• Treat CI as truthy (true/1/etc) and also detect GITHUB_ACTIONS + Cloud Run via K_SERVICE.

Implemented in commit 9a3451a.

[tsavo-at-pieces]

Fixed directly on main in commit cd4b73c (Voxtral tests rewritten to deterministic request-construction tests; no skipping + no external deps). Closing this PR.