chore: regenerate API client from latest OpenAPI spec

[giordano-lucas]

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

Last regenerated: 2026-08-29 10:33 UTC

[andreakiro]

Auto-approved: scheduled API client regeneration.

[greptile-apps]

Greptile Summary

This PR regenerates the Go API client to add managed-auth connect-link models, request methods, and typed response handling.

• Adds connect-link creation, context, status, and credential-submission operations.
• Adds connect-link data models, token-header parameters, status enums, and response parsers.
• Preserves and relocates the existing generated persona request builders.

Confidence Score: 4/5

The PR appears safe to merge, with the non-blocking concern that the newly generated endpoint contracts have no accompanying tests.

The generated methods, models, builders, and parsers are internally consistent, and no existing interface implementation or caller was found to break; only the repository’s missing-test requirement remains.

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

Important Files Changed

Filename	Overview
internal/api/client.gen.go	Adds a coherent generated connect-link API surface, but the PR includes no unit or integration coverage for its request and response contracts.

Prompt To Fix All With AI

### Issue 1
internal/api/client.gen.go:46-52
**Connect-link contracts lack tests**

The new request builders and response parsers have no unit or integration coverage, so regressions in methods, paths, token headers, serialization, or status mappings will not be caught by repository tests.

---

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.