[mofr]

Stacked on #350.

What

• The parameters of a route come from a fixed internal list of inspectors (path, query, PagePosition), mirroring the arguments that winter.web maps from the request since feat(web)!: resolve arguments from the request or the application's injector #345. Gone: register_route_parameters_inspector, get_route_parameters_inspectors, and the exports of RouteParametersInspector, the three inspectors and inspect_page. A parameter that no argument stands for, such as a header read by a request-scoped provider, is added to the spec that generate_openapi returns.
• register_type_inspector becomes the decorator @winter.openapi.type_inspector(T), without the call form with func=. Type inspectors stay global, like JSON encoders: they describe a type and its subclasses wherever it appears, in a body, a response or a parameter.
• register_global_exception is gone; @winter.openapi.global_exception remains as the only name of that annotation.
• winter.openapi.initialization is gone. Its four marks of Winter's own exceptions as global no longer affected anything: the check of @raises looks at the definitions of the application only, where Winter's classes are not. Page was registered twice. All tests pass without them.
• docs/architecture.md: OpenAPI type inspectors join the metadata that may be global; the deviations no longer list winter.openapi.

Why

The route parameter inspectors were the only behavioural registry of winter.openapi, and they describe what winter.web maps, which is now fixed. Decorators in Winter name what a thing is (@route_get, @problem, @global_exception); register_… named the mechanism.

To be confirmed on the consumer: whether it registers route parameter inspectors, subclasses RouteParametersInspector, or calls register_global_exception.

🤖 Generated with Claude Code