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-09-14 14:23 UTC

[andreakiro]

Auto-approved: scheduled API client regeneration.

[greptile-apps]

Confidence Score: 4/5

The PR is not safe to merge until session start honors the documented authentication-wait preference and the explicit testing requirement is addressed.

Findings

1.  Authentication Wait Is Ignored ▶

Fix with agent prompt

### Issue 1
internal/cmd/sessionstart_flags.gen.go:93
When Managed Auth requires background login, the API can return a session with status `authenticating`. Although this flag now says that SDKs implement waiting through readiness polling, the session-start command stores and prints the response without checking its status or polling the new readiness endpoint. As a result, the default behavior and `--wait-for-authentication` can return a session before authentication completes, leaving callers with a session that is not ready to use.

---

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

Summary

• Adds Managed Auth operation/readiness models and status enums.
• Adds GET /sessions/{session_id}/auth request and response support.
• Adds auth_retry fields and the --auth-retry CLI flag.
• Updates session status and authentication-waiting semantics.
• The CLI does not yet implement the readiness polling required by the new waiting contract.

_{Reviews (1) · Last reviewed commit: "chore: regenerate API client from latest..."}

[greptile-apps]

Authentication Wait Is Ignored

When Managed Auth requires background login, the API can return a session with status authenticating. Although this flag now says that SDKs implement waiting through readiness polling, the session-start command stores and prints the response without checking its status or polling the new readiness endpoint. As a result, the default behavior and --wait-for-authentication can return a session before authentication completes, leaving callers with a session that is not ready to use.

Prompt To Fix With AI

This is a comment left during a code review.
Path: internal/cmd/sessionstart_flags.gen.go
Line: 93

Comment:
**Authentication Wait Is Ignored**

When Managed Auth requires background login, the API can return a session with status `authenticating`. Although this flag now says that SDKs implement waiting through readiness polling, the session-start command stores and prints the response without checking its status or polling the new readiness endpoint. As a result, the default behavior and `--wait-for-authentication` can return a session before authentication completes, leaving callers with a session that is not ready to use.

---

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