Build Content Moderation Report API

[aji70]

Task: Build Content Moderation Report API

Overview

No reporting flow exists despite admin/audit infrastructure. Enable community safety with a minimal admin review queue.

---

Goals

• Entity: ContentReport (reporterId, targetType: post|comment, targetId, reason, status: open|resolved|dismissed)
• POST /api/v1/reports — authenticated
• GET /api/v1/admin/reports?status&page&limit — admin
• PATCH /api/v1/admin/reports/:id — resolve/dismiss + audit log

---

Deliverables

• ModerationModule, DTOs, admin guards
• Audit on resolve/dismiss
• Integration tests

---

Acceptance Criteria

• Duplicate open report from same user on same target returns 409
• Invalid/missing target returns 404
• Non-admin cannot access admin routes (403)
• Resolve/dismiss updates status and records admin actor
• At least 8 tests

[priscaenoch]

hello maintainer, I'd like to take this on.

I'd approach it by treating moderation reports as a small workflow rather than just another CRUD resource. The first step would be defining the ContentReport model and validation rules—particularly around duplicate open reports and verifying the target exists—so the API enforces the moderation lifecycle from the outset instead of leaving those checks to the client.

From there, I'd build the reporting and admin endpoints with clear separation between user and moderator responsibilities, ensuring all administrative actions are protected and automatically recorded in the audit log. I'll also back the implementation with integration tests covering the full flow, including duplicate reporting, authorization, invalid targets, and status transitions, so the moderation queue behaves predictably as it grows.

[grantfox-oss]

🦊 GrantFox — @priscaenoch has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #57)
2. Your PR will be reviewed by the MyFanss maintainers

Good luck! Track your progress on GrantFox.