fix: preserve schema-less client operations in 0.9.1

[lightsofapollo]

What

• preserve client generation for JSON and form request media entries that declare no schema
• keep generated Axum servers fail-closed with an operation- and media-specific error because there is no input contract to validate
• add client/server boundary regressions and bump crate metadata/changelog to 0.9.1

Why

The 0.9.0 server-validation work rejected schema-less request content during shared operation analysis, before the generator knew whether it was producing a client or server. That regressed client-only generation for the Cloudflare, GitHub, and Lithic corpus specs.

This introduces an explicit shared-analysis marker. Client and registry generation retain the historical no-body behavior; selected server operations reject the marker during server preflight.

Impact

• Existing schema-less client operations generate again without changing their historical signatures.
• Generated servers never silently accept an unvalidated schema-less body.
• The patch release metadata is 0.9.1.

Checks

• cargo test --all-features
• cargo clippy --all-features -- -D warnings
• RUSTDOCFLAGS='-D warnings' cargo doc --no-deps --all-features
• cargo fmt --all -- --check
• focused extraction/client/server tests: 38 passed
• failed corpus replay (cloudflare github lithic): 3 passed
• full parse-only corpus: 54 passed, 1 expected Swagger 2.0 skip
• generated Anthropic and OpenAI clients: both cargo-check
• official openai-python==2.45.0 against generated Axum server: passed

Follow-up to #38 and GitHub Actions run 30214707117.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
openapi-to-rust	Ready	Preview, Comment	Jul 26, 2026 8:37pm