v0.4.0

Changed

• Split outputSchema and structuredContent controls. The single
  INCLUDE_STRUCTURED_CONTENT setting (and per-binding
  include_structured_content override) used to gate both the
  outputSchema advertisement in tools/list and the structuredContent
  field in tools/call. They are now independent: a new
  INCLUDE_OUTPUT_SCHEMA setting (default True) and matching
  per-binding include_output_schema override control the schema
  announcement separately. The MCP spec invariant — advertising
  outputSchema requires emitting conforming structuredContent — is
  enforced explicitly: the spec-violating combination is rejected with
  ImproperlyConfigured at construction time (explicit per-binding
  conflicts) or at request time (setting-level conflicts).

  Migration: if you previously set
  REST_FRAMEWORK_MCP["INCLUDE_STRUCTURED_CONTENT"] = False, also set
  INCLUDE_OUTPUT_SCHEMA = False (or accept the new
  ImproperlyConfigured raised on requests against bindings with an
  output serializer). If you set include_structured_content=False on a
  binding, add include_output_schema=False to the same registration
  call.