docs: Task #117 spec — Trinity Console PWA

Full context from brainstorming session with Michael.
Implementation phases, Gemini consultation needs, open questions.

Chronicler #78 | firefrost-operations-manual

docs/tasks/task-117-trinity-console-pwa/README.md

@@ -0,0 +1,62 @@
+# Task #117: Trinity Console PWA — Mobile App for All Trinity Members
+
+**Created:** April 11, 2026
+**Origin:** Chronicler #78 + Michael brainstorming during task management redesign
+**Priority:** Medium (post-launch)
+**Owner:** Trinity
+
+---
+
+## Context
+
+Came up during task management system redesign session. Decap CMS was just decommissioned because the mobile experience was bad for Meg and Holly. Trinity Console is now the primary admin interface but is desktop-first. Michael manages from his phone regularly.
+
+**Cross-platform requirement:** Michael and Meg are Android, Holly is iPhone. No app store hassle.
+
+**Decision:** PWA (Progressive Web App) — install from browser, shows as native app icon, works offline for cached pages. Same URL, same codebase, all platforms.
+
+## Implementation Plan
+
+### Phase 1 — PWA Foundation
+- manifest.json (app name, icons, Fire+Frost theme colors, display: standalone)
+- Service worker for static asset caching
+- Responsive meta viewport tag
+- Test install on Android Chrome + iOS Safari
+
+### Phase 2 — Mobile Layout
+- Hamburger menu sidebar on mobile
+- Touch-friendly buttons (larger tap targets)
+- Card view for tables on small screens
+- Swipe gestures for task status changes
+
+### Phase 3 — Key Mobile Views
+- Tasks (primary use case — view, create, tap done)
+- Server Status (quick glance)
+- Dashboard (subscriber count, revenue)
+
+### Phase 4 — Push Notifications
+- Web Push API for server down alerts
+- Task assignment notifications
+- Per-category subscription preferences
+
+## Gemini Consultation
+
+Not yet consulted. Should consult on:
+- PWA best practices for admin dashboards
+- Service worker caching strategy (what to cache offline vs always-live)
+- Push notification architecture (Web Push API vs Discord as notification layer)
+- iOS Safari PWA limitations (push notifications need iOS 16.4+, confirm Holly's version)
+
+## Open Questions
+- Holly's iOS version?
+- Which views are most critical for mobile-first?
+- Optimize existing EJS views or build separate mobile SPA?
+
+## Decisions Made
+- PWA over native app (cross-platform, no app store)
+- Trinity Console is the target (not a separate app)
+- Post-launch priority (after April 15 soft launch)
+
+---
+
+**Fire + Frost + Foundation = Where Love Builds Legacy** 💙🔥❄️