bridge: RES for discord-action-log and subscriber-wiki-auth — both GO

docs/code-bridge/requests/RES-2026-04-15-discord-action-log.md

@@ -0,0 +1,24 @@
+# RES-2026-04-15-discord-action-log
+
+**From:** Chronicler #93
+**Date:** 2026-04-16
+**Status:** GO — build it
+
+## Decision
+
+Straightforward build, no architecture concerns. Proceed as specced.
+
+## Notes
+
+- Silent-fail pattern is correct — never let logging break the action
+- Migration number: check what's next after 141 (Issues was 141, so use 142)
+- Action types confirmed: reaction_role_add, reaction_role_remove, wanderer_assigned, welcome_dm, link_reminder_dm
+- Console view: recent 100, filter by action_type, discord_id search — keep it simple
+- This is day-two priority — we need visibility into what Arbiter is actually doing in Discord
+
+## Deploy Steps (after build)
+
+1. Run migration 142 on Command Center
+2. Copy files per standard deployment pattern
+3. Restart arbiter-3
+4. Verify sidebar link appears in Trinity Console

docs/code-bridge/requests/RES-2026-04-15-subscriber-wiki-auth.md

@@ -0,0 +1,32 @@
+# RES-2026-04-15-subscriber-wiki-auth
+
+**From:** Chronicler #93
+**Date:** 2026-04-16
+**Status:** GO — build it, but has a manual pre-req
+
+## Pre-Req (Michael does this before deploy)
+
+Wiki.js admin panel at subscribers.firefrostgaming.com needs:
+1. Create 6 user groups: Awakened, Elemental, Knight, Master, Legend, Sovereign
+2. Generate API key: Admin → API Access → add key → copy to .env as WIKIJS_API_KEY
+
+Code cannot deploy until Michael completes these two steps.
+
+## Decision
+
+Build proceeds as specced. No architecture concerns.
+
+## Notes
+
+- Email pattern confirmed: discordId@firefrost.local
+- Silent-fail is correct — wiki sync must never break the Stripe webhook
+- Hook into both checkout AND lifecycle handlers (cancellation/grace → demote to Awakened)
+- Add WIKIJS_API_KEY to .env.example with a comment explaining it
+
+## Deploy Steps (after pre-req complete)
+
+1. Michael creates Wiki.js groups + API key
+2. Add WIKIJS_API_KEY to .env on Command Center
+3. Copy files per standard deployment pattern
+4. Restart arbiter-3
+5. Verify a test checkout syncs the wiki user