glm-5.3-flash
29d98b8c22
- PRJ-16b: BatchResultEntry.error now refs a defined BatchError component (oneOf over the six protocol-code envelopes plus a generic BatchOperationError arm carrying the operation-declared code enum); the dangling #/components/schemas/CallError ref is gone - PRJ-17: operation-declared errors at protocol statuses with HTTP_-prefixed codes merge into the shared protocol response's oneOf (per-code CallError_<code> components) instead of clobbering it — the runtime genuinely emits both; non-protocol statuses overwrite as before - PRJ-18: /publish 400 dropped the INVALID_OPERATION_TYPE claim (runtime reports that at 401 without a token, error.rs); the 401 entry is the true one and already documented - PRJ-19: 415 (missing/non-JSON Content-Type) and plain-text 422 (shape-rejection) extractor slots documented, extending the plain-text extractor rejection family; /subscribe gains 415/422, /call gains 415 with the shape-rejection noted on 422, /search and /schema gain the slots too - PRJ-20: /call 401 now carries the identity-split oneOf (FORBIDDEN + INVALID_OPERATION_TYPE), matching error.rs's 401-without-identity mapping for both - PRJ-21: /batch's unreachable 500 removed (all dispatch failures are in-band entries; routes.rs has no 500 path) - PRJ-23: the OAS-invalid x-operation-error-statuses pseudo-schema key inside components.schemas removed (nothing consumed it; any openapiv3 registry rejects it as an invalid schema name) - info.version 1.3.0 per ADR-045 (doc-contract corrections, wire contract unchanged) Verification: cargo test (to_openapi suite 42/42 green, incl. the populated-registry openapiv3 parse and deterministic golden checks)