diff --git a/README.md b/README.md index 1e84036..96c249a 100644 --- a/README.md +++ b/README.md @@ -87,8 +87,10 @@ and integrate at explicit boundaries. req: laws/002 req: auth/001 cookies, and normal SameSite/browser semantics. hemx preserves submitted form fields and credentials semantics. See `docs/recipes/auth-session-csrf.md`. req: auth/004 req: auth/005 - **Observability, feature flags, killswitches, deploy:** use explicit platform - integrations around handlers, routes, and runtime assets. Core hemx must not - vendor providers or add framework-specific magic. See `docs/recipes/observability-flags.md` and `docs/recipes/deploy-versioning.md`. + integrations around handlers, routes, runtime assets, and mobile shells. Core + hemx must not vendor providers or add framework-specific magic. See + `docs/recipes/observability-flags.md`, `docs/recipes/deploy-versioning.md`, + and `docs/recipes/mobile-release.md`. req: examples/006 - **PWA/offline/sync:** optional adapters may reuse generated targets/effects, but core hemx must not gain a mandatory client state graph or local app runtime. Local truth is commands/events/projections, not stored DOM patches or diff --git a/REQUIREMENTS.md b/REQUIREMENTS.md index 16266bd..a5d55d7 100644 --- a/REQUIREMENTS.md +++ b/REQUIREMENTS.md @@ -809,6 +809,9 @@ what a valid business email is. ### req: examples/005 005 Canonical examples must not contain user-authored browser JavaScript. They may load the shared hemx runtime (`/hemx.js`) and may use declarative `data-hemx-*` attributes; inline `