diff --git a/AGENTS.md b/AGENTS.md index 9aa9f6f..a1d5eee 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -49,8 +49,8 @@ Keep it stable. Prefer pointers to canonical sources over copied structure, file - Prefer links or pointers to canonical sources over copied lists. - Avoid project trees, architecture maps, generated inventories, current file sizes, issue lists, TODO inventories, and other snapshots that will rot. - Stable commands: `cargo run -p hemx-xtask -- test`, `cargo check --workspace`, `redgate health --strict`. Use the xtask runner for full verification so jobs are capped from local CPU and memory. req: test/004 -- Run the workout product exemplar with `cargo run --bin hemx-workout-example` 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/001 -- Generate and verify the Workout mobile release kit with `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 and signing remain external blockers, not repo-owned secrets. req: examples/006 +- 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/001 +- 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 and signing remain external blockers, not repo-owned secrets. req: examples/006 - 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 96c249a..07b58e1 100644 --- a/README.md +++ b/README.md @@ -134,10 +134,11 @@ See `docs/versioning.md`. `docs/recipes/sqlx-persistence.md` shows the provider boundary without moving SQL into core. - `examples/workout`: phone-first local-first product exemplar. Run with - `cargo run --bin hemx-workout-example` and open `http://127.0.0.1:3028`. + `cargo run -p hemx-xtask -- workout dev` and open `http://127.0.0.1:3028`. It keeps workout truth as commands/events/projections and routes export through the host capability boundary; `examples/workout/README.md` documents - run, test, deploy, and failure-mode paths. req: examples/001 req: local/001 req: host/005 + the canonical dev, test, production build, mobile release, verification, and + failure-mode paths. req: examples/001 req: examples/006 req: local/001 req: host/005 - `examples/kanban`: advanced / north-star milestone boundary sketch. It may expose manual registry or render escape hatches while exploring product limits. - `examples/techdemo`: advanced integration demo with a leaf island and broader diff --git a/REQUIREMENTS.md b/REQUIREMENTS.md index 06782be..74fc9a2 100644 --- a/REQUIREMENTS.md +++ b/REQUIREMENTS.md @@ -810,7 +810,7 @@ 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 `