{"agent":"claude","input":"Migrate this Django REST Framework project from drf-yasg to drf-spectacular. Start with an inventory: every import from drf_yasg, every swagger_auto_schema and swagger_serializer_method decorator, the get_schema_view call and its routes, every key in SWAGGER_SETTINGS and REDOC_SETTINGS, and every project class that subclasses a drf-yasg generator, auto schema or inspector, with one line on what each customisation does. Before changing anything, generate the current schema with drf-yasg and save it. Then install drf-spectacular, set DEFAULT_SCHEMA_CLASS, move title, version, description, contact and license into SPECTACULAR_SETTINGS, and replace the schema routes with SpectacularAPIView, SpectacularSwaggerView and SpectacularRedocView at the same paths and under the same conditions. Convert each decorator to extend_schema (manual_parameters to parameters with OpenApiParameter, request_body to request, operation_summary and operation_description to summary and description, auto_schema=None to exclude=True). Reimplement each custom class with the drf-spectacular mechanism that fits (an AutoSchema subclass, a postprocessing hook, the paginator's get_paginated_response_schema, an OpenApiAuthenticationExtension) and delete the ones that become unnecessary. Form and file parameters have no OpenAPI 3 parameter form: describe them as a multipart request body. Run manage.py spectacular with --validate and --fail-on-warn and resolve every warning or list the ones you could not, with the reason. Compare the old and new schemas: every path and method present before must be present after, and report differences in parameters, response shapes, tags and security. If the project needs a database or cache to import its URL configuration, start what is needed or use a settings override, and say which. Remove drf-yasg from the manifests. Open a pull request.","resources":[{"url":"https://github.com/your-org/your-app"}]}