Make workout mobile-verify reject non-HTTPS origins and release kits that omit detected external signing/toolchain blockers, so verification checks objective release preconditions instead of pretending to predict store approval.
req: examples/006
Record share/haptics and the denied/timeout/unavailable/error host result kinds in Android and iOS release metadata, and make mobile verification require them.
req: examples/006
req: host/002
Route local dev, tests, production build, mobile release, mobile verification, and doctor through one Workout xtask surface, and update the canonical docs around that surface.
req: examples/001
req: examples/006
req: test/004
Add a workout-mobile verify command that checks the generated release kit and server artifact, then document it beside release/doctor so the mobile path has a recurring gate.
req: examples/006
Add one canonical Workout mobile release command that builds the production server and writes Android/iOS shell metadata, explicit production policy, and honest external signing/toolchain blockers.
req: examples/001
req: examples/006
req: host/002
req: local/001
Keep local/offline and host capability recipes on app-owned command/event/projection flow without teaching raw EffectBatch as the authoring boundary.
req: local/001
req: local/002
req: host/002
Represent denied, timeout, unavailable, and error host outcomes with one HostFailure result shape, update the browser adapter, and keep Workout host recovery flowing through app code before UI effects.
req: host/002
req: host/005
req: local/003
Expose generated ui::page as the canonical page-boundary rendering helper and move the Workout golden path and docs off beginner-visible ui::render calls.
req: public_api/002
req: codegen/002
req: canonical_authoring/006
Replace fixed /hemx.js wording with helper-provided runtime asset language so docs match hemx-axum runtime_js_path deployment boundaries.
req: axum_integration/005
req: examples/001
Define local/offline truth as commands, domain events, and projections rather than stored DOM patches or EffectBatch payloads; wire the techdemo through a local command-to-projection-to-effect flow; document that hemx-local is not a crate until reusable semantics are proven.
req: local/001
req: local/002
req: local/003
req: local/004
req: examples/001
Define local/offline truth as commands, domain events, and projections rather than stored DOM patches or EffectBatch payloads, and wire the techdemo through a local command-to-projection-to-effect flow.
req: local/001
req: local/002
req: local/003
req: local/004
req: examples/001
Introduce hemx-host with typed capability manifests, calls, events, host-check failures, reusable browser/PWA and native-shell profiles, and a tiny optional browser adapter for haptics/share that returns host events without DOM mutation.
req: host/001
req: host/002
req: host/003
req: host/004
req: host/005
Record the current v1 readiness closure matrix after the final gates and normal-path review, including the release decision for provider recipes and the remaining verification checklist for GOAL_DONE.
req: examples/001
req: diagnostics/001
req: public_api/001
req: runtime/003
req: runtime/004
Promote examples/saas from skeleton wording to the canonical tutorial app and record the v1 release decision that local persistence plus provider-explicit recipes is the supported production boundary for CI-friendly docs.
req: examples/001
req: auth/001
req: laws/004
req: public_api/005
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
Add a v1 readiness audit against the active Close when, clarifying satisfied vs remaining gaps and naming the next concrete waypoint before any GOAL_DONE attempt.
req: examples/001
req: public_api/001
req: diagnostics/001
req: runtime/003
req: runtime/004
Document the v1 diagnostics story for common template, derive, form, result-handler, and runtime/deploy mistakes. The guide names expected user-facing diagnostics and recurring verification gates without exposing raw ids/selectors as the beginner path.
req: diagnostics/001
req: diagnostics/002
req: diagnostics/003
req: failure/004
req: failure/005
req: public_api/005
req: test/003
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
slhx agent