docs: Add Gemini response and Michael's hybrid approach

WHAT:
- Added Gemini's complete architectural review
- Ghost = architectural debt (confirmed)
- Recommendation: 11ty/Hugo + Cloudflare Pages + Decap CMS
- Gemini's concern: 1-2 hour estimate is developer trap
- Michael's counter: hybrid test approach (2 hours, abort if issues)

GEMINI'S VERDICT:
- Ghost cleanup pre-launch, migrate post-launch (safe path)
- Static site IS the right long-term answer
- 11ty/Hugo + Cloudflare Pages recommended
- Decap CMS for Meg/Holly editing workflow
- Forms, SEO, meta tags are hidden Ghost value

MICHAEL'S HYBRID PLAN:
1. Test Hugo/11ty with homepage only (2 hours)
2. Deploy to test subdomain
3. Evaluate complexity with real data
4. GO: finish migration tomorrow
5. NO-GO: Ghost cleanup, ship on Ghost

NEW QUESTIONS FOR GEMINI:
- Hugo vs 11ty - which for our stack?
- Cloudflare Pages gotchas?
- Decap CMS complexity?
- Contact form best practice?
- SEO minimum viable for launch?
- Asset migration complexity?
- Abort criteria threshold?
- Hidden complexities to watch for?

STATUS: Awaiting Gemini's technical guidance on hybrid approach

Signed-off-by: Chronicler #55 <claude@firefrostgaming.com>

docs/planning/gemini-consultations/ghost-vs-static-website-2026-04-02.md

@@ -350,3 +350,168 @@ This is why we have you as our architectural partner - to see what we're too clo
 — Michael, Claude (Chronicler #55), and the whole Trinity
 
 **Fire + Frost + Foundation = Where Love Builds Legacy** 💙
+
+---
+
+## 🤖 GEMINI'S RESPONSE (April 2, 2026)
+
+Hey Michael, Claude, and the rest of the Trinity. Let's get right into this architectural review. You're at a classic crossroads, and it's the exact right time to be asking these questions.
+
+Here is the honest, unfiltered architectural assessment of your situation.
+
+### 1. Is Ghost earning its keep?
+**No. It is officially architectural debt.** Given the pivot to Discord and Paymenter, you are absolutely using a Ferrari to go to the grocery store. Ghost is a heavy, dynamic platform built for membership management, newsletters, and blogging. Running Node.js, MySQL, Nginx, and systemd just to serve 7 static HTML pages is unnecessary overhead. The $200/year (or the equivalent time in server maintenance) is no longer yielding a return on investment. 
+
+### 2. Michael's "do it now" argument - sound or risky?
+**It is dangerous scope creep disguised as pragmatism.**
+Your instinct to clean things up while you're "in the code" is a great developer trait, but it violates the "ship, then build" principle right now. Ghost *works today*. 
+
+The "1-2 hours to migrate" is a classic developer trap (Hofstadter's Law). That estimate accounts for moving HTML files, but it rarely accounts for:
+* Reconfiguring DNS and waiting for propagation.
+* Setting up a new form handler for the Contact page.
+* Fixing inevitable broken asset paths (images, CSS).
+* Re-testing mobile responsiveness across the new deployment.
+* Rebuilding the SEO meta-tags that Ghost is currently generating automatically.
+
+You have 13 days until soft launch. You have actual blockers (Unsubscribe UI, E2E testing) that impact user experience. Do not swap out the foundation of the house while you are painting the front door. Do the 1-hour cleanup on Ghost, launch, and put the migration on the roadmap for Phase 2.
+
+### 3. If we migrate, to what?
+**Recommendation: 11ty (Eleventy) or Hugo hosted on Cloudflare Pages.**
+* **Why not Custom (Node/Flask/Go):** Rebuilding a custom CMS for 7 static pages is reinventing the wheel. It introduces bugs you have to fix and code you have to maintain.
+* **Why not Plain HTML:** Maintaining identical headers, footers, and navbars across 7 pages manually gets tedious fast.
+* **The Sweet Spot:** An SSG (Static Site Generator) like 11ty or Hugo allows you to use layouts and partials. You write the content in Markdown or HTML, the SSG builds it into a hyper-fast static site, and Cloudflare Pages hosts it for free on an edge network.
+
+### 4. Content editing workflow?
+To keep things frictionless for Meg and Holly without teaching them Git, use a **Git-based Headless CMS** like Decap CMS (formerly Netlify CMS) or TinaCMS. 
+* It provides a friendly web-based Admin UI.
+* When Meg or Holly hit "Save," the CMS automatically commits the changes to your Git repository.
+* That commit triggers Cloudflare Pages to rebuild and deploy the site in seconds.
+* **Result:** They get the Ghost-like editing experience, and you get the pristine, database-free static architecture.
+
+### 5. What about SEO, analytics, forms?
+This is the hidden value Ghost is currently providing, and why the 1-2 hour migration estimate is risky pre-launch.
+* **Forms:** Static sites don't have backends to process forms. You will need to wire your contact page to a service like Formspree, Netlify Forms, or a simple Cloudflare Worker.
+* **SEO:** You will need to create a global `<head>` partial in your SSG that dynamically injects meta titles, descriptions, and Open Graph tags based on the page's frontmatter.
+* **Analytics:** Easily handled by pasting a lightweight script (like Plausible or basic GA) into your global footer. 
+
+### 6. The RV Vision Filter
+**Static sites are the holy grail for cellular remote management.**
+Managing a MySQL database and Node.js runtime over a spotty 4G connection in the middle of nowhere is a recipe for frustration. A static site on Cloudflare means zero server maintenance, no security patches for a CMS, and infinite scalability. If the server goes down, the site stays up. For a three-person team operating remotely, static architecture is the only logical long-term choice.
+
+---
+
+### The Verdict & Plan of Action
+
+**The 5-Year Reality:** Over the next 5 years, keeping Ghost will cost you ~$1,000 or hundreds of hours of server maintenance for features you aren't using. Migrating to a static site is the right move for the Firefrost legacy.
+
+**The 13-Day Reality:** Migrating *right now* introduces unnecessary risk. The groceries are already in the trunk of the Ferrari, and the store closes in 10 minutes. Don't swap cars in the parking lot.
+
+1.  **Pre-Launch (Today):** Spend the 1 hour cleaning up the existing Ghost pages. Strip the blog, remove the subscribe UI, and verify the 7 core pages look perfect. 
+2.  **Launch (April 15):** Ship the site on Ghost.
+3.  **Post-Launch:** Spin up an 11ty/Hugo repo, integrate Decap CMS for Meg and Holly, wire up a form handler, and take your time migrating the Git-backed HTML you just documented. Swap the DNS when it's flawless.
+
+Are we locked in on doing the quick Ghost cleanup today so we can pivot focus entirely to the Unsubscribe UI and E2E testing?
+
+---
+
+## 💙 MICHAEL'S RESPONSE & HYBRID APPROACH (April 2, 2026)
+
+Hey Gemini,
+
+Thank you for the brutal honesty - that's exactly why we consult you. You nailed the architectural assessment, and I hear your concerns about Hofstadter's Law. You're right that my "1-2 hours" estimate could be optimistic.
+
+**But here's what you don't know about me:** When I lock in on a project, we usually knock it off pretty quickly. My track record is solid on execution speed when I'm focused.
+
+So here's what I'm thinking - **a hybrid approach that respects your wisdom while testing my hypothesis:**
+
+### The Plan: Test First, Decide With Data
+
+**Today (April 2) - 2 hour experiment:**
+1. Set up Hugo/11ty project (30 min)
+2. Port the homepage ONLY (30 min)
+3. Deploy to test subdomain (test.firefrostgaming.com) (30 min)
+4. Evaluate complexity and identify issues (30 min)
+
+**Decision Point:**
+- **If it's smooth** → Continue with remaining 6 pages tomorrow (another 2 hours)
+- **If hitting your predicted issues** → Abort, do 1-hour Ghost cleanup, ship on Ghost as you recommended
+
+**This gives us:**
+- ✅ Real data on migration complexity (not estimates)
+- ✅ Low risk (test subdomain, Ghost still running)
+- ✅ Validates or invalidates the "1-2 hour trap" concern
+- ✅ No commitment until proven viable
+- ✅ Still 13 days to launch even if we abort
+
+### Why I Think This Could Work
+
+**We just documented everything today:**
+- All 7 pages backed up in Git with clean HTML
+- Fire/Frost branding is just CSS/styling (portable)
+- We know exactly what we have (no surprises)
+- Fresh in my mind from today's work
+
+**The concerns you raised:**
+- DNS propagation → Test on subdomain first, zero risk
+- Contact form → I'll use Formspree (5 min setup)
+- Asset paths → Can verify during homepage test
+- Mobile responsive → Already works, just needs validation
+- SEO meta tags → Basic ones for launch, perfect them later
+
+### New Questions For You
+
+If we proceed with this hybrid test approach, **what should we watch out for?**
+
+1. **Hugo vs 11ty - which one for us?**
+   - You recommended both. Given our stack (Node.js/Express for Trinity Console), does 11ty make more sense? Or is Hugo's single binary worth the language switch?
+
+2. **Cloudflare Pages setup - any gotchas?**
+   - Is it really as simple as: connect Git repo → auto-deploy on push?
+   - Any configuration pitfalls for a Hugo/11ty site?
+   - SSL/DNS setup complexity?
+
+3. **Decap CMS integration - complexity check:**
+   - You mentioned this for Meg/Holly's editing workflow
+   - Is this something we add Day 1, or post-launch?
+   - How complex is the initial setup?
+   - Does it work equally well with Hugo and 11ty?
+
+4. **Contact form - recommended approach?**
+   - You mentioned Formspree, Netlify Forms, or Cloudflare Worker
+   - Which is most reliable for our use case?
+   - Any SPAM concerns we need to handle?
+
+5. **SEO meta tags - minimum viable for launch?**
+   - What's the bare minimum for April 15 launch?
+   - Can we start with basic `<title>` and `<meta description>` and add Open Graph later?
+   - Or is that shooting ourselves in SEO foot?
+
+6. **Asset migration - anything tricky?**
+   - Images are hosted on Ghost currently (uploaded via admin)
+   - Do we need to download and re-host them?
+   - Or can we reference Ghost image URLs temporarily?
+
+7. **The abort criteria - when to pull the plug?**
+   - If the homepage test hits issues, what's the threshold for "abort and stick with Ghost"?
+   - What issues are "normal migration friction" vs "danger signs"?
+
+8. **Anything else we're not thinking about?**
+   - What's the hidden complexity we won't see until we start?
+   - What will bite us at 11 PM when we're mid-migration?
+   - What's the "one more thing" that always comes up?
+
+### The Commitment
+
+**I promise you this:**
+- If the 2-hour homepage test reveals your concerns are valid → I'll abort and follow your recommendation (Ghost cleanup, post-launch migration)
+- If it's smooth → I'll finish the migration properly (not rush it)
+- I will NOT let this derail the actual launch blockers (Unsubscribe UI, E2E testing)
+- If we hit hour 3 and it's not done → Stop, reassess
+
+**Your wisdom has saved us from scope creep before (Trinity Console task system). If this test reveals complexity, I'll trust that wisdom again.**
+
+Are there any technical landmines we should know about before we start this test? Anything that would make you say "definitely do NOT attempt this pre-launch"?
+
+Thanks for being our architectural partner and keeping us honest, friend. 🔥❄️
+
+— Michael & Claude (Chronicler #55)