Testing & Reliability

• gambling-bot-discord PRs: GitHub Actions runs coverage, Prettier, ESLint, tsc, build, and Vitest before merge.
• Push to main triggers deploy: Actions opens SSH to the VPS (retries on flaky connections) and runs the host deploy script as a dedicated deploy user.
• Production process is PM2 (ecosystem.config.cjs): fork mode, autorestart, 300M memory restart, logs under /var/log/gambling-bot, env loaded from a path outside the app tree.
• Deploy updates the app and reloads the supervised process so the bot does not stay offline - PM2 keeps it alive and brings it back under the same service definition.
• gambling-bot-shared: version bump → merge main → release workflow runs checks, builds, and publishes to npm (skips if that version is already on the registry). Consumers bump the dependency when ready.
• Shared bump script (pnpm bump) + CI release keeps Discord and admin on the same published package instead of drifting private copies.

Long-running Discord bots cannot rely on players to finish every session. A shared runWorkerLoop scheduler starts on clientReady and runs idempotent jobs on intervals defined in workerDefinitions.ts. Optional worker-log channels surface what ran. The full schedule is cataloged in docs/WORKERS_STRUCTURE.txt.

• docs/COMMANDS_STRUCTURE.txt - full slash-command tree: player (misc) ATM / casino / utils vs mod auth, setup-*, events, and ops tools (ban, history, manage-balance, money-manager, …).
• docs/WORKERS_STRUCTURE.txt - every job with interval, start delay, and a one-line purpose (from VIP expiry to plinko idle close).
• Generated / updated from the live CommandKit command tree and workerDefinitions so docs do not quietly drift from production behavior.
• Dev helpers (/mock-db, /mock-worker-db, /clear-mock-db) seed users, MockUserProfile avatars, and intentionally broken state for admin UI and workers.

Correctness is part of the product. All three repos run Vitest (unit + integration where relevant), ESLint, Prettier, and tsc --noEmit via pnpm check.

• Unit: blackjack/baccarat/mines/hilo engines (incl. continuous streak settle), European roulette planSpin/infer, plinko path/render, RTP helpers (incl. side bets), bet validation, cooldowns, slip merge helpers.
• Integration: casinoBet sessions, plinko session DB + recovery, daily bonus claims, prediction bets, raffle DB, VIP DB, workers (autolock, raffle draw, blackjack autostand, idle resolve).
• mongodb-memory-server for hermetic database tests.
• Shared package tests cover domain math used by both bot and admin (incl. roulette win/RTP over the European wheel).
• Moderator simulate / audit scripts for economy stress and jackpot-style math checks.

• Concurrency - MongoDB transactions + unique betId indexes prevent double-spend and duplicate settlement when users spam interactions.
• Dual balance - bonus-first bet consumption and locked balance keep withdrawable cash honest while still rewarding streak/quest play.
• Abandoned sessions - multi-step Discord UIs (blackjack splits, baccarat slips, mines boards, plinko drop batches, hi-lo streaks) need idle workers, in-flight recovery, and lock reconciliation.
• Config drift - central package + Zod schemas + guild sync worker keep bot memory and dashboard writes aligned.
• Permission model - dashboard distinguishes Discord Administrator vs configured manager role; settings UI hidden from limited managers.
• RP safety - gated ATM and audited staff actions document every sensitive balance change for moderator review.
• Multi-bet complexity - slips and multi-hand blackjack must lock the right totals, settle line-by-line, and still refund cleanly on cancel/idle close.