NeoModeration 1.4.1

NeoModeration 1.4.1 — Activation clarity

NeoModeration 1.4.1 makes the first-run and cloud-recovery paths explicit. A
fresh install still starts safely in monitor mode: it detects and reports,
but does not block or punish until an admin runs /nmod mode enforce.

Improved

• Guided first test. Startup, help, README, and marketplace copy now point
  to /nmod test badword. It proves the bundled local rule works and states
  that monitor mode will not execute an action.
• Truthful key setup. Saving a key no longer claims cloud moderation is
  active before it has been checked. /nmod doctor verifies the account and
  usage API, latency, and the current credit balance; /nmod test hello
  verifies the moderation-events path separately.
• Actionable cloud recovery. HTTP 401/403 is reported as a rejected key,
  while HTTP 402 is reported separately as insufficient credits. /nmod status, /nmod doctor, /nmod test, and /nmod usage provide the matching
  attributed key or billing link and a concrete command to verify recovery.
  No command or log line echoes an API key.
• Honest billing classification. Ordinary Minecraft chat explicitly uses
  the platform's general content class. Only the feature dedicated to NSFW
  map-art image scanning declares nsfw; ordinary chat is never mislabeled to
  obtain a free allowance.
• Separated cloud health. Chat tests and map-art scans feed the same
  moderation-event circuit/status state as normal chat. Account/usage checks
  are reported separately and cannot make a broken events endpoint look
  healthy. Malformed 4xx requests are no longer misreported as bad credentials.

Compatibility

• No configuration migration is required.
• Existing enforce-mode servers remain in enforce mode. Monitor is only the
  default for a genuinely new config.
• Marketplace metadata now matches the verified Minecraft 1.18.2–1.21.x range;
  this release does not advertise untested Folia support.
• Local word, URL, and anti-spam rules continue to run when the cloud is
  unavailable or out of credits.

Verified

• Automated regression coverage includes 401/403, 402, other 4xx, transient
  failures, separated account/event health, recovery-message routing, locale
  parity, payload billing classes, and the guided monitor-mode test path.
• The release matrix checks Paper 1.18.2, 1.19.4, 1.20.6, and 1.21.11,
  including monitor-once/enforce-once chat checks and representative commands.

Regenerate the final release JAR's SHA-256 checksum and matrix report from the
frozen release source immediately before publishing them beside these notes.