docs(api): remove context grant fields

[halfofning]

Summary

• Remove context-grant fields from the public API reference and generated OpenAPI examples.
• Align user-facing Workflow, schedule, and webhook documentation with native-tool routing authority.

Cross-Repo Change Set

Tracking issue: none

Related PRs:

• refactor(auth): remove context grant authority control-plane#24
• docs(api): remove context grant fields #16
• refactor(auth): remove context grant claims llm-gateway#7
• feat(ui): harden workflow workspace experience management-console#26

Merge order:

1. control-plane
2. docs-website
3. llm-gateway
4. management-console

Validation

• npm run validate passed in the repository Node 22 container.
• npm run links passed with no broken links.

Docs Impact

• This PR is the documentation portion of the coordinated contract removal.

Residual Risk

• Publish after the service contract changes so the reference does not get ahead of deployed behavior.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1eb018e264

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Remove stale grant claims from update operations

After removing approvedContextGrants, the descriptions for PATCH /api/v1/workflow-schedules/{scheduleId} and PATCH /api/v1/workflow-webhooks/{webhookId} still claim that these operations update grants. This directs API-reference users toward an unsupported payload, and the webhook schema rejects that payload because it disallows additional properties; remove the grant wording from both operation descriptions.

Useful? React with 👍 / 👎.