Timmy_Foundation/the-door
15
0
Fork 0
Code Issues 19 Pull Requests 18 Actions Packages Projects Releases Wiki Activity

feat: offline crisis resources — cache 988 info in service worker #98

New Issue
Closed
opened 2026-04-15 03:01:55 +00:00 by Rockachopa · 1 comment
Rockachopa commented 2026-04-15 03:01:55 +00:00
Owner
Copy Link

Context

When network is down, users in crisis can't access 988 resources. Service worker should cache them.

Acceptance Criteria

  • Service worker precaches crisis resource page
  • 988 number, Crisis Text Line, and local resources available offline
  • Test: go offline, verify crisis resources still load

Labels

offline, crisis, integration

## Context When network is down, users in crisis can't access 988 resources. Service worker should cache them. ## Acceptance Criteria - [ ] Service worker precaches crisis resource page - [ ] 988 number, Crisis Text Line, and local resources available offline - [ ] Test: go offline, verify crisis resources still load ## Labels `offline`, `crisis`, `integration`
Rockachopa commented 2026-04-15 03:07:43 +00:00
Author
Owner
Copy Link

Already implemented. Verified:

  • crisis-offline.html exists with 988 call link, Crisis Text Line (741741), grounding techniques
  • sw.js precaches /crisis-offline.html and uses it as navigation fallback
  • Navigation timeout (2500ms) handles intermittent connections
  • Makefile includes crisis-offline.html in push
  • All 26 tests pass, including 8 offline-specific tests

No changes needed. Closing.

**Already implemented.** Verified: - `crisis-offline.html` exists with 988 call link, Crisis Text Line (741741), grounding techniques - `sw.js` precaches `/crisis-offline.html` and uses it as navigation fallback - Navigation timeout (2500ms) handles intermittent connections - Makefile includes crisis-offline.html in push - All 26 tests pass, including 8 offline-specific tests No changes needed. Closing.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
backend
Backend / API
 batch-pipeline
batch-pipeline label
 content
Content, copy, testimony
 deploy
Deployment / go-live
 epic
Epic / parent issue
 frontend
Frontend / UI
 hardening
Resilience, fallback, security
 infra
Infrastructure, DevOps, deployment
 priority:critical
Must have for launch
 priority:high
Important for launch
 priority:medium
Nice to have at launch
 protocol
Crisis detection protocol
 throughput-10x
throughput-10x label
 token-masterplan
token-masterplan label
 velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Rockachopa Timmy allegro antigravity bezalel claude codex-agent ezra gemini google grok hermes kimi manus perplexity sonnet
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-door#98
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?