#65.6 Associate Rust-owned API responses with generated OpenAPI 3.1 schemas

[Joncallim]

Purpose

Migrate OpenAPI to 3.1 and directly associate Rust-generated JSON Schema components with every Rust-owned public response, including replacing anonymous inventory wrappers with named models.

Acceptance

• OAS 3.1 validates against official schema; no lossy 3.0 translation.
• Rust schema components are generated/runtime-packaged deterministically and byte-equal reviewed artifacts.
• All direct Rust routes and named inventory/detail wrappers have exact schema references.
• Real API responses validate; aliases/maps are exhaustively tested.
• Node/SSE/bodyless exceptions remain explicit and truthful.

[Joncallim]

Resolution Evidence

• What changed: PR feat(contracts): bind Rust responses to OpenAPI schemas #155 (4f15e61) migrates generated OpenAPI to 3.1.1, directly packages deterministic Rust JSON Schema components, and maps every Rust-owned route/alias to exact response schemas. Named inventory/detail wrappers remove anonymous public response shapes without changing JSON bytes.
• Why this resolves the issue: browser/OpenAPI schemas now derive from the same Rust model authority, including real daemon-to-Node pass-through validation; no lossy OpenAPI 3.0 translation remains.
• How I checked: independent review found and remediated mock-fallback false evidence. Final tests use an authenticated Node→daemon-stub fixture flow and validate canonical + v1 responses, including Compose dry-run edit-plan. OAS 3.1 refs are structurally checked; full CI passed twice.
• Remaining risk or follow-up: SSE remains an explicit event-stream exception; bodyless session operations remain explicit.

Recommendation: This issue appears resolved and can be closed by a maintainer.