chore: regenerate API client from latest OpenAPI spec

[giordano-lucas]

Regenerate the generated API client (internal/api, internal/cmd/*_flags.gen.go) from the latest staging OpenAPI spec.

The new POST /proxies/gateway/credentials operation is intentionally recorded as infrastructure-only: function runners call it to mint short-lived proxy-gateway credentials, so it is not exposed as a CLI command.

Verification:

• make check
• make check-endpoints
• make build
• go test -race -short ./...

[andreakiro]

Auto-approved: scheduled API client regeneration.

[greptile-apps]

Greptile Summary

This PR regenerates the API client to expose proxy credential minting through typed request and response models.

• Adds optional city and country request fields.
• Adds a POST request builder for /proxies/gateway/credentials.
• Adds typed handling for successful and validation-error responses.
• Does not add automated coverage for the new API operation.

Confidence Score: 4/5

The generated endpoint appears internally consistent, but the repository’s explicit test requirement must be satisfied before merging.

The endpoint uses the existing authenticated transport and follows established generated-client patterns; the sole accepted concern is the absence of automated coverage for its request construction and response parsing.

Files Needing Attention: internal/api/client.gen.go

Important Files Changed

Filename	Overview
internal/api/client.gen.go	Adds a generated proxy-credential endpoint whose transport integration is consistent with existing operations, but which lacks focused request and response tests.

Prompt To Fix All With AI

### Issue 1
internal/api/client.gen.go:14965
**Missing endpoint tests**

This PR adds a generated credential-minting endpoint without unit or integration coverage. That violates the repository directive requiring tests to be called out when none are added, so the requirement must be satisfied before merging. Add focused tests for the POST path and JSON body as well as the 200 and 422 response mappings, so future schema or generator regressions cannot silently break this API surface.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "chore: regenerate API client from latest..." | Re-trigger Greptile}

[andreakiro]

Auto-approved: scheduled API client regeneration.

[andreakiro]

Auto-approved: scheduled API client regeneration.