Pure checks for Anthropic Provider

Verification Boundary

The suite checks deterministic module behavior and declared configuration using local inputs.

What This Suite Proves

Cache marking remains within the provider bound. Live adapter construction rejects unsafe setup. Combined bindings require every named suite; a component assertion alone does not establish the full experiment.

What It Does Not Prove

These checks do not establish database transactions, deployed permissions, provider availability or a complete user journey.

Real Dependencies and Test Doubles

The production adapter constructor and the vendor client it creates are real. Literal environments supply configuration; no provider request is sent.

Must Not Be Doubled

Retain the function, configuration or boundary guard under test and its assertions; replacing them removes the evidence.