sync(openapi): agent-sdk/main 69d5249

[github-actions]

Summary of changes

This PR automatically syncs the OpenAPI specification from the agent-sdk repository.

Agent SDK Reference: main (commit: 69d5249)

Changes Made

• Updated openapi/agent-sdk.json with the latest OpenAPI spec from agent-sdk
• This is an automated sync performed by the sync-agent-sdk-openapi workflow

Checklist

• I have read and reviewed the documentation changes to the best of my ability.
• If the change is significant, I have run the documentation site locally and confirmed it renders as expected.

Note: This is an automated pull request. Please review the changes to ensure they are correct before merging.

[enyst]

@OpenHands Read this issue, and find and read the sync workflow that this, and another automated PR, are using.

We want to merge them automatically. How should we change the workflow to do that? Give me a few options. Respond directly on github, in a comment, and open a PR if you have a proposal you believe would be best.

[openhands-ai]

I'm on it! enyst can track my progress at all-hands.dev

[enyst]

I found the two sync workflows (.github/workflows/sync-agent-sdk-openapi.yml and sync-docs-code-blocks.yml). They already attempt auto-approve + gh pr merge, but create-pull-request currently uses the default GITHUB_TOKEN, which does not trigger required checks. That prevents auto-merge from completing reliably. Here are a few options:

Option A (recommended): use DOCS_SYNC_TOKEN for create-pull-request

• Set token + branch-token in create-pull-request to secrets.DOCS_SYNC_TOKEN (fallback to github.token).
• This makes the PR author a PAT/app token, which does trigger the usual PR checks so auto-merge can succeed once checks pass.
• I opened a draft PR with this change: chore: use docs sync token for auto-merge #318

Option B: switch to create-pull-request’s draft mode + manual "ready for review"

• Create PRs as draft so they don’t block. When ready, a human flips to ready-for-review to kick checks and auto-merge.
• Less automated, but avoids PAT usage.

Option C: use a GitHub App token in the workflows

• Generate a short-lived App token (fine-grained) and feed it to create-pull-request + gh commands.
• Most secure long-term, but requires app setup.

If you want, I can update the PR to non-draft and proceed with Option A.