v1.0.5: Console fetch fix rolled across all 6 builds

Console /rules now fetches from Discord async (was returning hardcoded
fallback without attempting fetch). DIAG logging kept for observability.
All 6 builds at 1.0.5. CHANGELOG.md, INSTALL.md, ACTIVE_CONTEXT.md updated.

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

docs/code-bridge/status/ACTIVE_CONTEXT.md

@@ -14,12 +14,13 @@ Rules mod config bug — iterating fixes for Otherworld (NC1, 1.20.1 Forge).
 - All 3 versions compiled (1.21.1 NeoForge on NC1, 1.20.1 + 1.16.5 Forge locally)
 - CurseForge project page copy pending from Chronicler
 
-### Rules Mod Config Bug — IN PROGRESS 🔧
+### Rules Mod Config Bug — FIXED ✅
 - v1.0.1: Added `ModConfigEvent.Loading` handler (symptom fix, not root cause)
-- v1.0.2: Switched `ModConfig.Type.SERVER` → `COMMON` (config now persists across restarts ✅)
-- v1.0.3: Fixed 1.20.1 event bus registration (config events were on wrong bus), added section header warnings to generated config
-- v1.0.4: Diagnostic build (1.20.1 only) — INFO-level `[DIAG]` logs in RulesCommand + DiscordFetcher to trace where config-to-fetch pipeline breaks
-- **Status:** Config loads correctly (Loading handler confirmed channel ID). `/rules` still returns defaults. Awaiting Chronicler's v1.0.4 diagnostic log output from Otherworld.
+- v1.0.2: Switched `ModConfig.Type.SERVER` → `COMMON` (config persists ✅)
+- v1.0.3: Fixed 1.20.1 event bus registration, added section header warnings
+- v1.0.4: Diagnostic build — revealed DIAG logs never fired
+- v1.0.5: **Root cause found** — console `/rules` hit early return, never fetched from Discord. Fixed: console path now fetches async. DIAG logging kept for observability.
+- **Status:** WORKING on Otherworld. All 6 builds at v1.0.5. Ready for CurseForge submission.
 
 ### Bridge Queue — CLEAR ✅
 - All REQs have matching RES files