Phase 2 — Wire Keys and confirm resolution

Add logical Keys references to your Testing configuration and prove one model resolution path works for test execution—BYOK-aligned, no second key vault.

Principles:

  • Use opaque refs in YAML—never commit raw provider keys.
  • Set Testing’s Keys env vars for judges (RESTORMEL_KEYS_BASE, RESTORMEL_GATEWAY_KEY — aliases RESTORMEL_KEYS_API_BASE_URL / RESTORMEL_KEYS_API_TOKEN — optional RESTORMEL_KEYS_API_TOKEN_ENV, usually RESTORMEL_PROJECT_ID) or the documented OpenAI fallback; full table in docs/testing/config-reference-mvp.md. Dashboard setup: Keys + Testing onboarding.
  • Confirm resolve behaviour matches how your app uses Keys in a non-production environment first.

Keys integration · ← Phase 1 · Phase 3 — First goal →

Agent prompts

Optional: use these with a coding agent to implement this phase in your repo in a safe, gated sequence. Expand only when you need them.

  1. Map our app’s Keys project and gateway usage; list env vars required for resolve in CI.
  2. Add logical model refs to restormel-testing.yaml; run a dry resolution or smallest possible test call.
  3. Verify failures when Keys is misconfigured are explicit (no silent fallback to wrong models in CI).