tmk241/hemx
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(recipes): add pwa offline boundary

Browse Source 
Document optional PWA/offline support as an adapter boundary: cached shell, domain-command queues, server-canonical replay, conflict/fingerprint behavior, and sync-crate shape without adding a client state graph or service worker to core.

req: canonical_authoring/008

req: runtime/003

req: runtime/004

req: auth/002

req: auth/004

req: failure/004

req: failure/005

req: sync/001

req: sync/007
This commit is contained in:
slhx agent
2026-06-05 10:03:39 +02:00
parent 16cb15fd98
commit 78aff362ff
5 changed files with 143 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tutorial-saas.md
+5 -3
View File
@@ -216,10 +216,12 @@ To move from the local tutorial skeleton to production:
`docs/recipes/auth-session-csrf.md`.
3. Wrap routes/handlers with app-owned metrics, flags, and killswitches from
`docs/recipes/observability-flags.md`.
4. Deploy server, generated output, and `/hemx.js` as one release unit following
4. Add optional PWA/offline behavior only through the adapter boundary in
`docs/recipes/pwa-offline.md`.
5. Deploy server, generated output, and `/hemx.js` as one release unit following
`docs/recipes/deploy-versioning.md`.
5. Follow `docs/versioning.md` for semver and upgrade notes.
6. Use `docs/diagnostics.md` when a template/build/derive/runtime mistake fails
6. Follow `docs/versioning.md` for semver and upgrade notes.
7. Use `docs/diagnostics.md` when a template/build/derive/runtime mistake fails
the app.
The handler and template model should stay recognizable throughout those swaps.