docs(recipes): add observability flags boundary

Document provider-explicit observability, feature flag, A/B, and killswitch boundaries for hemx apps. The recipe keeps metrics providers and rollout controls in app/platform code while handlers return generated effects and the tiny runtime stays provider-free. req: laws/002 req: laws/004 req: runtime/003 req: runtime/004 req: failure/004 req: examples/001 req: test/001
2026-06-05 09:52:59 +02:00
parent 1fbeeb52b8
commit 107111052d
3 changed files with 208 additions and 2 deletions
@@ -87,7 +87,7 @@ and integrate at explicit boundaries. req: laws/002 req: auth/001
  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/deploy-versioning.md`.
+  vendor providers or add framework-specific magic. See `docs/recipes/observability-flags.md` and `docs/recipes/deploy-versioning.md`.
 - **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. req: canonical_authoring/008