feat: add blood moon countdown module

[koji-assistant]

Summary

• Adds blood-moon-countdown, a 7 Days to Die helper module for /bloodmoon and /day7.
• Reads live game day with a configurable console command (gettime by default), with an explicit manual fallback mode so stale countdowns are opt-in.
• Adds optional Discord !bloodmoon / !day7 replies through a discord-message hook.

Discord source

• Source: cajunspike in #discussion
• Timestamp: 2026-07-04 (Akari created_at=1783185045448)
• Akari message id: 36d53f55-4b4b-4a46-92ec-0db3f9a2be15
• Quote: “is there a module like /day7 example command which tells you how many days till blood moon?”

Test evidence

• npm install --legacy-peer-deps
• npm run build
• node --test-concurrency 1 --import=ts-node-maintained/register/esm --test 'modules/blood-moon-countdown/test/*.test.ts' — 5 helper tests passing
• node dist/scripts/module-to-json.js modules/blood-moon-countdown /tmp/blood-moon-countdown.json — verified converted JSON has description, config, commands (bloodmoon, day7), hook (discordBloodmoon), and helper function.
• Sandbox API shape check: manual current-API create flow for QA module blood-moon-countdown-qa created module/version plus function, commands, and hook successfully; fetched module showed expected description/commands/hook/function.

Remaining QA

• Real 7D2D command execution still needs human/runtime verification. The repo import helper/API path imported an empty version via /module/import, so I used the current API create flow only for shape verification and did not claim in-game completion.
• Suggested human QA: install on a 7D2D testing lane, run /day7 and /bloodmoon, verify command-executed success plus PM text showing current day/next horde day/days remaining. Also test manual fallback by disabling parseConsoleTime and setting manualCurrentDay.

[koji-assistant]

CI update: Build and typecheck passed on head 3087a41c0069779dda9dd49bbac3238302621873; Integration tests failed before module tests ran because CI could not pull 967985385710.dkr.ecr.eu-west-3.amazonaws.com/takaro-app-api:latest (manifest unknown: Requested image not found). This looks like CI/environment image availability, not a module test failure.

Local evidence remains:

• npm run build passed.
• Focused blood-moon-countdown helper tests passed: 5/5.
• Module conversion and sandbox current-API shape verification succeeded for commands/hooks/functions.