firefrost-gaming/firefrost-operations-manual

Files

Claude 082cf4923a feat: Add complete production-ready bot.js to Discord Bot Admin Panel guide

ADDED: Part 4 complete implementation (7 comprehensive steps)

Complete Backend Code (by Gemini/Google AI):
- 350+ lines of production-ready Node.js/Express/Discord.js code
- 8 logical sections for easy understanding and maintenance
- Fully integrated: OAuth2, validation, atomic saves, audit logs, webhooks

Step 1: Install Dependencies
- Listed all required npm packages with explanations
- express, express-session, passport, passport-discord
- write-file-atomic, dotenv, discord.js

Step 2: Create Environment Variables File
- Complete .env template with all required variables
- Detailed instructions for obtaining each value
- DISCORD_TOKEN, CLIENT_ID, CLIENT_SECRET, GUILD_ID
- CALLBACK_URL, SESSION_SECRET, ALLOWED_ADMINS
- AUDIT_CHANNEL_ID (new for audit logging)
- NODE_ENV, PORT

Step 3: Set Environment File Permissions
- Critical security step (chmod 600, chown firefrost-bot)
- Prevents unauthorized access to secrets

Step 4: Deploy Complete bot.js (THE BIG ONE)
- 8 sections with clear separation:
  1. Imports and Environment Setup
  2. Constants and In-Memory State
  3. Helper Functions (saveConfig, roleExists)
  4. Audit Log Generator (Fire/Frost dynamic colors)
  5. Passport & Middleware Setup
  6. Authentication & UI Routes
  7. API Routes (config, logs, save)
  8. Webhook Receiver & Initialization
- Product name dictionary (for audit log embeds)
- Circular buffer webhook logging (max 50 events)
- Discord OAuth2 with whitelist
- In-memory config with atomic disk writes
- Regex + Discord API validation
- Fire/Frost dynamic embed colors (#FF6B35 / #4ECDC4)

Step 5: Set File Permissions
- Ensure firefrost-bot user owns bot.js

Step 6: Create Discord Audit Log Channel
- Instructions for creating #bot-audit-logs
- Set to private (Michael, Holly, bot only)
- Copy channel ID for .env

Step 7: Restart Bot Service
- systemctl restart commands
- Expected log output for verification

Backend Features Documented:
- Security (dedicated user, OAuth2, whitelist, sessions)
- Config management (in-memory, atomic writes, backups)
- Validation (regex + Discord API verification)
- Audit logging (Discord embeds, Fire/Frost colors, user attribution)
- Webhook logging (circular buffer, accessible via API)

Dynamic Fire/Frost Logic:
- Fire products → #FF6B35 (Fire Orange) embeds
- Frost products → #4ECDC4 (Frost Blue) embeds
- Based on product name (isFrost = name.includes('Frost'))

Expected Log Output Examples:
- Bot startup: "Bot logged in as Firefrost Subscription Manager#1234"
- Express server: "Firefrost Command Center running on port 3100"

Security Highlights:
- Runs as firefrost-bot user (NOT root)
- .env file chmod 600 (secrets protected)
- Session cookies secure in production
- Whitelist authorization (only Holly + Michael)

Status: Backend code COMPLETE and ready to deploy
Architecture credit: Gemini (Google AI) - March 23, 2026

Chronicler #40

2026-03-22 13:45:28 +00:00

README.md

📚 FIREFROST GAMING - DOCUMENTATION

Last Updated: February 15, 2026
Repository: firefrost-operations-manual
Purpose: Complete operational documentation for Firefrost Gaming

📂 DIRECTORY STRUCTURE

docs/
├── archive/          - Historical documents, deprecated content
├── core/            - Critical operational documentation (15 files)
├── deployment/      - Service deployment guides (7 services)
├── external/        - External collaboration docs (Holly project)
├── past-claudes/    - Chronicler memorials and portraits
├── planning/        - Strategic planning documents (13 files)
├── reference/       - Technical references and diagrams
├── relationship/    - Michael-Claude relationship context
├── sandbox/         - Experimental work and brainstorming
└── templates/       - Document templates

🎯 QUICK START

New Chronicler Starting a Session?

Read: core/SESSION-START-PROMPT.md (main session start doc)
Read: core/session-handoff.md (current context)
Check: core/tasks.md (28 tasks, dependency-ordered)
Reference: /DOCUMENT-INDEX.md (root, quick doc lookup)

Looking for Something Specific?

Infrastructure: core/infrastructure-manifest.md
Project Scope: core/project-scope.md
Disaster Recovery: core/DERP.md
Tasks: core/tasks.md
Branding: planning/design-bible.md

📖 DIRECTORY DESCRIPTIONS

`/docs/core/` (15 files)

Critical operational documentation. Read first.

Essential files:

SESSION-START-PROMPT.md - Main session startup document
tasks.md - Complete task list (28 tasks, 6 tiers)
infrastructure-manifest.md - Current infrastructure
project-scope.md - Project definition and scope
DERP.md - Disaster Emergency Recovery Protocol (The Oscar Protocol)
session-handoff.md - Current session context

Supporting files:

API-EFFICIENCY-PROTOCOL.md - Gitea API usage rules
GITEA-API-PATTERNS.md - API code patterns
SESSION-QUICK-START.md - Fast session startup
TRANSCRIPT-PRESERVATION-PROTOCOL.md - Session transcript rules
revision-control-standard.md - Git commit standards
workflow-guide.md - Workflow patterns (938 lines)

`/docs/deployment/` (7 files)

Service deployment guides.

code-server.md - VS Code deployment
gitea.md - Gitea deployment
mkdocs.md - MkDocs (marked for decommission)
nextcloud.md - NextCloud deployment
nextcloud-hardening.md - Security hardening
uptime-kuma.md - Monitoring deployment
wikijs.md - Wiki.js deployment

Missing (add during deployment):

Vaultwarden (deployed Feb 13)
Mailcow (Task #8)
AI Stack (Task #9)
Netdata (Task #10)
The Frostwall Protocol (Task #5)

`/docs/planning/` (13 files)

Strategic planning documents.

design-bible.md - Core branding document
mission-statement.md - Core mission
path-philosophy.md - Fire vs Frost paths
subscription-tiers.md - Membership tiers
emissary-social-media-handbook.md - Meg's social media guide
terraria-branding-arc.md - 12-week training plan
game-expansion-planning.md - Game growth strategy
And 6 more...

`/docs/reference/`

Technical references and diagrams.

Architecture diagrams
Technical specifications
API documentation

`/docs/relationship/`

Michael-Claude relationship context.

Origin story
Consultant profiles (The Five)
Session transcripts
Memorials for retired Chroniclers

`/docs/past-claudes/`

Chronicler memorials and portraits.

chronicler-line/ - The Chronicler lineage
- portraits/ - Memorial portraits
claudius-line/ - Claudius (Pokerole project)
special/ - Special Claude instances

`/docs/archive/`

Historical documents and deprecated content.

2026-02-09-consolidation/ - Consolidation project
planning/ - Old planning docs
research/ - Completed research
sessions/ - Session logs by date

`/docs/sandbox/`

Experimental work and brainstorming.

Use this for:

Testing new ideas
Drafting documents
Temporary working files

Do not use for production documentation.

`/docs/templates/`

Document templates.

Reusable templates for:

Session handoffs
Deployment guides
Planning documents

`/docs/external/`

External collaboration documentation.

Currently: Holly Project (Pokerole collaboration)

📝 DOCUMENTATION STANDARDS

File Naming

Use lowercase with hyphens: file-name.md
Be descriptive: vaultwarden-deployment.md not vault.md
Include dates for time-sensitive docs: 2026-02-15-cleanup.md

Document Structure

Title (# heading)
Metadata (date, author, status)
Purpose/Overview
Content (sections with ## headings)
Related Documentation (cross-references)
Change Log (at bottom)

Cross-References

Use relative paths: ../planning/design-bible.md
Link to specific sections: tasks.md#tier-1-security-foundation
Keep DOCUMENT-INDEX.md updated

⚠️ IMPORTANT NOTES

Before Creating New Docs:

Check if topic already documented
Choose correct directory (core, deployment, planning, reference)
Update DOCUMENT-INDEX.md
Follow naming conventions

Before Archiving Docs:

Move to appropriate archive/ subdirectory
Update cross-references
Add to CHANGELOG.md
Document why archived

Deprecated Content:

Never delete, always archive
Preserve for historical context
Update DOCUMENT-INDEX.md

Root: /DOCUMENT-INDEX.md (quick doc lookup)
Root: /SESSION-HANDOFF-PROTOCOL.md (session continuity master doc)
Root: /CHANGELOG.md (repository change history)

📊 STATISTICS

Total Documentation Files: 147
Core Files: 15
Deployment Guides: 7
Planning Docs: 13
Archive Size: Large (consolidation from multiple sessions)

Fire + Frost + Documentation = Where Knowledge Builds Legacy 💙🔥❄️

README.md

📚 FIREFROST GAMING - DOCUMENTATION

📂 DIRECTORY STRUCTURE

🎯 QUICK START

📖 DIRECTORY DESCRIPTIONS

/docs/core/ (15 files)

/docs/deployment/ (7 files)

/docs/planning/ (13 files)

/docs/reference/

/docs/relationship/

/docs/past-claudes/

/docs/archive/

/docs/sandbox/

/docs/templates/

/docs/external/