diff --git a/docs/code-bridge/archive/RES-2026-04-12-phase11d-badge-debug.md b/docs/code-bridge/archive/RES-2026-04-12-phase11d-badge-debug.md
new file mode 100644
index 0000000..01621d3
--- /dev/null
+++ b/docs/code-bridge/archive/RES-2026-04-12-phase11d-badge-debug.md
@@ -0,0 +1,43 @@
+# Architectural Response — Badge Debug Results
+
+**Re:** Phase 11D Badge Debug
+**Date:** 2026-04-12
+**From:** Chronicler #84 — The Meridian
+
+---
+
+## Diagnostic Results
+
+**1. ServerRow.tsx exists:** ✅
+```
+/var/www/pterodactyl/resources/scripts/components/dashboard/ServerRow.tsx
+```
+
+**2. UpdateBadge injection:** ✅ Present and correct
+```
+line 1: import UpdateBadge from "@/components/dashboard/UpdateBadge";
+line 106: <p css={tw`text-lg break-words`}>{server.name}<UpdateBadge serverUuid={server.uuid} /></p>
+```
+
+**3. Yarn build:** ❌ NEVER RUN — manifest.json is from April 7
+```
+/var/www/pterodactyl/public/assets/manifest.json — 2026-04-07 06:10
+```
+
+**4. Yarn build:production result:** 7 CSS module errors — build fails
+
+```
+ERROR in ./resources/scripts/blueprint/ui/badge/styles.module.css
+ERROR in ./resources/scripts/components/elements/activity/style.module.css
+ERROR in ./resources/scripts/components/elements/button/style.module.css
+ERROR in ./resources/scripts/components/elements/dialog/style.module.css
+ERROR in ./resources/scripts/components/elements/inputs/styles.module.css
+ERROR in ./resources/scripts/components/server/console/style.module.css
+ERROR in ./resources/scripts/components/server/files/style.module.css
+```
+
+These look pre-existing (not caused by our code). Are these known Blueprint beta CSS issues? Does the build need a specific Node/yarn version to succeed?
+
+The injection is correct — we just can't compile it.
+
+*— Chronicler #84, The Meridian*
diff --git a/docs/code-bridge/requests/REQ-2026-04-12-phase11d-badge-decision.md b/docs/code-bridge/requests/REQ-2026-04-12-phase11d-badge-decision.md
new file mode 100644
index 0000000..4f4b6ec
--- /dev/null
+++ b/docs/code-bridge/requests/REQ-2026-04-12-phase11d-badge-decision.md
@@ -0,0 +1,25 @@
+# Architectural Request
+
+**Date:** 2026-04-12
+**Topic:** Dashboard badges blocked by Blueprint CSS module build errors — decision needed
+
+## 1. Current State
+Badge injection into ServerRow.tsx is correct. But `yarn build:production` fails on 7 pre-existing CSS module errors from Blueprint beta — not caused by our code.
+
+## 2. The Blocker
+Blueprint beta-2026-01's webpack config doesn't have a CSS module loader configured. This breaks `yarn build:production` for any panel with Blueprint installed. Our badge code can't compile.
+
+## 3. Decision for Michael
+
+**Option A: Skip badges for v1.0.0 launch** (recommended)
+- Admin page + console widget both work
+- Badges are nice-to-have, not core functionality
+- Add badges in v1.1.0 when Blueprint fixes their build or we find a workaround
+- Zero risk to launch timeline
+
+**Option B: Patch webpack config**
+- Add `css-loader` with modules support to Blueprint's webpack
+- Risk: could break other Blueprint components, and gets overwritten on Blueprint updates
+- Not recommended 52 hours before launch
+
+Which way do you want to go?