Skip to content

Mirror x-omitempty filtering in OpenAPI sync fallback - #781

Open
warp-agent-staging[bot] wants to merge 1 commit into
mainfrom
factory/strip-x-omitempty-openapi-fallback
Open

warp-agent-staging[bot] wants to merge 1 commit into
mainfrom
factory/strip-x-omitempty-openapi-fallback

Conversation

@warp-agent-staging

Copy link
Copy Markdown
Contributor

Summary

Mirror the authoritative OpenAPI filter's x-omitempty handling in the docs repository's manual sync fallback. This prevents implementation-only serialization hints from reaching the public Agent API spec when the fallback path is used.

Related issues

Context: warpdotdev/warp-server#18081

Validation

  • python3 .agents/skills/sync-openapi-spec/scripts/sync_openapi.py --mode self-test (self-test: OK)
  • python3 -m py_compile .agents/skills/sync-openapi-spec/scripts/sync_openapi.py
  • git diff --check
  • trunk fmt not run because the Trunk CLI is unavailable in this environment.

Screenshots

Not applicable; this changes internal sync tooling only.

Follow-ups

None.

Documentation risk

Risk: low
Rationale: Mirrors an implementation-only OpenAPI strip flag in internal docs tooling.
Docs override: none

Unverified claims

None.

@cla-bot cla-bot Bot added the cla-signed label Sep 22, 2026
@vercel

vercel Bot commented Sep 22, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
docs Ready Ready Preview Sep 22, 2026 5:15pm UTC

Request Review

@warp-agent-staging warp-agent-staging Bot added factory:wilson warpy-factory Opened by the Warp factory agents labels Sep 22, 2026
@warp-agent-staging

Copy link
Copy Markdown
Contributor Author

This PR was generated with Warp.

Comment @warp-staging-factory on this PR to send it follow-up work.

View run View conversation View on Slack

@warp-agent-staging
warp-agent-staging Bot marked this pull request as ready for review September 22, 2026 17:13
@warp-for-oss

warp-for-oss Bot commented Sep 22, 2026 •

Copy link
Copy Markdown
Contributor

@warp-agent-staging[bot]

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@warp-for-oss warp-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview

This PR mirrors the upstream OpenAPI fallback filtering by adding x-omitempty to the recursive implementation-only extension strip list and extending the self-test fixture so the existing strip assertion covers it.

Concerns

  • No blocking correctness, security, comment-quality, test-quality, or spec-drift concerns found in the annotated diff.

Verdict

Found: 0 critical, 0 important, 0 suggestions

Approve

Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review summary

The independent agent completed its review for this commit.

Findings

  • .agents/skills/sync-openapi-spec/scripts/sync_openapi.py:81 — [IMPORTANT] Declared Risk: low, but this PR manually edits STRIP_FLAGS (governs what's stripped from the public developers/agent-api-openapi.yaml) based on an unverifiable claim about warp-server's private public_api/public-openapi-filter.yaml stripFlags list, with no Source files consulted or Requested engineering reviewers field. Per sync-openapi-spec/SKILL.md, a manual (non-passthrough) edit to the sync policy is engineering-review-required. Requested resolution: reclassify as Risk: engineering-review-required, cite the warp-server source file/SHA under Source files consulted, and request review from a warp-server owner who can confirm x-omitempty is in the upstream stripFlags list.
  • .agents/skills/sync-openapi-spec/scripts/sync_openapi.py:81 — [IMPORTANT] Adding x-omitempty to STRIP_FLAGS makes .agents/skills/sync-openapi-spec/references/sync-policy.md:55-59 (which enumerates STRIP_FLAGS as mirroring warp-server's stripFlags 'verbatim') stale, and skips that doc's own instruction at lines 76-77 to add new upstream strip-flag entries there too so the two filters 'stay in lockstep.' Requested resolution: update references/sync-policy.md's STRIP_FLAGS enumeration and lockstep note to include x-omitempty in this same PR.

Verdict

Request changes

This branch was successfully deployed

1 active deployment
Preview — cb485085 Deployed Sep 22, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed factory:wilson warpy-factory Opened by the Warp factory agents

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants