integration-testing

Run this repository's integration tests against a Veris dependency sandbox.

The sandbox is a set of stateful, contract-accurate twins of the services this code depends on. The code under test is never modified and never told: it keeps its production hostnames, credentials and client stack, and veris-proxy reroutes its outbound HTTP(S) into the sandbox from outside the process. Your job is to make the failure the task describes happen, change the code, watch it stop happening — and be able to prove all three.

Where you are

• No .veris/run.sh, or setting-up-veris's scripts/preflight.sh fails → that skill first. Transport is never improvised here.
• The design is still open, or the task rests on a claim about the vendor you have not seen it make — "the API has no X", "it always returns Y" → discovering-vendor-behavior first. Arriving with the design fixed leaves the sandbox one question: whether your code works. It will answer that, correctly, while the assumption underneath goes unexamined.
• Otherwise: run.