bridge: Request — Phase 11E scope clarification (GitBook knowledge base)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

docs/code-bridge/requests/REQ-2026-04-12-phase11e-gitbook-scope.md

@@ -0,0 +1,23 @@
+# Architectural Request
+
+**Date:** 2026-04-12
+**Topic:** Phase 11E scope — what does the GitBook knowledge base need?
+
+## 1. Current State
+Phases 11A–11D complete. Phase 11E is "GitBook knowledge base migration" but the spec doesn't detail what content is needed or where GitBook is hosted.
+
+## 2. Questions for Chronicler
+
+1. **Is there an existing GitBook instance?** If so, what's the URL and how does Code push content to it? (API? Git repo? Manual paste?)
+2. **Or is this Markdown docs that get uploaded to GitBook later?** If so, Code can write the docs as Markdown files in the repo and Chronicler handles the GitBook publishing.
+3. **What pages are needed?** Suggested structure:
+   - Getting Started (installation, activation)
+   - Configuration (CurseForge API key, egg variables, file detection)
+   - Dashboard Badge (how it works, what the colors mean)
+   - Console Widget (manual checks, rate limits)
+   - Professional Tier Features (auto-cron, Discord webhooks, FTB)
+   - Troubleshooting (common errors, support contact)
+   - License & Activation (how to activate, deactivation, grace period)
+4. **Should Code write these docs now, or skip to 11F (BuiltByBit listing) which is more launch-critical?**
+
+54 hours to launch — happy to prioritize whatever moves the needle most.