thirdparty-api-integration-test

# Third Party API Integration Test Write Go integration tests for real third-party API calls using explicit run gates, predictable safeguards, and strong contract assertions. ## Scope - Validate external API integration end-to-end with real config and real client. - Keep tests opt-in by default so normal CI/unit workflows are not blocked. - Follow the host repository's existing style — its assertion library (`testify/require`, `testify/assert`, or stdlib `t.Fatalf`), its config loader, and its test-package convention. The examples below use `testify/require` and `config.MustLoad()` as one common shape; mirror what the repo already does rather than importing a new dependency. Clear skip conditions and a bounded timeout are required regardless. - Apply to any third-party API integration. - Treat vendor examples (MCS/USS/etc.) as templates, not scope limits. - The NON-NEGOTIABLE parts are the safety gates (run gate, prod/host/account fail-closed checks, destructive gating, bounded budget, ID/URL redaction) — not the choice of assertion or config library. ## Scope Validation Gate Confirm the task targets a third-party vendor API: - Third-party HTTP or gRPC API client → proceed - Internal service/handler (own HTTP server) → redirect to `$api-integration-test`, **STOP** - Pure unit test → redirect to `$unit-test`, **STOP** - Full end-to-end browser journey → out of scope, inform user, **STOP** **Hard stop**: If the target is not a third-party vendor API, the entire ...