fix: switch GMW AI source from omniroute to 9router

- Change AI_LLM_BASE_URL default from omniroute.imrnes.team to 9router.asepharyana.my.id
- Update AI_LLM_MODEL default from 'text' to 'claude-opus-5' (bare model name
  compatible with 9router/OpenAI-compatible router)
- Update .env.example and inline comments to reflect 9router
- discord-gateway config now matches backend (which already uses 9router)

.env.example

@@ -1,5 +1,16 @@
 # Discord Bot Configuration
 # =============================================================================
+#
+# PRODUCTION ENV IS DECLARATIVE:
+# The runtime env files on the VPS (/etc/gmw/backend.env,
+# /etc/gmw/discord-gateway.env) are WRITTEN BY CI from Gitea Actions secrets
+# (BACKEND_ENV, GATEWAY_ENV) — see .gitea/workflows/deploy.yml.
+# To change production env: update the secret in Gitea repo settings
+# (Settings → Actions → Secrets), then push any commit to main. Never
+# SSH into the VPS to edit env files by hand — CI will overwrite them.
+#
+# This file documents every variable; values for production live in the
+# secrets, not here.
 
 # === Discord ===
 DISCORD_TOKEN=your_bot_token_here       # REQUIRED
@@ -28,7 +39,7 @@ AUDIO_CHANNELS=2                        # Number of audio channels (default: 2)
 AVATAR_SIZE=64                          # User avatar size in pixels (default: 64)
 
 # === Webserver ===
-WEBSERVER_PORT=3001                     # Backend HTTP/WS server port (default: 3001)
+WEBSERVER_PORT=4001                     # Backend HTTP/WS server port (default: 4001)
 
 # === Connection ===
 VOICE_CONNECTION_TIMEOUT_MS=15000       # Voice connection timeout in ms (default: 15000)
@@ -44,7 +55,7 @@ VERBOSE=false                           # Enable verbose/debug logging (default:
 
 # === Database (PostgreSQL) ===
 # Option 1: Connection string (overrides individual params)
-# DATABASE_URL=postgresql://user:password@localhost:5432/discord_bot
+DATABASE_URL=postgresql://asephs:***@100.121.180.82:6432/dcbot
 
 # Option 2: Individual connection parameters
 POSTGRES_HOST=localhost                 # PostgreSQL host (default: localhost)
@@ -56,11 +67,11 @@ POSTGRES_POOL_MIN=2                     # Minimum pool connections (default: 2)
 POSTGRES_POOL_MAX=10                    # Maximum pool connections (default: 10)
 
 # === Redis ===
-REDIS_URL=redis://localhost:6379        # Redis connection string (default: redis://localhost:6379)
+REDIS_URL=redis://100.121.180.82:6379        # Redis connection string (default: redis://localhost:6379)
 
 # === Voice PCM WebSocket (direct gateway→backend, bypasses Redis) ===
 VOICE_PCM_WS_ENABLED=true               # Use direct WS for PCM audio (default: true)
-BACKEND_WS_URL=ws://backend:3000/ws     # Backend WebSocket URL for gateway PCM streaming
+BACKEND_WS_URL=ws://backend:4001/ws     # Backend WebSocket URL for gateway PCM streaming
 BACKEND_WS_TOKEN=                       # REQUIRED if VOICE_PCM_WS_ENABLED=true. Internal shared secret
 
 # === Attachments ===
@@ -73,14 +84,20 @@ BACKLOG_SYNC_BATCH_SIZE=100             # Messages per backlog batch, max 100 (d
 
 # === AI Analysis ===
 AI_ANALYSIS_ENABLED=false               # Enable AI content moderation (default: false)
-# AI_LLM_API_KEY=                        # REQUIRED if AI_ANALYSIS_ENABLED=true. LLM API key
-AI_LLM_BASE_URL=https://9router.asepharyana.my.id/v1  # LLM API base URL (default)
-AI_LLM_MODEL=text                       # LLM text model name (default: text)
+AI_LLM_API_KEY=                        # REQUIRED if AI_ANALYSIS_ENABLED=true. LLM API key
+AI_LLM_BASE_URL=https://9router.asepharyana.my.id/v1  # LLM API base URL (9router — OpenAI-compatible router, replaces omniroute)
+AI_LLM_MODEL=claude-opus-5                   # LLM text model name (default: claude-opus-5)
 # AI_LLM_VISION_MODEL=                   # Vision model for image analysis (falls back to AI_LLM_MODEL)
+# AI_LLM_EMBEDDING_MODEL=                # Embedding model for semantic moderation cache (optional; enables near-duplicate text reuse to save LLM calls)
+# AI_LLM_EMBEDDING_MIN_SIMILARITY=0.97   # Min cosine similarity to reuse a cached verdict (default: 0.97)
+QDRANT_URL=http://100.121.180.82:6333        # Qdrant vector store for embeddings (semantic cache); when set, vectors are stored/searched in Qdrant instead of Postgres
+# QDRANT_COLLECTION=gmw_text_moderation  # Qdrant collection name (default: gmw_text_moderation)
+# QDRANT_API_KEY=                        # Qdrant API key (optional)
 AI_LLM_MAX_CONCURRENT=5                 # Max concurrent LLM API calls (default: 5)
 AI_LLM_IMAGE_MAX_DIMENSION=1024         # Max image dimension in pixels before resize (default: 1024)
 AI_LLM_TEXT_BATCH_SIZE=20               # Max messages per text-only moderation batch (default: 20)
 AI_LLM_MEDIA_ANALYSIS_TIMEOUT_MS=60000  # Timeout in ms for media analysis calls (default: 60000)
+AI_LLM_TEXT_ANALYSIS_TIMEOUT_MS=30000  # Timeout in ms for text-only analysis calls (default: 30000)
 
 # === AI Analysis Tuning ===
 AI_ANALYSIS_DEBOUNCE_MS=500             # Debounce window for batching messages in ms (default: 500)
@@ -94,11 +111,6 @@ AI_ANALYSIS_PROCESSING_TIMEOUT_MS=120000 # Conversation lock timeout in ms (defa
 AI_ANALYSIS_INDIVIDUAL_MAX_CONCURRENT=50 # Max concurrent individual-fallback jobs (default: 50)
 AI_ANALYSIS_INDIVIDUAL_CB_THRESHOLD=50  # Consecutive errors before circuit breaker trips (default: 50)
 
-# === OpenAI Moderation (optional separate provider) ===
-# OPENAI_MODERATION_API_KEY=              # OpenAI API key for moderation endpoint
-# OPENAI_MODERATION_BASE_URL=https://api.openai.com/v1  # OpenAI moderation base URL (default)
-# OPENAI_MODERATION_MODEL=omni-moderation-latest         # OpenAI moderation model (default)
-
 # === Auto-Delete ===
 AUTO_DELETE_FLAGGED_ENABLED=true        # Enable auto-deletion of flagged messages (default: true)
 AUTO_DELETE_FLAGGED_DRY_RUN=true        # Dry-run mode: log but do not delete (default: false)

.env.test.example

@@ -2,5 +2,5 @@ NODE_ENV=test
 # Use a separate database/data area for tests. It may be on the same PostgreSQL host,
 # but the database name must clearly be a test database so destructive test setup
 # cannot touch production data.
-TEST_DATABASE_URL=postgres://root:root@100.108.1.124:5432/hub_test
-DATABASE_URL=postgres://root:root@100.108.1.124:5432/hub_test
+TEST_DATABASE_URL=postgres://root:root@100.121.180.82:6432/hub_test
+DATABASE_URL=postgres://root:root@100.121.180.82:6432/hub_test

.gitea/workflows/deploy.yml

@@ -1,70 +0,0 @@
-name: Build & Deploy (Nix)
-
-on:
-  push:
-    branches:
-      - main
-
-jobs:
-  build-and-deploy:
-    runs-on: ubuntu-latest
-
-    strategy:
-      fail-fast: false
-      max-parallel: 1
-      matrix:
-        service: [backend, discord-gateway, proxy]
-
-    steps:
-      - name: Check out repository
-        run: |
-          git clone https://git.imrnes.team/MythEclipse/GMW.git .
-          git checkout ${{ github.sha }}
-
-      - name: Build & Deploy ${{ matrix.service }}
-        env:
-          VPS_HOST: ${{ secrets.VPS_HOST }}
-          VPS_USER: ${{ secrets.VPS_USER }}
-          VPS_SSH_KEY: ${{ secrets.VPS_SSH_KEY }}
-        run: |
-          set -eu
-
-          # --- Install Nix & Build ---
-          curl -fsSL https://install.determinate.systems/nix \
-            | sh -s -- install linux --no-confirm --init none 2>&1
-
-          mkdir -p /etc/nix
-          echo "experimental-features = nix-command flakes" >> /etc/nix/nix.conf
-
-          . /nix/var/nix/profiles/default/etc/profile.d/nix-daemon.sh
-
-          SERVICE="${{ matrix.service }}"
-          echo "=== Building: $SERVICE ==="
-          nix build ".#$SERVICE" --impure --option sandbox false 2>&1
-
-          STORE_PATH=$(readlink result)
-          echo "=== Store path: $STORE_PATH"
-
-          # --- Deploy ---
-          NIX_BIN="/nix/var/nix/profiles/default/bin"
-          PROFILE="/nix/var/nix/profiles/gmw-$SERVICE"
-
-          key_file=$(mktemp /tmp/deploy-key.XXXXXX)
-          printf '%s\n' "$VPS_SSH_KEY" > "$key_file"
-          chmod 600 "$key_file"
-
-          export NIX_SSHOPTS="-i $key_file -o StrictHostKeyChecking=no"
-          nix copy --to "ssh://${VPS_USER}@${VPS_HOST}" "$STORE_PATH" 2>&1
-
-          ssh -i "$key_file" -o StrictHostKeyChecking=no \
-            "${VPS_USER}@${VPS_HOST}" "
-            if [ -d $PROFILE ] && [ ! -L $PROFILE ]; then
-              rm -rf $PROFILE
-            fi
-            export PATH=\$PATH:$NIX_BIN
-            nix-env --profile $PROFILE --set $STORE_PATH
-            systemctl daemon-reload
-            systemctl restart gmw-$SERVICE
-            sleep 3
-            systemctl status gmw-$SERVICE --no-pager 2>&1 | head -12
-          " 2>&1

.github/workflows/deploy.yml

@@ -0,0 +1,260 @@
+name: Build & Deploy (Nix)
+
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+
+concurrency:
+  group: gmw-deploy
+  cancel-in-progress: false
+
+permissions:
+  contents: read
+  id-token: write
+
+env:
+  VPS_HOST: ${{ secrets.VPS_HOST }}
+  VPS_USER: ${{ secrets.VPS_USER }}
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v7
+        with:
+          fetch-depth: 0
+          submodules: false
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+
+      - name: Install pnpm
+        run: corepack enable && corepack prepare pnpm@11 --activate
+
+      - name: Install deps (backend)
+        working-directory: services/backend
+        run: pnpm install --ignore-scripts --no-frozen-lockfile
+
+      - name: Typecheck + test (backend)
+        working-directory: services/backend
+        run: |
+          ./node_modules/.bin/tsc --noEmit
+          # e2e.test.ts requires a live backend (API_BASE) — run unit tests only
+          ./node_modules/.bin/vitest run --exclude "src/e2e.test.ts"
+
+      - name: Install deps (discord-gateway)
+        working-directory: services/discord-gateway
+        run: pnpm install --ignore-scripts --no-frozen-lockfile
+
+      - name: Typecheck + test (discord-gateway)
+        working-directory: services/discord-gateway
+        run: |
+          ./node_modules/.bin/tsc --noEmit
+          ./node_modules/.bin/vitest run
+
+      - name: Biome check (all services)
+        run: |
+          cd services/backend && ./node_modules/.bin/biome check src/ tests/
+          cd ../discord-gateway && ./node_modules/.bin/biome check src/
+
+  build-and-deploy:
+    needs: test
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        service: [backend, discord-gateway, proxy, frontend]
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v7
+        with:
+          fetch-depth: 0
+          submodules: false
+
+      - name: Install Nix
+        uses: DeterminateSystems/nix-installer-action@v22
+        with:
+          determinate: false
+          extra-conf: |
+            sandbox = false
+            accept-flake-config = true
+            # Attic binary cache as substituter on the runner: lets CI pull the
+            # prebuilt attic client (and any cached deps/builds) over HTTPS,
+            # no SSH round-trip needed. extra-substituters (NOT
+            # extra-trusted-substituters) is required — Determinate Nix never
+            # merges trusted-* substituters for nix-store CLI clients.
+            extra-substituters = https://attic.asepharyana.my.id/gmw
+            extra-trusted-public-keys = gmw:Fq2Anzuhkb+T/hftWnPcveHSi21/RzIgIOeG8pCJa88=
+            # NOTE: nix-installer-action unconditionally injects
+            # 'build-provenance-tags' into /etc/nix/nix.conf (a Determinate
+            # Nix-only setting). With determinate:false the runner's upstream
+            # nix warns 'unknown setting build-provenance-tags' on every
+            # invocation — benign, cosmetic. Switching determinate:true would
+            # silence it but changes the runner's nix flavor.
+
+      - name: Cache Nix
+        uses: DeterminateSystems/magic-nix-cache-action@v14
+        with:
+          use-flakehub: false
+
+      - name: Build ${{ matrix.service }}
+        id: build
+        run: |
+          nix build .#${{ matrix.service }} --impure --option sandbox false --print-build-logs
+          STORE_PATH=$(readlink result)
+          echo "store-path=$STORE_PATH" >> "$GITHUB_OUTPUT"
+          echo "Build OK ${{ matrix.service }}: $STORE_PATH"
+
+      - name: Setup SSH key
+        env:
+          SSH_KEY: ${{ secrets.SSH_PRIVATE_KEY }}
+        run: |
+          mkdir -p ~/.ssh
+          echo "$SSH_KEY" > ~/.ssh/id_ed25519
+          chmod 600 ~/.ssh/id_ed25519
+          sed -i 's/\r$//' ~/.ssh/id_ed25519
+          ssh-keygen -y -f ~/.ssh/id_ed25519 >/dev/null 2>&1 || { echo "SSH key invalid"; exit 1; }
+          ssh-keyscan -H "$VPS_HOST" >> ~/.ssh/known_hosts 2>/dev/null
+
+      # Push build result to Attic binary cache (attic.asepharyana.my.id) so
+      # the VPS can substitute it instead of a single-stream `nix copy ssh://`.
+      #
+      # Fast path: push DIRECTLY from the runner to the public attic endpoint
+      # (validated 2026-08-10: token auth over public HTTPS works without
+      # Tailscale). This skips the ~794MB closure SSH copy to the VPS that
+      # used to take 25+ minutes per new store path.
+      #
+      # The attic client is NOT in nixpkgs anymore and has no prebuilt
+      # releases, so we pull the same prebuilt closure the VPS uses
+      # (/nix/store/fygyy3yk4rqdknxkiwkqambpnhyax0k4-attic-0.1.0, ~52MB).
+      # The closure itself lives in the attic cache (pushed once from the
+      # VPS), so the runner bootstraps it over HTTPS via the configured
+      # extra-substituters — no SSH round-trip. If that fails we fall back
+      # to `nix copy --from ssh://`, then the old VPS-hop flow (SSH copy to
+      # VPS, then attic push from the VPS over Tailscale) so the deploy step
+      # always has a working closure path.
+      - name: Push to Attic cache
+        env:
+          ATTIC_TOKEN: ${{ secrets.ATTIC_TOKEN }}
+        run: |
+          if [ -z "$ATTIC_TOKEN" ]; then
+            echo "ATTIC_TOKEN not set; skipping attic push"
+            exit 0
+          fi
+          STORE_PATH="${{ steps.build.outputs.store-path }}"
+          ATTIC_DIR="/nix/store/fygyy3yk4rqdknxkiwkqambpnhyax0k4-attic-0.1.0"
+          ATTIC_BIN="$ATTIC_DIR/bin/attic"
+
+          attic_push_vps_hop() {
+            echo "Fallback: VPS-hop attic push"
+            # Copy closure to VPS (fast if attic already has it via substitute)
+            ssh "$VPS_USER@$VPS_HOST" "sudo /nix/var/nix/profiles/default/bin/nix-store --realise '$STORE_PATH'" 2>/dev/null \
+              || nix copy --to "ssh://$VPS_USER@$VPS_HOST" "$STORE_PATH"
+            # Push from VPS → Attic over Tailscale.
+            # --ignore-upstream-cache-filter is REQUIRED: without it, attic skips
+            # writing the narinfo to gmw when chunks exist in the upstream
+            # cache.nixos.org — leaving the path 404 on gmw so the VPS deploy's
+            # nix-store --realise can't find it and falls back to ssh copy.
+            # sudo: attic must read root's config (~/.config/attic), which has
+            # the imrnes-ts server → Tailscale. Non-root users' configs only
+            # have the public `pub` server → "Server imrnes-ts does not exist".
+            ssh "$VPS_USER@$VPS_HOST" "sudo $ATTIC_BIN push imrnes-ts:gmw '$STORE_PATH' --jobs 4 --ignore-upstream-cache-filter" \
+              || echo "attic push failed (non-fatal; ssh copy fallback below)"
+          }
+
+          # ── Get an attic client on the runner ────────────────────────────
+          # Order: PATH → pull the prebuilt closure from the attic cache
+          # itself (extra-substituters configured in Install Nix step, HTTPS
+          # only, no SSH) → pull over ssh from the VPS → VPS-hop.
+          # The attic client closure is stored in the attic cache (pushed
+          # once from the VPS), so the fast path never depends on SSH.
+          ATTIC_BIN=""
+          if command -v attic >/dev/null 2>&1; then
+            ATTIC_BIN="$(command -v attic)"
+          elif nix-store --realise "$ATTIC_DIR" 2>/tmp/attic-bootstrap.err; then
+            echo "✅ Pulled attic client from attic cache (HTTPS substituter)"
+            ATTIC_BIN="$ATTIC_DIR/bin/attic"
+          elif nix copy --from "ssh://$VPS_USER@$VPS_HOST" "$ATTIC_DIR" 2>>/tmp/attic-bootstrap.err; then
+            echo "✅ Pulled attic client from VPS over ssh"
+            ATTIC_BIN="$ATTIC_DIR/bin/attic"
+          else
+            echo "attic client unavailable on runner; using VPS-hop flow"
+            echo "--- bootstrap errors (stderr) ---"
+            tail -5 /tmp/attic-bootstrap.err 2>/dev/null || true
+            attic_push_vps_hop
+            exit 0
+          fi
+
+          # ── Direct push: runner → attic public endpoint ──────────────────
+          # --ignore-upstream-cache-filter forces the narinfo write even when
+          # the path's chunks already exist in upstream cache.nixos.org (which
+          # attic would otherwise skip, leaving the path 404 on the gmw cache).
+          mkdir -p "$HOME/.config/attic"
+          cat > "$HOME/.config/attic/config.toml" <<EOF
+          default-server = "pub"
+
+          [servers.pub]
+          endpoint = "https://attic.asepharyana.my.id"
+          token = "$ATTIC_TOKEN"
+          EOF
+          # Retry the direct push — a transient 502 (e.g. atticd restart,
+          # Traefik blip) must not abort the whole closure upload. attic push
+          # is idempotent, so re-running only uploads what's still missing.
+          push_ok=""
+          for attempt in 1 2 3; do
+            if "$ATTIC_BIN" push pub:gmw "$STORE_PATH" --jobs 4 --ignore-upstream-cache-filter; then
+              echo "✅ Pushed $STORE_PATH to attic directly from runner"
+              push_ok=1
+              break
+            fi
+            echo "⚠️ Direct attic push attempt $attempt/3 failed; retrying in 10s..."
+            sleep 10
+          done
+          if [ -z "$push_ok" ]; then
+            echo "Direct attic push failed after 3 attempts; using VPS-hop flow"
+            attic_push_vps_hop
+          fi
+
+      # NOTE: env files /etc/gmw/backend.env & /etc/gmw/discord-gateway.env are
+      # managed MANUALLY on the VPS (source of truth). CI only builds & deploys.
+      - name: Deploy ${{ matrix.service }} to VPS
+        run: |
+          STORE_PATH="${{ steps.build.outputs.store-path }}"
+          echo "=== Copying ${{ matrix.service }}: $STORE_PATH ==="
+          if [ -n "${{ secrets.ATTIC_TOKEN }}" ] && ssh "$VPS_USER@$VPS_HOST" "sudo /nix/var/nix/profiles/default/bin/nix-store --realise '$STORE_PATH'" 2>/dev/null; then
+            echo "Substituted ${{ matrix.service }} from Attic cache"
+          else
+            echo "Attic substitute failed; falling back to ssh copy"
+            nix copy --to "ssh://$VPS_USER@$VPS_HOST" "$STORE_PATH"
+          fi
+
+          echo "=== Updating profile ==="
+          ssh "$VPS_USER@$VPS_HOST" "sudo /nix/var/nix/profiles/default/bin/nix-env --profile /nix/var/nix/profiles/gmw-${{ matrix.service }} --set '$STORE_PATH'"
+
+          echo "=== Restarting service ===\n"
+                    ssh "$VPS_USER@$VPS_HOST" \
+                      "sudo systemctl daemon-reload && sudo systemctl restart gmw-${{ matrix.service }} && for i in \$(seq 1 15); do state=\$(sudo systemctl is-active gmw-${{ matrix.service }} 2>/dev/null || echo inactive); [ \"\$state\" = \"active\" ] && break; sleep 2; done; echo \"final-state=\$state\"; [ \"\$state\" = \"active\" ]" 
+                    echo "✅ gmw-${{ matrix.service }} deployed"
+
+  cleanup:
+    # Bersihkan sampah Nix di VPS SETELAH semua deploy selesai: hapus generasi
+    # profile lama + nix store gc. Profil yang sedang dipakai tidak disentuh.
+    needs: build-and-deploy
+    if: always()
+    runs-on: ubuntu-latest
+    steps:
+      - name: Nix GC on VPS
+        env:
+          VPS_HOST: ${{ secrets.VPS_HOST }}
+          VPS_USER: ${{ secrets.VPS_USER }}
+          SSH_KEY: ${{ secrets.SSH_PRIVATE_KEY }}
+        run: |
+          mkdir -p ~/.ssh
+          echo "$SSH_KEY" > ~/.ssh/id_ed25519
+          chmod 600 ~/.ssh/id_ed25519
+          ssh-keyscan -H "$VPS_HOST" >> ~/.ssh/known_hosts 2>/dev/null
+          ssh "$VPS_USER@$VPS_HOST" "sudo /usr/local/bin/nix-gc-vps.sh" || echo "⚠️ Nix GC gagal (non-fatal)"

.github/workflows/flakehub-publish-rolling.yaml

@@ -0,0 +1,20 @@
+name: Publish to FlakeHub
+
+on:
+  push:
+    branches: [main, master]
+  workflow_dispatch:
+
+jobs:
+  flakehub-publish:
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+      contents: read
+    steps:
+      - uses: actions/checkout@v6
+      - uses: DeterminateSystems/determinate-nix-action@main
+      - uses: DeterminateSystems/flakehub-push@main
+        with:
+          visibility: public
+          rolling: true

.github/workflows/mirror-gitea.yml

@@ -0,0 +1,26 @@
+name: Mirror to Gitea
+
+on:
+  push:
+    branches: [main, master]
+  workflow_dispatch:
+
+permissions:
+  contents: write
+
+jobs:
+  mirror:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v7
+        with:
+          fetch-depth: 0
+
+      - name: Mirror to Gitea
+        env:
+          GITEA_TOKEN: ${{ secrets.GITEA_TOKEN }}
+        run: |
+          git remote add gitea "https://oauth2:${GITEA_TOKEN}@git.imrnes.team/MythEclipse/GMW.git"
+          git push --mirror gitea
+          echo "✅ Mirrored to Gitea (MythEclipse/GMW)"

.gitignore

@@ -12,7 +12,7 @@ worktrees/
 .worktrees/
 services/frontend/frontend/dist/
 target/
-
+nix/
 # Gitea CI runner logs
 .gitea/workflows/*.log
 

.hermes/plans/2026-08-18_gmw-public-features-2-6.md

@@ -0,0 +1,101 @@
+# GMW — Fitur Publik Lanjutan (#2–#6) Implementation Plan
+
+> **For Hermes:** Implement task-by-task. Build + lint + typecheck each service
+> after its changes. Deploy via push to main (CI handles Nix build + systemd).
+> Hard constraint (user 2026-08-18): public read-only web, fully automatic,
+> rules in code, NO admin endpoints, NO shadow mode, NO per-channel web config.
+> **EXPLICITLY EXCLUDED: User Reputation / Strike History** (user: "hapus
+> sepenuhnya fitur user reputation" — it was never built; do not add it).
+
+## Existing infra to reuse (verified)
+- **WS**: backend `ws/server.ts` broadcasts JSON `{type,data,timestamp}` to
+  frontendClients. Backend `ws/redis-bridge.ts` subscribes Redis channels
+  listed in `DISCORD_CHANNEL_TO_WS_EVENT` (backend `shared/redis-channels.ts`)
+  and re-emits as WS events. FE `src/lib/ws` auto-reconnect typed client.
+- **Gateway → Redis**: `EventBroadcaster` + `RedisEventPublisher` (
+  `discord-gateway/src/modules/event-broadcaster`). Publish via
+  `eventBroadcaster.publish(EventChannels.X, payload)`.
+- **Moderation data**: `moderation_actions` table (now has explainability
+  cols). `moderation.repository.listActions` returns rows. `ModerationAction`
+  FE type at `frontend/src/lib/types/moderation.ts`.
+- **Messages**: `messages.list` / `getMessagesByChannel` (backend oRPC +
+  repository). FE `messagesApi` + `useMessages`.
+- **Charts**: NO chart lib installed. Use **pure SVG/CSS** (consistent with
+  repo; avoid new deps).
+- **CSV**: client-side Blob download, no backend.
+
+## Task 1 — Live Moderation Feed (#2)
+**Gateway**: add `MODERATION_ACTION: "discord:moderation:action"` to
+`redis-channels.ts` (shared) + `EventChannels.MODERATION_ACTION` in
+`eventTypes.ts`. In `moderationActionsDb.createModerationAction`, after insert,
+publish `eventBroadcaster.publish(EventChannels.MODERATION_ACTION, actionRow)`.
+**Backend**: add `DISCORD_MODERATION_ACTION` constant + map
+`[DISCORD_MODERATION_ACTION]: "moderation_action"` in `DISCORD_CHANNEL_TO_WS_EVENT`.
+**FE**: in `src/lib/ws`, subscribe to `moderation_action`; add `useLiveModeration`
+hook (SWR-style with WS push, capped buffer ~50). Add `<LiveModerationFeed>`
+client component on `/moderation` page (top of list, animated new-row).
+Risk: gateway publish at every action (already async insert) — fire-and-forget,
+wrap in try/catch. Verify WS event reaches FE via `wscat`/curl or log.
+
+## Task 2 — Toxic Topic Trends (#3)
+**Backend**: add `moderation.trends` oRPC. Query `moderation_actions` grouped
+by `categories` (jsonb text[]) over last 30 days, count per category + severity
+breakdown. Also `action_type` distribution. Return
+`{ categories: {name,count}[], severities: {level,count}[], actions: {type,count}[] }`.
+Map jsonb array in SQL (use `unnest` or parse in JS). Reuse `getDatabase`.
+**FE**: `useModerationTrends` hook + `<TopicTrends>` SVG bar chart (top 10
+categories) + severity donut (SVG arcs). Place on `/moderation` as a panel.
+
+## Task 3 — Channel Timeline / Replay (#4)
+Reuse existing `messages.list` (guildId) + `getMessagesByChannel`. Add a
+**Timeline tab** to `/messages` that groups messages by date (client-side
+bucket from `created_at`). Load-more via cursor. No new backend (existing
+`messagesRouter.list` already supports guildId+limit+cursor). If needed, add
+`messages.timeline` aggregation (count per day) — but keep simple: client
+groups fetched rows. Verify existing endpoint returns enough history.
+
+## Task 4 — Export CSV (#5)
+**FE only**. `lib/csv.ts` `toCsv(rows, columns)` + `downloadCsv(filename, csv)`.
+Add "Export CSV" button on `/moderation` (exports current actions) and
+`/messages` (exports current list). Pure client-side, read-only. No backend.
+
+## Task 5 — Activity Heatmap (#6)
+**Backend**: add `messages.activity` oRPC: per-channel message count grouped by
+hour-of-day (0–23) over last 14 days. Return
+`{ channels: {channelId, name, byHour: number[24]}[], max }`. Use SQL
+`EXTRACT(hour from ...)` + group by channel. Channel name from
+`message.metadata->'channel'->>'channelName'`.
+**FE**: `useMessageActivity` hook + `<ActivityHeatmap>` SVG grid (channels ×
+24h, color intensity = count/max). Place on `/messages` or `/dashboard`.
+
+## Verification checklist
+- [ ] `pnpm typecheck && pnpm lint && pnpm build` green for gateway, backend, frontend
+- [ ] Backend `/trpc/moderation/trends` returns categories/severities/actions
+- [ ] Backend `/trpc/messages/activity` returns byHour grids
+- [ ] WS `moderation_action` received by FE (log or visible live row)
+- [ ] No admin/write endpoint added; all public read-only
+- [ ] No User Reputation code anywhere (grep "reputation|strike|reputasi")
+- [ ] Deploy via push; all 3 services `running`; moderation + messages pages load
+
+## Files touched (summary)
+- gateway: `shared/redis-channels.ts`, `event-broadcaster/eventTypes.ts`,
+  `event-broadcaster/eventBroadcaster.ts`, `message-capture/moderationActionsDb.ts`
+- backend: `shared/redis-channels.ts`, `orpc/router.ts`,
+  `modules/moderation/moderation.service.ts` (+repository),
+  `modules/messages/messages.service.ts` (+repository, +schema)
+- frontend: `lib/ws/*`, `hooks/use-moderation.ts`, `hooks/use-messages.ts`,
+  `lib/csv.ts`, `lib/types/*`, `app/(dashboard)/moderation/view.tsx`,
+  `app/(dashboard)/messages/view.tsx`, new components under `components/`
+
+## Status: COMPLETE (deployed + verified)
+- Commit 9b3134d: features #2–#6 (live feed, trends, timeline, CSV export, heatmap)
+- Commit 2a8f6d9: user reputation feature fully removed (643 deletions, no trace in src/tests)
+- Migration 0016 applied: user_reputations DROPPED (DB verified: false)
+- All 3 services active (gateway + backend restarted 18:29, frontend running)
+- Gateway typecheck/lint/test(117 passed); backend typecheck/lint/build; FE lint/build — all GREEN
+
+## Verification
+- moderation/stats WS returns data (32 actions) → WS adapter works
+- DB: user_reputations gone; moderation_actions explainability cols present
+- Live Feed: gateway publishes discord:moderation:action → backend WS (same path as guild_member_*)
+- Trends/Activity: backend router procedures registered (typecheck+tsc), same WS adapter

.hermes/plans/2026-08-18_gmw-public-features-7-15.md

@@ -0,0 +1,119 @@
+# GMW — Fitur Publik Lanjutan #7–#15 + Bug Fix Reputation Removal
+
+> **For Hermes:** Implement task-by-task. Build + lint + typecheck each service after its
+> changes. Deploy via push to main (CI handles Nix build + systemd). Apply any new
+> drizzle migration MANUALLY (systemd does NOT run migrations).
+> Hard constraint (user): public read-only web, fully automatic, rules in code,
+> NO admin endpoints, NO shadow mode, NO per-user reputation aggregation.
+
+## Bug fix discovered during planning (MUST do first)
+`services/backend/src/modules/dashboard/dashboard.repository.ts` still references
+`pgUserReputationsTable` (import line 8; JOINs at lines 173 + 457) — that table was
+DROPPED in migration `0016`. `dashboard.listUsers` / `dashboard.userDetail` will
+**crash at runtime** (undefined table). Remove the import + the `r.*` join columns
+(`trust_score`, `clean_message_streak`, `total_infractions`) from both queries.
+This is a regression introduced by the reputation removal commit.
+
+## Features to implement (#7–#15)
+All reuse existing infra: `moderation_actions`, `messages`, `channel_cultures`,
+`term_glossary_cache`, `ai_analysis_runs`, `message_edits`, gateway cron (for #15),
+WS (proven Live Feed pattern), oRPC over WS (proven), pure-SVG charts (no libs).
+
+| # | Feature | Data source | Surface |
+|---|---------|-------------|---------|
+| 7 | Flagged Link / Scam Domain Reporter | regex URL from `moderation_actions.content`/`evidence` | `/moderation` |
+| 8 | Top Flagged Channels | join `moderation_actions.message_id`→`messages.channel_id` | `/moderation` |
+| 9 | Moderation Heatmap by Hour | `moderation_actions.created_at` hour-of-day | `/moderation` |
+| 10 | Flag Category Drill-down | `moderation_actions.categories` (reuse Trends) | `/moderation` FE-only |
+| 11 | Channel Culture Glossary | `channel_cultures` (exists) | new `/channels` panel |
+| 12 | Term Knowledge Base | `term_glossary_cache` (exists) | new `/glossary` panel |
+| 13 | Edit/Evasion Tracker | `message_edits` (exists) | `/messages` |
+| 14 | Auto-mod Coverage Stats | `ai_analysis_runs` (exists) | `/moderation` metric tiles |
+| 15 | Weekly Digest (auto, cron) | aggregate #7/#8/#9 → Discord via gateway cron | gateway cron + `/moderation` |
+
+## Architecture per layer
+
+### Backend (oRPC, `services/backend/src`)
+- New repository methods (add to existing repos, follow `getTrends` SQL style):
+  - `moderation.repository.ts`:
+    - `getTopFlaggedDomains(days)` — `regexp_matches(content,'https?://([^/\s]+)')` on
+      `moderation_actions WHERE created_at>=since`, group by host, COUNT, order DESC LIMIT 20.
+    - `getTopFlaggedChannels(days)` — join `moderation_actions a` LEFT JOIN `messages m`
+      ON `m.id=a.message_id`, group by `m.channel_id`, COUNT, order DESC LIMIT 15.
+      Channel name via `m.metadata::jsonb->'channel'->>'channelName'`.
+    - `getHourlyModeration(days)` — `EXTRACT(HOUR FROM to_timestamp(created_at/1000))`
+      group by hour, COUNT, severity breakdown. (24 rows)
+    - `getFlaggedByCategory(days, category)` — list actions where `categories` contains
+      `category` (reuse `listActions` filter or new query), for drill-down #10.
+    - `getCoverage(days)` — from `ai_analysis_runs`: total runs, status breakdown
+      (clean/flagged/warn/error/pending), coverage % = (analyzed)/(captured in window).
+  - `dashboard.repository.ts` (or new `knowledge.repository.ts`):
+    - `listChannelCultures(limit, search?)` — `channel_cultures` rows (channel_id,
+      guild_id, channel_name from messages metadata, culture_summary, last_analyzed_at).
+    - `listGlossary(limit, search?)` — `term_glossary_cache` (term, definition, source_url,
+      resolved_at, hit_count) order by hit_count DESC.
+  - `messages.repository.ts`:
+    - `getEditHistory(limit, channelId?)` — `message_edits` join `messages` for
+      old_content + channel + username + edited_at, order DESC LIMIT.
+- `moderation.service.ts` / `dashboard.service.ts` / `messages.service.ts`: thin wrappers.
+- `orpc/router.ts`: add procedures (follow `trends` shape):
+  - `moderation.topDomains`, `moderation.topChannels`, `moderation.byHour`,
+    `moderation.byCategory` (input `{days,category}`), `moderation.coverage`.
+  - `dashboard.channelCultures`, `dashboard.glossary`.
+  - `messages.editHistory`.
+
+### Frontend (`services/frontend/src`)
+- `lib/types/moderation.ts`: add `FlaggedDomain`, `FlaggedChannel`, `HourlyModeration`,
+  `ModerationCoverage` interfaces.
+- `lib/types/index.ts` (+ message.ts): add `ChannelCultureRow`, `GlossaryRow`, `EditHistoryRow`.
+- `lib/api/moderation.ts`: add `topDomains`, `topChannels`, `byHour`, `byCategory`, `coverage`.
+- `lib/api/dashboard.ts` (or messages.ts): add `channelCultures`, `glossary`, `editHistory`.
+- `lib/api/server.ts`: add SSR seed fetchers (follow `getModerationStats`).
+- `hooks/use-moderation.ts`: add `useTopDomains`, `useTopChannels`, `useHourlyModeration`,
+  `useByCategory`, `useCoverage`. `hooks/use-dashboard.ts`/`use-messages.ts`: add culture/glossary/edit hooks. `hooks/index.ts`: export all.
+- New components (pure SVG/CSS, reuse `GlassPanel`/`SectionHeader`/`Badge`/`Donut`):
+  - `components/ScamDomains.tsx`, `components/TopChannels.tsx`, `components/ModerationHeatmap.tsx`,
+    `components/CoverageTiles.tsx`, `components/ChannelCultureGlossary.tsx`,
+    `components/TermGlossary.tsx`, `components/EditHistory.tsx`.
+- Wire into `app/(dashboard)/moderation/view.tsx` (grid col-span-2/3/5 as space allows)
+  and `app/(dashboard)/messages/view.tsx` (EditHistory panel) and new route pages
+  `app/(dashboard)/channels/page.tsx` + `app/(dashboard)/glossary/page.tsx` with
+  matching `view.tsx` (follow existing page→view SSR pattern; check `app/(dashboard)/dashboard/page.tsx`).
+- Export CSV buttons reuse `lib/csv.ts` `downloadCsv` (client-side) for domains/channels/edits.
+
+### Gateway (#15 Weekly Digest)
+- Add a cron/interval in `services/discord-gateway` (check existing scheduler pattern —
+  search `setInterval`/`cron` in `src`). On a 7-day cadence, query backend oRPC
+  (`dashboard.activity`, `moderation.trends`, `moderation.topChannels`) — OR compute
+  directly via a shared repository — and post a formatted summary to the monitor guild
+  channel (via existing `discordClient.channels.send` helper). Fully automatic, no UI.
+
+## Files touched (summary)
+- backend: `modules/moderation/{repository,service}.ts`, `modules/dashboard/{repository,service}.ts`,
+  `modules/messages/{repository,service}.ts`, `orpc/router.ts`, `shared/index.ts` (if new tables),
+  `lib/types/*` (FE)
+- frontend: `lib/api/*`, `lib/types/*`, `hooks/*`, `components/*`, `app/(dashboard)/*`
+- gateway: new digest scheduler + (none if reuse backend) maybe `shared/redis-channels.ts`
+
+## Constraints / pitfalls (from gmw-ops skill)
+- `created_at` is bigint epoch-MS — compare with `<`/`>`, do NOT divide by 1000 in SQL.
+- Pure SVG only — frontend has ZERO chart libs.
+- `Badge` Tone = signal|amber|vermilion|neutral (no "rose").
+- Frontend WS import is `@/lib/ws/context`; method `on` not `subscribe`.
+- Commit author `asepharyana`, no Co-Authored-By.
+- Rebuild `dist/` after gateway changes; apply drizzle migrations manually.
+
+## Verification
+- Per service: `pnpm typecheck && pnpm lint && pnpm build` green.
+- Gateway: `pnpm test` (117+ pass).
+- Live: `moderation/stats` WS returns data (proves adapter); new procedures registered
+  (typecheck = proof). `systemctl show` new ActiveEnterTimestamp after deploy.
+- DB: confirm `channel_cultures`/`term_glossary_cache`/`message_edits`/`ai_analysis_runs`
+  have rows before relying on them (some may be empty → components handle empty state).
+
+## Execution order
+1. Bug fix dashboard.repository (reputation JOIN) — deploy-safe.
+2. Backend repositories + service + router (#7,#8,#9,#14 dashboard; #11,#12; #13).
+3. FE types + api + hooks + components + wire (#7,#8,#9,#10,#11,#12,#13,#14).
+4. Gateway #15 digest (if scheduler exists) — verify via log, not UI.
+5. Build/lint all 3 services; commit; push; monitor CI; apply migrations; verify live.

.hermes/plans/2026-08-22_154707-ai-analysis-audit-optimize.md

@@ -0,0 +1,111 @@
+# AI Analysis Flow — Audit & Optimization (discord-gateway)
+
+**Goal:** Analisis alur AI analysis end-to-end, temukan bug/inconsistency yang merusak kualitas verdict, lalu perbaiki root cause-nya.
+
+## Scope
+- `services/discord-gateway/src/modules/ai-moderation/**`
+- Tidak menyentuh chatbot backend / frontend.
+
+## Alur saat ini (hasil tracing)
+```
+message capture → aiAnalyzer.queueMessageAnalysis(messageId)
+  → batchScheduler.scheduleConversationAnalysis(conversationKey)   [debounce 250ms, CB gate]
+  → messageStore.getPendingMessagesByConversation(≤200)
+  → skipAgeRestrictedMessages
+  → pickBatchWithinBudget(14000 tokens, 50/msg)
+  → processBatch [Piscina worker, ≤4 threads]
+      → ai-analysis-worker.processBatch
+          → getConversationContextBefore(20 msgs) + attachments
+          → attachment-upload race guard (pending upload → skip)
+          → runModerationAnalysis
+              → Phase 1: exact-hash cache (PG text_analysis_cache, per channel/thread)
+              → Phase 2: semantic cache (embedTexts → Qdrant batch search; PG fallback)
+              → split text-only vs media
+              → runTextOnlyBatch: URL fetch + wiki search + glossary (paralel)
+                  → dedup short messages → sub-batches (60/sub-batch)
+                  → vision evidence utk URL images (hoisted, 15s cap per image)
+                  → callModerationLLM per sub-batch (stream:true, retries 3, JSON parse + correction retry)
+              → runMediaBatch: download → vision per image (cache LRU→DB→live, lock) → 1 LLM call
+              → setCachedTextModeration (PG + Qdrant upsert w/ embedding)
+          → normalizeResult (confidence clamp, fallback analysis)
+          → updateMessagesAIAnalysisBulk → broadcast + scheduleAutoDelete
+  → recovery worker tiap 10s: pending keys → re-schedule; incomplete → individual fallback queue
+  → individual fallback: 1 msg = 1 worker job (context + full LLM)
+  → cache prune tiap 6 jam (PG expired + Qdrant expired points)
+```
+
+## Temuan audit (ranked)
+
+### F1 — Cache hit menghapus status "warn" (BUG AKURASI)
+`moderationOrchestrator.ts` Phase-2 semantic hit & PG-fallback memetakan status via
+`parseQdrantVerdict`: storedStatus bukan "warn"/"flagged" → dipaksa "clean".
+TAPI exact-hash lookup (`getCachedTextModeration`, textCacheStore.ts:288-295) lebih parah:
+hanya menerima "clean"|"flagged" — **"warn" jatuh ke branch flags.length===0 ? clean : flagged**
+→ warn dengan flags=["conflict_instigation"] dibaca sebagai FLAGGED.
+Efek: auto-delete eligibility (butuh recommendedAction delete/escalate + severity list) salah baca;
+dashboard menampilkan flagged padahal verdict asli warn. Root cause: type narrowing legacy
+(`status: "clean" | "flagged"`) tidak diupdate ketika "warn" ditambahkan ke schema.
+
+### F2 — Exact-cache key mengabaikan edit (BUG EVASION)
+Key = sha256(content)+context. Pesan yang DIEDIT (`edited_content`) menghasilkan hash berbeda,
+tapi verdict lama utk konten pre-edit tetap hidup; lebih penting: pesan edited="true" adalah sinyal
+evasion di prompt, sedangkan cache bisa menyajikan verdict dari konten lama jika content sama.
+(Minor, tapi konsistensi: `resolveIsEdited` ada di prompt, tidak ada di cache key.)
+
+### F3 — `pickBatchWithinBudget` skip-bukan-break (LATENSI/KUALITAS)
+Loop `if (usedTokens + msgTokens <= maxTokens) {push}` — pesan BESAR di tengah list dilewati
+dan iterasi lanjut mencoba msg berikutnya. Efek: batch berisi "lubang" (msg pending tetap pending,
+dianalisis di gelombang berikutnya = LLM call tambahan). Ini by-design tolerable, tapi ada bug halus:
+pesan >budget tunggal tidak pernah masuk (scheduler sudah punya fallback slice(0,1), OK).
+Keputusan: biarkan (bukan bug nyata), catat saja.
+
+### F4 — `callModerationLLM` max_tokens 16384 hardcoded (COST)
+Sub-batch 60 pesan × output ~150 token/pesan ≈ 9k token cukup; 16k aman. Biarkan.
+
+### F5 — Dead code builder user-profile/reputation
+`buildUserProfilesBlock`, `buildUserProfileRef`, `UserProfileEntry` di moderationBuilders.ts
+tidak dipakai lagi sejak context minimization (hanya tests). `<user_history>` juga tak pernah
+di-inject (rules masih menyebutnya — misleading bagi model). Bersihkan referensi prompt.
+
+### F6 — rules.ts menyebut `<user_history>` yang tidak pernah ada di payload
+Model diberi instruksi tentang blok yang tak pernah muncul → pemborosan token + potensi
+kelakuan aneh ("menunggu" data yang tak ada). Hapus/ubah kalimat.
+
+### F7 — system.ts "Blok Data" menyebut `<term_glossary> (SearXNG)` — STALE
+Sumber sudah Wikipedia. Komentar kode & teks prompt menyebut SearXNG. Perbaiki teks (kecil).
+
+### F8 — output.ts typo "secifik", baris tabel `-|-` rusak
+Kualitas prompt: typo + markdown table broken (`||-`) di beberapa baris. Rapikan.
+
+### F9 — llmCaller parse-error correction tail hanya di SYSTEM
+Correction tail ditambahkan ke system prompt; provider caching fine, tapi preview invalid
+content (800 char) ikut SYSTEM — ok. Skip.
+
+### F10 — `getLlmSemaphore` race kecil saat config berubah di tengah flight
+Non-issue praktis (config statis per proses). Skip.
+
+## Keputusan perbaikan (yang dieksekusi sekarang)
+1. **F1 (utama):** normalisasi status di SATU tempat — `normalizeStoredStatus()` di
+   textCacheStore.ts yang menerima clean/warn/flagged; pakai di getCachedTextModeration
+   DAN parseQdrantVerdict; perluas return types ke union penuh. Orchestrator tinggal pakai.
+2. **F6+F7+F8:** bersihkan stale references di prompts (user_history, SearXNG, typo).
+3. **F5:** hapus dead builders + test-nya (biome/tsc yang jaga).
+4. Regression test untuk F1 (vitest): warn tersimpan → warn terbaca (exact + qdrant path).
+
+## Files touched
+- services/discord-gateway/src/modules/ai-moderation/textCacheStore.ts (F1)
+- services/discord-gateway/src/modules/ai-moderation/moderationOrchestrator.ts (type only)
+- services/discord-gateway/src/modules/ai-moderation/prompts/rules.ts (F6)
+- services/discord-gateway/src/modules/ai-moderation/prompts/system.ts (F7)
+- services/discord-gateway/src/modules/ai-moderation/prompts/output.ts (F8)
+- services/discord-gateway/src/modules/ai-moderation/moderationBuilders.ts (F5)
+- services/discord-gateway/tests/contextEnrichment.test.ts (F5 test cleanup + F1 regression test baru)
+
+## Verification
+```
+cd services/discord-gateway
+npx tsc --noEmit
+npx biome check --diagnostic-level=error .
+npx vitest run
+```
+Semua harus hijau sebelum commit. Deploy via GHA (push main) — user konfirmasi belakangan.

.hermes/plans/2026-08-22_nonissue-optimizations.md

@@ -0,0 +1,33 @@
+# Optimisasi "non-issue" AI analysis pipeline
+
+## Scope
+Dua item yang sebelumnya dinyatakan non-issue, kini dioptimalkan + 1 bug ordering
+yang ditemukan saat menelusuri:
+
+1. **pickBatchWithinBudget: skip → break.** Pesan diurutkan `created_at ASC`
+   oleh DB. Setelah budget habis, pesan berikutnya pasti lebih besar/lebih kecil
+   arbitrer — skip-then-take menghasilkan batch non-kontigu (ada gap analisis
+   di tengah timeline). Ubah jadi stop at first overflow (break) supaya prefix
+   kronologis utuh; sisanya otomatis diambil gelombang berikutnya
+   (`shouldScheduleNext` sudah selalu true setelah sukses).
+2. **max_tokens dinamis.** Hard-coded 16384 di llmCaller.ts → parameter
+   opsional `maxTokens?`; default tetap 16384. Caller text/media batch pass
+   nilai berbasis ukuran prompt (tiktoken) dengan floor/ceiling.
+3. **Bug ordering UPDATE..RETURNING (bonus).** messagesAnalysis.ts
+   `getPendingMessagesByConversation`: SELECT ids di-order `created_at ASC`
+   tapi UPDATE...RETURNING tanpa ORDER BY → urutan rows balik tidak
+   terjamin. Konsumen pakai messages[0] sebagai anchor konteks
+   (beforeCreatedAt) dan pickBatchWithinBudget asumsi urutan. Fix: re-sort in
+   JS by created_at (stable) sebelum return.
+
+## Files touched
+- src/modules/ai-moderation/batchProcessor.ts — break bukan skip; test baru.
+- src/modules/ai-moderation/llmCaller.ts — param maxTokens.
+- src/modules/ai-moderation/textBatchProcessor.ts / mediaBatchProcessor.ts —
+  hitung token prompt & pass maxTokens.
+- src/modules/message-capture/messagesAnalysis.ts — sort hasil RETURNING.
+- tests/batchBudget.test.ts — baru.
+
+## Verification
+cd services/discord-gateway && bun run typecheck && bun run lint && bun run test
+lalu commit+push, watch GHA, restart service via deploy pipeline.

.hermes/plans/2026-08-22_voice-audio-playback-polish.md

@@ -0,0 +1,67 @@
+# Spec: Perbagus fitur Voice + Audio Playback (GMW frontend)
+
+Tanggal: 2026-08-22 · Scope: **frontend only** (backend/gateway API sudah cukup)
+
+## Masalah (audit)
+1. Recordings: semua kartu pakai `<audio controls>` native — tampilan identik,
+   tidak ada indikasi which-clip-playing / loading / paused, dan N audio bisa
+   play bareng (overlap).
+2. Media view: `thumbnailUrl` dari gateway tidak dipakai; tidak ada visual
+   "sedang playing" selain disc spin; queue item semua sama tanpa badge up-next.
+3. Mini-player (`lib/hooks/use-media-player.tsx`) ada tapi TIDAK PERNAH
+   dimount → dead code, user tidak lihat status musik di halaman lain.
+4. Voice page: `useMicTransmit.setVolume` + `useVoiceListen.setVolume`
+   tersedia tapi tak ada UI-nya; mic live tidak punya level feedback.
+
+## Desain
+
+### A. RecordingAudioPlayer (baru, `components/voice/recording-audio-player.tsx`)
+Custom player menggantikan `<audio controls>`:
+- Play/pause button (ikon berubah), spinner saat buffering (`waiting` event).
+- Progress bar seekable (click-to-seek) + time label `m:ss / m:ss`.
+- Waveform-ish equalizer bars saat playing (CSS animation, reduced-motion safe).
+- **Single-playback**: module-level registry `activePlayers` — memainkan satu
+  clip otomatis pause yang lain.
+- Kartu pemilik player aktif dapat highlight border signal + "Now playing" chip.
+
+### B. Recordings view — pasang player baru
+- Ganti `<audio>` → `<RecordingAudioPlayer src download_url>`.
+- Highlight kartu via state lifted: `playingId` di view, callback `onPlay`.
+
+### C. Media view polish
+- Hero: thumbnail (jika `current.thumbnailUrl`) sebagai disc center image;
+  fallback ListMusic icon. Equalizer bars animasi CSS saat `playing`.
+- Queue row pertama: badge "up next"; baris current track diberi ring signal.
+- Volume read-only tetap.
+
+### D. MiniPlayer global
+- Hapus `lib/hooks/use-media-player.tsx` (dead) — ganti dengan komponen
+  `components/media/mini-player.tsx` yang subscribe `useMediaState` +
+  `useMediaWsSync` langsung (SWR cache shared antar route), mounted di
+  `AppFrame` bawah layar (fixed bottom, hidden di route `/media`).
+- Menampilkan: thumbnail kecil/judul, tombol skip/stop, link ke /media.
+
+### E. Voice UI
+- Mic live: level meter (Equalizer bars) — mic-transmitter sudah punya worklet;
+  tambah `getLevel()` via AnalyserNode pada stream (simple RMS) di hook.
+- Listen: volume slider (input range) wired ke `listen.setVolume`.
+- Mic volume slider wired ke `mic.setVolume`.
+
+## File touched
+| File | Aksi |
+|---|---|
+| services/frontend/src/components/voice/recording-audio-player.tsx | new |
+| services/frontend/src/app/(dashboard)/recordings/view.tsx | edit |
+| services/frontend/src/app/(dashboard)/media/view.tsx | edit |
+| services/frontend/src/components/media/mini-player.tsx | new |
+| services/frontend/src/components/shell/ambient-app.tsx | mount MiniPlayer |
+| services/frontend/src/lib/hooks/use-media-player.tsx | delete |
+| services/frontend/src/hooks/use-voice.ts | tambah micLevel |
+| services/frontend/src/lib/audio/mic-transmit.ts | expose analyser level |
+| services/frontend/src/app/(dashboard)/voice/view.tsx | sliders + meter |
+
+## Verifikasi
+1. `pnpm lint` (biome) + `pnpm build` clean.
+2. Smoke di port **4024** (BUKAN 4017) → curl 200 semua route.
+3. Commit (tanpa trailer) → push → `gh run watch` → live check
+   https://imphnen.asepharyana.my.id/{media,recordings,voice}/ = 200.

.hermes/plans/2026-08-24-ai-analysis-cache-optimization.md

@@ -0,0 +1,127 @@
+# Spec: Optimasi AI Analysis GMW — Naikkan Cache Hit Tanpa Kehilangan Akurasi
+
+Tanggal: 2026-08-24 · Repo: `~/GMW` (branch `main`) · Service: `services/discord-gateway`
+
+## Latar & Evidence (audit 2026-08-24)
+
+State produksi:
+- Qdrant `gmw_text_moderation`: **1.550 poin, status green** (vectors size 2048, Cosine).
+- PG `text_analysis_cache`: 1.634 row `user_moderation`, 277 `vision_llm`; **sum(hit_count) = 0** →
+  hit-rate tidak pernah terukur.
+- Embedding aktif (`AI_LLM_EMBEDDING_MODEL` set, Nemotron-embed, dim 2048), `AI_LLM_EMBEDDING_MIN_SIMILARITY`
+  tidak diset di BWS → default **0.97** (sangat konservatif).
+- Messages: 9.375 total; 643 status `error` (banyak retry), 49 pending.
+
+Temuan audit alur (`moderationOrchestrator.ts` → `textCacheStore.ts` → `qdrantClient.ts`,
+`textBatchProcessor.ts`, `urlFetcher.ts`, `wikipediaClient.ts`, `visionAnalyzer.ts`):
+
+| # | Temuan | Dampak |
+|---|--------|--------|
+| F1 | Exact-hash cache key menyertakan context (channel/thread) → teks sama di channel lain selalu miss | Killer hit-rate #1 |
+| F2 | Semantic tier TIDAK memfilter context (Qdrant payload tak punya context) — sudah global tapi hanya aman krn sim 0.97 ketat | Inkonsisten dgn exact tier |
+| F3 | Phase-1 lookup loop `await getCachedTextModeration(key)` per pesan → N round-trip PgBouncer per batch (60 msg = 60 query serial) | Latensi + beban DB |
+| F4 | Verdict actionable (flagged/warn) dan clean sama-sama boleh di-serve semantic; toleransi akurasi beda | Risiko akurasi |
+| F5 | `hit_count` tidak pernah di-increment oleh reader manapun | Hit-rate tak terukur |
+| F6 | `wikipediaSearch()` (blok `<web_searches>`) tanpa cache — re-fetch tiap batch utk query sama | Latensi + spam ke WP |
+| F7 | `fetchUrlSafely()` tanpa cache — link sama di batch berikutnya di-download lagi penuh | Latensi + bandwidth |
+| F8 | Vision cache key dari data-URL base64 hasil resize → attachment sama via jalur berbeda (URL vs embed) = key beda → re-download + re-vision | Duplikasi kerja vision |
+
+Non-goals: mengubah pipeline enforcement (auto-mute/ban trust-store writes), mengubah prompt
+kebijakan moderasi, mengubah model/embedding provider.
+
+## Desain
+
+Semua perubahan degrade gracefully — cache gagal → perilaku lama (LLM). Akurasi dilindungi
+asimetris: **hemat boleh untuk verdict non-actionable, konservatif untuk yang memicu aksi.**
+
+### D1 — Cache metrics (F5)
+- `textCacheStore.getCachedTextModeration()`: saat hit valid, increment `hit_count`
+  (`UPDATE ... SET hit_count = hit_count + 1`) fire-and-forget (`.catch(()=>{})`), jangan blokir return.
+- Log info periodik ringkas di orchestrator sudah ada ("User moderation cache applied") — cukup.
+
+### D2 — Batched exact-cache lookup (F3)
+- Fungsi baru `getCachedTextModerations(keys: string[]): Promise<Map<string, StoredModerationVerdict>>`
+  di `textCacheStore.ts`: **satu** `SELECT ... WHERE text = ANY($1)` (chunk 200 key/query),
+  parse + `normalizeStoredStatus` per row (reuse helper existing).
+- Orchestrator fase-1: kumpulkan semua key unik → satu call batched → distribusi hasil.
+- Semantik identik dengan loop lama (row expired/error-artifact tetap miss); hanya jumlah round-trip
+  yang turun N→1.
+
+### D3 — Global exact reuse untuk verdict non-actionable (F1)
+- Key scoped-context TETAP ditulis (kompatibel, invalidasi moderator tetap presisi).
+- Reader tambahan: kalau key `<ctx>:<hash>` miss, coba key legacy global `text_mod:<hash>` (bare).
+- Guard akurasi (WAJIB semua terpenuhi):
+  - `status === "clean"` DAN `flags.length === 0`;
+  - `confidence >= AI_CACHE_GLOBAL_REUSE_MIN_CONFIDENCE` (default 0.85);
+  - `recommendedAction === "none"`;
+  - umur entry ≤ `AI_CACHE_GLOBAL_REUSE_MAX_AGE_H` (default 72h) — cek `analyzed_at`.
+- Flag baru `policyVersion: "cached-global-clean-2026-08"` supaya terlacak di dashboard/log.
+- Verdict flagged/warn TETAP context-scoped (tidak pernah lintas channel).
+
+### D4 — Semantic dua-band similarity (F2+F4)
+- Config baru: `AI_LLM_EMBEDDING_MIN_SIMILARITY_ACTIONABLE` default **0.97** (perilaku lama),
+  `AI_LLM_EMBEDDING_MIN_SIMILARITY_CLEAN` default **0.92**, keduanya coerce number 0..1.
+- Satu Qdrant batch search pakai threshold RENDAH (0.92). Per hit, klasifikasi ulang:
+  - verdict non-actionable (clean, no flags, action=none): terima jika `score >= CLEAN_BAND`;
+  - verdict actionable (warn/flagged atau flags ada / action != none): terima hanya jika
+    `score >= ACTIONABLE_BAND` (0.97 — persis gate lama);
+  - di antara dua band → buang hit, pesan lanjut ke LLM (fail-open ke akurasi).
+- Legacy PG fallback path: filter serupa di `findSimilarTextModeration` via parameter band.
+
+### D5 — Cache Wikipedia search (F6)
+- `wikipediaClient.wikipediaSearch(query)`: cek `cacheGet(makeCacheKey("wikisearch", q))` dulu;
+  miss → fetch (timeout existing) → sukses & hasil non-kosong → `cacheSet(..., TTL 6h)`.
+  Hasil kosong TIDAK di-cache (biar retry nanti). Redis down → langsung fetch (no-op cache).
+
+### D6 — Cache URL text fetch (F7)
+- `urlFetcher.fetchUrlSafely(url)`: wrapper async memoize in-process LRU (max 500, TTL 30 menit)
+  untuk `type === "text"` saja (image tetap selalu fresh-download karena dipakai sbg bukti vision
+  + buffer besar; error tidak di-cache).
+- Import `LRUCache` dari `lru-cache` (sudah dep gateway).
+
+### D7 — Unified vision cache key (F8)
+- `makeImageCacheKey(imageUrl)` di `textCacheStore.ts`: sebelum hash, strip query Discord CDN
+  (`?ex=&is=&hm=` signed tokens, `format/width/height/size`) — regex `(\?[^#]*)$` dibuang bila host
+  CDN discord (`cdn.discordapp.com`, `media.discordapp.net`, `images-ext-*.discordapp.net`);
+  URL non-Discord: hash full URL seperti sekarang.
+- Efek: attachment sama yang lolos lewat jalur embed vs inline vs re-fetch dgn token beda → SATU
+  entry cache → skip download+vision kedua kali. Data-URL base64 tetap di-hash apa adanya.
+
+## File yang disentuh
+
+1. `src/shared/config/index.ts` — 3 config baru (D3×2, D4×2 — total 4 nilai, 3 baris zod + deskripsi).
+2. `src/modules/ai-moderation/textCacheStore.ts` — hit_count inc (D1), batched getter (D2),
+   global-reuse guard helper (D3), image-key normalize (D7).
+3. `src/modules/ai-moderation/moderationOrchestrator.ts` — pakai batched getter (D2),
+   global bare-key fallback (D3), dua-band semantic accept (D4).
+4. `src/modules/ai-moderation/qdrantClient.ts` — `searchQdrantBatch` menerima threshold rendah
+   (sudah parametrik — mungkin tanpa perubahan; verifikasi).
+5. `src/modules/ai-moderation/wikipediaClient.ts` — cache layer (D5).
+6. `src/modules/ai-moderation/urlFetcher.ts` — LRU text-fetch memoize (D6).
+
+## Schema/type changes
+
+- Tidak ada migrasi DB (kolom `hit_count`, `analyzed_at`, `expires_at` sudah ada).
+- Tidak ada perubahan kontrak WS/oRPC/frontend.
+- Type baru: none public; internal `StoredModerationVerdict` dipakai ulang.
+
+## Verification
+
+1. Unit tests baru (`tests/`):
+   - `cacheBatchLookup.test.ts`: batched getter — hit/miss/expired/error-artifact mapping,
+     chunking >200 keys (mock executeAll), hit_count increment called.
+   - `globalReuseGuard.test.ts`: guard menerima clean+conf≥0.85+action none+umur ≤72h;
+     menolak flagged/warn/conf rendah/action≠none/stale.
+   - `semanticBands.test.ts`: clean @0.93 diterima, flagged @0.93 ditolak, flagged @0.98 diterima.
+   - `imageKeyNormalize.test.ts`: URL Discord dgn/ex token → key sama; non-Discord beda query → beda.
+2. Gate service: `pnpm typecheck && pnpm exec biome check --diagnostic-level=error . && pnpm exec vitest run`.
+3. Deploy via GHA (`git push origin main`) → watch `Build & Deploy (Nix)` → verifikasi
+   `systemctl show gmw-discord-gateway -p ActiveEnterTimestamp` baru.
+4. Runtime probe pasca-deploy: journalctl level 30 normal; beberapa jam kemudian
+   `SELECT sum(hit_count) FROM text_analysis_cache WHERE source='user_moderation'` > 0 membuktikan
+   metrics jalan; log "User moderation cache applied" menunjukkan hits>0 pada traffic ramai.
+
+## Rollback
+
+Semua fitur behind config defaults yang mempertahankan perilaku lama pada nilai konservatif;
+rollback = redeploy commit sebelumnya (tanpa migrasi DB, tanpa state eksternal).

.hermes/plans/2026-08-24-attachment-delay-fix.md

@@ -0,0 +1,56 @@
+# Spec: Perbaiki Delay Attachment 162s→<20s (GMW AI Analysis)
+
+Tanggal: 2026-08-24 · Repo `~/GMW` · Service discord-gateway
+
+## Evidence (audit produksi)
+
+Klaster pesan attachment delay ~330–400 detik. Trace pesan `1541417073245290638` (.gif):
+19:01:08 dibuat → 19:01:09 batch incomplete → fan-out individual → **guard upload-pending
+mengembalikan `results:[]`** → diperalakukan sukses (`complete ... (undefined)`) → row
+tertahan `ai_status='processing'` **tanpa penanggung jawab** → 19:06:12 cleanup mengembalikan
+ke `pending` (tepat 300s) → baru dianalisis. Plus vision gagal 3× utk GIF besar
+("Stream ended before producing a non-ping SSE event") → degradasi teks.
+
+## Root causes
+
+- **A (fatal)**: `individualFallbackProcessor.processIndividualFallback` memperlakukan
+  `ok:true + results:[]` sebagai sukses. Race-guard upload di `ai-analysis-worker.processIndividual`
+  sengaja balik `results:[]` (desain lama) → pesan yatim `processing` sampai cleanup 300s.
+- **B**: `llmVision` hanya mencoba `stream:true`; kegagalan SSE truncation pada gambar besar
+  = 3 retry sia-sia (semua jalur sama) → bukti media hilang.
+- **C**: safety-net cleanup 300s terlalu lambat sbg satu-satunya pemulih `processing`.
+
+## Fix
+
+1. **F1 — sinyal eksplisit upload-pending**: `IndividualOkResponse` + field opsional
+   `uploadPending?: boolean`. Worker set `uploadPending:true` saat race guard kena.
+2. **F2 — processor menangani 3 kondisi** via helper murni baru
+   `classifyIndividualWorkerResult(result): "success" | "upload_pending" | "incomplete" | "error"`
+   (modul baru `fallbackResultClassifier.ts`, zero-dep agar mudah dites):
+   - `upload_pending` → tulis ulang row ke `pending` (pola sama dgn revert apiFailed di
+     batchProcessor) + broadcast + **re-schedule analisis percakapan segera**
+     (dynamic import batchScheduler, pola anti-siklus yg sudah ada) → retry dalam ~250ms
+     begitu upload beres. Bukan error, tidak naikkan CB counter.
+   - `incomplete` (flags analysis_incomplete) → perilaku lama (exhausted path).
+   - `error` / `results kosong tanpa penjelasan` → throw transien (retry oleh recovery),
+     BUKAN sukses palsu. Log "(undefined)" hilang.
+3. **F3 — vision non-stream fallback**: di `llmVision`, jika error match
+   `/Stream ended before producing a non-ping SSE|stream ended/i` → coba SEKALI lagi dengan
+   `stream:false` (router agregasi penuh; timeout tetap 60s). Konversi hard-fail jadi sukses.
+4. **F4 — turunkan safety net**: default `revertStuckProcessingMessages` 300000 → 120000 ms.
+
+## File disentuh
+
+- `src/modules/ai-moderation/fallbackResultClassifier.ts` (BARU, pure)
+- `src/modules/ai-moderation/ai-analysis-worker.ts` (tipe + set flag uploadPending)
+- `src/modules/ai-moderation/individualFallbackProcessor.ts` (konsumsi classifier + reschedule)
+- `src/modules/ai-moderation/llmClient.ts` (fallback non-stream di llmVision)
+- `src/modules/message-capture/messagesCleanup.ts` (default 120s)
+
+## Verifikasi
+
+- Test baru `tests/fallbackResultClassifier.test.ts` (4 klasifikasi + edge kosong).
+- Gate: tsc --noEmit, biome error-level, vitest run semua hijau.
+- Deploy GHA sukses; pasca-deploy: pesan attachment baru p50 < 20s
+  (`SELECT percentile_cont(0.5) ... WHERE metadata attachments>0 AND created_at > deploy`),
+  tidak ada lagi "complete ... (undefined)".

.hermes/plans/2026-08-24_mono-gamemenu-mobile.md

@@ -0,0 +1,39 @@
+# GMW FE — Monokrom Hitam-Putih + Sidebar Ala Menu Game + Ringan di Mobile
+
+Tanggal: 2026-08-24 · Basis: `eda5c75` (shell usable hasil revert)
+
+## Tujuan
+1. Tema **monokrom murni** (hitam-putih, tanpa warna) di dark & light.
+2. Sidebar (desktop NavRail + mobile dock) beranimasi **ala menu game** — corner
+   brackets, sweep, stagger masuk, marker segitiga.
+3. **Ringan di mobile**: matikan WebGL ambient di layar kecil, kurangi biaya
+   blur/backdrop, animasi transform/opacity saja.
+
+## Non-goals
+- Tidak menyentuh backend, endpoint, hooks/data-flow, struktur route.
+- Tidak menambah dependensi baru (CSS murni untuk semua animasi).
+
+## File yang disentuh
+| File | Perubahan |
+|---|---|
+| `src/app/globals.css` | Token mono (dark+light): signal/amber/vermilion → skala putih-abu; `.glass` blur adaptif; kelas baru `.game-nav-item` (bracket ::before/::after, sweep, stagger via `--i`), `.game-frame` (panel sudut terpotong + garis tergambar), keyframes `sweep-x`, `draw-line`, `nav-in`; media query `<md`: blur 18→8px, hambat animasi berat |
+| `src/components/shell/nav-rail.tsx` | Item pakai `.game-nav-item` + `style={{'--i': n}}`; marker aktif jadi segitiga ▸ putih; hapus box-shadow glow besar (ganti sweep) |
+| `src/components/shell/mobile-nav.tsx` | Dock mono: tab aktif = bar atas putih + sweep sekali; target sentuh ≥44px; hapus glow blob |
+| `src/components/shell/topbar.tsx` | Aksen mono + `.game-frame` pada container (cek markup dulu) |
+| `src/components/ambient/ambient-canvas.tsx` | Early-return WebGL bila `(pointer: coarse)` / lebar <768 / `saveData` / core ≤4; fallback statik CSS tetap |
+| `src/components/ambient/status/signal tone` (`SIGNAL_RGB`) | Semua tone jadi grayscale (putih; intensitas beda per tone) |
+| `src/app/(dashboard)/dashboard/view.tsx` | Hero + kartu metrik pakai `.game-frame`/cut-corner sebagai showcase |
+
+## Keputusan desain
+- **Full monokrom termasuk danger**: flag/moderation tidak lagi merah —
+  ditandai badge putih-di-atlas-hitam inversi + pulse. Kalau user kangen merah,
+  tinggal isi ulang `--color-vermilion`.
+- Semua animasi hanya `transform`/`opacity` (compositor-friendly), hormati
+  `prefers-reduced-motion` (sudah ada kill-switch global).
+
+## Verifikasi (gerbang)
+1. `tsc --noEmit` bersih; biome 0 error 0 warning.
+2. `pnpm build` sukses; smoke lokal 4024 → 9 route 200.
+3. Push → GHA "Build & Deploy (Nix)" hijau → live 9×200.
+4. Visual check live: desktop (rail game-menu terlihat) + cek rule mobile
+   (media query & gate kode) — screenshot disimpan.

CLAUDE.md

@@ -1,695 +0,0 @@
-# CLAUDE.md
-
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
-
-## Project Overview
-
-**Bete (Discord Moderation Watcher)** — A comprehensive microservice-based Discord monitoring and moderation bot. Captures text messages, images, voice audio, and screenshares from Discord servers. Features AI-powered content moderation with auto-delete, voice recording with real-time streaming, music playback, and a React dashboard.
-
-Built with **pnpm workspace monorepo** with 3 services and 1 shared library:
-
-| Package | Path | Description |
-|---------|------|-------------|
-| `discord-moderation-backend` | `services/backend` | Express HTTP/WS server, REST API, Redis bridge |
-| `@bete/discord-gateway` | `services/discord-gateway` | Discord client, voice recording, message capture, AI moderation |
-| `frontend` | `services/frontend` | Next.js 16 (React 19) static dashboard, Tailwind v4, shadcn/ui |
-| `@bete/shared` | `packages/shared` | Shared types, errors, logger, utilities |
-
-**Database:** PostgreSQL (Drizzle ORM) — NOT SQLite.
-
-**Inter-service communication:** Redis pub/sub.
-
-## Architecture
-
-### High-Level Flow
-
-```
-Discord
-   |
-   v
-discord-gateway ---- Redis ---- backend ---- WebSocket ---- frontend
-   |                 pub/sub      (broadcast)                (Next.js static)
-   |                   |
-   |                   |
-   <------------------+
-   (command channel)
-```
-
-1. **discord-gateway** connects to Discord via `discord.js-selfbot-v13`, captures events (messages, voice, attachments), stores in PostgreSQL, and publishes events to Redis channels (e.g., `discord:message:created`, `discord:voice:pcm`).
-
-2. **backend** subscribes to Redis channels, broadcasts events to WebSocket clients, and serves REST API endpoints.
-
-3. **frontend** connects via WebSocket and HTTP to the backend, provides a dashboard for live monitoring (text, voice, media) and AI moderation oversight.
-
-4. **Command flow (reverse):** Frontend -> Backend HTTP/WS -> Redis (`backend:command`) -> discord-gateway (command handler) - for actions like connect voice, play media, moderate message.
-
-### Data Flow
-
-```
-Message Capture:
-  Discord -> messageCapture.ts -> messageStore.ts (PostgreSQL)
-                |
-                +> eventBroadcaster -> Redis -> backend -> WS clients
-
-Voice Recording:
-  Discord -> voiceController.ts -> recorder.ts -> OGG files on disk
-                |                       |
-                +> eventBroadcaster     +> decoder.ts -> PCM -> Redis -> WS clients
-
-AI Moderation:
-  messageStore -> aiAnalyzer.ts -> LLM API -> moderation result
-                    |                           |
-                    +> eventBroadcaster         +> update message in DB
-```
-
-## Service Breakdown
-
-### backend (`services/backend`)
-
-Express 5 + Helmet HTTP server with WebSocket (ws) on port 3001 (default).
-
-**REST API endpoints (all public):**
-- `GET /api/health` — Health check with optional `?verbose=true`
-- `GET /api/config` — App configuration
-- `GET /api/messages` — List messages (cursor pagination)
-- `GET /api/messages/:channelId` — Messages by channel
-- `GET /api/messages/:channelId/attachments` — Attachments by channel
-- `GET /api/messages/detail/:id` — Single message
-- `POST /api/messages/reanalyze-batch` — Bulk retry AI analysis
-- `POST /api/messages/:id/reanalyze` — Retry single message
-- `POST /api/messages/:id/moderate` — Dispatch moderation action
-- `GET /api/review` — Flagged/warned messages
-- `GET /api/analysis/search` — Full-text search with `?q=`
-- `POST /api/chat` — AI chatbot chat
-- `GET /api/chat/history` — Chat history
-- `POST /api/chat/clear` — Clear chat history
-- `POST /api/voice/command` — Send voice transmit commands
-- `GET /api/status` — Voice connection status
-- `POST /api/connect` — Connect to voice channel
-- `POST /api/disconnect` — Disconnect from voice
-- `GET /api/guilds` — List guilds
-- `GET /api/guilds/:guildId/channels` — Text channels
-- `GET /api/guilds/:guildId/voice-channels` — Voice channels
-- `GET /api/media/status` — Media player status
-- `POST /api/media/queue` — Queue media (music/screen)
-- `POST /api/media/skip` — Skip current track
-- `POST /api/media/stop` — Stop playback
-- `POST /api/media/volume` — Set volume
-- `GET /api/recordings` — Voice recordings list
-- `GET /api/ui-state` — Get persistent UI state
-- `POST /api/ui-state` — Save UI state
-
-**Modules (feature-based, under `src/modules/`):**
-- `health/` — Database connectivity check
-- `messages/` — Message + attachment CRUD, review, reanalyze
-- `voice/` — Voice connection, guilds, channels
-- `media/` — Music/screenshare player control
-- `analysis/` — Full-text search across analyzed messages
-- `chatbot/` — AI chatbot with server context
-- `recordings/` — Voice recording listing
-- `ui-state/` — Persistent UI state for dashboard
-- `config/` — App config endpoint
-
-**WebSocket events (outbound to frontend):**
-- `message_created`, `message_updated`, `message_deleted`, `message_analyzed`
-- `attachment_created`, `attachment_uploaded`
-- `voice_recording_started`, `voice_recording_stopped`, `voice_recording_uploaded`
-- `voice_active_user`, `voice_pcm_data`
-- `analysis_queue_status`
-- `user_state`, `ui_state`, `media_state`
-- `heartbeat` (every 30s)
-
-**WebSocket inbound (from frontend):**
-- JSON `{ type: "voice_transmit", buffer: "<base64 PCM>" }` — forwarded to Redis
-- JSON `{ type: "voice_command", command: "..." }` — forwarded to discord-gateway
-
-### discord-gateway (`services/discord-gateway`)
-
-The core service that connects to Discord using `discord.js-selfbot-v13`.
-
-**Modules:**
-
-- **`message-capture/`** — Listens to `messageCreate`, `messageUpdate`, `messageDelete` events. Stores messages in PostgreSQL. Handles edits, deletes, and backlog sync.
-  - `messageCapture.ts` — Event listeners
-  - `messageStore.ts` — Database operations (upsert, update, delete)
-  - `messageMetadata.ts` — User/channel metadata extraction
-  - `broadcaster.ts` — Internal event dispatch
-  - `pagination.ts` — Backlog sync for historical messages
-  - `analyticsStore.ts` — Per-channel analytics tracking
-
-- **`voice-recording/`** — Voice channel connection, recording, and real-time PCM streaming.
-  - `voiceController.ts` — Connection lifecycle (connect/disconnect per guild+channel)
-  - `recorder.ts` — Manages speaking users, subscribes to audio streams
-  - `recorder/audioStream.ts` — Opus packet subscription per user
-  - `recorder/decoder.ts` — Opus to PCM decoding with rotation/cooldown
-  - `recorder/segment.ts` — OGG file segment rotation (default 5s)
-  - `recorder/metadata.ts` — User metadata JSON for each segment
-  - `recorder/sessionRecording.ts` — Session-scoped recording management
-  - `recorder/uploader.ts` — Upload completed segments
-  - `player.ts` — Discord player (music/screenshare playback)
-  - `transmitter.ts` — Browser-to-Discord audio transmission (Redis -> Opus -> Discord)
-  - `muxer.ts` — Audio muxing logic
-  - `packetFilter.ts` — Opus packet filtering
-  - `ffmpegProcess.ts` — FFmpeg-based processing
-  - `mediaTypes.ts` — Audio/video format definitions
-  - `teleUpload.ts` — Upload to tele/picser
-
-- **`attachment-upload/`** — Downloads Discord attachments, uploads to external service.
-  - `attachmentUploader.ts` — Download + upload with retry
-  - `imageResizer.ts` — Resize images before upload
-  - `teleUpload.ts` — Upload to tele/picser API
-
-- **`ai-moderation/`** — AI-powered content moderation pipeline.
-  - `aiAnalyzer.ts` — Analysis worker (batch + individual fallback)
-  - `aiAnalysisWorker.ts` — Piscina worker thread for batch processing
-  - `llmClient.ts` — Generic LLM API client
-  - `llmModerationClient.ts` — Moderation-specific LLM client
-  - `moderationPrompt.ts` — System prompt builder with few-shot
-  - `autoDeleteManager.ts` — Auto-delete flagged messages
-  - `conversationContext.ts` — Conversation window builder
-  - `concurrencyLimiter.ts` — Rate limiter for LLM calls
-  - `channelCultureStore.ts` — Channel norms/slang context
-  - `cultureLearner.ts` — Learn channel culture over time
-  - `userReputationStore.ts` — User trust scores
-  - `textCacheStore.ts` — Deduplicate repeated text analysis
-  - `stickerCache.ts` — Upload and cache sticker images
-  - `stickerPrompt.ts` — Sticker analysis prompt
-  - `urlFetcher.ts` — Fetch URL content for analysis
-  - `responseLogger.ts` — Log moderation responses
-
-- **`event-broadcaster/`** — Redis pub/sub publisher for all events.
-  - `eventBroadcaster.ts` — `EventBroadcaster` class with typed methods
-  - `eventTypes.ts` — Channel constants and event interfaces
-
-- **`command-handler/`** — Listens on `backend:command` Redis channel for backend requests.
-  - `commandHandler.ts` — Handles voice connect/disconnect, guilds, channels, media, transmit
-
-**Infrastructure:**
-- `src/shared/config/config.ts` — Zod-validated env config (DISCORD_TOKEN, REDIS_URL, AI_LLM_*, etc.)
-- `src/shared/database/schema.ts` — Full PostgreSQL schema definition
-- `src/shared/database/drizzle.ts` — Drizzle + pg pool initialization
-- `src/shared/database/migrate.ts` — Migration runner with advisory locking
-- `src/shared/database/voiceRecordingRepo.ts` — Voice recording queries
-- `src/shared/discord/clientOptions.ts` — Discord client configuration
-
-### frontend (`services/frontend`)
-
-Next.js 16 (React 19) static export dashboard, built with TypeScript + Tailwind v4 + shadcn/ui + base-ui.
-
-**Tech stack:**
-- Next.js 16 (App Router, static export)
-- React 19 with React Compiler
-- TypeScript strict
-- Tailwind v4 + shadcn/ui + base-ui components
-- lucide-react icons
-
-**Feature structure:**
-- `src/app/` — App Router pages (login, dashboard with tabs)
-- `src/features/` — Feature components (dashboard, messages, live, chatbot)
-- `src/lib/` — Shared utilities (types, API client, WebSocket, hooks)
-- `src/components/` — Shared UI components (layout, ui)
-
-### shared (`packages/shared`)
-
-Shared library used by both backend and discord-gateway.
-
-**Exports:**
-- `@bete/shared` — Everything below
-- `@bete/shared/types` — AppConfig, MessageRecord, AttachmentRecord, VoiceSegment, etc.
-- `@bete/shared/errors` — AppError, ValidationError, NotFoundError, UnauthorizedError, DatabaseError, ConfigError, DiscordError, TimeoutError, etc.
-- `@bete/shared/logger` — Pino-based `createChildLogger(context)`
-- `@bete/shared/utils` — Shared utilities
-
-## Database Schema (PostgreSQL)
-
-All tables defined in `services/discord-gateway/src/shared/database/schema.ts`.
-
-### messages
-Stores text messages with AI moderation results.
-- `id` (text PK), `guild_id`, `channel_id`, `thread_id`
-- `user_id`, `username`, `avatar_url`
-- `content`, `edited_content`, `type` (text|edited|deleted)
-- `created_at`, `edited_at`, `deleted_at`
-- `ai_status` (pending|processing|clean|warn|flagged|error)
-- `ai_moderation_flags`, `ai_moderation_score`, `ai_analysis`, `ai_categories`
-- `ai_severity` (none|low|medium|high|critical), `ai_confidence`
-- `ai_recommended_action` (none|monitor|warn|review|delete|escalate)
-- `ai_analyzed_at`, `ai_error`, `metadata`
-- Indexes: channel, user, created_at, thread, channel+created, thread+created, ai_status+created, guild+ai_status+created, guild+created+deleted, channel+ai_status+created, thread+ai_status+created
-
-### attachments
-Discord attachment metadata with upload tracking.
-- `id` (text PK), `message_id` (FK -> messages cascade), `guild_id`, `channel_id`
-- `filename`, `size`, `type` (MIME), `discord_url`, `uploaded_url`
-- `upload_status` (pending|uploaded|failed), `upload_error`
-- `created_at`, `uploaded_at`
-- Indexes: channel, message, upload_status, channel+created, thread+created
-
-### voice_recordings
-Voice segment metadata.
-- `id` (text PK), `user_id`, `username`, `avatar_url`
-- `guild_id`, `channel_id`, `channel_name`
-- `filename`, `size_bytes`, `download_url`
-- `upload_status` (pending|uploaded|failed), `upload_error`
-- `created_at`, `uploaded_at`
-- Indexes: user_id, channel_id, created_at
-
-### ui_state
-Persistent dashboard UI state (key-value).
-- `key` (text PK), `value` (text), `updated_at`
-
-### ai_analysis_runs
-Tracks AI analysis batch runs.
-- `id` (text PK), `conversation_key`, `target_message_ids` (JSON)
-- `model`, `request_tokens_estimate`, `response_raw`
-- `status` (pending|processing|completed|failed), `error`
-- `created_at`, `completed_at`
-- Indexes: conversation_key, status, created_at
-
-### user_reputations
-User trust scores for AI context.
-- `user_id` (text PK), `guild_id`, `trust_score`, `clean_message_streak`
-- `total_infractions`, `last_infraction_at`, `created_at`, `updated_at`
-- Indexes: guild_id, trust_score
-
-### channel_cultures
-AI-generated channel norms and slang summaries.
-- `channel_id` (text PK), `guild_id`, `culture_summary`, `last_analyzed_at`
-- Index: guild_id
-
-### message_reviews
-Manual review tracking for flagged messages.
-- `id` (text PK), `message_id`, `guild_id`, `channel_id`
-- `reviewer_id`, `status` (pending|approved|rejected|escalated)
-- `notes`, `created_at`, `reviewed_at`
-- Indexes: message_id, status, created_at, guild+status+created
-
-### moderation_actions
-Action audit log (delete/mute/warn/kick/ban).
-- `id` (text PK), `message_id`, `user_id`, `guild_id`
-- `action_type` (delete_message|mute_user|warn_user|kick_user|ban_user)
-- `reason`, `executed_by`, `status` (pending|executed|failed)
-- `error`, `created_at`, `executed_at`
-- Indexes: message_id, user_id, status, guild+status+created
-
-### retention_policies
-Data retention rules per guild/channel.
-- `id` (text PK), `guild_id`, `channel_id`
-- `retention_days`, `apply_to_media`, `apply_to_voice`, `enabled`
-- `created_at`, `updated_at`
-- Indexes: guild_id, enabled
-
-### text_analysis_cache
-Caches normalized-text moderation results to avoid redundant LLM calls.
-- `text` (text PK), `flags` (JSON array), `source` (local|primary_ai|vision_llm)
-- `analyzed_at`, `expires_at`, `hit_count`
-- Indexes: expires_at, source
-
-### sticker_cache
-Uploaded sticker image URLs for vision analysis.
-- `name` (text PK), `image_url`, `mime_type`, `fetched_at`
-- Index: fetched_at
-
-### corrected_moderations
-Manual corrections (false positives) for few-shot injection.
-- `id` (text PK), `message_id`, `original_flags`, `corrected_flags`
-- `correction_notes`, `content_snippet`, `created_at`
-- Indexes: created_at, message_id
-
-### muxer_jobs
-Audio post-processing job queue.
-- `id` (text PK), `data` (JSON), `status` (pending|processing|completed|failed)
-- `attempts`, `maxAttempts`, `created_at`, `updated_at`, `error`
-- Indexes: status, created_at
-
-## Redis Communication
-
-### discord-gateway publishes (event channels):
-| Channel | Event type | When |
-|---------|-----------|------|
-| `discord:message:created` | `message_created` | New message |
-| `discord:message:updated` | `message_updated` | Message edited |
-| `discord:message:deleted` | `message_deleted` | Message deleted |
-| `discord:message:analyzed` | `message_analyzed` | AI analysis complete |
-| `discord:attachment:created` | `attachment_created` | New attachment |
-| `discord:attachment:uploaded` | `attachment_uploaded` | Upload complete |
-| `discord:voice:started` | `voice_recording_started` | Recording started |
-| `discord:voice:stopped` | `voice_recording_stopped` | Recording stopped |
-| `discord:voice:uploaded` | `voice_recording_uploaded` | Upload complete |
-| `discord:voice:active_user` | `voice_active_user` | Speaker state change |
-| `discord:voice:pcm` | `voice_pcm_data` | Live PCM audio chunk |
-| `discord:analysis:queue_status` | `analysis_queue_status` | Queue stats |
-
-### backend publishes (command channel):
-| Channel | Command type | Description |
-|---------|-------------|-------------|
-| `backend:command` | `voice:connect` | Connect to voice |
-| `backend:command` | `voice:disconnect` | Disconnect voice |
-| `backend:command` | `voice:channels` | List voice channels |
-| `backend:command` | `voice:transmit:start/stop` | Audio transmit |
-| `backend:command` | `guilds:list` | List guilds |
-| `backend:command` | `guilds:text-channels` | List text channels |
-| `backend:command` | `media:queue/skip/stop/volume` | Media control |
-| `backend:command` | `moderation:action` | Execute moderation action |
-
-Envelope format: `{ id, type, payload, replyChannel }`.
-
-Status keys: `voice:status`, `media:status` (set by discord-gateway, read by backend).
-
-## Development Commands
-
-```bash
-# Install all dependencies
-pnpm install
-
-# Run each service in development mode (separate terminal each)
-pnpm run dev:backend          # Backend on port 3001
-pnpm run dev:discord-gateway  # Discord client + all features
-pnpm run dev:web              # Frontend via next dev (port 3000)
-
-# Build
-pnpm run build:backend
-pnpm run build:discord-gateway
-pnpm run build:web            # next build (static export)
-
-# Type checking
-pnpm run typecheck            # Node services (pnpm -r)
-pnpm run typecheck:web        # Frontend typecheck (next build)
-
-# Lint (Biome)
-pnpm run lint
-
-# Format (Biome)
-pnpm run format
-
-# Run tests across all packages
-pnpm run test
-
-# Database migrations (Drizzle)
-pnpm run db:generate   # Generate new migration
-pnpm run db:migrate    # Apply pending migrations
-pnpm run db:studio     # Open Drizzle Studio
-
-# Install yt-dlp for media download
-pnpm run install:yt-dlp
-
-# Deploy to VPS (build + hot-patch running containers)
-./deploy.sh                    # Build + deploy all services
-./deploy.sh --frontend         # Frontend (Next.js) only
-./deploy.sh --backend          # Backend TypeScript only
-./deploy.sh --no-build         # Skip build, just copy files
-```
-
-## Configuration
-
-Configuration via `.env` (see `.env.example`). Managed by Zod schemas:
-- discord-gateway: `services/discord-gateway/src/shared/config/config.ts`
-- backend: `services/backend/src/shared/config/index.ts`
-
-### Core (both services)
-- `DISCORD_TOKEN` — Discord user token (required)
-- `MONITOR_GUILD_ID` — Target guild for text monitoring
-- `NODE_ENV` — development|production|test
-- `LOG_LEVEL` — Pino log level (default: info)
-- `VERBOSE` — Enable debug logging (default: false)
-
-### Database (PostgreSQL)
-- `DATABASE_URL` — Connection string (overrides individual params)
-- `POSTGRES_HOST`, `POSTGRES_PORT` (5432), `POSTGRES_USER`, `POSTGRES_PASSWORD`, `POSTGRES_DB`
-- `POSTGRES_POOL_MIN` (2), `POSTGRES_POOL_MAX` (10)
-- `AUTO_MIGRATE_ON_STARTUP` (default: true)
-
-### Redis
-- `REDIS_URL` — Connection string (default: redis://localhost:6379)
-
-### Voice Recording (discord-gateway)
-- `RECORDINGS_DIR` — Audio file output (default: ./recordings)
-- `RECORDING_SEGMENT_MS` — OGG segment duration (default: 5000)
-- `DECODER_ROTATE_MS` — Opus decoder rotation (default: 5000)
-- `DECODER_COOLDOWN_MS` — Decoder error cooldown (default: 30000)
-- `AUDIO_STREAM_SILENCE_DURATION_MS` — Silence threshold (default: 3000)
-- `VOICE_CONNECTION_TIMEOUT_MS` — Connection timeout (default: 15000)
-- `RECONNECT_TIMEOUT_MS` — Reconnect timeout (default: 5000)
-- `PACKET_FILTER_MIN_SIZE` — Minimum Opus packet size (default: 8)
-- `OPUS_FRAME_SIZE` (960), `AUDIO_SAMPLE_RATE` (48000), `AUDIO_CHANNELS` (2)
-- `VOICE_GUILD_ID`, `VOICE_CHANNEL_ID`
-
-### Attachments
-- `TELE_UPLOAD_URL` — Upload endpoint (default: https://upload.asepharyana.my.id/api/upload)
-- `ATTACHMENT_UPLOAD_TIMEOUT_MS` (30000), `ATTACHMENT_MAX_SIZE_MB` (100), `ATTACHMENT_RETRY_ATTEMPTS` (3)
-
-### AI Moderation (discord-gateway)
-- `AI_ANALYSIS_ENABLED` — Enable AI analysis (default: false)
-- `AI_LLM_API_KEY` — LLM API key (required if enabled)
-- `AI_LLM_BASE_URL` — LLM endpoint (default: https://9router.asepharyana.my.id/v1)
-- `AI_LLM_MODEL` — Text model (default: text)
-- `AI_LLM_VISION_MODEL` — Vision model (optional fallback)
-- `AI_LLM_MAX_CONCURRENT` (5), `AI_LLM_TEXT_BATCH_SIZE` (20)
-- `AI_LLM_MEDIA_ANALYSIS_TIMEOUT_MS` (60000), `AI_LLM_IMAGE_MAX_DIMENSION` (1024)
-- `AI_ANALYSIS_DEBOUNCE_MS` (500), `AI_ANALYSIS_MAX_BATCH_SIZE` (200)
-- `AI_ANALYSIS_PROCESSING_TIMEOUT_MS` (120000)
-- `PISCINA_MAX_THREADS` — Worker pool size (optional)
-
-### Auto-Delete
-- `AUTO_DELETE_FLAGGED_ENABLED` (true), `AUTO_DELETE_FLAGGED_DRY_RUN` (true)
-- `AUTO_DELETE_FLAGGED_DELAY_MS` (0), `AUTO_DELETE_MIN_CONFIDENCE` (0.5)
-- `AUTO_DELETE_ALLOWED_SEVERITIES`, `AUTO_DELETE_ALLOWED_CATEGORIES`
-- `AUTO_DELETE_EXCLUDED_CHANNEL_IDS`, `AUTO_DELETE_EXCLUDED_USER_IDS`
-- `AUTO_DELETE_NOTIFY_USER`, `AUTO_DELETE_LOG_CHANNEL_ID`
-
-### OpenAI Moderation (optional separate endpoint)
-- `OPENAI_MODERATION_API_KEY`, `OPENAI_MODERATION_BASE_URL`, `OPENAI_MODERATION_MODEL`
-
-### Backend
-- `WEBSERVER_PORT` (3001)
-- `BACKLOG_SYNC_HOURS` (24), `BACKLOG_SYNC_BATCH_SIZE` (100)
-
-### Retention
-- `RETENTION_MESSAGES_DAYS` (0=off), `RETENTION_ATTACHMENTS_DAYS`, `RETENTION_VOICE_DAYS`
-- `RETENTION_CLEANUP_INTERVAL_MS` (86400000), `RETENTION_DRY_RUN` (true)
-
-## Testing
-
-Tests use **Vitest**. Currently minimal test coverage. Test directories should be created per service:
-
-```
-services/backend/tests/
-services/discord-gateway/tests/
-services/frontend/tests/
-```
-
-Run tests: `pnpm run test` (runs `vitest run` in each package).
-
-## Code Style
-
-- **Formatter**: Biome (2-space indent)
-- **Linter**: Biome with strict rules
-- **Language**: TypeScript with strict mode
-- **Logging**: Use `createChildLogger(context)` from `@bete/shared/logger`
-- **Errors**: Throw custom `AppError` subclasses with `code` + `statusCode`
-- **Database**: Use Drizzle ORM or raw parameterized queries (never string interpolation)
-- **Imports**: Use `.js` extensions in source files (ESM convention)
-
-## Key Patterns
-
-### Event-Driven Architecture
-
-All inter-service communication happens through Redis pub/sub. The discord-gateway publishes events on typed channels, the backend subscribes and broadcasts to WebSocket clients. The backend publishes commands on `backend:command` with reply channels for request-response patterns.
-
-### Message Capture Lifecycle
-
-1. Discord event fires (`messageCreate`, `messageUpdate`, `messageDelete`)
-2. Check guild matches MONITOR_GUILD_ID
-3. Extract message metadata (user, channel, content, timestamp)
-4. Upsert into `messages` table in PostgreSQL
-5. Publish event to Redis (`discord:message:*`)
-6. If attachments exist, insert into `attachments` table with `status='pending'`
-7. Start async upload to tele/picser (non-blocking)
-8. On success: update `uploaded_url`, `status='uploaded'`
-9. On failure: store error, `status='failed'`
-
-### AI Moderation Pipeline
-
-1. Messages with `ai_status='pending'` are picked up by `aiAnalyzer.ts`
-2. Batches messages by conversation (thread/channel proximity)
-3. Builds context window (recent messages + channel culture + user reputation)
-4. Calls LLM via `llmModerationClient.ts` with moderation prompt
-5. Updates message with `ai_status`, `ai_moderation_flags`, `ai_severity`, `ai_confidence`, `ai_recommended_action`
-6. If `AUTO_DELETE_FLAGGED_ENABLED` and confidence meets threshold, triggers auto-delete
-7. Falls back to individual analysis for messages that could not be batched
-8. Caches normalized text results in `text_analysis_cache` to avoid repeat calls
-
-### Voice Recording Lifecycle
-
-1. `VoiceController.connect(guildId, channelId)` via Redis command
-2. Joins Discord voice channel, sets up audio receiver
-3. On user start speaking: create per-user stream, OGG segment manager, Opus decoder
-4. Opus packets -> OGG segments on disk + PCM decode for WebSocket broadcast
-5. PCM data published to Redis (`discord:voice:pcm`) -> backend -> WS clients
-6. On silence (3s timeout): close stream, finalize segment
-7. After segment complete: upload to external storage, update database
-8. `VoiceController.disconnect()` stops all recording
-
-### WebSocket Protocol (frontend)
-
-**Outbound (backend -> frontend):**
-- Binary: PCM audio (24kHz mono s16le), prefixed with 4-byte user hash
-- JSON events: all typed in `WSEventMap` — `message_*`, `voice_*`, `attachment_*`, `user_state`, `ui_state`, `media_state`
-
-**Inbound (frontend -> backend):**
-- JSON `{ type: "voice_transmit", buffer: "<base64 PCM>" }` for mic-to-Discord
-- JSON `{ type: "voice_command", command: "..." }` for voice control
-
-### Graceful Shutdown
-
-discord-gateway handles SIGINT/SIGTERM/uncaughtException/unhandledRejection:
-1. Close database pool
-2. Disconnect voice controller
-3. Close event broadcaster (Redis)
-4. Close command handler (Redis)
-5. Destroy Discord client
-6. Exit process
-
-### Public API
-
-All backend endpoints are publicly accessible — no authentication required.
-
-## Recording Structure
-
-```
-recordings/
-  +-- <user-id>/
-  |   +-- <user-id>-<session-start>-0.ogg
-  |   +-- <user-id>-<session-start>-0.json
-  |   +-- <user-id>-<session-start>-1.ogg
-  |   +-- ...
-```
-
-Each segment is 5s (configurable via `RECORDING_SEGMENT_MS`). Metadata JSON includes user info, roles, timestamps, duration.
-
-## Vendor Packages
-
-### discord.js-selfbot-v13 (`vendor/discord.js-selfbot-v13`)
-Fork of discord.js-selfbot-v13 (git submodule). Provides Discord API access via user account.
-
-### discord-video-stream (`vendor/discord-video-stream`)
-Go Live / video streaming support library. Includes:
-- H264 encoding (NVENC, VAAPI, software)
-- WebRTC wrapper for Discord voice/video connections
-- Stream connection management
-
-## Dependencies
-
-**Shared (`@bete/shared`):**
-- pino — Structured logging
-- zod — Schema validation
-
-**Backend:**
-- express 5 — HTTP server
-- ws — WebSocket server
-- helmet — Security headers
-- @discordjs/voice — Voice state querying (minimal)
-- drizzle-orm + pg — PostgreSQL ORM
-- ioredis — Redis client
-- pino, pino-http — Logging
-- prom-client — Prometheus metrics
-- axios — HTTP client
-- zod — Config validation
-
-**discord-gateway:**
-- discord.js-selfbot-v13 — Discord client (user account)
-- @discordjs/voice — Voice connection
-- @discordjs/opus — Native Opus codec
-- prism-media — Audio encode/decode
-- @snazzah/davey — DA-VEY (Discord Audio Video End-to-end encryption)
-- ioredis — Redis client
-- drizzle-orm + pg — PostgreSQL ORM
-- sharp — Image processing
-- openai — OpenAI API client
-- piscina — Worker threads for AI analysis
-- tiktoken — Token counting
-- p-retry, p-limit — Async utilities
-- lru-cache — In-memory caching
-- libsodium-wrappers — Encryption
-- node-crc — CRC checksums
-- imghash — Image hashing
-- ws — WebSocket (internal)
-- zod — Config validation
-
-**Frontend:**
-- react 19, react-dom 19
-- @tanstack/react-query — Data fetching
-- three, @react-three/fiber, @react-three/drei — 3D
-- gsap, framer-motion — Animations
-- @radix-ui/* — Accessible UI primitives
-- tailwindcss 4, @tailwindcss/postcss — Styling
-- lucide-react — Icons
-- clsx, tailwind-merge — Class management
-- vite 8 — Bundler
-
-## Notes
-
-- Bot uses selfbot variant (user account) — check Discord ToS
-- Opus decoding requires native `@discordjs/opus` or `opusscript` under Node.js
-- OGG segments include metadata JSON for each segment (user info, timestamps, duration)
-- WebSocket broadcasts PCM in real-time; browser can transmit audio back to Discord
-- Graceful shutdown ensures clean disconnection and resource cleanup
-- All database operations use parameterized queries to prevent SQL injection
-- Attachment uploads are non-blocking (async) to avoid blocking message capture
-- Message capture continues even if AI analysis or attachment upload fails
-
-## Common Tasks
-
-### Add a new config variable
-1. Add to config schema in both `services/backend/src/shared/config/index.ts` and `services/discord-gateway/src/shared/config/config.ts` with Zod validation
-2. Add to `.env.example` with description
-3. Use via `config.VARIABLE_NAME`
-
-### Add a new REST endpoint
-1. Create route handler in `services/backend/src/modules/<module>/<name>.routes.ts`
-2. Register in `services/backend/src/http/app.ts`
-3. Use `asyncHandler` wrapper for error handling
-4. Return JSON response
-
-### Add a new WebSocket event
-1. Add to `eventTypes.ts` in discord-gateway
-2. Add publish method to `EventBroadcaster` in discord-gateway
-3. Add subscription + broadcast mapping in `services/backend/src/ws/redis-bridge.ts`
-4. Add event type to `WSEventMap` in frontend `events.ts`
-5. Add handler to `WsHandlers` in frontend `socket.ts`
-
-### Add a new database table
-1. Add table definition in `services/discord-gateway/src/shared/database/schema.ts`
-2. Generate migration: `pnpm run db:generate`
-3. Check migration file in `drizzle/migrations/`
-4. Apply: `pnpm run db:migrate`
-
-### Add a new Redis command
-1. Add handler case in `commandHandler.ts` switch statement
-2. Add publish call on backend side (see `voice.service.ts` or `media.service.ts`)
-3. Update frontend API client if needed
-
-### Debug AI moderation
-- Set `AI_ANALYSIS_ENABLED=true` and `VERBOSE=true`
-- Check `ai_status`, `ai_error` fields in messages table
-- Monitor `/api/analysis/search?q=<text>` for analysis results
-- Check `ai_analysis_runs` table for batch run status
-- Adjust `AI_ANALYSIS_*` tuning variables
-
-### Debug voice recording
-- Set `VERBOSE=true`
-- Check `/api/status` for active connection
-- Monitor segment files in `recordings/<user-id>/`
-- Check `voice_recordings` table for upload status
-
-## CodeGraph Usage (Required)
-
-- Use CodeGraph first for repo-level questions: architecture, dependencies, references, callers/callees, impact, flow, routes, components.
-- If graph is missing or stale, run scan first to refresh `.codegraph/graph.json`.
-- Prefer graph-backed flow:
-  1. scan-codegraph (build/refresh graph)
-  2. query-codegraph (find definitions/references/callers/dependencies)
-  3. analyze-codegraph (architecture, impact, risk, cycles, orphans, hotspots)
-  4. export-codegraph (json/mermaid/dot/markdown/html when needed)
-  5. open-codegraph-ui (interactive visualization when requested)
-- Avoid broad grep/find or repeated wide file reads before graph lookup, except for exact literal search or known single-file edits.

README.md

@@ -1,118 +0,0 @@
-# Bete — Discord Moderation Dashboard
-
-Bot monitoring Discord yang merekam voice channel, menangkap pesan teks, menyimpan attachment, menjalankan analisis AI opsional, dan menyediakan dashboard web real-time.
-
-**Stack utama:** Node.js (Express 5), pnpm, TypeScript, React 19 (Next.js 16), Tailwind v4, shadcn/ui, Drizzle ORM, PostgreSQL, WebSocket, Redis pub/sub.
-
-## Prasyarat
-
-- Node.js 22+
-- pnpm 11.x
-- FFmpeg di `PATH` (untuk audio muxing dan playback media)
-- `yt-dlp` di `PATH` (untuk resolve audio YouTube/Spotify)
-- Bun (untuk frontend dev — opsional, bisa pake pnpm)
-- PostgreSQL 15+
-
-## Setup
-
-```bash
-pnpm install
-cp .env.example .env
-# Edit .env sesuai konfigurasi server
-```
-
-## Menjalankan
-
-```bash
-# Backend (port 3001)
-pnpm run dev:backend
-
-# Discord Gateway (capture messages, voice, dll)
-pnpm run dev:discord-gateway
-
-# Frontend (port 3000)
-pnpm run dev:web
-```
-
-## Build
-
-```bash
-pnpm run build:backend
-pnpm run build:discord-gateway
-pnpm run build:web        # next build — static export ke out/
-pnpm run build             # build semua service
-```
-
-## Deploy
-
-```bash
-./deploy.sh                # Build + deploy semua service ke VPS
-./deploy.sh --frontend     # Frontend only
-./deploy.sh --backend      # Backend only
-./deploy.sh --no-build     # Skip build, copy files aja
-```
-
-## Service Architecture
-
-```
-Discord
-   |
-   v
-discord-gateway ←→ Redis ←→ backend (Express 5) ←→ frontend (Next.js)
-   |               pub/sub       |                        |
-   |                             +— REST API (/api/*)     |
-   |                             +— WebSocket (/ws)       |
-   +— message capture            +— AI moderation         |
-   +— voice recording             +— dashboard data        +— dashboard UI
-   +— attachment upload                                    +— real-time updates
-```
-
-## Fitur
-
-- **Message capture**: Capture pesan baru, edit, dan delete dari Discord
-- **Voice recording**: Rekam voice channel ke segmen OGG per user, streaming PCM real-time ke WebSocket
-- **Attachment upload**: Download + upload attachment ke external storage
-- **AI moderation**: Analisis pesan opsional via LLM, auto-delete, queue management
-- **Dashboard**: Messages feed, AI analysis review, voice connection, music player, recordings, user/channel stats
-- **Media playback**: Playback dari URL, file lokal, YouTube, Spotify
-- **WebSocket**: Real-time event streaming untuk semua aktivitas
-- **Public API**: Semua endpoint REST dan WebSocket dapat diakses tanpa autentikasi
-
-## Struktur Proyek
-
-```
-services/
-├── backend/                # Express 5 REST API + WebSocket server
-│   ├── src/modules/        # Feature modules (messages, voice, media, dll)
-│   └── src/http/           # Express app setup, middleware
-├── discord-gateway/        # Discord client, voice recording, AI analysis
-│   ├── src/modules/        # message-capture, voice-recording, ai-moderation
-│   └── src/shared/         # Config, database, Discord client
-└── frontend/               # Next.js 16 dashboard (static export)
-    ├── src/app/            # Pages (login, dashboard tabs)
-    ├── src/features/       # Feature components (dashboard, live, messages)
-    └── src/lib/            # API client, WebSocket, types
-packages/
-└── shared/                 # Shared types, errors, logger, utilities
-```
-
-## Database
-
-PostgreSQL via Drizzle ORM. Migrasi:
-
-```bash
-pnpm run db:generate   # Generate migration
-pnpm run db:migrate    # Apply migration
-pnpm run db:studio     # Drizzle Studio
-```
-
-## WebSocket Events
-
-Backend broadcast event berikut ke frontend via WebSocket:
-
-- `message_created`, `message_updated`, `message_deleted`, `message_analyzed`
-- `attachment_created`, `attachment_uploaded`
-- `voice_recording_started`, `voice_recording_stopped`, `voice_recording_uploaded`
-- `voice_active_user`, `voice_pcm_data`
-- `media_state`
-- `reaction_*`, `thread_*`, `presence_updated`, `guild_member_*`

biome.json

@@ -35,12 +35,15 @@
       "suspicious": {
         "noUnknownAtRules": "off",
         "useIterableCallbackReturn": "off",
-        "noArrayIndexKey": "warn"
+        "noArrayIndexKey": "off",
+        "noExplicitAny": "off"
       },
       "a11y": {
         "useSemanticElements": "off",
         "useButtonType": "off",
-        "noAutofocus": "off"
+        "noAutofocus": "off",
+        "useMediaCaption": "off",
+        "noStaticElementInteractions": "off"
       },
       "performance": {
         "noImgElement": "warn"
@@ -50,7 +53,10 @@
       },
       "correctness": {
         "noInvalidUseBeforeDeclaration": "off",
-        "noUnusedFunctionParameters": "warn"
+        "noUnusedFunctionParameters": "warn",
+        "noUnusedVariables": "warn",
+        "noUnusedImports": "warn",
+        "noUnusedPrivateClassMembers": "warn"
       }
     },
     "domains": {

docs/superpowers/plans/2026-07-27-cicd-overhaul.md

@@ -1,542 +0,0 @@
-# CI/CD Overhaul Implementation Plan
-
-> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
-
-**Goal:** Migrate from hybrid CI/CD (GitHub Actions + GitLab CI + hot-deploy) to single Gitea CI pipeline with container registry — VPS pulls only.
-
-**Architecture:** Three Docker images (backend, discord-gateway, proxy) built in Gitea CI, pushed to `git.imrnes.team/MythEclipse/GMW/*`, VPS pulls and restarts via SSH. No more hot-deploy bind-mounts.
-
-**Tech Stack:** Gitea CI (Act Runner, GitHub Actions-compatible syntax), Docker Buildx, Gitea Container Registry, appleboy/ssh-action
-
-## Global Constraints
-
-- Docker images must be self-contained (no bind-mount overlay at runtime)
-- All three images must be built from monorepo root using `infra/docker/Dockerfile.*`
-- Frontend static export built inside proxy Dockerfile (multi-stage, Next.js → Nginx)
-- Gitea CI variables: GITEA_REGISTRY_TOKEN (secret), VPS_HOST (secret), VPS_USER (secret), VPS_SSH_KEY (secret), ENV_FILE (secret), GITEA_REGISTRY (variable)
-- Registry URL: `git.imrnes.team/MythEclipse/GMW/`
-- Work on `main` branch only
-- Must preserve voice recordings volume persistence across container restarts
-
----
-### Task 1: Create Gitea CI workflow
-
-**Files:**
-- Create: `.gitea/workflows/deploy.yml`
-
-**Interfaces:**
-- Consumes: Dockerfiles at `infra/docker/Dockerfile.{backend,discord-gateway,proxy}`
-- Produces: Docker images pushed to `git.imrnes.team/MythEclipse/GMW/bete-*:latest` and `:{sha}`
-- Depends on: Task 2 (proxy Dockerfile), Task 3 (backend Dockerfile) — but workflow can reference files that are being written in the same commit
-
-- [ ] **Step 1: Create `.gitea/workflows/` directory and `deploy.yml`**
-
-```bash
-mkdir -p .gitea/workflows
-```
-
-- [ ] **Step 2: Write the workflow file**
-
-Create `.gitea/workflows/deploy.yml`:
-
-```yaml
-name: Build & Deploy
-run-name: "Build & Deploy ${{ gitea.sha }}"
-
-on:
-  push:
-    branches: [main]
-
-jobs:
-  build-and-push:
-    runs-on: ubuntu-latest
-    strategy:
-      fail-fast: false
-      max-parallel: 2
-      matrix:
-        service: [backend, discord-gateway, proxy]
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-        with:
-          submodules: recursive
-
-      - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@v4
-
-      - name: Login to Gitea Registry
-        uses: docker/login-action@v4
-        with:
-          registry: ${{ vars.GITEA_REGISTRY }}
-          username: ${{ gitea.actor }}
-          password: ${{ secrets.GITEA_REGISTRY_TOKEN }}
-
-      - name: Build & Push ${{ matrix.service }}
-        uses: docker/build-push-action@v7
-        with:
-          context: .
-          file: infra/docker/Dockerfile.${{ matrix.service }}
-          push: true
-          tags: |
-            ${{ vars.GITEA_REGISTRY }}/MythEclipse/GMW/bete-${{ matrix.service }}:${{ gitea.sha }}
-            ${{ vars.GITEA_REGISTRY }}/MythEclipse/GMW/bete-${{ matrix.service }}:latest
-          cache-from: type=gha,scope=bete-${{ matrix.service }}
-          cache-to: type=gha,mode=max,scope=bete-${{ matrix.service }}
-          build-args: |
-            VITE_BE_API_URL=https://imphnen.asepharyana.my.id
-            VITE_BE_WS_URL=wss://imphnen.asepharyana.my.id
-
-  deploy:
-    needs: build-and-push
-    runs-on: ubuntu-latest
-    if: gitea.ref == 'refs/heads/main'
-    steps:
-      - name: Deploy to VPS
-        uses: appleboy/ssh-action@v1.2.5
-        env:
-          ENV_FILE: ${{ secrets.ENV_FILE }}
-        with:
-          host: ${{ secrets.VPS_HOST }}
-          username: ${{ secrets.VPS_USER }}
-          key: ${{ secrets.VPS_SSH_KEY }}
-          envs: ENV_FILE
-          script: |
-            set -eu
-            APP_DIR=/opt/imphenbot
-            cd "$APP_DIR/infra/docker"
-            printf '%s\n' "$ENV_FILE" | tr -d '\r' > .env
-            docker compose pull
-            docker compose up -d --remove-orphans
-            docker image prune -f
-```
-
-Note: Gitea's Act Runner supports `gitea.*` context variables (`gitea.sha`, `gitea.actor`, `gitea.ref`). If `gitea.*` vars don't resolve, fall back to `github.*` equivalents (Act Runner emulates GitHub context).
-
-- [ ] **Step 3: Commit**
-
-```bash
-git add .gitea/workflows/deploy.yml
-git commit -m "ci: add Gitea CI workflow for build & deploy
-
-Gitea CI builds three Docker images (backend, discord-gateway, proxy),
-pushes to Gitea Container Registry, then deploys to VPS via SSH pull.
-
-Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>"
-```
-
----
-### Task 2: Rewrite Dockerfile.proxy for Next.js static export
-
-**Files:**
-- Rewrite: `infra/docker/Dockerfile.proxy`
-
-**Interfaces:**
-- Consumes: `services/frontend/` (Next.js app), `packages/shared/` (workspace dep), `infra/docker/nginx/nginx.conf`
-- Produces: Nginx image serving Next.js static export at `/usr/share/nginx/html/`
-
-- [ ] **Step 1: Rewrite Dockerfile.proxy**
-
-Replace entire content with:
-
-```dockerfile
-# ---- Stage 1: Build Next.js static export ----
-FROM node:22-slim AS frontend-builder
-
-WORKDIR /app
-
-# Install pnpm
-RUN corepack enable
-
-# Install build essentials for native deps
-RUN apt-get update -qq && apt-get install -y -qq --no-install-recommends \
-    python3 make g++ && rm -rf /var/lib/apt/lists/*
-
-# Copy dependency manifests first for layer caching
-COPY pnpm-lock.yaml pnpm-workspace.yaml package.json ./
-COPY packages/shared/package.json ./packages/shared/package.json
-COPY services/frontend/package.json ./services/frontend/package.json
-COPY services/frontend/tsconfig.json ./services/frontend/tsconfig.json
-
-# Install dependencies (frontend + shared)
-RUN --mount=type=cache,id=pnpm-store,target=/root/.local/share/pnpm/store \
-    pnpm install --frozen-lockfile --filter './packages/shared' --filter './services/frontend'
-
-# Copy source code
-COPY packages/shared/ ./packages/shared/
-COPY services/frontend/ ./services/frontend/
-
-# Pass API/WS URLs as build args for the frontend
-ARG VITE_BE_API_URL
-ARG VITE_BE_WS_URL
-ENV VITE_BE_API_URL=${VITE_BE_API_URL}
-ENV VITE_BE_WS_URL=${VITE_BE_WS_URL}
-
-# Build shared lib first, then frontend static export
-RUN --mount=type=cache,id=pnpm-store,target=/root/.local/share/pnpm/store \
-    pnpm --filter './packages/shared' run build
-RUN --mount=type=cache,id=pnpm-store,target=/root/.local/share/pnpm/store \
-    pnpm --filter frontend run build
-
-# ---- Stage 2: Nginx ----
-FROM nginx:alpine
-
-# Nginx config (API/WS proxy + static file serving)
-COPY infra/docker/nginx/nginx.conf /etc/nginx/conf.d/default.conf
-
-# Static export from frontend builder
-COPY --from=frontend-builder /app/services/frontend/out/ /usr/share/nginx/html/
-
-EXPOSE 80
-
-HEALTHCHECK --interval=30s --timeout=3s --start-period=10s --retries=3 \
-  CMD wget -qO- http://localhost:80/ || exit 1
-
-CMD ["nginx", "-g", "daemon off;"]
-```
-
-- [ ] **Step 2: Validate nginx.conf handles static files correctly**
-
-Read and confirm `infra/docker/nginx/nginx.conf`.
-
-```bash
-cat infra/docker/nginx/nginx.conf
-```
-
-Verify it has:
-- Static file location with `try_files $uri /index.html` (SPA fallback)
-- `/api` and `/ws` proxied to `http://backend:3000`
-
-- [ ] **Step 3: Commit**
-
-```bash
-git add infra/docker/Dockerfile.proxy
-git commit -m "docker(proxy): rewrite for Next.js static export
-
-Replaced stale Rust WASM build with multi-stage Docker build:
-stage 1 builds Next.js static export, stage 2 serves via Nginx.
-Includes VITE_BE_API_URL/VITE_BE_WS_URL build args.
-
-Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>"
-```
-
----
-### Task 3: Add build args to Dockerfile.backend
-
-**Files:**
-- Modify: `infra/docker/Dockerfile.backend`
-
-- [ ] **Step 1: Add VITE build args to Dockerfile.backend**
-
-Insert after `WORKDIR /app`:
-
-```dockerfile
-# Build args for frontend API URLs (passed through for future use)
-ARG VITE_BE_API_URL
-ARG VITE_BE_WS_URL
-ENV VITE_BE_API_URL=${VITE_BE_API_URL}
-ENV VITE_BE_WS_URL=${VITE_BE_WS_URL}
-```
-
-Note: These are consumed by the proxy Dockerfile (Task 2), not needed by backend itself but passed through the CI workflow to all three images for consistency.
-
-- [ ] **Step 2: Commit**
-
-```bash
-git add infra/docker/Dockerfile.backend
-git commit -m "docker(backend): add VITE_BE_API_URL and VITE_BE_WS_URL build args
-
-Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>"
-```
-
----
-### Task 4: Rewrite docker-compose.yml for Gitea registry + no bind-mounts
-
-**Files:**
-- Rewrite: `infra/docker/docker-compose.yml`
-
-- [ ] **Step 1: Write new docker-compose.yml**
-
-Replace entire content:
-
-```yaml
-version: '3.8'
-
-services:
-  proxy:
-    image: ${GITEA_REGISTRY}/MythEclipse/GMW/bete-proxy:${IMAGE_TAG:-latest}
-    container_name: imphenbot-proxy
-    restart: unless-stopped
-    labels:
-      - "traefik.enable=true"
-      - "traefik.http.routers.imphenbot.rule=Host(`imphnen.asepharyana.my.id`)"
-      - "traefik.http.routers.imphenbot.entrypoints=websecure"
-      - "traefik.http.routers.imphenbot.tls=true"
-      - "traefik.http.services.imphenbot.loadbalancer.server.port=80"
-    depends_on:
-      - backend
-    healthcheck:
-      test: ["CMD", "wget", "-qO-", "http://127.0.0.1/"]
-      interval: 30s
-      timeout: 5s
-      retries: 3
-    deploy:
-      resources:
-        limits:
-          memory: 64M
-    networks:
-      - app-shared-net
-
-  backend:
-    image: ${GITEA_REGISTRY}/MythEclipse/GMW/bete-backend:${IMAGE_TAG:-latest}
-    container_name: imphenbot-backend
-    restart: unless-stopped
-    env_file:
-      - .env
-    environment:
-      NODE_ENV: production
-      WEBSERVER_PORT: 3000
-    healthcheck:
-      test: ["CMD", "wget", "-qO-", "http://localhost:3000/api/health"]
-      interval: 30s
-      timeout: 10s
-      start_period: 15s
-      retries: 3
-    deploy:
-      resources:
-        limits:
-          memory: 256M
-    networks:
-      - app-shared-net
-
-  discord-gateway:
-    image: ${GITEA_REGISTRY}/MythEclipse/GMW/bete-discord-gateway:${IMAGE_TAG:-latest}
-    container_name: imphenbot-discord-gateway
-    restart: unless-stopped
-    env_file:
-      - .env
-    environment:
-      NODE_ENV: production
-    volumes:
-      - recordings:/app/recordings
-    healthcheck:
-      test: ["CMD-SHELL", "kill -0 1 || exit 1"]
-      interval: 30s
-      timeout: 5s
-      start_period: 30s
-      retries: 3
-    deploy:
-      resources:
-        limits:
-          memory: 512M
-    networks:
-      - app-shared-net
-
-volumes:
-  recordings:
-
-networks:
-  app-shared-net:
-    name: app-shared-net
-    external: true
-```
-
-Key changes:
-- Image refs: `registry.gitlab.com/...` → `${GITEA_REGISTRY}/MythEclipse/GMW/...`
-- Removed all bind-mount volumes: `./backend-dist`, `./gateway-dist`, `./frontend-dist`, `./shared-dist`
-- Changed `./recordings` bind-mount → named volume `recordings:` (persists across restarts)
-- Added `depends_on: backend` to proxy (proxy needs backend for API/WS, though Nginx handles startup gracefully)
-
-- [ ] **Step 2: Commit**
-
-```bash
-git add infra/docker/docker-compose.yml
-git commit -m "docker(compose): switch to Gitea registry, remove bind-mounts
-
-Images now come from git.imrnes.team/MythEclipse/GMW. All hot-deploy
-bind-mounts removed — containers are fully self-contained. Voice
-recordings use a named volume instead of bind-mount.
-
-Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>"
-```
-
----
-### Task 5: Create lightweight deploy.sh
-
-**Files:**
-- Create: `deploy.sh`
-
-- [ ] **Step 1: Write deploy.sh**
-
-```bash
-#!/bin/bash
-set -euo pipefail
-
-SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
-INFRA_DIR="$SCRIPT_DIR/infra/docker"
-
-: "${VPS_HOST:?required}"
-: "${VPS_USER:?required}"
-: "${VPS_SSH_KEY:?required}"
-
-echo "=== Deploy to $VPS_HOST ==="
-
-# Copy local .env if it exists (overrides CI env)
-if [ -f "$INFRA_DIR/.env" ]; then
-  scp -i "$VPS_SSH_KEY" "$INFRA_DIR/.env" "$VPS_USER@$VPS_HOST:/opt/imphenbot/infra/docker/.env"
-fi
-
-ssh -i "$VPS_SSH_KEY" "$VPS_USER@$VPS_HOST" << 'REMOTESCRIPT'
-  set -eu
-  cd /opt/imphenbot/infra/docker
-  echo "=== Pulling images ==="
-  docker compose pull
-  echo "=== Restarting containers ==="
-  docker compose up -d --remove-orphans
-  echo "=== Cleaning up ==="
-  docker image prune -f
-  echo "=== Active containers ==="
-  docker ps --filter "name=imphenbot" --format "table {{.Names}}\t{{.Image}}\t{{.Status}}"
-REMOTESCRIPT
-
-echo "=== Deploy complete ==="
-```
-
-- [ ] **Step 2: Make executable**
-
-```bash
-chmod +x deploy.sh
-```
-
-- [ ] **Step 3: Commit**
-
-```bash
-git add deploy.sh
-git commit -m "chore: rewrite deploy.sh as lightweight SSH pull script
-
-Replaced hot-deploy tar-pipe script with simple SSH-based deploy
-that pulls latest images from Gitea registry and restarts containers.
-
-Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>"
-```
-
----
-### Task 6: Disable old CI files
-
-**Files:**
-- Disable: `.github/workflows/deploy-docker.yml`
-- Keep: `.gitlab-ci.yml` if exists (already may have been removed)
-
-- [ ] **Step 1: Rename GitHub Actions workflow to .disabled**
-
-```bash
-mv .github/workflows/deploy-docker.yml .github/workflows/deploy-docker.yml.disabled
-```
-
-- [ ] **Step 2: Remove docker compose file's old frontend-dist directory from git** (if tracked)
-
-```bash
-# Check if frontend-dist is tracked (it should be gitignored, but check)
-git ls-files infra/docker/frontend-dist 2>/dev/null || echo "Not tracked — OK"
-```
-
-- [ ] **Step 3: Commit**
-
-```bash
-git add .github/workflows/deploy-docker.yml.disabled
-git rm --cached .github/workflows/deploy-docker.yml 2>/dev/null || true
-git commit -m "ci: disable GitHub Actions workflow
-
-Renamed to .disabled. All CI now goes through Gitea CI (.gitea/workflows/).
-
-Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>"
-```
-
----
-### Task 7: Update .gitignore
-
-**Files:**
-- Modify: `.gitignore`
-
-- [ ] **Step 1: Add .gitea exclusion note and any missing entries**
-
-Read current `.gitignore`:
-
-```bash
-cat .gitignore
-```
-
-Then append (only if not already present):
-
-```
-# Gitea workflow logs (local runners)
-.gitea/workflows/*.log
-```
-
-The `.gitea/workflows/` YAML files themselves should be tracked in git.
-
-- [ ] **Step 2: Commit**
-
-```bash
-git add .gitignore
-git commit -m "chore: update gitignore for Gitea CI artifacts
-
-Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>"
-```
-
----
-### Task 8: Push and verify CI pipeline
-
-- [ ] **Step 1: Verify all changes**
-
-```bash
-git status
-git log --oneline -10
-```
-
-Expected: clean working tree, all 7 commits ready to push.
-
-- [ ] **Step 2: Push to main**
-
-```bash
-git push origin main
-```
-
-- [ ] **Step 3: Monitor CI run**
-
-Watch Gitea CI at `https://git.imrnes.team/MythEclipse/GMW/actions`.
-
-Expected outcome:
-1. `build-and-push` job runs 3 matrix builds (backend, discord-gateway, proxy) in parallel (max 2)
-2. Each image is pushed to `git.imrnes.team/MythEclipse/GMW/bete-*` with both `:latest` and `:{sha}` tags
-3. `deploy` job SSHes into VPS, pulls images, restarts containers
-4. All 3 containers `imphenbot-proxy`, `imphenbot-backend`, `imphenbot-discord-gateway` are running
-
-- [ ] **Step 4: Verify containers on VPS**
-
-```bash
-# SSH into VPS and check
-ssh -i "$VPS_SSH_KEY" "$VPS_USER@$VPS_HOST" "
-  docker ps --filter 'name=imphenbot' --format 'table {{.Names}}\t{{.Image}}\t{{.Status}}'
-  docker compose -f /opt/imphenbot/infra/docker/docker-compose.yml ps
-"
-```
-
-- [ ] **Step 5: Verify no hot-deploy artifacts remain**
-
-```bash
-ssh -i "$VPS_SSH_KEY" "$VPS_USER@$VPS_HOST" "
-  ls -la /opt/imphenbot/infra/docker/ | grep -E 'dist$' || echo 'No dist dirs — clean'
-"
-```
-
----
-## Rollback
-
-If the pipeline fails at any point:
-
-1. **Fix and re-push**: Edit the broken file, commit, push to main — CI re-runs automatically
-2. **Emergency rollback**: SSH to VPS, run `docker compose up -d` with a known-good IMAGE_TAG:
-   ```bash
-   IMAGE_TAG=<last-working-sha> docker compose up -d
-   ```
-3. **Restore old CI**: Move `.github/workflows/deploy-docker.yml.disabled` back and push

docs/superpowers/plans/2026-07-27-refactor-backend-gateway-p1.md

@@ -1,736 +0,0 @@
-# Backend & Gateway Refactoring — Phase 1 Implementation Plan
-
-> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
-
-**Goal:** Clean up ~130 lines of dead/duplicate code, consolidate duplicated database initialization, and simplify the MessageStore layering in discord-gateway.
-
-**Architecture:** Three independent tasks that can be done in any order. Task 1 consolidates database pool/drizzle init into `@bete/shared` so both services use one canonical pattern. Task 2 removes backward-compat function wrappers from `messageStore.ts`. Task 3 deletes dead files and functions.
-
-**Tech Stack:** TypeScript, Node.js, Drizzle ORM, PostgreSQL, pnpm workspace
-
-## Global Constraints
-
-- All imports use `.js` extensions (ESM convention)
-- Follow existing code style (Biome, 2-space indent)
-- Keep `@bete/shared` as the single source of truth for shared infrastructure
-- No package.json changes needed — `@bete/shared` already has `drizzle-orm` and `pg` as dependencies
-- Do not change any business logic — only structural refactoring
-
----
-
-### Task 1: Consolidate Database Initialization into `@bete/shared`
-
-**Files:**
-- Create: `packages/shared/src/database/init.ts`
-- Modify: `packages/shared/src/database/pool.ts` — add `getPool()` export
-- Modify: `packages/shared/src/index.ts` — export new `./database/init.js`
-- Modify: `packages/shared/package.json` — add `"./database/init"` export entry
-- Modify: `services/backend/src/shared/database/index.ts` — re-export from shared
-- Modify: `services/discord-gateway/src/shared/database/drizzle.ts` — re-export from shared
-- Delete: (functions migrate, no file deletion here — both local files stay as thin wrappers)
-
-**Interfaces:**
-- Produces:
-  - `@bete/shared/database/init` exports:
-    - `let db: ReturnType<typeof drizzle> | null` (module-level, for getDatabase())
-    - `let rawPool: Pool | null` (module-level, for getPool())
-    - `initializeDatabase(schema?: Record<string, unknown>): Promise<ReturnType<typeof drizzle>>` — creates pool via `createPoolFromConfig`, wraps with `drizzle()`. Accepts optional schema object (gateway needs it, backend doesn't). Reads config from env/config module internally.
-    - `getDatabase(): ReturnType<typeof drizzle>` — throws if not initialized
-    - `getPool(): Pool` — returns raw pool for raw SQL queries, throws if not initialized
-    - `closeDatabase(): Promise<void>` — closes pool and nullifies references
-    - `executeAll(sql: string, params?: unknown[]): Promise<unknown[]>` — raw SQL query, returns all rows
-    - `executeGet(sql: string, params?: unknown[]): Promise<unknown>` — raw SQL query, returns first row or null
-    - `withDatabaseClient<T>(callback: (client: PoolClient) => Promise<T>): Promise<T>`
-
-- [ ] **Step 1: Create `packages/shared/src/database/init.ts`**
-
-This is the canonical database initialization module. It merges what both services currently do:
-
-```typescript
-import { createChildLogger } from "@bete/shared/logger";
-import { closePool, createPoolFromConfig } from "@bete/shared/database/pool";
-import { drizzle } from "drizzle-orm/node-postgres";
-import type { Pool, PoolClient } from "pg";
-import { config } from "../config/index.js";
-
-const logger = createChildLogger("database.init");
-
-let db: ReturnType<typeof drizzle> | null = null;
-let rawPool: Pool | null = null;
-
-export async function initializeDatabase(schema?: Record<string, unknown>) {
-  if (db !== null) return db;
-
-  const pool = config.DATABASE_URL
-    ? createPoolFromConfig({
-        url: config.DATABASE_URL,
-        min: config.POSTGRES_POOL_MIN,
-        max: config.POSTGRES_POOL_MAX,
-      })
-    : createPoolFromConfig({
-        host: config.POSTGRES_HOST,
-        port: config.POSTGRES_PORT,
-        user: config.POSTGRES_USER,
-        password: config.POSTGRES_PASSWORD,
-        database: config.POSTGRES_DB,
-        min: config.POSTGRES_POOL_MIN,
-        max: config.POSTGRES_POOL_MAX,
-      });
-
-  rawPool = pool;
-  db = drizzle(pool, schema ? { schema } : undefined);
-
-  // Test connection
-  try {
-    const client = await pool.connect();
-    client.release();
-    logger.info("Database connection successful");
-  } catch (err) {
-    logger.error({ err }, "Failed to connect to database");
-    throw err;
-  }
-
-  return db;
-}
-
-export function getDatabase() {
-  if (db === null) {
-    throw new Error("Database not initialized. Call initializeDatabase() first.");
-  }
-  return db;
-}
-
-export function getPool() {
-  if (!rawPool) {
-    throw new Error("Database not initialized. Call initializeDatabase() first.");
-  }
-  return rawPool;
-}
-
-export async function closeDatabase() {
-  if (rawPool !== null) {
-    await closePool(rawPool);
-  }
-  rawPool = null;
-  db = null;
-  logger.info("Database connection closed");
-}
-
-function convertPlaceholdersForPostgres(sql: string) {
-  let i = 0;
-  return sql.replace(/\?/g, () => `$${++i}`);
-}
-
-export async function executeAll(sql: string, params?: unknown[]) {
-  if (!rawPool) {
-    throw new Error("Database not initialized. Call initializeDatabase() first.");
-  }
-  const query = convertPlaceholdersForPostgres(sql);
-  const result = await rawPool.query(query, params || []);
-  return result.rows;
-}
-
-export async function executeGet(sql: string, params?: unknown[]) {
-  if (!rawPool) {
-    throw new Error("Database not initialized. Call initializeDatabase() first.");
-  }
-  const query = convertPlaceholdersForPostgres(sql);
-  const result = await rawPool.query(query, params || []);
-  return result.rows[0] ?? null;
-}
-
-export async function withDatabaseClient<T>(
-  callback: (client: PoolClient) => Promise<T>,
-): Promise<T> {
-  if (!rawPool) {
-    throw new Error("Database not initialized. Call initializeDatabase() first.");
-  }
-  const client = await rawPool.connect();
-  try {
-    return await callback(client);
-  } finally {
-    client.release();
-  }
-}
-```
-
-**Note:** This uses `config` from `@bete/shared/config`. The backend's config proxies to that already (`services/backend/src/shared/config/index.ts` re-exports from `@bete/shared/config`). The gateway's config at `services/discord-gateway/src/shared/config/config.ts` has the same field names but is its own Zod schema. Since `@bete/shared/config` doesn't have the PostgreSQL pool config fields currently, we need to check what it exports.
-
-Actually — `@bete/shared/config` may not have `POSTGRES_HOST` etc. Let me adjust: the `initializeDatabase` function should accept config values as parameters instead of reading from a shared config.
-
-Revised approach for `packages/shared/src/database/init.ts`:
-
-```typescript
-import { createChildLogger } from "@bete/shared/logger";
-import { closePool, createPoolFromConfig } from "./pool.js";
-import { drizzle } from "drizzle-orm/node-postgres";
-import type { Pool, PoolClient } from "pg";
-
-const logger = createChildLogger("database.init");
-
-let db: ReturnType<typeof drizzle> | null = null;
-let rawPool: Pool | null = null;
-
-export interface DatabaseConfig {
-  DATABASE_URL?: string;
-  POSTGRES_HOST?: string;
-  POSTGRES_PORT?: number;
-  POSTGRES_USER?: string;
-  POSTGRES_PASSWORD?: string;
-  POSTGRES_DB?: string;
-  POSTGRES_POOL_MIN?: number;
-  POSTGRES_POOL_MAX?: number;
-}
-
-export async function initializeDatabase(
-  cfg: DatabaseConfig,
-  schema?: Record<string, unknown>,
-) {
-  if (db !== null) return db;
-
-  const pool = cfg.DATABASE_URL
-    ? createPoolFromConfig({
-        url: cfg.DATABASE_URL,
-        min: cfg.POSTGRES_POOL_MIN,
-        max: cfg.POSTGRES_POOL_MAX,
-      })
-    : createPoolFromConfig({
-        host: cfg.POSTGRES_HOST,
-        port: cfg.POSTGRES_PORT,
-        user: cfg.POSTGRES_USER,
-        password: cfg.POSTGRES_PASSWORD,
-        database: cfg.POSTGRES_DB,
-        min: cfg.POSTGRES_POOL_MIN,
-        max: cfg.POSTGRES_POOL_MAX,
-      });
-
-  rawPool = pool;
-  db = drizzle(pool, schema ? { schema } : undefined);
-
-  try {
-    const client = await pool.connect();
-    client.release();
-    logger.info("Database connection successful");
-  } catch (err) {
-    logger.error({ err }, "Failed to connect to database");
-    throw err;
-  }
-
-  return db;
-}
-
-export function getDatabase() {
-  if (db === null) {
-    throw new Error("Database not initialized. Call initializeDatabase() first.");
-  }
-  return db;
-}
-
-export function getPool() {
-  if (!rawPool) {
-    throw new Error("Database not initialized. Call initializeDatabase() first.");
-  }
-  return rawPool;
-}
-
-export async function closeDatabase() {
-  if (rawPool !== null) {
-    await closePool(rawPool);
-  }
-  rawPool = null;
-  db = null;
-  logger.info("Database connection closed");
-}
-
-function convertPlaceholdersForPostgres(sql: string) {
-  let i = 0;
-  return sql.replace(/\?/g, () => `$${++i}`);
-}
-
-export async function executeAll(sql: string, params?: unknown[]) {
-  if (!rawPool) {
-    throw new Error("Database not initialized. Call initializeDatabase() first.");
-  }
-  const query = convertPlaceholdersForPostgres(sql);
-  const result = await rawPool.query(query, params || []);
-  return result.rows;
-}
-
-export async function executeGet(sql: string, params?: unknown[]) {
-  if (!rawPool) {
-    throw new Error("Database not initialized. Call initializeDatabase() first.");
-  }
-  const query = convertPlaceholdersForPostgres(sql);
-  const result = await rawPool.query(query, params || []);
-  return result.rows[0] ?? null;
-}
-
-export async function withDatabaseClient<T>(
-  callback: (client: PoolClient) => Promise<T>,
-): Promise<T> {
-  if (!rawPool) {
-    throw new Error("Database not initialized. Call initializeDatabase() first.");
-  }
-  const client = await rawPool.connect();
-  try {
-    return await callback(client);
-  } finally {
-    client.release();
-  }
-}
-```
-
-- [ ] **Step 2: Add export to `packages/shared/src/index.ts`**
-
-```typescript
-export * from "./database/init.js";
-```
-
-- [ ] **Step 3: Add export to `packages/shared/package.json`**
-
-```json
-"./database/init": "./dist/database/init.js",
-```
-
-- [ ] **Step 4: Build the shared package to verify it compiles**
-
-```bash
-cd /home/code/GMW/packages/shared
-pnpm run build
-```
-
-- [ ] **Step 5: Rewrite `services/backend/src/shared/database/index.ts`**
-
-Change to a thin wrapper that imports from `@bete/shared/database/init` and passes the backend's config:
-
-```typescript
-import { createChildLogger } from "@bete/shared/logger";
-import { initializeDatabase as sharedInit, getDatabase as sharedGetDb, getPool as sharedGetPool, closeDatabase as sharedCloseDb } from "@bete/shared/database/init";
-import { config } from "../config/index.js";
-
-const logger = createChildLogger("database");
-
-const dbConfig = {
-  DATABASE_URL: config.DATABASE_URL,
-  POSTGRES_HOST: config.POSTGRES_HOST,
-  POSTGRES_PORT: config.POSTGRES_PORT,
-  POSTGRES_USER: config.POSTGRES_USER,
-  POSTGRES_PASSWORD: config.POSTGRES_PASSWORD,
-  POSTGRES_DB: config.POSTGRES_DB,
-  POSTGRES_POOL_MIN: config.POSTGRES_POOL_MIN,
-  POSTGRES_POOL_MAX: config.POSTGRES_POOL_MAX,
-};
-
-export async function initializeDatabase() {
-  logger.info("Initializing database");
-  return sharedInit(dbConfig);
-}
-
-export function getDatabase() {
-  return sharedGetDb();
-}
-
-export function getPool() {
-  return sharedGetPool();
-}
-
-export async function closeDatabase() {
-  logger.info("Closing database");
-  return sharedCloseDb();
-}
-```
-
-- [ ] **Step 6: Rewrite `services/discord-gateway/src/shared/database/drizzle.ts`**
-
-Change to a thin wrapper:
-
-```typescript
-import { createChildLogger } from "@bete/shared/logger";
-import { initializeDatabase as sharedInit, getDatabase as sharedGetDb, closeDatabase as sharedCloseDb, executeAll as sharedExecAll, executeGet as sharedExecGet, withDatabaseClient as sharedWithClient } from "@bete/shared/database/init";
-import { config } from "../../shared/config/config.js";
-import * as schema from "./schema.js";
-
-const logger = createChildLogger("drizzle");
-
-const dbConfig = {
-  DATABASE_URL: config.DATABASE_URL,
-  POSTGRES_HOST: config.POSTGRES_HOST,
-  POSTGRES_PORT: config.POSTGRES_PORT,
-  POSTGRES_USER: config.POSTGRES_USER,
-  POSTGRES_PASSWORD: config.POSTGRES_PASSWORD,
-  POSTGRES_DB: config.POSTGRES_DB,
-  POSTGRES_POOL_MIN: config.POSTGRES_POOL_MIN,
-  POSTGRES_POOL_MAX: config.POSTGRES_POOL_MAX,
-};
-
-export async function initializeDatabase() {
-  return sharedInit(dbConfig, schema);
-}
-
-export function getDatabase() {
-  return sharedGetDb();
-}
-
-export { sharedCloseDb as closeDatabase };
-export { sharedExecAll as executeAll, sharedExecGet as executeGet, sharedWithClient as withDatabaseClient };
-```
-
-- [ ] **Step 7: Run typecheck on all packages to verify**
-
-```bash
-cd /home/code/GMW
-pnpm run typecheck
-```
-
-- [ ] **Step 8: Commit**
-
-```bash
-git add packages/shared/src/database/init.ts packages/shared/src/index.ts packages/shared/package.json
-git add services/backend/src/shared/database/index.ts services/discord-gateway/src/shared/database/drizzle.ts
-git commit -m "refactor: consolidate database initialization into @bete/shared/database/init"
-```
-
----
-
-### Task 2: Remove Backward-Compat Function Wrappers from MessageStore
-
-**Files:**
-- Modify: `services/discord-gateway/src/modules/message-capture/messageStore.ts` — remove lines 310-398 (backward-compat wrappers), export singleton directly
-- Modify: `services/discord-gateway/src/modules/message-capture/index.ts` — update re-exports to use `messageStore` singleton
-- Modify: `services/discord-gateway/src/modules/message-capture/messageCapture.ts` — update imports to use `messageStore.methodName()`
-- Modify: `services/discord-gateway/src/modules/ai-moderation/batchProcessor.ts` — update imports
-- Modify: `services/discord-gateway/src/modules/ai-moderation/batchScheduler.ts` — update imports
-- Modify: `services/discord-gateway/src/modules/ai-moderation/individualFallbackProcessor.ts` — update imports
-- Modify: `services/discord-gateway/src/modules/ai-moderation/moderationBuilders.ts` — update imports
-- Modify: `services/discord-gateway/src/modules/ai-moderation/aiAnalysisWorker.ts` — update imports (uses `getConversationContextBefore` and `updateMessagesAIAnalysisBulk`)
-- Modify: `services/discord-gateway/src/modules/ai-moderation/aiAnalyzer.ts` — update imports (uses many functions)
-- Possibly modify: other files that import the wrapper functions
-
-**Interfaces:**
-- Consumes: Existing `MessageStore` class methods (unchanged signatures)
-- Produces: Singleton `messageStore` instance as the single export point
-
-The key insight: the backward-compat wrappers at lines 310-398 of `messageStore.ts` are function-level exports that delegate to `getInstance()`. Every importer can instead import the singleton `messageStore` instance and call methods on it directly.
-
-Current importers of wrapper functions:
-
-| File | Functions Used |
-|------|---------------|
-| `messageCapture.ts` | `getMessageById`, `insertMessageEdit`, `updateMessageAsEdited`, `updateMessageAsDeleted`, `upsertMessageForCapture` |
-| `batchProcessor.ts` | `updateMessagesAIAnalysisBulk` |
-| `batchScheduler.ts` | `getPendingMessagesByConversation` |
-| `individualFallbackProcessor.ts` | `updateMessagesAIAnalysisBulk` |
-| `moderationBuilders.ts` | `getMessageById` |
-| `aiAnalysisWorker.ts` | `getConversationContextBefore`, `updateMessagesAIAnalysisBulk` |
-| `aiAnalyzer.ts` | `getConversationKeysWithIncompleteAnalysis`, `getIncompleteMessagesByConversation`, `getMessageById`, `getPendingConversationKeys`, `updateMessageAIAnalysis` |
-
-- [ ] **Step 1: Modify `messageStore.ts`** — replace backward-compat wrappers with a singleton export
-
-Replace lines 22-33 (lazy singleton pattern) and lines 310-398 (wrapper functions) with:
-
-```typescript
-// ─── Singleton instance ─────────────────────────────────────────────────────
-
-const logger = createChildLogger("message-store");
-const database = getDatabase() as unknown as NodePgDatabase<typeof schema>;
-export const messageStore = new MessageStore(database, logger);
-```
-
-Then remove everything from line 310 onward (the backward-compat function wrappers section).
-
-- [ ] **Step 2: Update `message-capture/index.ts`**
-
-Change the re-exports from individual functions to the `messageStore` singleton:
-
-```typescript
-export { messageStore } from "../message-capture/messageStore.js";
-export {
-  getDisplayContent,
-  getMessageLocation,
-  getMessageMetadata,
-} from "../message-capture/messageMetadata.js";
-// ... rest unchanged
-```
-
-Also remove the individual function re-exports since they no longer exist.
-
-- [ ] **Step 3: Update `messageCapture.ts`**
-
-Change imports from:
-```typescript
-import {
-  getMessageById,
-  insertMessageEdit,
-  upsertMessageForCapture,
-  updateMessageAsDeleted,
-  updateMessageAsEdited,
-} from "./messageStore.js";
-```
-To:
-```typescript
-import { messageStore } from "./messageStore.js";
-```
-
-Then update every call site:
-- `upsertMessageForCapture(messageRecord)` → `messageStore.upsertMessageForCapture(messageRecord)`
-- `insertMessageEdit(...)` → `messageStore.insertMessageEdit(...)`
-- `updateMessageAsEdited(...)` → `messageStore.updateMessageAsEdited(...)`
-- `updateMessageAsDeleted(...)` → `messageStore.updateMessageAsDeleted(...)`
-- `getMessageById(...)` → `messageStore.getMessageById(...)`
-
-- [ ] **Step 4: Update `batchProcessor.ts`**
-
-Change from:
-```typescript
-import { updateMessagesAIAnalysisBulk } from "../message-capture/messageStore.js";
-```
-To:
-```typescript
-import { messageStore } from "../message-capture/messageStore.js";
-```
-
-Then update call sites:
-- `updateMessagesAIAnalysisBulk(updates)` → `messageStore.messages.updateMessagesAIAnalysisBulk(updates)`
-
-Wait — `updateMessagesAIAnalysisBulk` is actually defined in `MessagesAnalysis` class, which is called via `MessageStore` → `MessagesDb` → `MessagesAnalysis`. Let me check the actual delegation chain.
-
-Looking at the wrapper functions:
-```typescript
-export const updateMessagesAIAnalysisBulk = (
-  updates: Array<{ messageId: string; result: AIAnalysisUpdate }>,
-): Promise<MessageRecord[]> =>
-  getInstance().updateMessagesAIAnalysisBulk(updates);
-```
-
-And in the class:
-```typescript
-class MessageStore {
-  readonly messages: MessagesDb;
-  // ...
-}
-
-class MessagesDb {
-  readonly analysis: MessagesAnalysis;
-  // ...
-  updateMessagesAIAnalysisBulk(...) {
-    return this.analysis.updateMessagesAIAnalysisBulk(...)
-  }
-}
-```
-
-So the call chain is: `messageStore.messages.updateMessagesAIAnalysisBulk()`. But actually, looking at `MessagesDb`, it might have its own `updateMessagesAIAnalysisBulk` that delegates to `this.analysis.updateMessagesAIAnalysisBulk()`. Let me verify...
-
-Actually, for simplicity and to minimize changes, let me look at whether `MessagesDb` has `updateMessagesAIAnalysisBulk` or if only the wrapper has it.
-
-Let me check:
-
-Actually I already read that `MessagesDb` has methods. Let me look at what methods `MessagesDb` exposes vs the wrapper functions.
-
-Instead of guessing, the safe approach is to keep the thin function wrappers but simplify them. Actually, a better approach for this task:
-
-**Revised approach:** Instead of making all importers use `messageStore.messages.analysis.methodName()`, add all the forwarded methods directly to the `MessageStore` class (which it already does for most), and just have external files import the singleton and call `messageStore.methodName()`.
-
-Let me check what methods `MessageStore` already has vs what's only available as backward-compat wrappers:
-
-Looking at the code:
-- `insertMessageEdit` — EXISTS in MessageStore class (line 54)
-- `upsertMessageForCapture` — EXISTS in MessageStore class
-- `updateMessageAsEdited` — EXISTS in MessageStore class
-- `updateMessageAsDeleted` — EXISTS in MessageStore class
-- `getMessagesByChannel` — EXISTS in MessageStore class
-- `updateMessageAIAnalysis` — EXISTS in MessageStore class
-- `updateMessagesAIAnalysisBulk` — EXISTS in MessageStore class
-- `getPendingAIAnalysisMessages` — EXISTS in MessageStore class
-- `getMessageById` — EXISTS in MessageStore class
-- `listMessages` — EXISTS in MessageStore class (delegates to MessagesPagination)
-- `listReviewMessages` — EXISTS in MessageStore class (delegates to MessagesPagination)
-- `getConversationContextBefore` — EXISTS in MessageStore class
-- `getPendingMessagesByConversation` — EXISTS in MessageStore class
-- `getPendingConversationKeys` — EXISTS in MessageStore class
-- `getConversationKeysWithIncompleteAnalysis` — EXISTS in MessageStore class
-- `getIncompleteMessagesByConversation` — EXISTS in MessageStore class
-
-So every function wrapper has a corresponding method on `MessageStore` class. The change is straightforward.
-
-Now, after creating the singleton `messageStore`, all importers just do `messageStore.updateMessagesAIAnalysisBulk(...)` instead of calling the bare function.
-
-But there's one complication: `MessagesDb.updateMessagesAIAnalysisBulk` is actually calling `this.analysis.updateMessagesAIAnalysisBulk()`. Does the `MessageStore` class have its own direct `updateMessagesAIAnalysisBulk`? Let me check the class definition...
-
-Actually, I already saw from the grep output that `MessageStore` class has `updateMessagesAIAnalysisBulk` — the wrapper says `getInstance().updateMessagesAIAnalysisBulk(updates)`, and the class has that method.
-
-OK so the mapping is 1:1 between wrapper functions and MessageStore class methods. This is safe.
-
-- [ ] **Step 5: Update `batchScheduler.ts`**
-
-```typescript
-// Before:
-import { getPendingMessagesByConversation } from "../message-capture/messageStore.js";
-// After:
-import { messageStore } from "../message-capture/messageStore.js";
-```
-And call: `messageStore.getPendingMessagesByConversation(...)`
-
-- [ ] **Step 6: Update `individualFallbackProcessor.ts`**
-
-```typescript
-// Before:
-import { updateMessagesAIAnalysisBulk } from "../message-capture/messageStore.js";
-// After:
-import { messageStore } from "../message-capture/messageStore.js";
-```
-And call: `messageStore.updateMessagesAIAnalysisBulk(...)`
-
-- [ ] **Step 7: Update `moderationBuilders.ts`**
-
-```typescript
-// Before:
-import { getMessageById } from "../message-capture/messageStore.js";
-// After:
-import { messageStore } from "../message-capture/messageStore.js";
-```
-And call: `messageStore.getMessageById(...)`
-
-- [ ] **Step 8: Update `aiAnalysisWorker.ts`**
-
-```typescript
-// Before:
-import { getConversationContextBefore, updateMessagesAIAnalysisBulk } from "../message-capture/messageStore.js";
-// After:
-import { messageStore } from "../message-capture/messageStore.js";
-```
-And update all call sites.
-
-- [ ] **Step 9: Update `aiAnalyzer.ts`**
-
-```typescript
-// Before:
-import {
-  getConversationKeysWithIncompleteAnalysis,
-  getIncompleteMessagesByConversation,
-  getMessageById,
-  getPendingConversationKeys,
-  updateMessageAIAnalysis,
-} from "../message-capture/messageStore.js";
-// After:
-import { messageStore } from "../message-capture/messageStore.js";
-```
-And update all call sites.
-
-- [ ] **Step 10: Update `message-capture/index.ts`**
-
-Remove individual function re-exports, replace with `messageStore`:
-
-```typescript
-export { messageStore } from "./messageStore.js";
-export {
-  getDisplayContent,
-  getMessageLocation,
-  getMessageMetadata,
-} from "./messageMetadata.js";
-export type {
-  AIRecommendedAction,
-  AISeverity,
-  AIStatus,
-  AttachmentRecord,
-  MessageRecord,
-  VoiceSegmentRecord,
-} from "./types.js";
-export type { TextCaptureTarget } from "./messageCapture.js";
-export {
-  captureMessage,
-  registerMessageCapture,
-  setEventBroadcaster,
-} from "./messageCapture.js";
-```
-
-- [ ] **Step 11: Run typecheck**
-
-```bash
-cd /home/code/GMW
-pnpm run typecheck
-```
-
-- [ ] **Step 12: Commit**
-
-```bash
-git add services/discord-gateway/src/modules/message-capture/
-git add services/discord-gateway/src/modules/ai-moderation/
-git commit -m "refactor: remove backward-compat function wrappers from messageStore"
-```
-
----
-
-### Task 3: Remove Dead Code
-
-**Files:**
-- Delete: `services/backend/src/modules/response.ts` — empty deprecated file
-- Delete: `services/discord-gateway/src/modules/webhook-notifications/webhookNotifier.ts`
-- Delete: `services/discord-gateway/src/modules/webhook-notifications/index.ts`
-- Delete: `services/discord-gateway/src/modules/webhook-notifications/` (directory)
-- Modify: `services/backend/src/ws/server.ts` — remove duplicate `broadcastBinaryToFrontend()` function, keep only `broadcastBinary()`
-
-**Interfaces:**
-- None — these are deletions only, no consumer impact
-
-- [ ] **Step 1: Delete `modules/response.ts`**
-
-```bash
-rm /home/code/GMW/services/backend/src/modules/response.ts
-```
-
-- [ ] **Step 2: Fix `ws/server.ts`** — remove duplicate `broadcastBinaryToFrontend`
-
-In `ws/server.ts`, `broadcastBinaryToFrontend` (line 238) and `broadcastBinary` (line 267) do exactly the same thing. Replace the `broadcastBinaryToFrontend(data)` call on line 147 with a call to `broadcastBinary(data)`, then delete the `broadcastBinaryToFrontend` function.
-
-Edit line 147:
-```typescript
-// Before:
-        broadcastBinaryToFrontend(data);
-// After:
-        broadcastBinary(data);
-```
-
-Remove the `broadcastBinaryToFrontend` function (lines 238-248):
-```typescript
-  // Remove this entire function:
-  function broadcastBinaryToFrontend(data: Buffer) {
-    for (const client of frontendClients) {
-      if (client.readyState === WebSocket.OPEN) {
-        try {
-          client.send(data);
-        } catch (err) {
-          logger.error({ err }, "Failed to send binary to frontend client");
-        }
-      }
-    }
-  }
-```
-
-- [ ] **Step 3: Check if anything imports `webhook-notifications`**
-
-```bash
-grep -rn "webhook-notifications\|webhookNotifier\|triggerWebhook" /home/code/GMW/services/ --include='*.ts' | grep -v "node_modules" | grep -v "services/discord-gateway/src/modules/webhook-notifications/"
-```
-
-Expected: empty (confirmed earlier)
-
-- [ ] **Step 4: Delete webhook-notifications module**
-
-```bash
-rm -rf /home/code/GMW/services/discord-gateway/src/modules/webhook-notifications/
-```
-
-- [ ] **Step 5: Run typecheck to verify no broken imports**
-
-```bash
-cd /home/code/GMW
-pnpm run typecheck
-```
-
-- [ ] **Step 6: Commit**
-
-```bash
-git add services/backend/src/modules/response.ts services/backend/src/ws/server.ts
-git add services/discord-gateway/src/modules/webhook-notifications/
-git commit -m "chore: remove dead code (response.ts, broadcastBinaryToFrontend, webhook-notifications)"
-```

docs/superpowers/plans/2026-07-27-services-refactoring.md

@@ -1,579 +0,0 @@
-# Services Refactoring Implementation Plan
-
-> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
-
-**Goal:** Refactor backend (4.2k lines) and discord-gateway (17.9k lines) for consistency, reduced file sizes, deduplication, and pattern uniformity across 11 phases.
-
-**Architecture:** Phase1-3 target backend unchanged; Phase4-8 split large gateway files; Phase9 deduplicates shared database init; Phase10-11 are minor consolidation. Each phase is independently testable by verifying the service still compiles and runs.
-
-**Tech Stack:** TypeScript (ESM), Express 5, ws, Discord.js selfbot, Drizzle ORM, Redis (ioredis), pino logger, Biome (formatter)
-
-## Global Constraints
-
-- All files use ESM (`.js` extensions in imports)
-- Biome formatter handles formatting — run `pnpm run format` after each phase
-- TypeScript strict mode — run `pnpm run typecheck` after each phase (for node services)
-- Logging uses `createChildLogger(context)` from `@bete/shared/logger`
-- Import via barrel files where available
-- No logic changes — pure refactoring
-
----
-
-## Task 1: Fix messages.controller.ts pattern (Phase 1)
-
-**Files:**
-- Modify: `services/backend/src/modules/messages/messages.controller.ts`
-
-**Interfaces:**
-- Consumes: `asyncHandler` from `../../shared/middlewares/index.js`
-- Produces: Same exported handler functions, but using decorator pattern
-
-- [ ] **Step 1: Read current messages.controller.ts**
-
-The file currently uses the convoluted pattern:
-```ts
-export function handleListMessages(req, res, next) {
-  return asyncHandler(async (req, res) => {
-    // ...
-  })(req, res, next);
-}
-```
-
-- [ ] **Step 2: Rewrite all handlers to decorator pattern**
-
-Replace every handler to use the clean decorator pattern:
-
-```ts
-import { createChildLogger } from "@bete/shared/logger";
-import type { Request, Response } from "express";
-import { asyncHandler } from "../../shared/middlewares/index.js";
-import { messageQuerySchema } from "./messages.schema.js";
-import { messagesService } from "./messages.service.js";
-
-const logger = createChildLogger("messages.controller");
-
-export const handleListMessages = asyncHandler(async (req: Request, res: Response) => {
-  const query = messageQuerySchema.parse(req.query);
-  logger.debug({ query }, "Handling list messages request");
-  const result = await messagesService.listMessages(query);
-  res.json(result);
-});
-
-export const handleGetMessagesByChannel = asyncHandler(async (req: Request, res: Response) => {
-  const channelId = String(req.params.channelId ?? "");
-  if (!channelId) {
-    res.status(400).json({ error: "MISSING_CHANNEL_ID" });
-    return;
-  }
-  const query = messageQuerySchema.parse(req.query);
-  logger.debug({ channelId, query }, "Handling get messages by channel");
-  const result = await messagesService.getMessagesByChannel(channelId, query);
-  res.json(result);
-});
-
-export const handleGetMessageById = asyncHandler(async (req: Request, res: Response) => {
-  const id = String(req.params.id ?? "");
-  if (!id) {
-    res.status(400).json({ error: "MISSING_ID" });
-    return;
-  }
-  logger.debug({ id }, "Handling get message by ID");
-  const result = await messagesService.getMessageById(id);
-  res.json(result);
-});
-
-export const handleGetImageMessages = asyncHandler(async (req: Request, res: Response) => {
-  const guildId = String(req.query.guildId ?? "");
-  if (!guildId) {
-    res.status(400).json({ error: "MISSING_GUILD_ID" });
-    return;
-  }
-  const limit = Number(req.query.limit) || 50;
-  logger.debug({ guildId, limit }, "Handling get image messages");
-  const result = await messagesService.getImageMessages(guildId, limit);
-  res.json(result);
-});
-
-export const handleGetAttachmentsByChannel = asyncHandler(async (req: Request, res: Response) => {
-  const channelId = String(req.params.channelId ?? "");
-  if (!channelId) {
-    res.status(400).json({ error: "MISSING_CHANNEL_ID" });
-    return;
-  }
-  const query = messageQuerySchema.parse(req.query);
-  logger.debug({ channelId, query }, "Handling get attachments by channel");
-  const result = await messagesService.getAttachmentsByChannel(channelId, query);
-  res.json(result);
-});
-```
-
-NOTE: The old pattern used `requireParam` from middlewares to validate params. The new pattern uses simple string checks with early returns. This is equivalent since `requireParam` threw `ValidationError` which the errorHandler middleware catches — but for these handlers the decorator pattern can't throw synchronously in the handler wrapper; the `asyncHandler` catches async rejects. Early return with explicit error response is cleaner.
-
-- [ ] **Step 3: Verify the module still compiles**
-
-Run: `cd /home/code/GMW && pnpm run typecheck`
-Expected: No TypeScript errors
-
-- [ ] **Step 4: Run biome format**
-
-Run: `cd /home/code/GMW && pnpm run format`
-
-- [ ] **Step 5: Commit**
-
-```bash
-git add services/backend/src/modules/messages/messages.controller.ts
-git commit -m "refactor(backend): fix messages.controller.ts to use decorator pattern
-
-Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>"
-```
-
----
-
-## Task 2: Clean up response.ts usage (Phase 2)
-
-**Files:**
-- Modify: `services/backend/src/modules/health/health.controller.ts` (remove `success()` usage, use plain `res.json()`)
-- Modify: `services/backend/src/modules/response.ts` (deprecate/remove)
-
-**Interfaces:**
-- Consumes: all response-producing route files
-- Produces: consistent plain `res.json()` pattern everywhere
-
-- [ ] **Step 1: Check all places that import from response.ts**
-
-Run: `grep -r 'from.*response\.js' services/backend/src/`
-
-- [ ] **Step 2: Remove `success()` usage from health.controller.ts**
-
-Replace:
-```ts
-import { success } from "../response.js";
-// ...
-res.status(status).json(success(result));
-```
-With:
-```ts
-res.status(status).json({ success: true, data: result });
-```
-
-- [ ] **Step 3: Run biome format + typecheck**
-
-Run: `cd /home/code/GMW && pnpm run format && pnpm run typecheck`
-
-- [ ] **Step 4: Commit**
-
-```bash
-git add services/backend/src/modules/health/health.controller.ts services/backend/src/modules/response.ts
-git commit -m "refactor(backend): remove response.ts helpers, inline health response
-
-Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>"
-```
-
----
-
-## Task 3: Add ws/ barrel (Phase 3)
-
-**Files:**
-- Create: `services/backend/src/ws/index.ts`
-
-- [ ] **Step 1: Create barrel file**
-
-```ts
-export { setBroadcastFunctions, clearBroadcastFunctions, broadcastEvent, broadcastBinary } from "./broadcast.js";
-export { startRedisBridge, stopRedisBridge } from "./redis-bridge.js";
-export { createWebSocketServer, closeWebSocketServer } from "./server.js";
-```
-
-- [ ] **Step 2: Run typecheck**
-
-Run: `cd /home/code/GMW && pnpm run typecheck`
-
-- [ ] **Step 3: Commit**
-
-```bash
-git add services/backend/src/ws/index.ts
-git commit -m "refactor(backend): add ws barrel index
-
-Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>"
-```
-
----
-
-## Task 4: Split moderationPrompt.ts (Phase 4)
-
-**Files:**
-- Create: `services/discord-gateway/src/modules/ai-moderation/prompts/text-analysis.ts`
-- Create: `services/discord-gateway/src/modules/ai-moderation/prompts/media-analysis.ts`
-- Create: `services/discord-gateway/src/modules/ai-moderation/prompts/stickers.ts`
-- Create: `services/discord-gateway/src/modules/ai-moderation/prompts/emojis.ts`
-- Create: `services/discord-gateway/src/modules/ai-moderation/prompts/system.ts`
-- Modify: `services/discord-gateway/src/modules/ai-moderation/moderationPrompt.ts` (become barrel re-export)
-
-- [ ] **Step 1: Read the full moderationPrompt.ts**
-
-Read the file to identify all exports and their dependencies.
-
-- [ ] **Step 2: Create `prompts/system.ts` — system prompt builder + shared helpers**
-
-Move: `buildSystemPrompt` function, `sanitizeAiContent`, `escapeXml`, `buildCustomEmojiVisionPrompt`, any shared helper functions.
-
-- [ ] **Step 3: Create `prompts/text-analysis.ts` — text moderation prompts**
-
-Move: All text-specific prompt strings and builders.
-
-- [ ] **Step 4: Create `prompts/media-analysis.ts` — image/video prompts**
-
-Move: `buildGeneralImageVisionPrompt` and related media prompt builders.
-
-- [ ] **Step 5: Create `prompts/stickers.ts` — sticker prompts**
-
-Move: `buildStickerVisionPrompt`, `buildStickerTextOnlyWarning`.
-
-- [ ] **Step 6: Create `prompts/emojis.ts` — emoji prompts**
-
-Move: `buildCustomEmojiVisionPrompt` if it exists separately.
-
-- [ ] **Step 7: Replace moderationPrompt.ts with barrel re-exports**
-
-```ts
-export { buildSystemPrompt, sanitizeAiContent } from "./prompts/system.js";
-export { buildGeneralImageVisionPrompt } from "./prompts/media-analysis.js";
-export { buildStickerVisionPrompt, buildStickerTextOnlyWarning } from "./prompts/stickers.js";
-export { buildCustomEmojiVisionPrompt } from "./prompts/emojis.js";
-```
-
-- [ ] **Step 8: Run typecheck**
-
-Run: `cd /home/code/GMW && pnpm run typecheck`
-Expected: No errors. Existing importers continue to work via the barrel.
-
-- [ ] **Step 9: Run biome format**
-
-Run: `cd /home/code/GMW && pnpm run format`
-
-- [ ] **Step 10: Commit**
-
-```bash
-git add services/discord-gateway/src/modules/ai-moderation/prompts/ services/discord-gateway/src/modules/ai-moderation/moderationPrompt.ts
-git commit -m "refactor(gateway): split moderationPrompt.ts into domain-specific prompt files
-
-Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>"
-```
-
----
-
-## Task 5: Split moderationOrchestrator.ts (Phase 5)
-
-**Files:**
-- Create: `services/discord-gateway/src/modules/ai-moderation/textBatchProcessor.ts`
-- Create: `services/discord-gateway/src/modules/ai-moderation/mediaBatchProcessor.ts`
-- Create: `services/discord-gateway/src/modules/ai-moderation/simpleFallback.ts`
-- Modify: `services/discord-gateway/src/modules/ai-moderation/moderationOrchestrator.ts` (extract & re-export)
-- Modify: `services/discord-gateway/src/modules/ai-moderation/index.ts` (update exports if needed)
-
-- [ ] **Step 1: Read full moderationOrchestrator.ts**
-
-Map all exports and dependencies.
-
-- [ ] **Step 2: Extract `runTextOnlyBatch` into `textBatchProcessor.ts`**
-
-Move the function and its helper `buildCorrectedFewShotExamples`. Export it.
-
-- [ ] **Step 3: Extract `runMediaBatch` into `mediaBatchProcessor.ts`**
-
-Move the function and all its dependencies. Export it.
-
-- [ ] **Step 4: Extract `runSimpleTextFallback` into `simpleFallback.ts`**
-
-Move the function. Export it.
-
-- [ ] **Step 5: Update moderationOrchestrator.ts**
-
-Replace extracted functions with imports:
-```ts
-export { runTextOnlyBatch } from "./textBatchProcessor.js";
-export { runMediaBatch } from "./mediaBatchProcessor.js";
-export { runSimpleTextFallback } from "./simpleFallback.js";
-```
-Keep the `runModerationAnalysis` entry point function which orchestrates text + media + caching.
-
-- [ ] **Step 6: Run typecheck**
-
-Run: `cd /home/code/GMW && pnpm run typecheck`
-
-- [ ] **Step 7: Run biome format**
-
-Run: `cd /home/code/GMW && pnpm run format`
-
-- [ ] **Step 8: Commit**
-
-```bash
-git add services/discord-gateway/src/modules/ai-moderation/textBatchProcessor.ts services/discord-gateway/src/modules/ai-moderation/mediaBatchProcessor.ts services/discord-gateway/src/modules/ai-moderation/simpleFallback.ts services/discord-gateway/src/modules/ai-moderation/moderationOrchestrator.ts
-git commit -m "refactor(gateway): split moderationOrchestrator into dedicated processors
-
-Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>"
-```
-
----
-
-## Task 6: Split mediaAnalysisClient.ts (Phase 6)
-
-**Files:**
-- Create: `services/discord-gateway/src/modules/ai-moderation/mediaCache.ts`
-- Create: `services/discord-gateway/src/modules/ai-moderation/mediaDownloader.ts`
-- Create: `services/discord-gateway/src/modules/ai-moderation/visionAnalyzer.ts`
-- Modify: `services/discord-gateway/src/modules/ai-moderation/mediaAnalysisClient.ts` (become barrel)
-
-- [ ] **Step 1: Read full mediaAnalysisClient.ts**
-
-Map all exports and dependencies across the 826 lines.
-
-- [ ] **Step 2: Extract all cache logic into `mediaCache.ts`**
-
-Move: LRU cache, phash dedup, `getCachedMediaAnalysis`, `setCachedMediaAnalysis`, `computeImagePhash`, `deleteCachedMediaAnalysis`, `acquireMediaAnalysisLock`.
-
-- [ ] **Step 3: Extract all download logic into `mediaDownloader.ts`**
-
-Move: Image download, video download, ffmpeg frame extraction, temporary file handling.
-
-- [ ] **Step 4: Extract vision LLM logic into `visionAnalyzer.ts`**
-
-Move: Vision LLM calls, message preparation for vision, `prepareMediaMessage`.
-
-- [ ] **Step 5: Update mediaAnalysisClient.ts to re-export**
-
-```ts
-export { getCachedMediaAnalysis, setCachedMediaAnalysis, computeImagePhash } from "./mediaCache.js";
-export { downloadAndExtractFrame } from "./mediaDownloader.js";
-export { prepareMediaMessage, hasMediaContent } from "./visionAnalyzer.js";
-```
-
-- [ ] **Step 6: Run typecheck**
-
-Run: `cd /home/code/GMW && pnpm run typecheck`
-
-- [ ] **Step 7: Run biome format**
-
-Run: `cd /home/code/GMW && pnpm run format`
-
-- [ ] **Step 8: Commit**
-
-```bash
-git add services/discord-gateway/src/modules/ai-moderation/mediaCache.ts services/discord-gateway/src/modules/ai-moderation/mediaDownloader.ts services/discord-gateway/src/modules/ai-moderation/visionAnalyzer.ts services/discord-gateway/src/modules/ai-moderation/mediaAnalysisClient.ts
-git commit -m "refactor(gateway): split mediaAnalysisClient into cache, downloader, and vision analyzer
-
-Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>"
-```
-
----
-
-## Task 7: Extract retention cleanup from bootstrap.ts (Phase 7)
-
-**Files:**
-- Create: `services/discord-gateway/src/app/retention.ts`
-- Modify: `services/discord-gateway/src/app/bootstrap.ts`
-
-- [ ] **Step 1: Create `app/retention.ts`**
-
-Move `deleteExpiredRecords` and `startRetentionCleanup` from `bootstrap.ts`:
-```ts
-import { createChildLogger } from "@bete/shared/logger";
-import { lt, inArray } from "drizzle-orm";
-import type { NodePgDatabase } from "drizzle-orm/node-postgres";
-import { config } from "../shared/config/config.js";
-import { getDatabase } from "../shared/database/drizzle.js";
-import * as schema from "../shared/database/schema.js";
-import { messagesTable, attachmentsTable, voiceRecordingsTable } from "../shared/database/schema.js";
-
-const log = createChildLogger("retention");
-
-// ... move deleteExpiredRecords here ...
-
-// ... move startRetentionCleanup here ...
-
-export { startRetentionCleanup };
-```
-
-- [ ] **Step 2: Remove inline retention code from bootstrap.ts**
-
-- Remove the `deleteExpiredRecords` function
-- Remove the `startRetentionCleanup` function
-- Add: `import { startRetentionCleanup } from "./retention.js";`
-- Replace the call: call `startRetentionCleanup()` directly
-
-- [ ] **Step 3: Run typecheck**
-
-Run: `cd /home/code/GMW && pnpm run typecheck`
-
-- [ ] **Step 4: Run biome format**
-
-Run: `cd /home/code/GMW && pnpm run format`
-
-- [ ] **Step 5: Commit**
-
-```bash
-git add services/discord-gateway/src/app/retention.ts services/discord-gateway/src/app/bootstrap.ts
-git commit -m "refactor(gateway): extract retention cleanup from bootstrap into dedicated module
-
-Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>"
-```
-
----
-
-## Task 8: Consolidate EventBroadcaster (Phase 8)
-
-**Files:**
-- Modify: `services/discord-gateway/src/modules/event-broadcaster/eventBroadcaster.ts`
-- Modify: `services/discord-gateway/src/modules/event-broadcaster/index.ts`
-
-- [ ] **Step 1: Read current eventBroadcaster.ts**
-
-Identify `RedisEventPublisher` and `EventBroadcaster` classes.
-
-- [ ] **Step 2: Merge RedisEventPublisher into EventBroadcaster**
-
-Inline `RedisEventPublisher` as a private detail inside `EventBroadcaster`. Keep the public API unchanged.
-
-- [ ] **Step 3: Update index.ts if needed**
-
-Ensure the barrel still exports `EventBroadcaster`.
-
-- [ ] **Step 4: Run typecheck**
-
-Run: `cd /home/code/GMW && pnpm run typecheck`
-
-- [ ] **Step 5: Run biome format**
-
-Run: `cd /home/code/GMW && pnpm run format`
-
-- [ ] **Step 6: Commit**
-
-```bash
-git add services/discord-gateway/src/modules/event-broadcaster/eventBroadcaster.ts services/discord-gateway/src/modules/event-broadcaster/index.ts
-git commit -m "refactor(gateway): merge RedisEventPublisher into EventBroadcaster
-
-Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>"
-```
-
----
-
-## Task 9: Cross-cutting database initialization dedup (Phase 9)
-
-**Files:**
-- Modify: `packages/shared/src/database/schema.ts` — add database lifecycle helpers
-- Modify: `services/backend/src/shared/database/index.ts` — use shared helpers
-- Modify: `services/discord-gateway/src/shared/database/drizzle.ts` — use shared helpers
-
-- [ ] **Step 1: Check current shared database setup**
-
-Read `packages/shared/` structure to see if there's already a database module.
-
-- [ ] **Step 2: Add pool creation helper in @bete/shared**
-
-In `packages/shared/src/database/schema.ts` or create `packages/shared/src/database/pool.ts`:
-
-```ts
-import { Pool } from "pg";
-
-export function createPostgresPool(url: string, opts?: { min?: number; max?: number }): Pool {
-  return new Pool({
-    connectionString: url,
-    min: opts?.min ?? 2,
-    max: opts?.max ?? 10,
-  });
-}
-
-export interface PoolConfig {
-  host?: string;
-  port?: number;
-  user?: string;
-  password?: string;
-  database?: string;
-  url?: string;
-  min?: number;
-  max?: number;
-}
-
-export function createPoolFromConfig(cfg: PoolConfig): Pool {
-  if (cfg.url) return createPostgresPool(cfg.url, { min: cfg.min, max: cfg.max });
-  return new Pool({
-    host: cfg.host,
-    port: cfg.port,
-    user: cfg.user,
-    password: cfg.password,
-    database: cfg.database,
-    min: cfg.min ?? 2,
-    max: cfg.max ?? 10,
-  });
-}
-```
-
-Export from `packages/shared/src/database/schema.ts` or create a barrel.
-
-- [ ] **Step 3: Update backend's shared/database/index.ts**
-
-Replace inline Pool creation with `createPoolFromConfig` from `@bete/shared`.
-
-- [ ] **Step 4: Update gateway's shared/database/drizzle.ts**
-
-Replace inline Pool creation with `createPoolFromConfig` from `@bete/shared`.
-
-- [ ] **Step 5: Run typecheck across all services**
-
-Run: `cd /home/code/GMW && pnpm run typecheck`
-
-- [ ] **Step 6: Run biome format**
-
-Run: `cd /home/code/GMW && pnpm run format`
-
-- [ ] **Step 7: Commit**
-
-```bash
-git add packages/shared/src/database/ services/backend/src/shared/database/index.ts services/discord-gateway/src/shared/database/drizzle.ts
-git commit -m "refactor: extract shared database pool creation into @bete/shared
-
-Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>"
-```
-
----
-
-## Task 10: Audit moderationState vs conversationState overlap (Phase 10)
-
-**Files:**
-- Read: `services/discord-gateway/src/modules/ai-moderation/moderationState.ts`
-- Read: `services/discord-gateway/src/modules/ai-moderation/conversationState.ts`
-
-- [ ] **Step 1: Read both files and identify overlap**
-
-Look for duplicated state management (maps, sets, timers).
-
-- [ ] **Step 2: If overlap found, merge into one file**
-
-Otherwise, just add comments documenting the boundary.
-
-- [ ] **Step 3: Commit**
-
-```bash
-git add services/discord-gateway/src/modules/ai-moderation/
-git commit -m "refactor(gateway): consolidate conversattion/moderation state management
-
-Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>"
-```
-
----
-
-## Task 11: Redis connection audit (Phase 11)
-
-**Files:**
-- Read: all Redis connection sites in gateway
-
-- [ ] **Step 1: Identify all Redis connections**
-
-Search for `new Redis(` patterns in gateway.
-
-- [ ] **Step 2: Verify each has a valid reason for a separate connection**
-
-Document with comments if needed.
-
-- [ ] **Step 3: Commit (if any changes made)**
-

docs/superpowers/specs/2026-07-27-cicd-overhaul-design.md

@@ -1,455 +0,0 @@
-# CI/CD Overhaul: Gitea CI + Container Registry Design
-
-**Status:** Draft
-**Last updated:** 2026-07-27
-
-## 1. Problem Statement
-
-The current CI/CD pipeline has multiple issues:
-
-1. **Split across 3 CI systems**: GitHub Actions (build + deploy), GitLab CI (build only, no deploy), and `deploy.sh` (hot-deploy bind-mounts)
-2. **Registry mismatch**: GitHub Actions pushes to `ghcr.io` but `docker-compose.yml` references `registry.gitlab.com` — the deploy route is unclear
-3. **Hot-deploy complexity**: `deploy.sh` builds locally, tars dist files, SSH pipes, and binds into containers at runtime. Fragile and not reproducible
-4. **No frontend in Docker**: Frontend is never built into an image — only hot-deployed via bind-mounts
-5. **Stale Dockerfile**: `Dockerfile.proxy` builds a Rust WASM frontend that no longer exists
-6. **Dockerfile.frontend is missing**: Frontend image doesn't exist at all
-7. **Shared package fragility**: The previous refactor added `@bete/shared/database/init` export, but Docker images built from `master` don't have it — containers crash
-
-## 2. Goal
-
-Single CI/CD pipeline that:
-
-- Builds Docker images for all 3 services (backend, discord-gateway, proxy-serving-frontend)
-- Pushes them to Gitea's built-in Container Registry
-- On the VPS, only pulls images and restarts containers — no more hot-deploy bind-mounts
-- All 3 services built in one pipeline, deployed together atomically
-
-## 3. Architecture
-
-```
-Developer pushes to main
-        │
-        ▼
-┌────────────────────────────┐
-│  Gitea Runner (server X)   │
-│                            │
-│  Job 1: build-and-push     │
-│  ├── bete-backend:latest   │──────────▶ Gitea Container Registry
-│  ├── bete-discord-gateway  │──────────▶ git.imrnes.team/MythEclipse/GMW/
-│  │     :latest             │              bete-backend:{sha,latest}
-│  └── bete-proxy:latest     │──────────▶ bete-discord-gateway:{sha,latest}
-│                            │──────────▶ bete-proxy:{sha,latest}
-│  Job 2: deploy (SSH)       │
-│  └─── SSH ke VPS ──────────┤
-└────────────────────────────┘
-        │
-        ▼
-┌────────────────────────────┐
-│  VPS Production            │
-│  /opt/imphenbot/infra/     │
-│  docker/                   │
-│                            │
-│  docker compose pull       │
-│  docker compose up -d      │
-│  docker image prune -f     │
-│                            │
-│  3 containers:             │
-│  ┌────────┐ ┌──────────┐   │
-│  │ proxy  │ │  backend │   │
-│  │  :80   │ │  :3000   │   │
-│  └───┬────┘ └──────────┘   │
-│      │    ┌─────────────┐  │
-│      └────┤discord-     │  │
-│           │gateway      │  │
-│           └─────────────┘  │
-└────────────────────────────┘
-```
-
-### 3.1 Service Images
-
-| Image | From | Runs |
-|-------|------|------|
-| `bete-backend` | `Dockerfile.backend` | Express HTTP/WS on port 3000 |
-| `bete-discord-gateway` | `Dockerfile.discord-gateway` | Discord client, internal only |
-| `bete-proxy` | `Dockerfile.proxy` (rewritten) | Nginx serving frontend + proxying `/api` and `/ws` to backend |
-
-### 3.2 Registry
-
-Gitea provides a built-in container registry per repository at:
-```
-git.imrnes.team/MythEclipse/GMW/<image-name>:<tag>
-```
-
-Images are tagged with both `latest` and the commit SHA for traceability.
-
-## 4. Files to Create / Modify
-
-### 4.1 Create: `.gitea/workflows/deploy.yml`
-
-One workflow, two jobs:
-
-```yaml
-name: Build & Deploy
-on:
-  push:
-    branches: [main]
-
-jobs:
-  build-and-push:
-    runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        service: [backend, discord-gateway, proxy]
-      max-parallel: 2
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          submodules: recursive
-      - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@v3
-      - name: Login to Gitea Registry
-        uses: docker/login-action@v3
-        with:
-          registry: ${{ vars.GITEA_REGISTRY }}
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITEA_REGISTRY_TOKEN }}
-      - name: Build & Push
-        uses: docker/build-push-action@v6
-        with:
-          context: .
-          file: infra/docker/Dockerfile.${{ matrix.service }}
-          push: true
-          tags: |
-            ${{ vars.GITEA_REGISTRY }}/${{ github.repository }}/bete-${{ matrix.service }}:${{ github.sha }}
-            ${{ vars.GITEA_REGISTRY }}/${{ github.repository }}/bete-${{ matrix.service }}:latest
-          cache-from: type=gha
-          cache-to: type=gha,mode=max
-
-  deploy:
-    runs-on: ubuntu-latest
-    needs: build-and-push
-    if: github.ref == 'refs/heads/main'
-    steps:
-      - name: SSH & Deploy
-        uses: appleboy/ssh-action@v1.2.5
-        with:
-          host: ${{ secrets.VPS_HOST }}
-          username: ${{ secrets.VPS_USER }}
-          key: ${{ secrets.VPS_SSH_KEY }}
-          script: |
-            cd /opt/imphenbot/infra/docker
-            echo "${{ secrets.ENV_FILE }}" > .env
-            docker compose pull
-            docker compose up -d --remove-orphans
-            docker image prune -f
-```
-
-Note: Gitea CI uses GitHub Actions-compatible syntax (Act Runner). The above uses the standard `actions/*` actions and `docker/*` actions that work with both GitHub and Gitea. If Gitea's runner doesn't fully support `docker/build-push-action`, fallback to inline `docker build` and `docker push` commands.
-
-Sensitive variables: `GITEA_REGISTRY_TOKEN`, `VPS_HOST`, `VPS_USER`, `VPS_SSH_KEY`, `ENV_FILE` set in Gitea repo Settings → Actions → Secrets. Non-sensitive: `GITEA_REGISTRY` as a Variable.
-
-### 4.2 Rewrite: `Dockerfile.proxy`
-
-Current proxy Dockerfile builds a Rust WASM frontend (stale — no longer exists in codebase). Replace with multi-stage build:
-
-```dockerfile
-# Stage 1: Build frontend (Next.js 16 static export)
-FROM node:22-slim AS frontend-builder
-
-WORKDIR /app
-
-# Install pnpm
-RUN corepack enable
-
-# Copy dependency manifests
-COPY pnpm-lock.yaml pnpm-workspace.yaml package.json ./
-COPY packages/shared/package.json ./packages/shared/package.json
-COPY services/frontend/package.json ./services/frontend/package.json
-
-# Install dependencies
-RUN pnpm install --frozen-lockfile --filter './services/frontend' --filter '@bete/shared'
-
-# Copy source code
-COPY packages/shared/ ./packages/shared/
-COPY services/frontend/ ./services/frontend/
-
-# Build Next.js static export
-RUN pnpm --filter frontend run build
-# Result in services/frontend/out/
-
-# Stage 2: Nginx
-FROM nginx:alpine
-
-# Nginx config
-COPY infra/docker/nginx/nginx.conf /etc/nginx/conf.d/default.conf
-
-# Static frontend files
-COPY --from=frontend-builder /app/services/frontend/out/ /usr/share/nginx/html/
-
-EXPOSE 80
-
-HEALTHCHECK --interval=30s --timeout=3s --start-period=10s --retries=3 \
-  CMD wget -qO- http://localhost:80/ || exit 1
-```
-
-### 4.3 Modify: `Dockerfile.backend`
-
-Add `VITE_BE_API_URL` and `VITE_BE_WS_URL` build args (already listed in GitHub Actions but not in Dockerfile):
-
-```dockerfile
-# Add to existing Dockerfile.backend — after FROM, before WORKDIR
-ARG VITE_BE_API_URL
-ARG VITE_BE_WS_URL
-ENV VITE_BE_API_URL=${VITE_BE_API_URL}
-ENV VITE_BE_WS_URL=${VITE_BE_WS_URL}
-```
-
-These build args are now consumed at build time for future-proofing even though they were previously only needed for frontend builds (which now lives in the proxy Dockerfile).
-
-### 4.4 Modify: `Dockerfile.discord-gateway`
-
-No structural changes needed — verify Drizzle migrations path:
-
-```dockerfile
-# COPY drizzle, line in existing Dockerfile.discord-gateway:
-COPY services/discord-gateway/drizzle/ ./services/discord-gateway/drizzle/
-# This should work as-is since workspace is copied at /app
-```
-
-### 4.5 Rewrite: `deploy.sh`
-
-From hot-deploy tar-pipe SSH to lightweight SSH exec:
-
-```bash
-#!/bin/bash
-set -euo pipefail
-
-SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
-INFRA_DIR="$SCRIPT_DIR/infra/docker"
-
-: "${VPS_HOST:?required}"
-: "${VPS_USER:?required}"
-: "${VPS_SSH_KEY:?required}"
-
-echo "=== Deploy to $VPS_HOST ==="
-
-# Copy .env if it exists locally
-if [ -f "$INFRA_DIR/.env" ]; then
-  scp -i "$VPS_SSH_KEY" "$INFRA_DIR/.env" "$VPS_USER@$VPS_HOST:/opt/imphenbot/infra/docker/.env"
-fi
-
-ssh -i "$VPS_SSH_KEY" "$VPS_USER@$VPS_HOST" << 'REMOTESCRIPT'
-  set -e
-  cd /opt/imphenbot/infra/docker
-  echo "=== Pulling images ==="
-  docker compose pull
-  echo "=== Restarting containers ==="
-  docker compose up -d --remove-orphans
-  echo "=== Cleaning up ==="
-  docker image prune -f
-  echo "=== Verify ==="
-  docker ps --filter "name=imphenbot" --format "table {{.Names}}\t{{.Image}}\t{{.Status}}"
-REMOTESCRIPT
-
-echo "=== Deploy complete ==="
-```
-
-### 4.6 Rewrite: `infra/docker/docker-compose.yml`
-
-Replace all GitLab registry image references with Gitea registry. Remove bind-mounts. Add recordings named volume.
-
-```yaml
-version: "3.8"
-
-services:
-  proxy:
-    image: ${GITEA_REGISTRY}/${GITEA_REPO}/bete-proxy:${IMAGE_TAG:-latest}
-    container_name: imphenbot-proxy
-    restart: unless-stopped
-    ports:
-      - "127.0.0.1:8080:80"
-    networks:
-      - app-shared-net
-    healthcheck:
-      test: wget -qO- http://localhost:80/ || exit 1
-      interval: 30s
-      timeout: 3s
-      start_period: 10s
-      retries: 3
-    deploy:
-      resources:
-        limits:
-          memory: 64M
-    labels:
-      traefik.enable: "true"
-      traefik.http.routers.imphenbot.rule: "Host(`imphnen.asepharyana.my.id`)"
-      traefik.http.routers.imphenbot.entrypoints: websecure
-      traefik.http.routers.imphenbot.tls: "true"
-      traefik.http.services.imphenbot.loadbalancer.server.port: "80"
-
-  backend:
-    image: ${GITEA_REGISTRY}/${GITEA_REPO}/bete-backend:${IMAGE_TAG:-latest}
-    container_name: imphenbot-backend
-    restart: unless-stopped
-    env_file:
-      - .env
-    environment:
-      NODE_ENV: production
-      WEBSERVER_PORT: 3000
-    networks:
-      - app-shared-net
-    healthcheck:
-      test: wget -qO- http://localhost:3000/api/health || exit 1
-      interval: 30s
-      timeout: 5s
-      start_period: 20s
-      retries: 3
-    deploy:
-      resources:
-        limits:
-          memory: 256M
-    depends_on:
-      - proxy
-
-  discord-gateway:
-    image: ${GITEA_REGISTRY}/${GITEA_REPO}/bete-discord-gateway:${IMAGE_TAG:-latest}
-    container_name: imphenbot-discord-gateway
-    restart: unless-stopped
-    env_file:
-      - .env
-    environment:
-      NODE_ENV: production
-    volumes:
-      - recordings:/app/recordings
-    networks:
-      - app-shared-net
-    healthcheck:
-      test: sh -c "kill -0 1"
-      interval: 30s
-      timeout: 5s
-      start_period: 20s
-      retries: 3
-    deploy:
-      resources:
-        limits:
-          memory: 512M
-
-volumes:
-  recordings:
-
-networks:
-  app-shared-net:
-    external: true
-```
-
-Key changes:
-- Image refs: `registry.gitlab.com/mytheclipse-group/gmw/...` → `${GITEA_REGISTRY}/${GITEA_REPO}/...`
-- **All bind-mounts removed** (`./backend-dist`, `./gateway-dist`, `./frontend-dist`, `./shared-dist`)
-- `recordings` → named volume (persists across container restarts/recreates)
-- `proxy` binds to `127.0.0.1:8080` instead of host port 80 (Traefik handles external routing)
-- Added `depends_on: proxy` to backend for startup ordering
-
-### 4.7 Remove: GitHub Actions & GitLab CI files
-
-After Gitea CI is verified working:
-- Delete `.github/workflows/deploy-docker.yml` (or rename to `.github/workflows/deploy-docker.yml.disabled`)
-- Delete `.gitlab-ci.yml` (or rename to `.gitlab-ci.yml.disabled`)
-
-### 4.8 Ensure: `.gitea/workflows/` directory
-
-The directory must exist in git. Some setups ignore `.gitea/` — verify `.gitignore` does not exclude it.
-
-## 5. Gitea Registry Integration
-
-### 5.1 Enable Container Registry in Gitea
-
-In Gitea Admin Settings:
-- Go to Settings → Repository → Enable "Container Registry"
-- Default registry URL format: `gitea.<domain>/<owner>/<repo>`
-
-### 5.2 Registry Token
-
-Create a Gitea access token with `read` and `write` access to packages:
-- Settings → Applications → Generate Token → `registry-token` → scope: `write:packages`
-
-### 5.3 CI Variables
-
-Set these in Gitea repo → Settings → Actions → Secrets:
-
-| Name | Example Value | Notes |
-|------|---------------|-------|
-| `GITEA_REGISTRY_TOKEN` | `gitea_token_abc123` | Docker login password |
-| `VPS_HOST` | `123.123.123.123` | VPS IP/hostname |
-| `VPS_USER` | `root` | SSH user |
-| `VPS_SSH_KEY` | `-----BEGIN OPENSSH PRIVATE KEY-----...` | Private key |
-| `ENV_FILE` | full .env content | Written to VPS before compose |
-
-As Variables (not secrets, visible but non-sensitive):
-
-| Name | Example Value | Notes |
-|------|---------------|-------|
-| `GITEA_REGISTRY` | `git.imrnes.team` | Registry hostname — no protocol prefix |
-
-### 5.4 VPS Setup (one-time)
-
-```bash
-# 1. Docker login to Gitea registry
-docker login git.imrnes.team
-# Use Gitea username + access token (with write:packages scope)
-
-# 2. Create recordings named volume
-docker volume create imphenbot_recordings
-
-# 3. Remove old bind-mount directories (after verifying old containers stopped)
-rm -rf /opt/imphenbot/infra/docker/backend-dist
-rm -rf /opt/imphenbot/infra/docker/gateway-dist
-rm -rf /opt/imphenbot/infra/docker/shared-dist
-rm -rf /opt/imphenbot/infra/docker/frontend-dist
-
-# 4. Ensure compose file is updated (via git pull)
-cd /opt/imphenbot && git pull origin main
-```
-
-## 6. Migration Plan
-
-### Phase 1: Prepare (this session)
-
-1. Write `.gitea/workflows/deploy.yml` 
-2. Rewrite `Dockerfile.proxy` for Next.js
-3. Modify `infra/docker/docker-compose.yml` for Gitea registry + named volumes
-4. Rewrite `deploy.sh` to SSH-only
-5. Mark old CI files as disabled (rename, not delete yet)
-6. Add VITE_BE_API_URL/VITE_BE_WS_URL build args to backend Dockerfile
-
-### Phase 2: VPS Preparation (one-time SSH)
-
-7. User runs `docker login` to Gitea registry on VPS
-8. User sets CI secrets in Gitea UI
-9. User creates `imphenbot_recordings` named volume
-
-### Phase 3: Deploy
-
-10. Commit and push to `main`
-11. Gitea CI triggers — builds 3 images, pushes to registry
-12. Deploy job SSHes into VPS, pulls images, restarts containers
-13. Verify with `docker ps` and health checks
-
-### Phase 4: Cleanup
-
-14. After all services running stably for 1-2 pushes: delete old CI files
-15. Remove old Dockerfiles if no longer referenced
-
-## 7. Rollback Plan
-
-If something goes wrong:
-
-1. **Quick rollback**: `docker compose up -d` with previous `IMAGE_TAG` (pin to last working SHA)
-2. **Full rollback**: Revert git changes, push to `main` — Gitea CI will rebuild with old config
-3. **Emergency**: SSH to VPS, use `docker compose` commands to restart specific containers
-
-## 8. Future Considerations
-
-- **Auto-deploy on tag**: Optionally trigger CI only on version tags (`v*`) instead of every `main` push
-- **Health check notifications**: Add webhook notification on deploy failure
-- **Multi-architecture builds**: Add `--platform linux/amd64,linux/arm64` for future ARM VPS migration
-- **Secrets management**: Consider HashiCorp Vault or Gitea's built-in encrypted secrets for larger teams

docs/superpowers/specs/2026-07-27-frontend-refactor-design.md

@@ -1,154 +0,0 @@
-# Frontend Refactor: Cleanup, API Alignment & Rebrand
-
-## Goal
-Refactor the frontend (`services/frontend/`) to be cleaner, more maintainable, properly aligned with backend API, and rebranded from "bete/GMW" to "Discord Automod" and from "chatbot" to "chatbot".
-
-## Scope
-
-### A. Code Quality & Structure
-1. **Extract inline page components** into dedicated files under `components/<feature>/`
-2. **Remove dead code** (`live-stats.tsx`, `useSearch`, `Item`, etc.)
-3. **Remove duplicate code** (merge `extractImage`/`extractFirstImage`, consolidate `WsHook` type, consolidate `isActive` functions)
-4. **Fix Tailwind v4 dynamic class** (`grid-cols-${columns}`) in `LoadingSkeleton`
-5. **Fix navigation icon** (Settings should use `Settings`, not `BarChart3`)
-
-### B. API Layer Separation
-- Split `voiceApi` into `voiceApi` + `mediaApi`
-- Keep `chatbot.ts` as is (frontend already uses "chatbot" naming)
-
-### C. Data Fetching Consistency
-- `GuildSelector` → use `useGuilds` + `useConfig` React Query hooks
-- `useVoiceChannels` → convert from manual `useState` to `useQuery`
-- Chatbot → convert to `useQuery` + `useMutation` (user approved this)
-
-### D. Rebrand
-- **bete/GMW → Discord Automod**: page title, sidebar, settings, comments
-- **chatbot → chatbot**: the frontend already uses "chatbot" naming for the component and API module; backend paths (`/api/chatbot/chat`) stay unchanged on frontend since they reference the actual backend path
-
-### E. Dead Code Removal
-- Remove `components/landing/` (including `live-stats.tsx`)
-- Remove `components/ui/item.tsx` (unused)
-- Remove `useSearch` from `use-messages.ts`
-- Remove unused shadcn/ui components (verified by grep)
-
-## Target Directory Structure
-
-```
-src/
-  app/(dashboard)/
-    messages/page.tsx        # slim → imports from components/messages/
-    dashboard/page.tsx       # slim
-    voice/page.tsx           # slim
-    media/page.tsx           # slim
-    recordings/page.tsx      # slim
-    analysis/page.tsx        # slim
-    settings/page.tsx        # slim
-    layout.tsx               # unchanged
-  app/layout.tsx             # update title
-  app/page.tsx               # unchanged (redirect)
-  
-  components/
-    messages/
-      message-card.tsx          # from inline in messages/page.tsx
-      message-detail-view.tsx   # from inline DetailView
-      ai-status-badge.tsx       # from inline AiStatusBadge
-      images-grid.tsx           # images tab content
-      review-list.tsx           # review tab content
-    dashboard/
-      stats-section.tsx
-      users-section.tsx
-      user-detail-section.tsx
-      channels-section.tsx
-      channel-detail-section.tsx
-    voice/
-      voice-connection-card.tsx
-      active-speakers-panel.tsx
-      microphone-card.tsx
-    media/
-      music-player.tsx
-    recordings/
-      recording-list.tsx
-    analysis/
-      search-panel.tsx
-    shared/                     # existing
-    layout/                     # existing
-    chatbot/                    # existing
-    ui/                         # shadcn — remove unused
-    
-  hooks/
-    use-messages.ts             # cleaned, use shared WsHook type
-    use-dashboard.ts
-    use-voice.ts                # cleaned
-    use-media.ts                # cleaned
-    use-recordings.ts           # cleaned
-    use-guilds.ts
-    use-config.ts
-    use-mobile.ts
-    index.ts
-    
-  lib/
-    ws-hook.ts                  # NEW: shared WsHook type
-    api/
-      client.ts
-      messages.ts
-      voice.ts                  # voice-only
-      media.ts                  # NEW: extracted from voiceApi
-      dashboard.ts
-      recordings.ts
-      config.ts
-      chatbot.ts
-      ui-state.ts
-      index.ts
-    types/                      # no structural changes, verify alignment
-    ws/                         # no structural changes
-    format.ts
-    navigation.ts
-    utils.ts
-```
-
-## Key Changes Detail
-
-### 1. Component Extraction
-Each page file that has inline components (messages=689 lines, dashboard=570 lines) will have those components extracted into dedicated files. The page file becomes a thin composition layer.
-
-### 2. WsHook Type Consolidation
-Three files define `type WsHook = { on: <E>(eventType: E, handler: ...) => () => void }`. This moves to `lib/ws-hook.ts` and all three hooks import it.
-
-### 3. LoadingSkeleton Fix
-Replace dynamic `grid-cols-${columns}` with explicit Tailwind classes or inline style:
-```tsx
-const gridCols = columns === 2 ? "grid-cols-1 md:grid-cols-2" : "grid-cols-1";
-```
-
-### 4. API Separation
-```typescript
-// lib/api/voice.ts — voice + guilds only
-export const voiceApi = {
-  getGuilds, getTextChannels, getVoiceChannels,
-  getStatus, connect, disconnect, sendCommand,
-};
-
-// lib/api/media.ts — media player only (NEW)
-export const mediaApi = {
-  getStatus, queue, skip, stop, volume,
-};
-```
-
-### 5. Data Fetching Consistency
-`GuildSelector` will use `useGuilds()` and `useConfig()` hooks instead of manual fetch in useEffect.
-`useVoiceChannels` will use `useQuery` with `enabled: !!guildId`.
-Chatbot will use `useQuery` for history and `useMutation` for send.
-
-### 6. Rebrand
-- `app/layout.tsx`: title → "Discord Automod"
-- Sidebar brand: keep "DC Automod" (already done)
-- Settings page: keep "DC Automod" reference
-- Comments referencing "bete" → update
-- No changes to package names or external references (backend still "bete" internally)
-
-### Non-Goals
-- No changes to backend API paths
-- No changes to package.json names (pnpm workspace naming)
-- No changes to Router/App Router structure
-- No changes to CSS/styling system
-- No functional changes — visual behavior identical

docs/superpowers/specs/2026-07-27-services-refactoring-design.md

@@ -1,134 +0,0 @@
-# Refactoring Backend & Discord-Gateway Services
-
-**Date:** 2026-07-27
-**Status:** Draft
-
-## Overview
-
-Comprehensive refactoring of `services/backend` (4.2k lines) and `services/discord-gateway` (17.9k lines) targeting code consistency, file-size reduction, deduplication, and pattern uniformity.
-
-## Scope
-
-### Phase 1 — Backend Controller Consistency
-
-**Problem:** Two competing controller patterns.
-
-- `messages.controller.ts`, `chatbot-chat.controller.ts` use convoluted `asyncHandler` inside function body (Gaya A)
-- `voice.controller.ts`, `health.controller.ts` use clean `asyncHandler` decorator (Gaya B)
-
-**Fix:** Convert all controllers to **Gaya B** (decorator pattern).
-
-Before (Gaya A):
-```ts
-export function handleListMessages(req, res, next) {
-  return asyncHandler(async (req, res) => {
-    // ...
-  })(req, res, next);
-}
-```
-
-After (Gaya B):
-```ts
-export const handleListMessages = asyncHandler(async (req, res) => {
-  // ...
-});
-```
-
-**Files affected:**
-- `modules/messages/messages.controller.ts`
-- `modules/chatbot-chat/chatbot-chat.controller.ts`
-
-### Phase 2 — Backend `response.ts` Cleanup
-
-**Problem:** `success()`/`error()` helpers exist but are unused (except health controller).
-
-**Fix:** Apply `success()` consistently to all API responses that are successful data returns. Remove `error()` if unused after audit.
-
-**Files affected:** All route/service files that `res.json()` data.
-
-### Phase 3 — Backend `ws/` Barrel
-
-**Problem:** `ws/broadcast.ts`, `ws/redis-bridge.ts`, `ws/server.ts` — no barrel.
-
-**Fix:** Add `ws/index.ts` barrel.
-
-### Phase 4 — Gateway: Split `moderationPrompt.ts` (1015 lines)
-
-**Problem:** Monolithic prompt file mixing all prompt types.
-
-**Fix:** Split into:
-- `prompts/text-analysis.ts` — Text moderation prompts
-- `prompts/media-analysis.ts` — Image/video analysis prompts
-- `prompts/stickers.ts` — Sticker analysis prompts
-- `prompts/emojis.ts` — Custom emoji prompts
-- `prompts/system.ts` — System prompt builder and shared helpers
-
-### Phase 5 — Gateway: Split `moderationOrchestrator.ts` (955 lines)
-
-**Problem:** Entry point that also contains inline text-only batch, media batch, and simple fallback.
-
-**Fix:** Extract into:
-- `textBatchProcessor.ts` — All text-only batching logic
-- `mediaBatchProcessor.ts` — All media batching logic
-- `simpleFallback.ts` — The `runSimpleTextFallback` function
-
-### Phase 6 — Gateway: Split `mediaAnalysisClient.ts` (826 lines)
-
-**Problem:** Cache logic (LRU + phash + DB), download logic (image/video + ffmpeg), and vision LLM in one file.
-
-**Fix:** Extract into:
-- `mediaCache.ts` — All caching layers (LRU, phash dedup, DB)
-- `mediaDownloader.ts` — Image/video download, ffmpeg frame extraction
-- `visionAnalyzer.ts` — Vision LLM orchestration
-
-### Phase 7 — Gateway: Consolidate `bootstrap.ts`
-
-**Problem:** 304-line bootstrap that embeds retention cleanup inline.
-
-**Fix:** Extract `startRetentionCleanup` into `app/retention.ts`. Leave event registrations in bootstrap as they're inherently app-wide wiring.
-
-### Phase 8 — Gateway: Simplify EventBroadcaster
-
-**Problem:** `RedisEventPublisher` wrapping is thin — only adds a `publish` wrapper.
-
-**Fix:** Merge `RedisEventPublisher` into `EventBroadcaster` as a private inner detail.
-
-### Phase 9 — Cross-cutting: Database initialization dedup
-
-**Problem:** Backend (`shared/database/index.ts`) and gateway (`shared/database/drizzle.ts`) have near-identical pool creation and lifecycle code.
-
-**Fix:** Extract common pool/drizzle lifecycle into `@bete/shared`:
-```ts
-// packages/shared/src/database/index.ts
-export function createDatabasePool(url: string, opts?: PoolOpts): Pool
-export function createDrizzleClient(pool: Pool): DrizzleClient
-export function closePool(pool: Pool): Promise<void>
-```
-Both services keep their own getDatabase/close wrappers but delegate pool creation to shared.
-
-### Phase 10 — Gateway: Consolidate `moderationState.ts` / `conversationState.ts`
-
-**Problem:** Two state files with overlapping concerns.
-
-**Fix:** Audit both for overlap, merge if significant duplication found.
-
-### Phase 11 — Gateway: Redis connection usage audit
-
-**Problem:** Multiple independent Redis connections for EventBroadcaster and CommandHandler.
-
-**Fix:** Both already need separate connections (Redis pub/sub limits). Document the pattern. No structural change.
-
-## Files Changed
-
-| Phase | Files | Type |
-|-------|-------|------|
-| 1 | 3 | edit |
-| 2 | ~15 | edit |
-| 3 | 1 | create |
-| 4 | ~6 | split |
-| 5 | ~4 | split |
-| 6 | ~4 | split |
-| 7 | 2 | split |
-| 8 | 2 | refactor |
-| 9 | 2 | refactor |
-| 10 | 1-2 | audit+merge |

docs/superpowers/specs/2026-07-27-visual-redesign.md

@@ -1,37 +0,0 @@
-# Visual Redesign: Discord Automod Dashboard
-
-## Design Direction
-
-**Vibe:** "Monitoring hub" — deep, technical, trustworthy. Think security operations center meets modern dev tool.
-
-## Palette
-
-**Dark (primary):**
-| Token | Value | Role |
-|-------|-------|------|
-| `--bg` | `oklch(0.09 0.015 245)` | Deeper navy canvas |
-| `--card` | `oklch(0.13 0.02 245)` | Surface with subtle separation |
-| `--primary` | `oklch(0.62 0.17 215)` | Teal-cyan accent (shift from sky blue) |
-| `--accent` | `oklch(0.7 0.18 260)` | Electric blue-purple for secondary highlights |
-| `--warn` | `oklch(0.7 0.17 75)` | Amber-gold for warnings (distinct from red) |
-| `--border` | `oklch(1 0 0 / 0.06)` | Softer borders |
-
-## Typography
-- Geist Sans (body) + Geist Mono (code/data) — already loaded
-- H1: `text-lg font-semibold tracking-tight`
-- Card titles: `text-sm font-semibold tracking-tight`
-- Labels/captions: `text-xs text-muted-foreground tracking-wide uppercase`
-
-## Layout Changes
-
-1. **Background**: Subtle dot-grid pattern (`radial-gradient(circle, oklch(1 0 0 / 0.03) 1px, transparent 1px)`) — monitoring station feel
-2. **Sidebar**: Slightly wider (w-64), active item gets a glow bar + subtle teal tint background, connection dot with breathing animation
-3. **Cards**: Hover state adds a thin teal border-top glow, softer shadow
-4. **Stat cards**: Gradient background per stat type (like live-stats had), with icon in colored bubble
-5. **Severity indicators**: Colored dot + label instead of just colored border
-6. **Mobile nav**: Tighter spacing, active indicator as dot above icon
-7. **Header**: Clean, thin bottom border glow, page title larger
-
-## Signature Element
-- **Grid background** + **teal glow** on active/interactive elements
-- **Gradient accent bar** on sidebar active item (wider, glowing)

docs/superpowers/specs/2026-07-28-discord-automod-redesign.md

@@ -1,508 +0,0 @@
----
-name: "Discord Automod — Neo Surveillance Redesign"
-version: "1.0.0"
-date: "2026-07-28"
-status: "approved"
-inspiration:
-  - "Summit Cloud Migration Platform (glassmorphic, dark premium)"
-  - "AeroNet Visualization (data panels, modular layout)"
-colors:
-  canvas: "oklch(0.07 0.015 250)"
-  surface: "oklch(0.11 0.02 245 / 0.6)"
-  surface-hover: "oklch(0.15 0.02 245 / 0.7)"
-  border: "oklch(1 0 0 / 0.06)"
-  border-glow: "oklch(0.62 0.17 215 / 0.3)"
-  primary: "oklch(0.62 0.17 215)"
-  primary-glow: "oklch(0.62 0.17 215 / 0.4)"
-  accent-purple: "oklch(0.65 0.2 280)"
-  accent-amber: "oklch(0.7 0.17 75)"
-  text-primary: "oklch(0.93 0.01 245)"
-  text-secondary: "oklch(0.55 0.02 245)"
-  text-mono: "oklch(0.62 0.17 215)"
-  glass-bg: "oklch(1 0 0 / 0.04)"
-  glass-border: "oklch(1 0 0 / 0.08)"
-  glass-shadow: "0 8px 32px oklch(0 0 0 / 0.4)"
-typography:
-  display: "Inter 28-48px weight 600"
-  body: "Inter 14-16px weight 400"
-  mono: "JetBrains Mono 11-13px weight 500-600"
-  data: "JetBrains Mono 24-36px weight 600, teal tint"
-radius:
-  card: "16px"
-  panel: "12px"
-  control: "8px"
-  pill: "9999px"
----
-
-# Discord Automod — Neo Surveillance Redesign
-
-Full frontend redesign for Discord Automod, a Discord moderation watcher dashboard. Complete rewrite of layout, design system, navigation, and page architecture.
-
----
-
-## 1. Design Philosophy
-
-**"Neo Surveillance"** — a Security Operations Center (SOC) inspired dashboard where monitoring feels immersive and powerful. Full-screen glass panels float over a dark animated canvas. No persistent sidebar clutter. The interface disappears into the background, letting live data and alerts take center stage.
-
-Key pillars:
-- **Immersion** — Full-viewport canvas with ambient motion, glass panels float over content
-- **Awareness** — Live data streams, real-time voice waveforms, animated moderation alerts
-- **Presence** — Live2D vtuber chatbot character as chatbot interface, reacts to server events
-
----
-
-## 2. Layout & Navigation System
-
-### 2.1 Global Structure
-
-```
-┌──────────────────────────────────────────────────────┐
-│  ● Discord Automod  Dashboard Msgs Voice …  🟢 ●  │  ← Floating Top Bar (~44px)
-├──────────────────────────────────────────────────────┤
-│  [Sub-navigation tabs] ← muncul per-page              │
-│━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━│
-│                                                        │
-│   ┌─────────┐  ┌──────────────┐                       │
-│   │  Glass   │  │   Content    │                       │
-│   │  Panels  │  │   Area       │                       │
-│   │          │  │   (scroll)   │                       │
-│   └─────────┘  └──────────────┘                       │
-│                                                        │
-├──────────────────────────────────────────────────────┤
-│ 🎵 [Mini-player] ← bottom-left        🎭 [Chatbot] ← BR │
-└──────────────────────────────────────────────────────┘
-```
-
-### 2.2 Floating Top Navigation Bar
-
-- **Style:** Glass (`backdrop-blur-xl`), subtle glow border bottom, `h-11` (44px)
-- **Left:** App logo "Discord Automod" with teal live dot indicator + current page name
-- **Center:** Horizontal nav links — Dashboard, Messages, Voice, Recordings, Settings
-  - Icon + label, active state with glow underline (`box-shadow` teal)
-  - Hover: text brighter, no background fill
-  - **Search** has no nav link — triggered globally via Cmd+K or `/` shortcut, opens spotlight
-- **Right:** Connection status dot (pulse when connected) + theme toggle (sun/moon icon)
-- **Hover sidebar hotspot:** Left edge 4px trigger → slide-in sidebar with guild selector, bookmarks, recent channels (auto-hide 300ms after mouse leave)
-
-### 2.3 Sub-navigation
-
-Each page has its own tab bar below the top nav, also glass-styled:
-- Dashboard: Stats | Live | Activity
-- Messages: All | Images | Review
-- Voice: Connection | Activity
-- Recordings: Library | Stats
-- Settings: Connection | Appearance | Config | About
-
-### 2.4 Hidden Sidebar (Hover-activated)
-
-- Trigger: 4px hotspot at left screen edge
-- Slide-in animation (150ms, ease-out-expo)
-- Contains: guild selector dropdown, bookmarked channels, recent activity shortcuts
-- Auto-hide on mouse leave with 300ms delay
-
-### 2.5 Floating Media Player
-
-- No dedicated Media page — persistent floating mini-player at bottom-left
-- Visible only when a track is active
-- Click to expand: full queue management overlay
-- Controls: play/pause, skip, stop, volume slider, progress bar
-
----
-
-## 3. Design Tokens
-
-### 3.1 Color Palette
-
-| Token | Value | Usage |
-|-------|-------|-------|
-| `--canvas` | `oklch(0.07 0.015 250)` | Deep navy background |
-| `--surface` | `oklch(0.11 0.02 245 / 0.6)` | Glass card base |
-| `--surface-hover` | `oklch(0.15 0.02 245 / 0.7)` | Card hover state |
-| `--border` | `oklch(1 0 0 / 0.06)` | Subtle border |
-| `--border-glow` | `oklch(0.62 0.17 215 / 0.3)` | Active card border glow |
-| `--primary` | `oklch(0.62 0.17 215)` | Teal-cyan accent, buttons |
-| `--primary-glow` | `oklch(0.62 0.17 215 / 0.4)` | Active state glow |
-| `--accent-purple` | `oklch(0.65 0.2 280)` | Moderation flagged items |
-| `--accent-amber` | `oklch(0.7 0.17 75)` | Warnings |
-| `--text-primary` | `oklch(0.93 0.01 245)` | Body text |
-| `--text-secondary` | `oklch(0.55 0.02 245)` | Secondary labels |
-| `--text-mono` | `oklch(0.62 0.17 215)` | Data metrics (teal tint) |
-| `--glass-bg` | `oklch(1 0 0 / 0.04)` | Glass base |
-| `--glass-border` | `oklch(1 0 0 / 0.08)` | Glass border |
-| `--glass-shadow` | `0 8px 32px oklch(0 0 0 / 0.4)` | Glass shadow |
-
-### 3.2 Typography
-
-| Role | Font | Size / Weight |
-|------|------|--------------|
-| Display | Inter | 28-48px, weight 600 |
-| Body | Inter | 14-16px, weight 400 |
-| Label / Mono | JetBrains Mono | 11-13px, weight 500-600 |
-| Data metrics | JetBrains Mono | 24-36px, weight 600, teal tint |
-
-### 3.3 Radius System
-
-| Token | Value |
-|-------|-------|
-| Card | 16px |
-| Panel | 12px |
-| Button / Control | 8px |
-| Pill | 9999px |
-
-### 3.4 Motion Tokens
-
-```css
---ease-out-expo: cubic-bezier(0.19, 1, 0.22, 1);
---ease-smooth: cubic-bezier(0.4, 0, 0.2, 1);
---duration-fast: 150ms;
---duration-normal: 250ms;
---duration-slow: 400ms;
-```
-
----
-
-## 4. Component System
-
-### 4.1 Glass Card System
-
-- **Base:** `glass-bg` + `glass-border` + border-radius `16px`
-- **Elevated:** Deeper shadow + subtle primary glow border
-- **Interactive:** Hover `scale(1.01)` + border glow intensify
-- **Danger:** Red-tinted border for critical items
-- Inner padding: `20px` (card), `16px` (panel), `12px` (dense)
-
-### 4.2 Button Variants
-
-| Variant | Style |
-|---------|-------|
-| Primary | `bg-primary` + `shadow-[0_0_12px] shadow-primary/40` (glow) |
-| Secondary | `glass-bg` + `border` |
-| Ghost | Transparent, hover → subtle glass bg |
-| Icon | Size 32px, rounded 8px |
-| Danger | Red-tinted variant for destructive actions |
-
-### 4.3 Status Indicators
-
-- **Live dot:** Pulsing ring animation (`pulse-ring` 1.5s)
-- **AI Badge:** Teal pill with sparkle icon, mono font
-- **Severity badges:** Clean (green), Warn (amber), Flagged (purple), Critical (red)
-- **Connection:** Green (connected), Yellow (connecting), Red (disconnected)
-
-### 4.4 Charts (Recharts)
-
-Custom theme matching design tokens:
-- Line/Area: gradient fill (primary → transparent)
-- Bar: rounded bars, teal-cyan gradient
-- Heatmap: activity by hour × weekday
-- Radar: multi-axis for moderation categories
-
-### 4.5 Live2D Chatbot / Chatbot
-
-- Replaces the existing `Chatbot` component entirely — chatbot panel is the new chat interface
-- **Location:** Floating panel, bottom-right corner, draggable
-- **Default size:** Compact — upper body visible (~200×280px)
-- **Click character:** Expand with full chat panel
-- **Dynamic expressions:**
-  - Idle: subtle breathing, blink every 4s
-  - New message: head tilt "listening"
-  - Flagged detected: eyes widen, ! bubble
-  - User click: happy wave
-  - Voice active: ear/head tilt toward audio
-  - Chat reply: mouth sync animation
-  - Disconnect: sad expression
-- **Technology:** Live2D Cubism SDK (WebGL via pixi.js wrapper), `.model3.json` + `.moc3` format
-- **Chat panel:** Glass-styled input + message history, context-aware (server context)
-
-### 4.6 Loading States
-
-- **Skeleton:** Glass card shape with shimmer gradient (teal → transparent → teal)
-- **Button loading:** Spinner within button
-- **Full page:** Glass skeleton grid matching target layout
-
----
-
-## 5. Page Layouts
-
-### 5.1 Dashboard — "Ops Center"
-
-Full-viewport command center:
-- **Stat cards row:** Total Messages, Today, Users, Active 24h, Flagged, Clean — each with micro sparkline chart (Recharts mini area) behind the number
-- **Live Message Stream:** Auto-scrolling glass panel showing recent messages, fade-in animation, click for detail
-- **Mod Queue:** Flagged messages with quick action buttons (approve/delete/escalate)
-- **Message Trend Chart:** 7-day area chart
-- **Activity Heatmap:** Hour × day-of-week, moderation event density
-- **Top Channels:** Bar chart with channel names
-- **Chatbot visible** floating bottom-right
-
-### 5.2 Messages — Split Pane
-
-- **Left pane:** Scrollable message list, glass cards with severity badge, channel tag, timestamp
-- **Right pane:** Detail/preview — full message content, attachments gallery, AI analysis breakdown (severity, flags, confidence, categories)
-- **Global search bar** in top area: spotlight-style overlay (Cmd+K)
-- **State in URL params:** `?guild=xxx&channel=yyy&selected=msg123&tab=all`
-- **Tabs:** All | Images (grid view) | Review (flagged queue)
-- **Actions:** Reanalyze, Moderate (dropdown: delete/warn/escalate)
-
-### 5.3 Voice — Connection Center
-
-- **Connection card:** Guild/channel selectors, status with live dot + duration
-- **Active Speakers:** Per-user waveform visualization (canvas-based, 100ms update)
-- **Microphone/Transmit:** Toggle mic, volume slider
-- **Voice Activity Timeline:** Bar chart showing who spoke and total duration
-- **Recordings quick link** to Recordings page
-
-### 5.4 Recordings — Voice Library
-
-- **Search + filter bar:** By user, channel, date range
-- **Recording cards:** Glass card, waveform preview (canvas), duration, timestamp
-- **Inline playback:** Play button, audio player without leaving page
-- **Actions:** Download, Copy Link
-
-### 5.5 Settings
-
-- **Sections:** Connection (WebSocket status, guild info), Appearance (theme toggle), Server Config (read-only), About
-- All glass cards, mono font for config values
-- Toggle switches with glass styling
-
----
-
-## 6. Animations & Micro-interactions
-
-### 6.1 Ambient Background
-- Gradient mesh with slow-shift (30s cycle)
-- 2-3 soft color blobs (teal, purple, amber), opacity 0.03-0.06
-- Grid dot pattern: `radial-gradient(circle, oklch(1 0 0 / 0.025) 1px, transparent 1px)`, 24px spacing
-
-### 6.2 Page Transitions
-- Route change: `fade-in-up` 200ms ease-out
-- Content section: `scale(0.98→1)` + `opacity(0.6→1)`
-
-### 6.3 Card Interactions
-- Hover: `scale(1.01)` + border glow intensify + shadow lift
-- Click: `scale(0.98)` brief (100ms)
-- Panel enter: `translateY(-4px)` + `opacity` fade-in
-- Stat counter: count-up animation (JS tween, 400ms)
-
-### 6.4 Live Data
-- Message stream: fade-in from top, slide down as new arrive
-- Voice waveform: real-time canvas draw, 100ms interval
-- Recording: pulsing dot + ring expansion (1.5s loop)
-- Connection: slow pulse when connected
-- Flagged: brief red/purple border flash on new flagged message
-
-### 6.5 Micro-interactions
-- Toggle: slide with glow
-- Scrollbar: custom thin (6px), auto-hide, rounded
-- Drag handle: subtle dot grip for split pane
-- Copy: brief "Copied!" toast
-- Reanalyze: 360° icon rotation
-
----
-
-## 7. Data Flow & State Management
-
-### 7.1 Architecture
-
-```
-WS Provider (auto-reconnect, typed events, event buffer)
-  ↓
-TanStack Query (fetches + cache)
-  ↓
-Query invalidation on WS events
-  ↓
-Optimistic cache updates for real-time data
-```
-
-### 7.2 WS → Cache Strategy
-
-| WS Event | Action |
-|----------|--------|
-| `message_created` | Optimistic insert to message list + dashboard stats |
-| `message_analyzed` | Update AI fields in message cache |
-| `message_deleted` | Remove from cache + update counters |
-| `voice_recording_started` | Update voice status |
-| `voice_pcm_data` | Buffer to waveform canvas (bypass React) |
-| `voice_active_user` | Update speakers cache |
-| `analysis_queue_status` | Update queue progress |
-
-### 7.3 Query Config
-
-- `staleTime: 10_000` (10s)
-- `gcTime: 5 * 60 * 1000` (5 min)
-- `refetchOnWindowFocus: false`
-
-### 7.4 Global State (React Context)
-
-- `useMediaPlayer()` — current track, queue, play/skip/stop/volume
-- `useChatbot()` — expression, minimized, chatHistory, setExpression
-  - Externally triggerable: `chatbot.setExpression("surprise")` on flagged message, `("listening")` on voice activity
-
-### 7.5 URL State
-
-Persistent page state via search params (not React state):
-```
-/messages?guild=xxx&channel=yyy&selected=msg123&tab=all
-```
-
-### 7.6 Error Boundaries
-
-Each page has its own error boundary. One page failure doesn't affect others.
-
----
-
-## 8. Technology Stack
-
-- **Framework:** Next.js 16 (App Router, static export)
-- **Language:** TypeScript strict
-- **Styling:** Tailwind v4 + CSS custom properties
-- **UI Base:** shadcn/ui components (adapted for glass theme)
-- **Icons:** lucide-react
-- **State/data:** @tanstack/react-query v5
-- **Charts:** Recharts 3.8 (with custom theme)
-- **3D/Chatbot:** Live2D Cubism SDK WebGL (pixi.js wrapper)
-- **Audio:** Web Audio API for waveform visualization
-- **Animation:** CSS animations + transitions (no GSAP/framer-motion dependency unless specifically needed)
-
----
-
-## 9. File Structure (New)
-
-```
-src/
-├── app/
-│   ├── layout.tsx                    # Root layout (fonts, theme script, Toaster)
-│   ├── page.tsx                      # Redirect → /dashboard
-│   ├── globals.css                   # Complete redesign CSS (tokens, glass, animations)
-│   └── (dashboard)/
-│       ├── layout.tsx                # Dashboard layout (top nav, QueryClient, WS, chatbot)
-│       ├── dashboard/
-│       │   └── page.tsx              # Ops Center
-│       ├── messages/
-│       │   └── page.tsx              # Split pane messages
-│       ├── voice/
-│       │   └── page.tsx              # Voice connection center
-│       ├── recordings/
-│       │   └── page.tsx              # Recording library
-│       └── settings/
-│           └── page.tsx              # Settings page
-│
-├── components/
-│   ├── layout/
-│   │   ├── top-nav.tsx               # Floating top navigation bar
-│   │   ├── sub-nav.tsx               # Per-page sub-navigation tabs
-│   │   ├── hidden-sidebar.tsx        # Hover-activated guild sidebar
-│   │   └── mobile-nav.tsx           # Mobile bottom nav (updated design)
-│   │
-│   ├── glass/
-│   │   ├── card.tsx                  # Glass card component (base, elevated, interactive)
-│   │   ├── panel.tsx                 # Glass panel wrapper
-│   │   └── divider.tsx              # Glass-styled separator
-│   │
-│   ├── dashboard/
-│   │   ├── stat-card.tsx             # Stat card with micro sparkline
-│   │   ├── live-stream.tsx           # Auto-scrolling message stream
-│   │   ├── mod-queue.tsx             # Moderation queue with quick actions
-│   │   ├── message-trend-chart.tsx   # 7-day area chart
-│   │   ├── activity-heatmap.tsx      # Hour × day heatmap
-│   │   └── top-channels-chart.tsx    # Top channels bar chart
-│   │
-│   ├── messages/
-│   │   ├── message-list.tsx          # Left pane — scrollable message list
-│   │   ├── message-card.tsx          # Individual message card (redesigned)
-│   │   ├── message-detail.tsx        # Right pane — full detail
-│   │   ├── attachments-grid.tsx      # Attachments gallery
-│   │   ├── ai-analysis-panel.tsx     # AI analysis breakdown
-│   │   └── search-overlay.tsx        # Cmd+K search spotlight
-│   │
-│   ├── voice/
-│   │   ├── connection-card.tsx       # Guild/channel selector + status
-│   │   ├── speaker-waveform.tsx      # Canvas waveform per speaker
-│   │   ├── mic-control.tsx           # Mic toggle + volume
-│   │   └── activity-timeline.tsx     # Voice activity bar chart
-│   │
-│   ├── recordings/
-│   │   ├── recording-card.tsx        # Glass card with waveform preview
-│   │   └── recording-player.tsx      # Inline audio player
-│   │
-│   ├── chatbot/
-│   │   ├── chatbot-container.tsx      # Floating L2D container
-│   │   ├── chatbot-canvas.tsx         # WebGL canvas for L2D rendering
-│   │   ├── chat-panel.tsx            # Chat input + history
-│   │   └── chatbot-context.tsx        # Context provider
-│   │
-│   ├── media/
-│   │   └── mini-player.tsx           # Floating mini media player
-│   │
-│   ├── shared/
-│   │   ├── error-state.tsx           # Error boundary fallback
-│   │   ├── loading-skeleton.tsx      # Glass shimmer skeleton
-│   │   └── empty-state.tsx           # Empty state illustration
-│   │
-│   └── ui/                           # shadcn/ui components (adapted to glass)
-│       ├── button.tsx, badge.tsx, dialog.tsx, ...
-│
-├── lib/
-│   ├── api/                          # Existing API client (unchanged)
-│   ├── ws/
-│   │   ├── context.tsx               # WS provider (unchanged)
-│   │   └── types.ts                  # WS event types
-│   ├── hooks/                        # Existing hooks + new ones
-│   │   ├── use-media-player.ts       # Global media state
-│   │   ├── use-chatbot.ts             # Chatbot context hook
-│   │   └── use-heatmap.ts           # Heatmap data hook
-│   ├── types/                        # Existing types (unchanged)
-│   ├── navigation.ts                 # Nav items (updated)
-│   └── format.ts                     # Format utilities
-```
-
----
-
-## 10. Implementation Order
-
-### Phase 1 — Foundation
-1. Update `globals.css` with new design tokens (colors, glass, radius, typography, animations)
-2. Rewrite root `layout.tsx` with theme system
-3. Build glass component system (`card.tsx`, `panel.tsx`)
-4. Build `top-nav.tsx`, `sub-nav.tsx`, `hidden-sidebar.tsx`
-5. Update dashboard layout with new nav
-
-### Phase 2 — Dashboard Ops Center
-6. Build `stat-card.tsx` with micro sparkline
-7. Build `live-stream.tsx`
-8. Build `mod-queue.tsx`
-9. Build charts: `message-trend-chart.tsx`, `activity-heatmap.tsx`, `top-channels-chart.tsx`
-10. Rewrite dashboard page
-
-### Phase 3 — Messages (Split Pane)
-11. Build `message-list.tsx`, `message-card.tsx` (redesigned)
-12. Build `message-detail.tsx`, `ai-analysis-panel.tsx`, `attachments-grid.tsx`
-13. Build `search-overlay.tsx`
-14. Rewrite messages page with split-pane layout
-
-### Phase 4 — Voice, Recordings, Settings
-15. Build voice components and rewrite voice page
-16. Build recording components and rewrite recordings page
-17. Rewrite settings page
-
-### Phase 5 — Floating Elements
-18. Build `mini-player.tsx` for media
-19. Build chatbot components (L2D integration)
-
----
-
-## 11. Testing
-
-- Visual regression checks per component
-- WS integration tests for cache updates
-- Responsive breakpoint testing (mobile bottom nav)
-- L2D chatbot load + expression trigger
-
----
-
-## 12. Non-Goals (Out of Scope)
-
-- Authentication — remains public
-- Backend API changes — only frontend redesign
-- Database changes — no schema modifications
-- New backend WebSocket events — reuse existing
-- L2D model creation — integration only (model file provided separately)

flake.nix

@@ -7,10 +7,32 @@
   };
 
   outputs = { self, nixpkgs, flake-utils }:
-    flake-utils.lib.eachDefaultSystem (system:
+    flake-utils.lib.eachSystem [ "x86_64-linux" ] (system:
       let
         pkgs = import nixpkgs { inherit system; };
 
+        # Source filter: `path:` literals do NOT respect .gitignore by default,
+        # so a dirty local out/ (stale chunks from previous builds) leaks into
+        # the sandbox. Filter out build artifacts explicitly.
+        filterSource = { dir, ignore }: builtins.path {
+          path = dir;
+          name = "source";
+          filter = (path: type: let base = baseNameOf path; in !(builtins.elem base ignore));
+        };
+        frontendSrc = filterSource {
+          dir = ./services/frontend;
+          ignore = [ "out" ".next" "node_modules" "pnpm-lock.yaml" ];
+        };
+
+        # OpenSSL headers (.dev output) + STATIC libs (pkgsStatic.openssl.out —
+        # node-datachannel's CMakeLists sets OPENSSL_USE_STATIC_LIBS=TRUE, and
+        # the default `pkgs.openssl` resolves to `bin` which has no lib/) merged
+        # into one tree so FindOpenSSL resolves both via OPENSSL_ROOT_DIR.
+        opensslDevEnv = pkgs.symlinkJoin {
+          name = "openssl-dev-env";
+          paths = [ pkgs.pkgsStatic.openssl.out pkgs.openssl.dev ];
+        };
+
         # ---- Shared build tools ----
         nodejs = pkgs.nodejs_22;
         pnpm = pkgs.pnpm.override { nodejs = nodejs; };
@@ -26,8 +48,8 @@
           export GIT_SSL_CAINFO=${pkgs.cacert}/etc/ssl/certs/ca-bundle.crt
           export NIX_SSL_CERT_FILE=${pkgs.cacert}/etc/ssl/certs/ca-bundle.crt
 
-          # pnpm uses node-gyp for native addons — provide build tools
-          export npm_config_build_from_source=true
+          # pnpm uses node-gyp for native addons — provide build tools (kept for
+          # the rare case a prebuilt is unavailable and it falls back to compile).
           export CPPFLAGS="-I${pkgs.lib.getDev pkgs.openssl}/include"
           export LDFLAGS="-L${pkgs.lib.getLib pkgs.openssl}/lib"
 
@@ -37,6 +59,36 @@
           pnpm rebuild 2>&1 || true
         '';
 
+        # Shrink the shipped node_modules to production deps only. The full
+        # install's .pnpm virtual store carries dev-only packages (biome,
+        # typescript, esbuild, drizzle-kit, vitest, ... ~150MB+) that are never
+        # needed at runtime, so we delete every .pnpm dir that is not part of
+        # the resolved production graph (`pnpm list --prod`).
+        #
+        # NOTE: do NOT use `pnpm install --prod` here — it collapses the
+        # public-hoist dir (.pnpm/node_modules) that runtime peer resolution
+        # relies on (e.g. @lng2004/node-datachannel and @seydx/node-av-linux-x64
+        # are only reachable through it), silently breaking voice.
+        # Instead we keep the full install's symlink layout and only prune
+        # orphaned package dirs + broken symlinks.
+        # Must run AFTER tsc (typescript is a devDep) and after native builds.
+        pruneProd = ''
+          echo "=== Pruning devDependencies (production-only node_modules) ==="
+          pnpm list --prod --depth 999 --parseable 2>/dev/null \
+            | grep -o '\.pnpm/[^/]*' | sort -u > $TMPDIR/prod-pnms.txt
+          ( cd node_modules/.pnpm \
+              && for d in */; do \
+                   d="''${d%/}"; \
+                   [ "$d" = "node_modules" ] && continue; \
+                   grep -qF ".pnpm/$d" $TMPDIR/prod-pnms.txt || rm -rf "$d"; \
+                 done ) || true
+          # Drop symlinks whose .pnpm target was pruned (top-level, scoped dirs,
+          # hoist, .bin — any depth). Mirrors stdenv's noBrokenSymlinks check,
+          # which would otherwise fail the fixupPhase.
+          find node_modules -type l ! -exec test -e {} \; -delete 2>/dev/null || true
+          du -sh node_modules
+        '';
+
         # ---- Backend ----
         backend = pkgs.stdenv.mkDerivation {
           pname = "gmw-backend";
@@ -49,33 +101,10 @@
           buildPhase = pnpmInstall + ''
             echo "=== Compiling TypeScript ==="
             npx tsc 2>&1
-            echo "=== Fixing @/ path aliases to relative paths ==="
-            node -e "
-              const fs = require('fs');
-              const path = require('path');
-              let count = 0;
-              function walk(dir) {
-                if (!fs.existsSync(dir)) return;
-                for (const e of fs.readdirSync(dir, {withFileTypes: true})) {
-                  const p = path.join(dir, e.name);
-                  if (e.isDirectory()) walk(p);
-                  else if (e.name.endsWith('.js')) {
-                    const c = fs.readFileSync(p, 'utf8');
-                    const pat = /from\s+['\"]@\/([^'\"]+)['\"]/g;
-                    const n = c.replace(pat, (m, p1) => {
-                      const target = path.join('dist', p1) + '.js';
-                      const rel = path.relative(path.dirname(p), target);
-                      return 'from \"' + (rel.startsWith('.') ? rel : './' + rel) + '\"';
-                    });
-                    if (n !== c) { fs.writeFileSync(p, n); count++; }
-                  }
-                }
-              }
-              walk('dist');
-              console.log('Fixed ' + count + ' files');
-            "
+            echo "=== Fixing @/ path aliases + extensionless relative imports for node ESM ==="
+            node scripts/fix-imports.mjs
             echo "=== Build complete ==="
-          '';
+          '' + pruneProd;
 
           installPhase = ''
             mkdir -p $out/lib/gmw-backend
@@ -84,7 +113,8 @@
             mkdir -p $out/bin
             cat > $out/bin/gmw-backend << WRAPPER
 #!${pkgs.runtimeShell}
-exec ${nodejs}/bin/node $out/lib/gmw-backend/dist/index.js
+cd $out/lib/gmw-backend
+exec ${nodejs}/bin/node dist/index.js
 WRAPPER
             chmod +x $out/bin/gmw-backend
           '';
@@ -104,43 +134,55 @@ WRAPPER
 
           nativeBuildInputs = [
             nodejs pnpm
-            pkgs.python3 pkgs.gnumake pkgs.gcc
+            pkgs.python3 pkgs.gnumake pkgs.gcc pkgs.cmake
             pkgs.rustc pkgs.cargo
             pkgs.pkg-config
             pkgs.openssl
+            pkgs.openssl.dev
+            pkgs.git # for any FetchContent-based deps during native builds
             pkgs.cacert
           ];
 
+          # Runtime tools for the voice pipeline: ffmpeg (mic transmit encode,
+          # music stream decode, segment muxing) and yt-dlp (YouTube/Spotify/
+          # search media resolution). Must be on PATH inside the wrapper below.
+          buildInputs = [ pkgs.ffmpeg-headless pkgs.yt-dlp ];
+
+          # cmake is only needed for node-datachannel's postinstall build —
+          # do NOT let stdenv run its own cmake configure phase on the source.
+          dontUseCmakeConfigure = true;
+
+          # The gateway bundles native node_modules (.node addons plus .o/.a
+          # object files left in prebuilt dirs). stdenv's fixupPhase walks
+          # $out/node_modules and runs patchELF + shrinkELF over every ELF it
+          # finds, choking on the non-ET_DYN files (.o/.a) and the prebuilt
+          # .node addons — emitting hundreds of harmless "patchelf: wrong ELF
+          # type" lines per build. The real binary is node (external, already
+          # RPATH-fixed in its own derivation) and the .node addons are
+          # self-contained prebuilts loaded via dlopen, so Nix's fixup pass is
+          # neither needed nor wanted here. Skip it entirely.
+          dontFixup = true;
+
           buildPhase = pnpmInstall + ''
-            echo "=== Compiling TypeScript ==="
+            echo "=== Building native voice deps ==="
+            # pnpm rebuild aborts on the first failing package and runs scripts
+            # from the wrong cwd — build each native dep explicitly with its own
+            # install script. Each failure is tolerated (|| true); the packages
+            # @discordjs/opus ships prebuilt binaries for Node 22 (ABI node-v127,
+            # linux-x64-glibc-2.35) — node-pre-gyp downloads the prebuilt .node
+            # instead of compiling C++ from source. With build_from_source unset
+            # (above), `pnpm rebuild` runs the package's own install script which
+            # fetches the matching prebuilt; it only falls back to a source build
+            # if the download fails. This keeps voice working without a per-build
+            # native compile.
+            echo "=== Rebuilding @discordjs/opus (prebuilt download) ==="
+            pnpm rebuild @discordjs/opus 2>&1 || true
+            echo "=== Compiling TypeScript ===="
             npx tsc 2>&1
-            echo "=== Fixing @/ path aliases to relative paths ==="
-            node -e "
-              const fs = require('fs');
-              const path = require('path');
-              let count = 0;
-              function walk(dir) {
-                if (!fs.existsSync(dir)) return;
-                for (const e of fs.readdirSync(dir, {withFileTypes: true})) {
-                  const p = path.join(dir, e.name);
-                  if (e.isDirectory()) walk(p);
-                  else if (e.name.endsWith('.js')) {
-                    const c = fs.readFileSync(p, 'utf8');
-                    const pat = /from\s+['\"]@\/([^'\"]+)['\"]/g;
-                    const n = c.replace(pat, (m, p1) => {
-                      const target = path.join('dist', p1) + '.js';
-                      const rel = path.relative(path.dirname(p), target);
-                      return 'from \"' + (rel.startsWith('.') ? rel : './' + rel) + '\"';
-                    });
-                    if (n !== c) { fs.writeFileSync(p, n); count++; }
-                  }
-                }
-              }
-              walk('dist');
-              console.log('Fixed ' + count + ' files');
-            "
+            echo "=== Fixing @/ path aliases + extensionless relative imports for node ESM ==="
+            node scripts/fix-imports.mjs
             echo "=== Build complete ==="
-          '';
+          '' + pruneProd;
 
           installPhase = ''
             mkdir -p $out/lib/gmw-discord-gateway
@@ -152,7 +194,9 @@ WRAPPER
             mkdir -p $out/bin
             cat > $out/bin/gmw-discord-gateway << WRAPPER
 #!${pkgs.runtimeShell}
-exec ${nodejs}/bin/node $out/lib/gmw-discord-gateway/dist/index.js
+cd $out/lib/gmw-discord-gateway
+export PATH=${pkgs.ffmpeg-headless}/bin:${pkgs.yt-dlp}/bin:\$PATH
+exec ${nodejs}/bin/node dist/index.js
 WRAPPER
             chmod +x $out/bin/gmw-discord-gateway
           '';
@@ -163,39 +207,57 @@ WRAPPER
           };
         };
 
-        # ---- Frontend (Next.js static export) ----
+        # ---- Frontend (Next.js SSR standalone) ----
         frontend = pkgs.stdenv.mkDerivation {
           pname = "gmw-frontend";
           version = "1.0.0";
 
-          src = ./services/frontend;
+          src = frontendSrc;
 
           nativeBuildInputs = [ nodejs pnpm pkgs.gnumake pkgs.gcc pkgs.cacert ];
 
           buildPhase = pnpmInstall + ''
-            echo "=== Building Next.js static export ==="
-            # Build args are provided as env vars
+            echo "=== Building Next.js SSR (standalone) ==="
             export NEXT_TELEMETRY_DISABLED=1
+            export GMW_BACKEND_URL=http://127.0.0.1:4001
             npx next build 2>&1
           '';
 
           installPhase = ''
-            mkdir -p $out/share/gmw-frontend
-            cp -r out $out/share/gmw-frontend/out 2>/dev/null || \
-            cp -r dist $out/share/gmw-frontend/dist 2>/dev/null || \
-            cp -r .next $out/share/gmw-frontend/.next 2>/dev/null || true
+            echo "=== Packaging standalone server ==="
+            mkdir -p $out/lib/gmw-frontend/standalone
+            # The standalone server bundles its own minimal node_modules but
+            # needs the build assets + public copied INSIDE its tree.
+            cp -r .next/standalone/. $out/lib/gmw-frontend/standalone/
+            mkdir -p $out/lib/gmw-frontend/standalone/.next
+            cp -r .next/static $out/lib/gmw-frontend/standalone/.next/static
+            cp -r public $out/lib/gmw-frontend/standalone/public 2>/dev/null || true
 
-            # Copy node_modules for standalone mode if it exists
-            cp -r node_modules $out/share/gmw-frontend/ 2>/dev/null || true
+            # Remove dangling symlinks left by pnpm's hoisted .pnpm layout
+            # (e.g. node_modules/.pnpm/node_modules/...). The standalone server
+            # never resolves those at runtime — it bundles its own node_modules
+            # — and they trip stdenv's noBrokenSymlinks check.
+            find $out/lib/gmw-frontend/standalone -type l \
+              ! -exec test -e {} \; -delete 2>/dev/null || true
+
+            mkdir -p $out/bin
+            cat > $out/bin/gmw-frontend << WRAPPER
+#!${pkgs.runtimeShell}
+cd $out/lib/gmw-frontend/standalone
+export PORT=''${GMW_FRONTEND_PORT:-4017}
+export HOSTNAME=127.0.0.1
+exec ${nodejs}/bin/node server.js
+WRAPPER
+            chmod +x $out/bin/gmw-frontend
           '';
 
           meta = {
-            description = "GMW Frontend — Next.js static dashboard";
+            description = "GMW Frontend — Next.js SSR dashboard";
             platforms = pkgs.lib.platforms.linux;
           };
         };
 
-        # ---- Proxy (nginx serving frontend) ----
+        # ---- Proxy (nginx: / -> Next SSR, /api + /ws -> backend) ----
         proxy = pkgs.stdenv.mkDerivation {
           pname = "gmw-proxy";
           version = "1.0.0";
@@ -210,11 +272,10 @@ WRAPPER
             mkdir -p $out/bin $out/etc $out/share
 
             # Substitute placeholders in nginx template
-            sed \
-              -e "s|@NGINX_MIME@|${pkgs.nginx}/conf/mime.types|g" \
-              -e "s|@FRONTEND_ROOT@|${frontend}/share/gmw-frontend/out|g" \
-              ${./infra/nix/nginx.conf.template} \
-              > $out/etc/nginx.conf
+            sed -e "s|@NGINX_MIME@|${pkgs.nginx}/conf/mime.types|g" \
+                -e "s|@NEXT_PORT@|4017|g" \
+                ${./infra/nix/nginx.conf.template} \
+                > $out/etc/nginx.conf
 
             cat > $out/bin/gmw-proxy << WRAPPER
 #!${pkgs.runtimeShell}
@@ -224,7 +285,7 @@ WRAPPER
           '';
 
           meta = {
-            description = "GMW Proxy — nginx serving frontend";
+            description = "GMW Proxy — nginx -> Next.js + backend";
             platforms = pkgs.lib.platforms.linux;
           };
         };

infra/docker/Dockerfile.backend

@@ -33,9 +33,9 @@ COPY --from=builder --chown=node:node /build/node_modules ./node_modules
 COPY --from=builder --chown=node:node /build/package.json ./
 
 USER node
-EXPOSE 3000
+EXPOSE 4001
 
 HEALTHCHECK --interval=30s --timeout=10s --start-period=15s --retries=3 \
-  CMD node -e "require('http').get('http://localhost:3000/api/health',r=>process.exit(r.statusCode===200?0:1))"
+  CMD node -e "require('http').get('http://localhost:4001/api/health',r=>process.exit(r.statusCode===200?0:1))"
 
 CMD ["node", "dist/index.js"]

infra/docker/docker-compose.yml

@@ -33,9 +33,9 @@ services:
       - .env
     environment:
       NODE_ENV: production
-      WEBSERVER_PORT: 3000
+      WEBSERVER_PORT: 4001
     healthcheck:
-      test: ["CMD", "wget", "-qO-", "http://localhost:3000/api/health"]
+      test: ["CMD", "wget", "-qO-", "http://localhost:4001/api/health"]
       interval: 30s
       timeout: 10s
       start_period: 15s

infra/nix/nginx.conf.template

@@ -11,24 +11,44 @@ http {
     ''      close;
   }
 
+  # Next.js standalone SSR server (backend-fetching on every render).
+  # Not for hand-editing: @NEXT_PORT@ is substituted at build time.
+  upstream gmw_next {
+    server 127.0.0.1:@NEXT_PORT@;
+    keepalive 16;
+  }
+
+  upstream gmw_backend {
+    server 127.0.0.1:4001;
+    keepalive 16;
+  }
+
   server {
-    listen 127.0.0.1:8080;
+    listen 4009;
     server_name _;
 
+    # Use relative redirects (Location: /dashboard/) instead of absolute
+    # URLs that leak the internal listen port (4009) through the reverse proxy.
+    absolute_redirect off;
+
     gzip on;
     gzip_types text/plain text/css application/json application/javascript application/wasm image/svg+xml;
     gzip_min_length 256;
 
+    # ── Backend REST ───────────────────────────────────────────────
     location ^~ /api {
-      proxy_pass http://127.0.0.1:3001$uri$is_args$args;
+      proxy_pass http://gmw_backend$uri$is_args$args;
+      proxy_http_version 1.1;
+      proxy_set_header Connection "";   # keepalive to backend
       proxy_set_header Host              $host;
       proxy_set_header X-Real-IP         $remote_addr;
       proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
       proxy_set_header X-Forwarded-Proto $scheme;
     }
 
+    # ── Backend WebSocket (realtime shared state + voice PCM) ──────
     location ^~ /ws {
-      proxy_pass http://127.0.0.1:3001$uri$is_args$args;
+      proxy_pass http://gmw_backend$uri$is_args$args;
       proxy_http_version 1.1;
       proxy_set_header Upgrade              $http_upgrade;
       proxy_set_header Connection           $connection_upgrade;
@@ -41,16 +61,49 @@ http {
       proxy_send_timeout 86400s;
     }
 
-    location /assets/ {
-      root @FRONTEND_ROOT@;
+    # ── Backend oRPC (structured data RPCs over WebSocket + HTTP POST)
+    #     Browser reaches this via partysocket (wss://…/trpc); SSR/RSC uses
+    #     the fetch RPCLink (POST /trpc). Same path, same backend handler:
+    #     oRPC's RPCHandler (HTTP) + ORPCWebSocketServer (WS) on :4001. ──
+    location ^~ /trpc {
+      proxy_pass http://gmw_backend$uri$is_args$args;
+      proxy_http_version 1.1;
+      # Upgrade headers required for the WebSocket transport; harmless for POST.
+      proxy_set_header Upgrade              $http_upgrade;
+      proxy_set_header Connection           $connection_upgrade;
+      proxy_set_header Host                 $host;
+      proxy_set_header X-Real-IP            $remote_addr;
+      proxy_set_header X-Forwarded-For      $proxy_add_x_forwarded_for;
+      proxy_set_header X-Forwarded-Proto    $scheme;
+      proxy_buffering off;
+      proxy_read_timeout 86400s;
+      proxy_send_timeout 86400s;
+    }
+
+    # ── Next.js build assets — immutable, edge/shareable ───────────
+    location ^~ /_next/static/ {
+      proxy_pass http://gmw_next$uri$is_args$args;
+      proxy_http_version 1.1;
+      proxy_set_header Host              $host;
+      proxy_set_header X-Real-IP         $remote_addr;
+      proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
+      proxy_set_header X-Forwarded-Proto $scheme;
       expires 1y;
       add_header Cache-Control "public, immutable";
     }
 
+    # ── Everything else → Next.js server (SSR) ──
     location / {
-      root @FRONTEND_ROOT@;
-      index index.html;
-      try_files $uri $uri/ /index.html;
+      proxy_pass http://gmw_next$uri$is_args$args;
+      proxy_http_version 1.1;
+      proxy_set_header Connection "";
+      proxy_set_header Host              $host;
+      proxy_set_header X-Real-IP         $remote_addr;
+      proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
+      proxy_set_header X-Forwarded-Proto $scheme;
+      proxy_set_header X-Next-Prefetch  $http_x_next_prefetch;
+      proxy_buffering off;
+      proxy_read_timeout 30s;
     }
   }
-}
+}

scripts/add-ai-analysis-duration.sql

@@ -0,0 +1,10 @@
+-- Migration: add ai_analysis_duration_ms to messages
+-- Tracks how long the AI moderation LLM call took, per message (ms).
+-- Idempotent: safe to re-run.
+--
+-- Run against the production GMW database, e.g.:
+--   PGPASSWORD=*** psql -h 100.121.180.82 -p 6432 -U asephs -d dcbot \
+--     -f scripts/add-ai-analysis-duration.sql
+
+ALTER TABLE "messages"
+  ADD COLUMN IF NOT EXISTS "ai_analysis_duration_ms" BIGINT;

scripts/drop-materi-documents.sql

@@ -0,0 +1,14 @@
+-- Migration: Drop materi_documents table (feature removed)
+-- Run: PGPASSWORD=<pw> psql -h <host> -U <user> -d <db> -f scripts/drop-materi-documents.sql
+-- Reverses scripts/add-materi-documents.sql which was deleted with the feature.
+
+BEGIN;
+
+DROP INDEX IF EXISTS idx_materi_search;
+DROP INDEX IF EXISTS idx_materi_guild;
+DROP INDEX IF EXISTS idx_materi_owner;
+DROP INDEX IF EXISTS idx_materi_category;
+
+DROP TABLE IF EXISTS public.materi_documents;
+
+COMMIT;

scripts/fix-missing-tables.sql

@@ -1,5 +1,5 @@
 -- Fix: missing messages and attachments tables on VPS
--- Run: PGPASSWORD=hunterz psql -h 100.108.1.124 -U asephs -d hub -f scripts/fix-missing-tables.sql
+-- Run: PGPASSWORD=hunterz psql -h 100.121.180.82 -U asephs -d hub -f scripts/fix-missing-tables.sql
 
 BEGIN;
 

services/backend/ARCHITECTURE.md

@@ -225,21 +225,21 @@ All config via environment variables (`.env`), validated with Zod in `shared/con
 
 ```env
 # Server
-WEBSERVER_PORT=3001
+WEBSERVER_PORT=4001
 NODE_ENV=development
 LOG_LEVEL=info
 
 # Database
-DATABASE_URL=postgresql://user:pass@localhost:5432/discord_moderation
+DATABASE_URL=postgresql://asephs:***@100.121.180.82:6432/discord_moderation
 # OR
-DATABASE_HOST=localhost
-DATABASE_PORT=5432
+DATABASE_HOST=100.121.180.82
+DATABASE_PORT=6432
 DATABASE_NAME=discord_moderation
 DATABASE_USER=postgres
 DATABASE_PASSWORD=secret
 
 # Redis (optional, for pub/sub)
-REDIS_URL=redis://localhost:6379
+REDIS_URL=redis://100.121.180.82:6379
 
 # Discord
 MONITOR_GUILD_ID=123456789
@@ -263,7 +263,7 @@ Use Vitest with mocked database and services.
 2. **Implement repository queries** for each module using Drizzle ORM
 3. **Add WebSocket server** in `src/ws/server.ts` with Redis pub/sub listener
 4. **Create Discord Gateway service** in `services/discord-gateway/` (separate microservice)
-5. **Add Docker & CI/CD** for multi-service deployment
+5. **Add Nix & CI/CD** for multi-service deployment (flake.nix + GitHub Actions → nix copy → systemd)
 6. **Write integration tests** for full request flow
 
 ## Circular Dependency Check

services/backend/package.json

@@ -15,6 +15,7 @@
   },
   "dependencies": {
     "@discordjs/voice": "^0.19.2",
+    "@orpc/server": "1.15.0",
     "axios": "^1.16.1",
     "dotenv": "^17.4.2",
     "drizzle-orm": "^0.45.2",
@@ -31,10 +32,10 @@
     "@biomejs/biome": "latest",
     "@types/express": "^5.0.6",
     "@types/node": "^25.9.0",
+    "@types/pg": "^8.20.0",
     "@types/ws": "^8.18.1",
     "tsx": "^4.22.2",
     "typescript": "^5.9.3",
-    "@types/pg": "^8.20.0",
     "vitest": "latest"
   }
 }

services/backend/scripts/fix-imports.mjs

@@ -0,0 +1,58 @@
+// Rewrite import specifiers in the compiled dist/ so the output runs under
+// plain `node dist/index.js` (native ESM, no bundler / no tsx).
+//
+// Background: tsconfig uses moduleResolution:"bundler", so `tsc` emits BARE
+// relative specifiers WITHOUT extensions (e.g. `import "./router"`) and leaves
+// the `@/*` path-alias imports untouched. Node's native ESM resolver rejects
+// extensionless relative specifiers and knows nothing about the `@/` alias, so
+// the emitted dist/ crashes at startup (`ERR_MODULE_NOT_FOUND`). This script
+// fixes both:
+//   1. `@/foo`            -> relative path to dist/foo.js
+//   2. `./foo` / `../foo` -> `./foo.js` / `../foo.js` (append .js)
+// Already-extensioned relative imports (.js/.json/.node/.mjs/.cjs) and bare
+// package specifiers are left untouched (idempotent).
+import { readFileSync, writeFileSync, existsSync, readdirSync } from "node:fs";
+import { join, relative, dirname } from "node:path";
+
+let count = 0;
+function walk(dir) {
+  if (!existsSync(dir)) return;
+  for (const e of readdirSync(dir, { withFileTypes: true })) {
+    const p = join(dir, e.name);
+    if (e.isDirectory()) walk(p);
+    else if (e.name.endsWith(".js")) {
+      const c = readFileSync(p, "utf8");
+      const pat = /from\s+['"]([^'"]+)['"]/g;
+      const n = c.replace(pat, (m, spec) => {
+        if (spec.startsWith("@/")) {
+          // Source may already carry an extension (e.g. "@/shared/config/index.js");
+          // only append ".js" when the specifier has none — otherwise we'd
+          // produce "index.js.js".
+          const core = spec.slice(2);
+          let target;
+          if (/\.(js|json|node|mjs|cjs)$/.test(core)) {
+            target = join("dist", core);
+          } else {
+            target = join("dist", core) + ".js";
+          }
+          let rel = relative(dirname(p), target);
+          if (!rel.startsWith(".")) rel = "./" + rel;
+          return `from "${rel}"`;
+        }
+        if (
+          (spec.startsWith("./") || spec.startsWith("../")) &&
+          !/\.(js|json|node|mjs|cjs)$/.test(spec)
+        ) {
+          return `from "${spec}.js"`;
+        }
+        return m;
+      });
+      if (n !== c) {
+        writeFileSync(p, n);
+        count++;
+      }
+    }
+  }
+}
+walk("dist");
+console.log(`Fixed ${count} import specifiers in dist/`);

services/backend/src/e2e.test.ts

@@ -1,10 +1,10 @@
 /**
  * E2E API tests — runs against a running backend instance.
- * Usage: API_BASE=http://localhost:3001 vitest run
+ * Usage: API_BASE=http://localhost:4001 vitest run
  */
 import { describe, expect, it } from "vitest";
 
-const BASE = process.env.API_BASE ?? "http://localhost:3001/api";
+const BASE = process.env.API_BASE ?? "http://localhost:4001/api";
 
 async function api(path: string, init?: RequestInit) {
   const res = await fetch(`${BASE}${path}`, {

services/backend/src/http/app.ts

@@ -1,4 +1,5 @@
-import { createChildLogger } from "@/shared/logger/index";
+import { onError } from "@orpc/server";
+import { RPCHandler } from "@orpc/server/node";
 import express, {
   type Express,
   type NextFunction,
@@ -6,19 +7,18 @@ import express, {
   type Response,
 } from "express";
 import helmet from "helmet";
-import { createAnalysisRouter } from "../modules/analysis/index.js";
-import { createConfigRouter } from "../modules/config/index.js";
-import { createDashboardRouter } from "../modules/dashboard/index.js";
+import { createChildLogger } from "@/shared/logger/index";
 import { createHealthRouter } from "../modules/health/index.js";
-import { createChatbotRouter } from "../modules/chatbot/index.js";
-import { createMediaRouter } from "../modules/media/index.js";
-import { createMessagesRouter } from "../modules/messages/index.js";
-import { createRecordingsRouter } from "../modules/recordings/index.js";
-import { createUiStateRouter } from "../modules/ui-state/index.js";
-import { createVoiceRouter } from "../modules/voice/index.js";
+import { appRouter } from "../orpc/router";
 import { errorHandler } from "../shared/middlewares/index.js";
 
-// Auth removed — dashboard is public
+// Auth removed — dashboard is public.
+// All data APIs (dashboard, messages, moderation, media, voice, recordings,
+// analysis, chatbot, config, ui-state) now flow over oRPC, served on TWO
+// transports sharing the /trpc path:
+//   - WebSocket (browser live RPCs)  — see orpc/ws.ts
+//   - HTTP POST   (server-side / RSC fetch) — handled below
+// Only infra endpoints (health, prometheus metrics) remain plain HTTP.
 
 const logger = createChildLogger("http.app");
 
@@ -32,7 +32,7 @@ export function createHttpApp(): Express {
     }),
   );
 
-  // Body parsing
+  // Body parsing (still needed for any JSON POST; oRPC is WS/HTTP-based)
   app.use(express.json());
   app.use(express.urlencoded({ extended: true }));
 
@@ -58,23 +58,38 @@ export function createHttpApp(): Express {
     next();
   });
 
-  // All routes are public
+  // Infra-only HTTP endpoints
   app.use("/api", createHealthRouter());
-  app.use("/api", createConfigRouter());
-  app.use("/api", createDashboardRouter());
-  app.use("/api", createMessagesRouter());
-  app.use("/api", createAnalysisRouter());
-  app.use("/api", createChatbotRouter());
-  app.use("/api", createRecordingsRouter());
-  app.use("/api", createUiStateRouter());
-  app.use("/api", createMediaRouter());
-  app.use("/api", createVoiceRouter());
+
+  // oRPC over HTTP (server-side / RSC fetch). The same appRouter the browser
+  // reaches over the /trpc WebSocket. oRPC's node RPCHandler writes the full
+  // response itself; if no procedure matched we fall through to the 404 below.
+  const orpcHandler = new RPCHandler(appRouter, {
+    interceptors: [onError((error) => logger.error({ error }, "oRPC error"))],
+  });
+
+  app.use((req: Request, res: Response, next: NextFunction) => {
+    if (!req.path.startsWith("/trpc")) {
+      next();
+      return;
+    }
+    orpcHandler
+      .handle(req, res, { prefix: "/trpc", context: {} })
+      .then(({ matched }) => {
+        if (!matched) next();
+      })
+      .catch((err: unknown) => {
+        logger.error({ err }, "oRPC HTTP handler failed");
+        if (!res.headersSent) res.status(500).json({ error: "INTERNAL" });
+      });
+  });
 
   // 404 handler
   app.use((_req: Request, res: Response) => {
     res.status(404).json({
       error: "NOT_FOUND",
-      message: "Endpoint not found",
+      message:
+        "Endpoint not found — data APIs are served over /trpc (WebSocket/HTTP)",
     });
   });
 

services/backend/src/http/server.ts

@@ -1,5 +1,6 @@
 import { createServer, type Server } from "node:http";
 import { createChildLogger } from "@/shared/logger/index";
+import { createORPCWebSocketServer } from "../orpc/ws.js";
 import { config } from "../shared/config/index.js";
 import { initializeDatabase } from "../shared/database/index.js";
 import { startRedisBridge } from "../ws/redis-bridge.js";
@@ -16,8 +17,9 @@ export async function startHttpServer(): Promise<Server> {
 
   const server = createServer(app);
 
-  // Attach WebSocket server to the same HTTP server
-  createWebSocketServer(server);
+  // Attach WebSocket servers to the same HTTP server
+  createWebSocketServer(server); // /ws — voice PCM + gateway events
+  createORPCWebSocketServer(server); // /trpc — structured data RPCs
 
   // Start Redis pub/sub bridge to forward discord-gateway events to WS clients
   await startRedisBridge();

services/backend/src/index.ts

@@ -24,6 +24,15 @@ async function main() {
 async function shutdown(signal: string) {
   logger.info({ signal }, "Shutting down gracefully");
 
+  // Failsafe: graceful shutdown must never hang the process forever.
+  // httpServer.close() waits for ALL open connections (including lingering
+  // WebSocket/keep-alive sockets), so on a stuck connection the process would
+  // otherwise sit zombie and systemd (Restart=always) can never revive it.
+  const forceExitTimer = setTimeout(() => {
+    logger.error({ signal }, "Graceful shutdown timed out; forcing exit");
+    process.exit(1);
+  }, 10_000);
+
   try {
     // 1. Stop accepting new HTTP connections
     if (httpServer) {
@@ -54,9 +63,11 @@ async function shutdown(signal: string) {
     );
 
     logger.info("Graceful shutdown completed");
+    clearTimeout(forceExitTimer);
     process.exit(0);
   } catch (err) {
     logger.error({ err }, "Error during graceful shutdown");
+    clearTimeout(forceExitTimer);
     process.exit(1);
   }
 }

services/backend/src/modules/analysis/analysis.repository.ts

@@ -1,7 +1,7 @@
-import { pgMessagesTable } from "../../shared/index.js";
-import { createChildLogger } from "../../shared/logger/index.js";
 import { and, desc, eq, ilike, type SQL } from "drizzle-orm";
 import { getDatabase } from "../../shared/database/index.js";
+import { pgMessagesTable } from "../../shared/index.js";
+import { createChildLogger } from "../../shared/logger/index.js";
 import {
   type MappedMessage,
   mapMessageRow,

services/backend/src/modules/analysis/analysis.routes.ts

@@ -1,27 +0,0 @@
-import { createChildLogger } from "@/shared/logger/index";
-import type { Request, Response, Router } from "express";
-import express from "express";
-import { asyncHandler } from "../../shared/middlewares/index.js";
-import { analysisService } from "./analysis.service.js";
-
-const logger = createChildLogger("analysis.routes");
-
-export function createAnalysisRouter(): Router {
-  const router = express.Router();
-
-  // GET /api/analysis/search
-  router.get(
-    "/analysis/search",
-    asyncHandler(async (req: Request, res: Response) => {
-      const q = (req.query.q as string) || "";
-      const channelId = (req.query.channelId as string) || undefined;
-      const limit = Number(req.query.limit) || 20;
-
-      logger.debug({ q, channelId, limit }, "Analysis search requested");
-      const result = await analysisService.search({ q, channelId, limit });
-      res.json(result);
-    }),
-  );
-
-  return router;
-}

services/backend/src/modules/analysis/index.ts

@@ -1 +0,0 @@
-export { createAnalysisRouter } from "./analysis.routes.js";

services/backend/src/modules/chatbot/chatbot.controller.ts

@@ -1,84 +0,0 @@
-import { createChildLogger } from "@/shared/logger/index";
-import type { Request, Response } from "express";
-import { asyncHandler } from "../../shared/middlewares/index.js";
-import { chatbotService } from "./chatbot.service.js";
-
-const logger = createChildLogger("chatbot.controller");
-
-interface AuthenticatedRequest extends Request {
-  userId?: string;
-}
-
-export const handleChatbotChat = asyncHandler(
-  async (req: Request, res: Response) => {
-    const { message, context } = req.body as {
-      message: string;
-      context?: Record<string, unknown>;
-    };
-
-    // Validate required fields
-    if (!message || typeof message !== "string") {
-      return res.status(400).json({
-        error: "INVALID_INPUT",
-        message: "Message is required and must be a string",
-      });
-    }
-
-    // Get user ID from auth middleware (if available)
-    const userId = (req as AuthenticatedRequest).userId || "anonymous";
-
-    logger.debug(
-      { userId, messageLength: message.length, context },
-      "Received chatbot chat message",
-    );
-
-    // Process message & generate response
-    const response = await chatbotService.processMessage(
-      message,
-      context,
-      userId,
-    );
-
-    // Save conversation to database
-    await chatbotService.saveConversation({
-      userId,
-      userMessage: message,
-      botResponse: response,
-      context,
-      timestamp: new Date(),
-    });
-
-    logger.info({ userId }, "Chatbot chat processed successfully");
-
-    res.status(200).json({
-      response,
-      timestamp: new Date().toISOString(),
-    });
-  },
-);
-
-export const getChatbotHistory = asyncHandler(
-  async (req: Request, res: Response) => {
-    const userId = (req as AuthenticatedRequest).userId || "anonymous";
-    const limit = Math.min(parseInt(req.query.limit as string, 10) || 50, 100);
-
-    const history = await chatbotService.getChatHistory(userId, limit);
-
-    res.status(200).json({
-      history,
-      total: history.length,
-    });
-  },
-);
-
-export const clearChatbotHistory = asyncHandler(
-  async (req: Request, res: Response) => {
-    const userId = (req as AuthenticatedRequest).userId || "anonymous";
-
-    await chatbotService.clearChatHistory(userId);
-
-    res.status(200).json({
-      message: "Chat history cleared successfully",
-    });
-  },
-);