feat(KNO-12791): Add workflow recipient runs to docs

[andy-knock]

Description

Add docs for workflow recipient runs. Copy pasta yml from stainless.

Screenshots

![Uploading Screenshot 2026-04-21 at 12.24.35 PM.png…]()

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Apr 22, 2026 5:22pm

[linear]

KNO-12791 [Docs/SDKs] Add workflow recipient run endpoints to OpenAPI specs

[andy-knock]

• feat(KNO-12791): Add workflow recipient runs to docs #1398 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[cursor]

Risk MEDIUM: Adds new workflow recipient runs resource to the API docs via OpenAPI spec and sidebar navigation changes.

Reasons

• Sidebar navigation file modified (data/sidebars/apiOverviewSidebar.ts) — adds a new workflow_recipient_runs entry, which affects API reference page ordering
• Two OpenAPI spec files modified (data/specs/api/customizations.yml and data/specs/api/stainless.yml) — these define a new API resource and can affect API reference rendering
• .vscode/settings.json modified — low-risk IDE config change (disables YAML format-on-save), but not a build/deploy config
• Small diff size (22 additions, 2 deletions across 4 meaningful files) keeps this from being HIGH risk
• No .tsx/.ts component, layout, or lib files are modified, so no HIGH risk triggers apply

Notes

• Verify the new workflow_recipient_runs sidebar entry renders correctly and links to the expected API reference page
• Confirm the OpenAPI spec additions (WorkflowRecipientRun, WorkflowRecipientRunDetail, WorkflowRecipientRunEvent schemas) are present in the generated spec — the customizations and stainless YAML reference these schemas but they must exist in the base spec
• Check that the new API endpoints (GET /v1/workflow_recipient_runs and GET /v1/workflow_recipient_runs/{id}) render properly in the API reference UI
• The .vscode/settings.json change is a team DX preference — confirm this is intentional to include in the repo

  

_{Sent by Cursor Automation: Docs PR classifier}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 48ca9e9. Configure here.}

[rachael-t]

Thank you for working on this 🙏 only thing is the bugbot comment

[andy-knock]

Thank you for working on this 🙏 only thing is the bugbot comment

Which part are you referring to?

The first note is verified as per the screenshots.

The second note is verified (in the scope of this PR) as the screenshots show the doc pages for those objects in the spec

The third note idk what that even refers to, in the context of this PR I guess they would refer to the things referenced by the last two screenshots.

The last item is valid and an accidental change that I reverted.

[rachael-t]

@andy-knock sorry, it was just the last one about the next-env.d.ts file that you just changed 👍

[andy-knock]

• vscode/settings.json

technically, the last point was actually about a diff I introduced to vscode/settings.json, because when copy pasting in the yaml files (from the stainless yaml file manually) my editor likes correcting all the single quotes to double quotes and I was trying to prevent that to prevent a massive file diff