DOCUMENTATION

This mirror documents how the bot, dashboard, and webhook pieces fit together.

The static docs page is intentionally practical: it points to the real runtime model, the server routes, and the deployment path, rather than repeating the original prototype copy.

ARCHITECTURE

The bot runs as a modular command loader, the server exposes status/logs/admin/API routes, and the webhook deployment path restarts the runtime when GitHub pushes land.

COMMAND HANDLER

Commands are loaded from a data file and expanded through individual modules. That keeps the slash-command surface modular and easy to extend without adding a giant switch statement to the bot entrypoint.

src/data/commands.json
src/cmds/*.js
src/bot.js

WEBHOOK

The webhook path verifies the GitHub signature, rejects malformed payloads, and triggers the deploy script only for the expected branch.

Admin login uses the real password; the hash in the environment is only for verification. That same pattern keeps the dashboard session cookie separate from the stored secret.

RECENT SIGNALS

The terminal below preserves ANSI escapes so status text stays colour-coded in the docs preview.