verify

To test model-gateway behavior safely, you need isolated validation using controlled temporary homes and ephemeral localhost ports. This approach captures response bodies and inspects resulting settings JSON, ensuring CLI and HTTP shim surfaces are verified without touching production environments.

Settings migration verification validates that legacy settings are rewritten correctly during ensure and env workflows. It requires inspecting the resulting settings JSON within a controlled temporary home to confirm that configuration migrations execute safely and accurately.

Yes, you can validate HTTP shim message forwarding and model listing by exercising these paths within an isolated temporary environment. This captures response bodies and confirms the running HTTP shim processes model listing and message forwarding correctly without network side effects.

The best way to verify compatibility mode and DNS recursion protection is through isolated compatibility and safety testing. This confirms RC-compatibility mode, port fallback behavior, and DNS guard scenarios operate correctly under controlled conditions using ephemeral localhost ports.

Yes, model-gateway end-to-end testing requires controlled temporary homes and ephemeral localhost ports. These prerequisites ensure that CLI validation, HTTP shim checks, and environment wiring tests remain fully isolated from real user settings and production network services.

Model-gateway verification focuses on both CLI and HTTP shim surfaces to provide complete end-to-end testing coverage. Checking both interfaces ensures that model listing, message forwarding, and environment wiring function correctly across all available interaction paths before shipping changes.