docs: add response.web_search_call.in_progress and response.web_search_call.completed to stream response type enums

[Pratham-Mishra04]

Summary

Adds two missing streaming event types for web search calls — response.web_search_call.in_progress and response.web_search_call.completed — to the OpenAPI spec and schema definitions, bringing the web search call lifecycle events in line with other tool call types.

Changes

• Added response.web_search_call.in_progress and response.web_search_call.completed to the ResponsesStreamResponseType enum in the responses schema and all corresponding locations in the generated OpenAPI JSON.

Type of change

• Bug fix
• Feature
• Refactor
• Documentation
• Chore/CI

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (React)
• Docs

How to test

Verify that the OpenAPI spec correctly enumerates response.web_search_call.in_progress and response.web_search_call.completed alongside the existing response.web_search_call.searching, response.web_search_call.results.added, and response.web_search_call.results.completed event types.

Breaking changes

• Yes
• No

Related issues

Security considerations

None.

Checklist

• I read docs/contributing/README.md and followed the guidelines
• I added/updated tests where appropriate
• I updated documentation where needed
• I verified builds succeed (Go and UI)
• I verified the CI pipeline passes locally if applicable

[Pratham-Mishra04]

• feat: validate routing rule scope_id resolves to an existing entity at write time and during config.json sync #5371
• docs: expand output field schema in OpenAPI from generic object to typed oneOf (string, content blocks, computer screenshot) #5350
• docs: add response.web_search_call.in_progress and response.web_search_call.completed to stream response type enums #5345 👈 (View in Graphite)
• docs: add retrieve, delete, cancel, and list input items endpoints for stored responses #5344
• docs: add Response Lifecycle endpoints and expand streaming event types table for OpenAI Responses API #5343
• docs: add append_fallbacks_to_pinned as a fifth load-balancer switch and update all references to pinned-request fallback behavior #5336
• docs: clarify that Level 1 LB always runs for pinned providers, appending healthy fallbacks instead of skipping #5135
• refactor: make RefineModelForProvider idempotent and unify Groq/Replicate/Perplexity into a single case #5133
• dev

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

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 44 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 887052f0-f07f-4bc4-99fe-19aa254357da

📥 Commits

Reviewing files that changed from the base of the PR and between 683aa2c and 43b0268.

📒 Files selected for processing (2)

• docs/openapi/openapi.json
• docs/openapi/schemas/inference/responses.yaml

📝 Walkthrough

Walkthrough

The streaming response schema and OpenAPI documentation now include response.web_search_call.in_progress and response.web_search_call.completed alongside the existing searching event.

Changes

Web search lifecycle events

Layer / File(s)	Summary
Expand web search response events docs/openapi/schemas/inference/responses.yaml, docs/openapi/openapi.json	The streaming response enum and repeated OpenAPI event sequences add the in_progress and completed web search call events while retaining searching.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested reviewers: danpiths, akshaydeo

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly and accurately summarizes the primary change: adding missing web search call stream event enums.
Description check	✅ Passed	The PR description covers summary, changes, type, affected area, testing, breaking changes, security, and checklist, with only minor omissions.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 07-18-docs_fix_responses_stream_event_enum_drift_in_openapi_spec

---

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.

Important Files Changed

Filename	Overview
docs/openapi/schemas/inference/responses.yaml	Adds the two missing web-search lifecycle values to the streaming response enum.
docs/openapi/openapi.json	Updates all generated copies of the streaming response enum.

_{Reviews (3): Last reviewed commit: "docs: fix responses stream event enum dr..." | Re-trigger Greptile}

[Pratham-Mishra04]

Merge activity

• Jul 20, 7:33 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jul 20, 7:49 AM UTC: Graphite rebased this pull request as part of a merge.
• Jul 20, 7:50 AM UTC: @Pratham-Mishra04 merged this pull request with Graphite.

The base branch was changed.