feat(web): self-contained local test mode for the dashboard

[karaktaka]

Summary

• Adds docker compose -f docker-compose.test.yml up as a zero-dependency way to run the full dashboard UI with synthetic data — no Discord bot, Valkey, or real guild data required
• VITE_TEST_MODE=true (build arg) bakes a mock API interceptor into the frontend bundle; tree-shaken from normal production builds
• NERPYBOT_TEST_MODE=true (runtime env) enables a GET /auth/test-login endpoint and makes /auth/me return a synthetic operator user, bypassing Discord OAuth and Valkey entirely
• Four test guilds cover all major dashboard scenarios: full-featured guild, minimal guild, bot-not-present (Add to Server), and support-mode (operator read-only view with PII redacted)
• Support-mode guild applies the same [redacted] PII masking as the real backend (_redact() in guilds.py), and all write operations return 403 — same as production behaviour

Test plan

• docker compose -f docker-compose.test.yml up --build starts cleanly, no external services needed
• Navigate to http://localhost:8080 → Login page shows "Test Login" button
• Click Test Login → redirected to dashboard with test guilds in the sidebar
• Nerdcraft Central — all tabs populated (moderator roles, reminders, reaction roles, applications with submissions, WoW guild news + crafting board)
• Quiet Corner — most tabs show correct empty states; language set to DE
• Cool Guild — appears in "Add to Server" section on Server Overview
• External Server — support mode banner visible (amber); all tabs show data with PII fields replaced by [redacted]; any save/edit attempt returns an error
• Sidebar shows amber "Test mode — synthetic data" strip when expanded
• Normal production build (npm run build) contains no references to test guild IDs (tree-shaken)

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features

  • Test mode for the app, including a "Test Login" option and a visible "Test mode — synthetic data" banner.
  • Frontend can operate with comprehensive synthetic data and a mock API to exercise UI flows without external services.

• Chores

  • Added a containerized test compose configuration and build-time toggle to run the app in test mode.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds an opt-in "test mode" across frontend and backend: build flag and compose file, fake Valkey client, test-user authentication endpoint and dependency branches, frontend request interception with in-memory fixtures/resolver, UI test login/indicator, and many synthetic frontend fixtures for three test guilds.

Changes

Cohort / File(s)	Summary
Docker & Compose Dockerfile, docker-compose.test.yml	Adds VITE_TEST_MODE build arg/env and new docker-compose.test.yml to run the web service in test mode with test env vars and port mapping.
Backend init & auth web/app.py, web/routes/auth.py	Creates fake ValkeyClient when test mode enabled; adds /auth/test-login JWT endpoint and short-circuits /me for synthetic test operator.
Backend dependencies & access checks web/dependencies.py	Introduces test-mode flags and constants; bypasses operator/premium checks for the test user and adds support-mode branches in require_guild_access.
Frontend API client web/frontend/src/api/client.ts	Lazily loads @/dev in test mode; when isTestRequest(path) true, short-circuits network fetches to return resolver-provided mocked responses.
Frontend test harness web/frontend/src/dev/index.ts, web/frontend/src/dev/resolver.ts, web/frontend/src/dev/fixtures.ts	Adds test-mode entrypoint, a large set of synthetic fixtures (~600 lines), and a route-driven in-memory resolver with read/write semantics and support-mode redaction (resolveTestRequest).
Frontend UI web/frontend/src/views/LoginView.vue, web/frontend/src/views/guild/GuildDetailView.vue, web/frontend/src/dev/TestModeIndicator.vue	Adds test login button/handler, conditionally renders a test-mode indicator in guild sidebar, and adjusts permission computation for support mode.

Sequence Diagram(s)

sequenceDiagram
    participant Browser as User/Browser
    participant Client as Frontend API Client
    participant DevModule as "@/dev" (index/resolver/fixtures)
    participant Resolver as Test Resolver
    participant Backend as Real API / Valkey

    Browser->>Client: Send API request (method, path, body)
    Client->>Client: Check VITE_TEST_MODE
    alt VITE_TEST_MODE == "true"
        Client->>DevModule: Lazy-import "@/dev"
        Client->>DevModule: isTestRequest(path)?
        alt isTestRequest == true
            Client->>Resolver: resolveTestRequest(method,path,body)
            Resolver->>Resolver: Read/modify in-memory fixtures (supportMode/redaction)
            Resolver-->>Client: { data, supportMode }
            Client-->>Browser: Return mocked response
        else
            Client->>Backend: Perform real fetch (Authorization included)
            Backend-->>Client: Real response
            Client-->>Browser: Return real response
        end
    else
        Client->>Backend: Perform real fetch
        Backend-->>Client: Real response
        Client-->>Browser: Return real response
    end

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• feat: add web dashboard REST API (Phase 1) #283: Earlier test-mode foundations touching VITE_TEST_MODE, Valkey/client initialization, and dependencies — strong overlap with this PR's Valkey/test-mode logic.
• feat(web): operator monitoring dashboard — Phase 3 #317: Modifies require_guild_access and related auth branches; directly related to the test/support-mode changes here.
• feat(web): web dashboard Phase 2 — full CRUD, UI polish, and shared component refactors #312: Overlaps frontend auth and client request handling changes (LoginView, client.ts) that this PR extends for test mode.

Suggested labels

review

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 62.50% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly and clearly describes the main change: adding self-contained local test mode for the dashboard with synthetic data.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/test-mode

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@web/dependencies.py`:
- Line 17: _CURRENT: _TEST_MODE is set via
bool(os.environ.get("NERPYBOT_TEST_MODE")) which treats any non-empty string
(including "false" or "0") as True; change the logic that sets _TEST_MODE to
parse the string value explicitly (e.g., normalize to lower-case and check
membership in a set of truthy values like {"1","true","yes","y","on"} or use a
utility like distutils.util.strtobool) so that "false", "0", empty or unset
values produce False; update the assignment for the _TEST_MODE constant to use
this explicit parsing approach.

In `@web/frontend/src/dev/resolver.ts`:
- Around line 585-602: The mock resolver branch that handles
"/application-submissions" incorrectly redacts decision_reason by calling
ni(s.decision_reason); update the mapping in the block (the map callback that
spreads s and transforms fields) to stop applying ni to decision_reason and
return it as-is (preserve nullable string), i.e., remove the ni(...) call for
decision_reason so the frontend mock matches backend _submission_to_schema
behavior.

In `@web/routes/auth.py`:
- Around line 24-53: Add the missing support-mode guild to the _TEST_GUILDS
list: insert a GuildSummary entry with id "999000000000000003", name matching
the other test entries (e.g., "Support Guild" or consistent naming), icon=None,
permission_level="admin", bot_present=True, and invite_url=None so the backend
fixture matches the frontend and the permission system (update the _TEST_GUILDS
definition where GuildSummary entries are declared).

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: d0ea2cff-6acb-44a0-b451-6cfd25302ea4

📥 Commits

Reviewing files that changed from the base of the PR and between 86b9832 and 546def9.

📒 Files selected for processing (12)

• Dockerfile
• docker-compose.test.yml
• web/app.py
• web/dependencies.py
• web/frontend/src/api/client.ts
• web/frontend/src/dev/TestModeIndicator.vue
• web/frontend/src/dev/fixtures.ts
• web/frontend/src/dev/index.ts
• web/frontend/src/dev/resolver.ts
• web/frontend/src/views/LoginView.vue
• web/frontend/src/views/guild/GuildDetailView.vue
• web/routes/auth.py