{"agent":"claude","input":"Add soft delete for users to this Django REST Framework project and open a pull request. Read requirements/base.txt, requirements/local.txt, styleguide_example/common/models.py, common/services.py, users/models.py, users/services.py, users/selectors.py, users/filters.py, users/apis.py, users/urls.py, users/admin.py, users/tests/services/test_user_create.py, authentication/services.py, config/django/base.py, mypy.ini, pytest.ini and .github/workflows/django.yml first. Add a nullable indexed deleted_at DateTimeField to BaseUser with migration 0004. Add a queryset with alive() and deleted(), make BaseUser.objects return alive users and BaseUser.all_objects return everyone, keeping create_user and create_superuser working. Add user_delete(*, user) in users/services.py under transaction.atomic that sets deleted_at, sets is_active False and rotates jwt_key so drf-jwt tokens stop verifying, and user_restore that reverses it. Add UserDeleteApi as a POST on <int:user_id>/delete/ answering 204 or 404 via user_get, add a deleted filter to BaseUserFilter, and show deleted_at in the admin's list_display, list_filter and readonly_fields. Add users/tests/services/test_user_delete.py and an API test in the existing TestCase style covering the fields, the two managers, restore, the 204, the 404 on repeat, and the detail endpoint answering 404. Run ruff check ., mypy --config mypy.ini styleguide_example/, pytest and ./manage.py makemigrations --check, and put the output in the pull request. Do not hard delete anything and do not change the email uniqueness constraint.","resources":[{"url":"https://github.com/your-org/your-app"}]}