slhx agent
107111052d
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
slhx agent
1fbeeb52b8
docs(hemx): define v1 versioning policy
...
Add a compact semver and upgrade policy for v1: stable beginner APIs, stable wire/runtime compatibility, advanced escape-hatch tier, breaking-change rules, upgrade-note template, and release checklist.
req: abi/001
req: abi/002
req: abi/003
req: abi/004
req: abi/005
req: public_api/001
req: public_api/002
req: public_api/005
req: runtime/003
req: runtime/004
2026-06-05 09:49:30 +02:00
slhx agent
bf6add03ef
docs(recipes): add deploy versioning boundary
...
Document deployment and version compatibility for hemx apps: release unit, runtime asset caching, rolling deploy policy, fingerprint mismatch behavior, semver buckets, upgrade notes, and deployment checks without adding platform code to core.
req: abi/001
req: abi/002
req: abi/003
req: abi/004
req: abi/005
req: runtime/004
req: failure/005
2026-06-05 09:32:25 +02:00
slhx agent
a7012b94c2
docs(recipes): add auth csrf boundary
...
Document the provider-explicit auth/session and CSRF boundary for the SaaS tutorial. The recipe keeps cookies, sessions, CSRF policy, and rejection behavior in Axum/Tower/app code while hemx handlers continue to receive typed context/forms and return generated effects.
req: laws/002
req: auth/001
req: auth/002
req: auth/003
req: auth/004
req: auth/005
req: failure/004
req: examples/001
2026-06-05 09:30:13 +02:00
slhx agent
2c043d2f96
docs(recipes): add sqlx persistence boundary
...
Document a provider-explicit SQLx persistence adapter for the SaaS tutorial without adding SQLx to hemx core or the workspace. The recipe keeps auth/session, CSRF, generated helpers, and Result handler mapping as the app boundary.
req: laws/002
req: laws/004
req: auth/001
req: auth/002
req: auth/004
req: examples/001
req: canonical_authoring/002
req: failure/004
2026-06-05 09:27:08 +02:00