Furries PH Docs
Dashboard
Report system docs

Reference

Certification Checklist

Checklist for verifying Report System docs, routes, forms, permissions, workflows, and state behavior.

First created Last updated

reportscertificationvalidationreference

Overview

Use this checklist before treating Report System documentation or dashboard behavior as production-ready. The checklist mirrors the active routes and the docs pages in this section.

Certification workflow

flowchart TD
  source["Audit dashboard source"] --> docs["Check matching docs page"]
  docs --> routes["Verify route and query behavior"]
  routes --> inputs["Verify every visible input/control is documented"]
  inputs --> permissions["Verify role-gated states"]
  permissions --> build["Run docs check and build"]
  build --> evidence["Record validation evidence"]

Route coverage

RequirementEvidence
Every active route in Route Map has a docs page.Route map table and sidebar navigation.
Every route with id or entryId explains query behavior.Surface docs and route map.
Legacy /reports/mine is documented as compatibility.Mine Compatibility.
FPH-admin routes document denied states.Cross-ban Requests and Ban Appeals.

Surface input coverage

SurfaceInputs and controls to verify
New ReportSeverity, status, incident details, people fields, violation checkboxes, markdown fields, witnesses, action types, ban scope, appeal process, cross-ban recommendation, officer fields, signature, submit.
Manage ReportStatus, severity, report fields, action fields, ban scope, markdown upload contexts, cross-ban recommendation, save, revert, redirect on denied edit.
All/My/Mine ReportsSearch, status filters, row actions, detail/manage links, empty states.
Report DetailQuery ID, edit link, local ban modals, network-ban appeal link, rendered sections, revision history.
Watchlists and BansLocal/shared sections, searches, detail links, local ban edit, network appeal links, my appeals card.
Cross-ban RequestsTabs, searches, approve/deny, scope radios, reason, confirm decision, appeals tab.
Network Ban AppealCreate, edit, resubmit, pending, decided, revision, and error states.
Ban AppealsFPH-admin access, entry lookup, appeal rows, review notes, approve/deny, confirm decision.
Person ProfilesSuggestions, create/edit/delete, aliases, notes, add picker, link/unlink, audit log.

Validation commands

pnpm check
pnpm build
git diff --check -- src/pages/reports src/lib/docs-nav.ts src/content/updates.md

End-to-end operator runbook

  1. Audit source: Compare docs with partners.furries.ph/src/pages/reports/**, ReportsLayout.astro, and dashboard-scenes.ts.
  2. Check each surface: Confirm every visible and conditional control is documented.
  3. Check workflows: Confirm Mermaid diagrams cover intake, update, watchlist/ban, cross-ban, appeal, profile, and maintenance flows.
  4. Run validation: Execute check, build, and diff hygiene commands.
  5. Record evidence: Update the task file with changed files and command results.

Common mistakes

Do not certify docs from route names alone. Certification needs source-backed control coverage and a passing docs build.

All docs