A developer added a new DELETE /api/v2/users/:id endpoint to a REST API. The endpoint soft-deletes users by setting deleted_at timestamp rather than removing the row. The developer wants to make sure this change didn't introduce any regressions in the broader user management system. Write a regression scout report to report.md.

=============== FILE: inputs/user-service.md ===============

User Service Overview

New Endpoint

• DELETE /api/v2/users/:id — soft delete (sets deleted_at, does not remove row)
• Implemented in: src/routes/users.js
• Uses: src/models/user.js (added softDelete() method)

Related Components

• src/routes/users.js — user CRUD routes (CHANGED: new DELETE handler added)
• src/models/user.js — User model (CHANGED: softDelete() method added)
• src/middleware/auth.js — JWT auth, checks user exists before authorizing
• src/routes/orders.js — order routes, joins with users table
• src/routes/posts.js — posts routes, filters by author user_id
• src/services/emailService.js — sends emails to users
• src/services/search.js — user search, may return soft-deleted users

Existing Behaviors

• Auth middleware queries users table for user existence check
• Order and post queries do not currently filter out deleted users
• Email service does not check deleted_at before sending
• Search indexes are rebuilt nightly from the users table =============== END FILE ===============