Claude
028ba8c5e4
Players whose linked Discord identity was banned or muted can now submit an appeal from the portal and track it; staff get a queue in the admin moderation section to claim and resolve (approve/deny) appeals. Approving a ban/mute appeal best-effort asks the Discord bot to reverse the action (unban / clear timeout) via the internal API and posts a mod-log embed; a down bot never fails the resolution (reversal_status is recorded). - Schema: new server-owned `appeals` table (no cross-owner FK to mod_actions; existence validated in app code). - Server: model/appeals/* + player appeals controller (submit/mine/ eligible/withdraw) and admin queue handlers (list/claim/resolve/ per-user) under the existing admin+moderator gate; one-active-appeal enforced app-side; eligibility keyed on the caller's linked Discord id. - 6d: bot POST /internal/mod-reverse (+ modLog.postReversal) and server botInternalClient.reverseModAction, wired into resolve(). - Client: admin Appeals queue + resolve modal, ModerationUser appeals tab, player Appeals page (submit/withdraw), nav + routes + api methods. - Docs: swagger annotations + component schemas, regenerated output. - Tests: appeals controller + pure suites (server npm test 224 green). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XmHdsbnLzDMAVQkAoTQSBe
16 lines
400 B
JavaScript
16 lines
400 B
JavaScript
const express = require('express')
|
|
|
|
const requireInternalKey = require('./requireInternalKey')
|
|
const ctrl = require('./internal.controller')
|
|
|
|
const router = express.Router()
|
|
|
|
router.use(requireInternalKey)
|
|
|
|
router.post('/config', ctrl.setConfig)
|
|
router.get('/status', ctrl.getStatus)
|
|
router.post('/announce', ctrl.announce)
|
|
router.post('/mod-reverse', ctrl.reverseModAction)
|
|
|
|
module.exports = router
|