docs: Add Task #89 - DERP Protocol Review & Formalization

WHAT WAS DONE:
- Added Task #89 to tasks.md (Tier 2 priority)
- Documented need to review DERP protocol usage
- Identified gap between intended and actual Gemini collaboration workflow
- Captured questions about gemini-workspace repo usage
- Connected to RV Dream (disaster recovery must work remotely)

WHY:
- gemini-workspace repo exists but sits empty
- Gemini consultations happening ad-hoc (e.g., March 31 monorepo session)
- No formalized workflow for Gemini collaboration
- DERP protocol may need updating based on actual usage patterns
- Firefrost Codex relationship to Gemini unclear

CONTEXT:
During gemini-workspace repo review (similar to brainstorming cleanup),
realized DERP protocol established Feb 2026 but never actually stress-tested
or formalized. Need comprehensive review to ensure disaster recovery strategy
is operational, not just theoretical.

FILES:
- docs/core/tasks.md (modified, +31 lines for Task #89)

Signed-off-by: The Golden Chronicler <claude@firefrostgaming.com>

docs/core/tasks.md

@@ -2969,6 +2969,40 @@ Complete mobile-responsive CSS media queries ready to inject via Ghost Admin →
 
 ---
 
+### 89. DERP Protocol Review & Formalization
+**Time:** 2-4 hours  
+**Status:** IDENTIFIED — Needs comprehensive review  
+**Priority:** Tier 2 — Infrastructure Health  
+**Documentation:** `docs/core/DERP.md`, `gemini-workspace` repo
+
+**WHY THIS MATTERS:**
+DERP (Disaster Emergency Recovery Protocol) was established as backup when Claude.ai fails, with Gemini as backup Chronicler. However, current usage is ad-hoc and gemini-workspace repo sits mostly empty despite being "active infrastructure."
+
+**Current State:**
+- gemini-workspace repo exists with empty directory structure
+- Gemini consultations happen (like March 31 monorepo architecture session)
+- Results documented in ops-manual, not gemini-workspace
+- No formalized workflow for Gemini collaboration
+- Firefrost Codex (local AI) not yet complete
+
+**Questions to Answer:**
+1. Should Gemini collaboration be formalized with structured workflow?
+2. Should gemini-workspace actively store Gemini session transcripts/proposals?
+3. What's relationship between Gemini (cloud) and Firefrost Codex (local)?
+4. Is current ad-hoc Gemini usage acceptable or needs formalization?
+5. Does DERP protocol need updating based on actual usage patterns?
+
+**Deliverables:**
+- Review and update DERP protocol documentation
+- Decide on Gemini collaboration workflow (formal vs ad-hoc)
+- Determine gemini-workspace usage pattern
+- Clarify Firefrost Codex role in disaster recovery
+- Update infrastructure-manifest.md with AI partner strategy
+
+**Impact:** Ensures disaster recovery strategy is actually usable when needed, not just theoretical. RV Dream requires working backup systems.
+
+---
+
 
 ---