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
parent d37480fb72
commit 2c043d2f96
3 changed files with 181 additions and 3 deletions
@@ -12,9 +12,11 @@ What it proves today:
 - page shell with plain CSS and one explicit metrics island script
 - compile-time surface generation plus interaction tests

+For a provider-explicit persistence boundary, see `../../docs/recipes/sqlx-persistence.md`.
+
 What it deliberately does not claim yet:

- real SQLx migrations or a database pool
+- a checked-in SQLx migration crate or database pool
 - production cookie/session middleware
 - a deploy target, flags, analytics, billing, or offline sync
 - browser automation for the metrics island