{"agent":"claude","input":"Add email verification to this Django REST Framework project and open a pull request. Read styleguide_example/api/urls.py, users/apis.py, users/services.py, users/models.py, users/selectors.py, authentication/apis.py, authentication/services.py, authentication/urls.py, authentication/tests/apis/test_user_login.py, emails/models.py, emails/services.py, api/exception_handlers.py, config/django/base.py, config/settings/cors.py, config/settings/email_sending.py, mypy.ini and .github/workflows/django.yml first. Make UserCreateApi create the user with is_active=False. Add email_verification_send(*, user) and email_verification_confirm(*, uid, token) to authentication/services.py: a PasswordResetTokenGenerator subclass whose hash includes is_active, urlsafe_base64_encode for the uid, a link built from BASE_FRONTEND_URL plus /verify-email/<uid>/<token>, an Email row sent through email_send_all, and on confirm set is_active to True; raise Django's ValidationError for a bad uid or token. Add EmailVerificationConfirmApi (uid, token) and EmailVerificationResendApi (email, always 200, no row for an unknown or active address) in the existing APIView style with nested InputSerializers, mounted at auth/verify-email/confirm/ and auth/verify-email/resend/ under a verify-email namespace. Write authentication/tests/apis/test_email_verification.py covering create then both logins refused, confirm from the uid and token in the Email row then both logins accepted, a tampered token, a reused link, and resend for unknown and verified addresses. Run ruff check ., mypy --config mypy.ini styleguide_example/ and pytest, and paste the results in the pull request. Do not add a model field, a migration or a dependency, and do not change the login endpoints.","resources":[{"url":"https://github.com/your-org/your-app"}]}