diff --git a/AGENTS.md b/AGENTS.md index 0028520..9d269db 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -54,7 +54,7 @@ Keep it stable. Prefer pointers to canonical sources over copied structure, file - Stable commands: `cargo run -p hemx-xtask -- test`, `cargo run -p hemx-xtask -- html-examples-smoke`, `cargo check --workspace`, `redgate health --strict`. Use the xtask runner for full verification so jobs are capped from local CPU and memory; use the html_examples smoke for focused browser verification of the HTML pattern gallery. req: test/004 req: test/006 - Example behavior tests should prefer `hemx_test` generated-resource assertions over raw slot constants or raw effect/payload matching. req: test/008 - Run the workout product exemplar with `cargo run -p hemx-xtask -- workout dev` and open `http://127.0.0.1:3028`; set `HEMX_WORKOUT_ADDR=127.0.0.1:3030` if the default port is busy. Its durable visual direction and recovery expectations live in `examples/workout/DESIGN.md`. req: examples/008 -- Use the same Workout command surface for tests, production build, and mobile release: `cargo run -p hemx-xtask -- workout test`, `cargo run -p hemx-xtask -- workout build`, `HEMX_WORKOUT_ORIGIN=https://workout.example.com cargo run -p hemx-xtask -- workout mobile-release`, and `HEMX_WORKOUT_ORIGIN=https://workout.example.com cargo run -p hemx-xtask -- workout mobile-verify`; Android/iOS SDKs, store submission targets, and signing remain external blockers, not repo-owned secrets. req: examples/006 +- Use the same Workout command surface for tests, production build, and mobile release: `cargo run -p hemx-xtask -- workout test`, `cargo run -p hemx-xtask -- workout build`, `HEMX_WORKOUT_ORIGIN=https://workout.example.com cargo run -p hemx-xtask -- workout mobile-release`, and `HEMX_WORKOUT_ORIGIN=https://workout.example.com cargo run -p hemx-xtask -- workout mobile-verify`; Android/iOS SDKs, store submission targets, and signing remain external blockers, not repo-owned secrets. req: examples/006 req: examples/011 - hemx core stays small: effects, typed ids, registries, and wire schema only. - Routing, auth, sessions, transport, transitions, sync, and storage belong in integration/user crates. - Public examples and beginner APIs should use generated resources and `IntoEffect`, not raw ids or runtime opcodes. diff --git a/README.md b/README.md index 92c70e2..ee10db9 100644 --- a/README.md +++ b/README.md @@ -109,7 +109,7 @@ and integrate at explicit boundaries. req: laws/002 req: auth/001 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 + and `docs/recipes/mobile-release.md`. req: examples/011 - **Mobile starter:** create the phone-first path with `cargo run -p hemx-xtask -- app new --mobile PATH`. The starter carries a real app flow, typed host capabilities, command/event/projection recovery truth, and diff --git a/REQUIREMENTS.md b/REQUIREMENTS.md index fa1b859..8d90371 100644 --- a/REQUIREMENTS.md +++ b/REQUIREMENTS.md @@ -879,7 +879,13 @@ what a valid business email is. 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 `