@eventmodelers/cli 1.0.155 → 1.0.157

package/README.md

@@ -202,7 +202,7 @@ and the agent starts building — `--local` skips platform config and credential
 
 **Backend → UI handover.** Besides the usual statuses a slice can be `Ready` (modeling done, waiting to be planned) and `Handover` (backend built, UI contract published, waiting for the UI kit). The flow is `Ready → Planned → InProgress → Handover → InProgress → Done`. Install with `init --handover` (or `re-init --handover`; switch later with `eventmodelers config --handover on|off`; for a single run `run --handover` overrides the setting without saving anything), which saves `"handover": true` in `.eventmodelers/config.json` — then a backend kit ends STATE_VIEW / STATE_CHANGE slices at `Handover` instead of `Done` (the `ui-contract` skill, Step 4, owns that rule); without the flag nothing changes: slices end at `Done`, exactly as before. A kit claims work from the status named in its `lib/kit.json` — `{ "pickupStatus": "Handover" }` for the `react` / `supabase-react` UI kits, absent (= `Planned`) for backend kits. A new UI kit ships that file and sets `Done` when its half is built; a new backend kit just invokes `ui-contract`. Needs a platform with the `Ready` / `Handover` statuses.
 
-**UI contract.** The scaffolded `build-state-view` / `build-state-change` skills already end by invoking the shared `ui-contract` skill, which publishes each slice's read (`GET`) or write (`POST`) contract — the endpoint's OpenAPI operation, as a ```` ```yaml ui-contract ```` block — as a `## UI Contract` section in the slice's feedback-lane markdown node (exported in `slice.json` `notes[]`, so a UI build kit can look it up directly). Two things are yours to decide: *where the contract is derived from* (point the `UI Contract` section of those skills at your stack's machine-readable API description, if it has one — the `node`/`supabase` stacks use their `@openapi` blocks via a `ui-contract-from-openapi.md` reference, taking the operation verbatim — otherwise the skill writes the equivalent OpenAPI operation from the route code), and, if you need a different shape or location, a whole-skill override: ship `.claude/skills/ui-contract/SKILL.md` in the stack's templates and it replaces the shared one (stack templates are applied after `shared/skills/`).
+**UI contract (handover only).** With handover on, the scaffolded `build-state-view` / `build-state-change` skills end by invoking the shared `ui-contract` skill, which publishes each slice's read (`GET`) or write (`POST`) contract — the endpoint's OpenAPI operation, as a ```` ```yaml ui-contract ```` block — as a `## UI Contract` section in the slice's feedback-lane markdown node (exported in `slice.json` `notes[]`, so a UI build kit can look it up directly). Two things are yours to decide: *where the contract is derived from* (point the `UI Contract` section of those skills at your stack's machine-readable API description, if it has one — the `node`/`supabase` stacks use their `@openapi` blocks via a `ui-contract-from-openapi.md` reference, taking the operation verbatim — otherwise the skill writes the equivalent OpenAPI operation from the route code), and, if you need a different shape or location, a whole-skill override: ship `.claude/skills/ui-contract/SKILL.md` in the stack's templates and it replaces the shared one (stack templates are applied after `shared/skills/`).
 
 Installing both a build stack and `init-modeling` into the same project reuses this one `.eventmodelers/config.json` — run whichever `init` command second and it finds the existing config already satisfies the required fields and skips straight past the credential prompt.
 
@@ -668,7 +668,7 @@ npx @eventmodelers/cli run --handover                 # this run only — writes
 
 | | Handover off (default) | Handover on |
 |---|---|---|
-| Backend kit, STATE_VIEW / STATE_CHANGE slice | ends at `Done` | publishes the UI contract, ends at `Handover` |
+| Backend kit, STATE_VIEW / STATE_CHANGE slice | ends at `Done`, no UI contract published | publishes the UI contract, ends at `Handover` |
 | Backend kit, automation / translation | `Done` | `Done` — no UI counterpart |
 | UI kit (`react`, `supabase-react`) | claims `Handover` only | claims `Handover` only, sets `Done` when its UI is built |
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eventmodelers/cli",
-  "version": "1.0.155",
+  "version": "1.0.157",
   "description": "Eventmodelers CLI — real-time Claude agent + skills for Claude Code, for any stack (Node, Supabase, Axon, OpenCQRS, UmaDB, Kurrent, or modeling-only)",
   "type": "module",
   "bin": {

package/shared/skills/ui-contract/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ui-contract
-description: Publish the slice's UI contract — the OpenAPI operation of its endpoint (read = GET, write/state-change = POST) — as its own `## UI Contract` section in the slice's MARKDOWN node in the feedback lane, which the slice export carries in `slice.json` `notes[]` — so the UI build kit finds the contract in one lookup instead of parsing the whole note. Called by every build-state-view / build-state-change skill after the endpoint is built. A build kit can override it by shipping its own `ui-contract` skill.
+description: When handover is on (`run --handover`), publish the slice's UI contract — the OpenAPI operation of its endpoint (read = GET, write/state-change = POST) — as its own `## UI Contract` section in the slice's MARKDOWN node in the feedback lane, which the slice export carries in `slice.json` `notes[]` — so the UI build kit finds the contract in one lookup instead of parsing the whole note. Called by every build-state-view / build-state-change skill after the endpoint is built. A build kit can override it by shipping its own `ui-contract` skill.
 ---
 
 # UI Contract
@@ -18,6 +18,8 @@ records that as a contract — the endpoint's **OpenAPI operation**, one per sli
 
 ## When
 
+**Only when handover is on** — the task request's `Handover: on|off` line (authoritative; the runner resolves `run --handover` over the project setting), else `"handover": true` in `.eventmodelers/config.json`. With handover **off/unset**, do nothing: publish no contract, write no `## UI Contract` section, and finish the slice as `Done` (Step 4). The contract exists only for the UI kit that picks up `Handover` slices.
+
 At the end of building a slice, **after** the endpoint exists (so the contract describes the real
 route, not the plan), before the final commit:
 

package/stacks/axon/templates/.claude/skills/build-state-change/SKILL.md

@@ -437,7 +437,7 @@ leave it undocumented rather than fabricating an assertion.
 
 ## UI Contract
 
-Once the command endpoint is built, invoke the `ui-contract` skill (write contract, `POST`): it publishes
+**Only when handover is on** (the task's `Handover: on` line, else `"handover": true` in `.eventmodelers/config.json`; with it off, skip this section): once the command endpoint is built, invoke the `ui-contract` skill (write contract, `POST`): it publishes
 the endpoint's contract as the `## UI Contract` section of the slice's feedback-lane markdown node, which the slice export then carries in `slice.json` `notes[]`. Do not restate the format here — the skill owns it
 (a build kit may override it).
 

package/stacks/axon/templates/.claude/skills/build-state-view/SKILL.md

@@ -321,7 +321,7 @@ class {SliceName}ProjectorTest {
 
 ## UI Contract
 
-Once the read endpoint is built, invoke the `ui-contract` skill (read contract, `GET`): it publishes
+**Only when handover is on** (the task's `Handover: on` line, else `"handover": true` in `.eventmodelers/config.json`; with it off, skip this section): once the read endpoint is built, invoke the `ui-contract` skill (read contract, `GET`): it publishes
 the endpoint's contract as the `## UI Contract` section of the slice's feedback-lane markdown node, which the slice export then carries in `slice.json` `notes[]`. Do not restate the format here — the skill owns it
 (a build kit may override it).
 

package/stacks/axon/templates/build-kit/lib/backend-prompt.md

@@ -36,7 +36,7 @@ You work within **exactly ONE context at a time** — the one named in `.build-k
 10. The slice in the json is always true, the code follows what is defined in the json
 11. slice is only 'Done' if business logic is implemented as defined in the JSON, APIs are implemented, all scenarios in  JSON are implemented in code and it
     fulfills the slice.json. There must be no specification in json, that has no equivalent in code.
-12. Invoke the `ui-contract` skill for STATE_VIEW / STATE_CHANGE slices (publishes the UI Contract section to the slice's feedback-lane markdown node)
+12. Only when `handover` is on (the task's `Handover: on` line), invoke the `ui-contract` skill for STATE_VIEW / STATE_CHANGE slices; with handover off skip this step (publishes the UI Contract section to the slice's feedback-lane markdown node)
 13. Run quality checks — it is enough to run the tests for the slice only, not all tests:
     - Compile: `./mvnw compile -q`
     - Test:    `./mvnw test -Dtest="<SliceName>*" -q`

package/stacks/blank/templates/.claude/skills/build-state-change/SKILL.md

@@ -44,7 +44,7 @@ TODO — this stack's build command and how to run only this slice's tests (not
 
 ## UI Contract
 
-Once the command endpoint is built, invoke the `ui-contract` skill (write contract, `POST`): it publishes the contract
+**Only when handover is on** (the task's `Handover: on` line, else `"handover": true` in `.eventmodelers/config.json`; with it off, skip this section): once the command endpoint is built, invoke the `ui-contract` skill (write contract, `POST`): it publishes the contract
 as the `## UI Contract` section of the slice's feedback-lane markdown node, which the slice export then carries in `slice.json` `notes[]`. Do not restate the format here — the skill owns it.
 
 TODO — **Source for this stack:** say where the contract is derived from. If your stack maintains a

package/stacks/blank/templates/.claude/skills/build-state-view/SKILL.md

@@ -43,7 +43,7 @@ TODO — this stack's build command and how to run only this slice's tests (not
 
 ## UI Contract
 
-Once the read endpoint is built, invoke the `ui-contract` skill (read contract, `GET`): it publishes the contract
+**Only when handover is on** (the task's `Handover: on` line, else `"handover": true` in `.eventmodelers/config.json`; with it off, skip this section): once the read endpoint is built, invoke the `ui-contract` skill (read contract, `GET`): it publishes the contract
 as the `## UI Contract` section of the slice's feedback-lane markdown node, which the slice export then carries in `slice.json` `notes[]`. Do not restate the format here — the skill owns it.
 
 TODO — **Source for this stack:** say where the contract is derived from. If your stack maintains a

package/stacks/blank/templates/build-kit/CLAUDE.md

@@ -58,7 +58,7 @@ TODO
 
 ## UI Contract
 
-`build-state-view` and `build-state-change` end by invoking the shared `ui-contract` skill (publishes the
-slice's read/write contract for the UI build kit). Decide for your stack where it is derived from — see
+`build-state-view` and `build-state-change` end by invoking the shared `ui-contract` skill when handover is on (publishes the
+slice's read/write contract for the UI build kit; skipped with handover off). Decide for your stack where it is derived from — see
 the `UI Contract` section of those two skills — or override the skill entirely by shipping
 `.claude/skills/ui-contract/SKILL.md`.

package/stacks/blank/templates/build-kit/lib/backend-prompt.md

@@ -30,7 +30,7 @@ You work within **exactly ONE context at a time** — the one named in `.build-k
 9. Analyze and Implement that single slice, making use of the skills in the skills directory plus your previously collected knowledge. Make a TODO list for what needs to be done, and adjust the implementation according to the JSON definition. Carefully inspect events, fields and compare against the implemented slice. JSON is the desired state. ATTENTION: a "planned" task can also be just added specifications. So always look at the slice itself, but also the specifications. If specifications were added in json which are not on code, you need to add them in code.
 10. The slice in the json is always true, the code follows what is defined in the json
 11. Slice is only 'Done' if business logic is implemented as defined in the JSON, APIs are implemented, all scenarios in JSON are implemented in code and it fulfills the slice.json. There must be no specification in json that has no equivalent in code.
-12. Invoke the `ui-contract` skill for STATE_VIEW / STATE_CHANGE slices (publishes the UI Contract section to the slice's feedback-lane markdown node)
+12. Only when `handover` is on (the task's `Handover: on` line), invoke the `ui-contract` skill for STATE_VIEW / STATE_CHANGE slices; with handover off skip this step (publishes the UI Contract section to the slice's feedback-lane markdown node)
 13. Run quality checks — TODO: your stack's build command, TODO: your stack's test command (slice-scoped only; do not run all tests).
 14. If checks pass, commit ALL changes with message: `feat: [Slice Name]` and merge back to main as FF merge (update first)
 15. Update the PRD to set `status: Done` for the completed story in index.json **and** update the slice status on the eventmodelers board using the `update-slice-status` skill (or MCP if available). For STATE_VIEW/STATE_CHANGE slices when `handover` is enabled the status to set is `Handover`, not `Done` — see the `ui-contract` skill, Step 4.

package/stacks/classic/templates/.claude/skills/build-state-change/SKILL.md

@@ -103,7 +103,7 @@ After the commit, invoke `/record-evidence`: it writes this slice's element →
 
 ## UI Contract
 
-Once the command endpoint is built, invoke the `ui-contract` skill (write contract, `POST`): it publishes
+**Only when handover is on** (the task's `Handover: on` line, else `"handover": true` in `.eventmodelers/config.json`; with it off, skip this section): once the command endpoint is built, invoke the `ui-contract` skill (write contract, `POST`): it publishes
 the endpoint's contract as the `## UI Contract` section of the slice's feedback-lane markdown node, which the slice export then carries in `slice.json` `notes[]`. Do not restate the format here — the skill owns it
 (a build kit may override it).
 

package/stacks/classic/templates/.claude/skills/build-state-view/SKILL.md

@@ -107,7 +107,7 @@ After the commit, invoke `/record-evidence`: it writes this slice's element →
 
 ## UI Contract
 
-Once the read endpoint is built, invoke the `ui-contract` skill (read contract, `GET`): it publishes
+**Only when handover is on** (the task's `Handover: on` line, else `"handover": true` in `.eventmodelers/config.json`; with it off, skip this section): once the read endpoint is built, invoke the `ui-contract` skill (read contract, `GET`): it publishes
 the endpoint's contract as the `## UI Contract` section of the slice's feedback-lane markdown node, which the slice export then carries in `slice.json` `notes[]`. Do not restate the format here — the skill owns it
 (a build kit may override it).
 

package/stacks/classic/templates/build-kit/lib/backend-prompt.md

@@ -33,7 +33,7 @@ You work within **exactly ONE context at a time** — the one named in `.build-k
 9. Analyze and Implement that single slice, making use of the skills in the skills directory plus your previously collected knowledge. Make a TODO list for what needs to be done, and adjust the implementation according to the JSON definition. Carefully inspect events, fields and compare against the implemented slice. JSON is the desired state. ATTENTION: a "planned" task can also be just added specifications. So always look at the slice itself, but also the specifications. If specifications were added in json which are not on code, you need to add them in code.
 10. The slice in the json is always true, the code follows what is defined in the json
 11. Slice is only 'Done' if business logic is implemented as defined in the JSON, APIs are implemented, all scenarios in JSON are implemented in code and it fulfills the slice.json. There must be no specification in json that has no equivalent in code.
-12. Invoke the `ui-contract` skill for STATE_VIEW / STATE_CHANGE slices (publishes the UI Contract section to the slice's feedback-lane markdown node)
+12. Only when `handover` is on (the task's `Handover: on` line), invoke the `ui-contract` skill for STATE_VIEW / STATE_CHANGE slices; with handover off skip this step (publishes the UI Contract section to the slice's feedback-lane markdown node)
 13. Run the quality checks listed in `.build-kit/ARCHITECTURE.md` — build/compile, then only the tests touched by this slice (do not run all tests).
 14. If checks pass, commit ALL changes with message: `feat: [Slice Name]` and merge back to main as FF merge (update first)
 15. Invoke `/record-evidence` to write the implementation evidence (element → code mapping, files, specification → test mapping, seams, assumptions, commit) as a note into the slice's column, in the chapter's `Implementation` feedback lane.

package/stacks/kurrent/templates/.claude/skills/build-state-change/SKILL.md

@@ -406,7 +406,7 @@ assertion.
 
 ## UI Contract
 
-Once the command endpoint is built, invoke the `ui-contract` skill (write contract, `POST`): it publishes
+**Only when handover is on** (the task's `Handover: on` line, else `"handover": true` in `.eventmodelers/config.json`; with it off, skip this section): once the command endpoint is built, invoke the `ui-contract` skill (write contract, `POST`): it publishes
 the endpoint's contract as the `## UI Contract` section of the slice's feedback-lane markdown node, which the slice export then carries in `slice.json` `notes[]`. Do not restate the format here — the skill owns it
 (a build kit may override it).
 

package/stacks/kurrent/templates/.claude/skills/build-state-view/SKILL.md

@@ -381,7 +381,7 @@ undocumented rather than fabricating an assertion.
 
 ## UI Contract
 
-Once the read endpoint is built, invoke the `ui-contract` skill (read contract, `GET`): it publishes
+**Only when handover is on** (the task's `Handover: on` line, else `"handover": true` in `.eventmodelers/config.json`; with it off, skip this section): once the read endpoint is built, invoke the `ui-contract` skill (read contract, `GET`): it publishes
 the endpoint's contract as the `## UI Contract` section of the slice's feedback-lane markdown node, which the slice export then carries in `slice.json` `notes[]`. Do not restate the format here — the skill owns it
 (a build kit may override it).
 

package/stacks/kurrent/templates/build-kit/lib/backend-prompt.md

@@ -36,7 +36,7 @@ You work within **exactly ONE context at a time** — the one named in `.build-k
 10. The slice in the json is always true, the code follows what is defined in the json
 11. slice is only 'Done' if business logic is implemented as defined in the JSON, APIs are implemented, all scenarios in  JSON are implemented in code and it
     fulfills the slice.json. There must be no specification in json, that has no equivalent in code.
-12. Invoke the `ui-contract` skill for STATE_VIEW / STATE_CHANGE slices (publishes the UI Contract section to the slice's feedback-lane markdown node)
+12. Only when `handover` is on (the task's `Handover: on` line), invoke the `ui-contract` skill for STATE_VIEW / STATE_CHANGE slices; with handover off skip this step (publishes the UI Contract section to the slice's feedback-lane markdown node)
 13. Run quality checks — it is enough to run the tests for the slice only, not all tests:
     - Compile: `./mvnw compile -q`
     - Test:    `./mvnw test -Dtest="<SliceName>*" -q`

package/stacks/node/templates/.claude/skills/build-state-change/SKILL.md

@@ -419,7 +419,7 @@ import {api as {SliceName}Api} from './slices/{context}/{SliceName}/routes';
 
 ## UI Contract
 
-Once the command endpoint is built, invoke the `ui-contract` skill (write contract, `POST`): it publishes
+**Only when handover is on** (the task's `Handover: on` line, else `"handover": true` in `.eventmodelers/config.json`; with it off, skip this section): once the command endpoint is built, invoke the `ui-contract` skill (write contract, `POST`): it publishes
 the endpoint's contract as the `## UI Contract` section of the slice's feedback-lane markdown node, which the slice export then carries in `slice.json` `notes[]`. Do not restate the format here — the skill owns it
 (a build kit may override it).
 

package/stacks/node/templates/.claude/skills/build-state-view/SKILL.md

@@ -486,7 +486,7 @@ import {api as {SliceName}Api} from './slices/{context}/{SliceName}/routes';
 
 ## UI Contract
 
-Once the read endpoint is built, invoke the `ui-contract` skill (read contract, `GET`): it publishes
+**Only when handover is on** (the task's `Handover: on` line, else `"handover": true` in `.eventmodelers/config.json`; with it off, skip this section): once the read endpoint is built, invoke the `ui-contract` skill (read contract, `GET`): it publishes
 the endpoint's contract as the `## UI Contract` section of the slice's feedback-lane markdown node, which the slice export then carries in `slice.json` `notes[]`. Do not restate the format here — the skill owns it
 (a build kit may override it).
 

package/stacks/node/templates/build-kit/lib/backend-prompt.md

@@ -32,7 +32,7 @@ You work within **exactly ONE context at a time** — the one named in `.build-k
 10. The slice in the json is always true, the code follows what is defined in the json
 11. slice is only 'Done' if business logic is implemented as defined in the JSON, APIs are implemented, all scenarios in  JSON are implemented in code and it
     fulfills the slice.json. There must be no specification in json, that has no equivalent in code.
-12. Invoke the `ui-contract` skill for STATE_VIEW / STATE_CHANGE slices (publishes the UI Contract section to the slice's feedback-lane markdown node)
+12. Only when `handover` is on (the task's `Handover: on` line), invoke the `ui-contract` skill for STATE_VIEW / STATE_CHANGE slices; with handover off skip this step (publishes the UI Contract section to the slice's feedback-lane markdown node)
 13. Run quality checks ( npm run build, npm run test ) - Attention - it´s enough to run the tests for the slice. Do not run all tests.
 14. even if the slice is fully implemented, run your test-analyzer skill and provide the code-slice.json file as defined in the skill
 15. If checks pass, commit ALL changes with message: `feat: [Slice Name]` and merge back to main as FF merge ( update

package/stacks/node/templates/root/package.json

@@ -7,7 +7,7 @@
     "dev": "node --env-file=.env --require ts-node/register server.ts",
     "build": "tsc",
     "start": "NODE_ENV=production node --env-file=.env --require ts-node/register server.ts",
-    "test": "tsx --test 'src/**/*.test.ts'",
+    "test": "tsx --test \"src/**/*.test.ts\"",
     "run:checks": "node .build-kit/lib/check-commit-scope.cjs"
   },
   "dependencies": {

package/stacks/node/templates/root/server.ts

@@ -16,15 +16,15 @@ async function startServer() {
     const slicesBase = join(__dirname, 'dist/src/slices');
     const routesPattern = join(slicesBase, '**/routes{,-*}.js');
 
-    const routeFiles = await glob(routesPattern, {nodir: true});
+    const routeFiles = await glob(routesPattern, {nodir: true, windowsPathsNoEscape: true});
     console.log('Found route files:', routeFiles);
 
     const processorPattern = join(slicesBase, '**/processor{,-*}.js');
-    const processorFiles = await glob(processorPattern, {nodir: true});
+    const processorFiles = await glob(processorPattern, {nodir: true, windowsPathsNoEscape: true});
     console.log('Found processor files:', processorFiles);
 
     const commonPattern = join(__dirname, 'src/common/routes{,-*}.@(ts|js)');
-    const commonRouteFiles = await glob(commonPattern, {nodir: true});
+    const commonRouteFiles = await glob(commonPattern, {nodir: true, windowsPathsNoEscape: true});
     console.log('Found common route files:', commonRouteFiles);
 
 

package/stacks/opencqrs/templates/.claude/skills/build-state-change/SKILL.md

@@ -401,7 +401,7 @@ leave it undocumented rather than fabricating an assertion.
 
 ## UI Contract
 
-Once the command endpoint is built, invoke the `ui-contract` skill (write contract, `POST`): it publishes
+**Only when handover is on** (the task's `Handover: on` line, else `"handover": true` in `.eventmodelers/config.json`; with it off, skip this section): once the command endpoint is built, invoke the `ui-contract` skill (write contract, `POST`): it publishes
 the endpoint's contract as the `## UI Contract` section of the slice's feedback-lane markdown node, which the slice export then carries in `slice.json` `notes[]`. Do not restate the format here — the skill owns it
 (a build kit may override it).
 

package/stacks/opencqrs/templates/.claude/skills/build-state-view/SKILL.md

@@ -344,7 +344,7 @@ test — leave it undocumented in code rather than fabricating an assertion.
 
 ## UI Contract
 
-Once the read endpoint is built, invoke the `ui-contract` skill (read contract, `GET`): it publishes
+**Only when handover is on** (the task's `Handover: on` line, else `"handover": true` in `.eventmodelers/config.json`; with it off, skip this section): once the read endpoint is built, invoke the `ui-contract` skill (read contract, `GET`): it publishes
 the endpoint's contract as the `## UI Contract` section of the slice's feedback-lane markdown node, which the slice export then carries in `slice.json` `notes[]`. Do not restate the format here — the skill owns it
 (a build kit may override it).
 

package/stacks/opencqrs/templates/build-kit/lib/backend-prompt.md

@@ -36,7 +36,7 @@ You work within **exactly ONE context at a time** — the one named in `.build-k
 10. The slice in the json is always true, the code follows what is defined in the json
 11. slice is only 'Done' if business logic is implemented as defined in the JSON, APIs are implemented, all scenarios in  JSON are implemented in code and it
     fulfills the slice.json. There must be no specification in json, that has no equivalent in code.
-12. Invoke the `ui-contract` skill for STATE_VIEW / STATE_CHANGE slices (publishes the UI Contract section to the slice's feedback-lane markdown node)
+12. Only when `handover` is on (the task's `Handover: on` line), invoke the `ui-contract` skill for STATE_VIEW / STATE_CHANGE slices; with handover off skip this step (publishes the UI Contract section to the slice's feedback-lane markdown node)
 13. Run quality checks — it is enough to run the tests for the slice only, not all tests:
     - Compile: `./mvnw compile -q`
     - Test:    `./mvnw test -Dtest="<SliceName>*" -q`

package/stacks/supabase/templates/.claude/skills/build-state-change/SKILL.md

@@ -426,7 +426,7 @@ import {api as {SliceName}Api} from './slices/{context}/{SliceName}/routes';
 
 ## UI Contract
 
-Once the command endpoint is built, invoke the `ui-contract` skill (write contract, `POST`): it publishes
+**Only when handover is on** (the task's `Handover: on` line, else `"handover": true` in `.eventmodelers/config.json`; with it off, skip this section): once the command endpoint is built, invoke the `ui-contract` skill (write contract, `POST`): it publishes
 the endpoint's contract as the `## UI Contract` section of the slice's feedback-lane markdown node, which the slice export then carries in `slice.json` `notes[]`. Do not restate the format here — the skill owns it
 (a build kit may override it).
 

package/stacks/supabase/templates/.claude/skills/build-state-view/SKILL.md

@@ -461,7 +461,7 @@ import {api as {SliceName}Api} from './slices/{context}/{SliceName}/routes';
 
 ## UI Contract
 
-Once the read endpoint is built, invoke the `ui-contract` skill (read contract, `GET`): it publishes
+**Only when handover is on** (the task's `Handover: on` line, else `"handover": true` in `.eventmodelers/config.json`; with it off, skip this section): once the read endpoint is built, invoke the `ui-contract` skill (read contract, `GET`): it publishes
 the endpoint's contract as the `## UI Contract` section of the slice's feedback-lane markdown node, which the slice export then carries in `slice.json` `notes[]`. Do not restate the format here — the skill owns it
 (a build kit may override it).
 

package/stacks/supabase/templates/build-kit/lib/backend-prompt.md

@@ -32,7 +32,7 @@ You work within **exactly ONE context at a time** — the one named in `.build-k
 10. The slice in the json is always true, the code follows what is defined in the json
 11. slice is only 'Done' if business logic is implemented as defined in the JSON, APIs are implemented, all scenarios in  JSON are implemented in code and it
     fulfills the slice.json. There must be no specification in json, that has no equivalent in code.
-12. Invoke the `ui-contract` skill for STATE_VIEW / STATE_CHANGE slices (publishes the UI Contract section to the slice's feedback-lane markdown node)
+12. Only when `handover` is on (the task's `Handover: on` line), invoke the `ui-contract` skill for STATE_VIEW / STATE_CHANGE slices; with handover off skip this step (publishes the UI Contract section to the slice's feedback-lane markdown node)
 13. Run quality checks ( npm run build, npm run test ) - Attention - it´s enough to run the tests for the slice. Do not run all tests.
 14. even if the slice is fully implemented, run your test-analyzer skill and provide the code-slice.json file as defined in the skill
 15. If checks pass, commit ALL changes with message: `feat: [Slice Name]` and merge back to main as FF merge ( update

package/stacks/supabase/templates/root/package.json

@@ -7,7 +7,7 @@
     "dev": "node --env-file=.env --require ts-node/register server.ts",
     "build": "tsc",
     "start": "NODE_ENV=production node --env-file=.env --require ts-node/register server.ts",
-    "test": "tsx --test 'src/**/*.test.ts'",
+    "test": "tsx --test \"src/**/*.test.ts\"",
     "run:checks": "node .build-kit/lib/check-commit-scope.cjs"
   },
   "dependencies": {

package/stacks/supabase/templates/root/server.ts

@@ -17,11 +17,11 @@ async function startServer() {
     const slicesBase = join(__dirname, 'dist/src/slices');
     const routesPattern = join(slicesBase, '**/routes{,-*}.js');
 
-    const routeFiles = await glob(routesPattern, {nodir: true});
+    const routeFiles = await glob(routesPattern, {nodir: true, windowsPathsNoEscape: true});
     console.log('Found route files:', routeFiles);
 
     const processorPattern = join(slicesBase, '**/processor{,-*}.js');
-    const processorFiles = await glob(processorPattern, {nodir: true});
+    const processorFiles = await glob(processorPattern, {nodir: true, windowsPathsNoEscape: true});
     console.log('Found processor files:', processorFiles);
 
     // Common routes (e.g. projection replay) are privileged/operational and are
@@ -29,7 +29,7 @@ async function startServer() {
     const commonRoutesEnabled = process.env.COMMON_ROUTES_ENABLED === 'true';
     const commonPattern = join(__dirname, 'src/common/routes{,-*}.@(ts|js)');
     const commonRouteFiles = commonRoutesEnabled
-        ? await glob(commonPattern, {nodir: true})
+        ? await glob(commonPattern, {nodir: true, windowsPathsNoEscape: true})
         : [];
     console.log(commonRoutesEnabled
         ? `Found common route files: ${commonRouteFiles}`

package/stacks/umadb/templates/.claude/skills/build-state-change/SKILL.md

@@ -366,7 +366,7 @@ fabricating an assertion.
 
 ## UI Contract
 
-Once the command endpoint is built, invoke the `ui-contract` skill (write contract, `POST`): it publishes
+**Only when handover is on** (the task's `Handover: on` line, else `"handover": true` in `.eventmodelers/config.json`; with it off, skip this section): once the command endpoint is built, invoke the `ui-contract` skill (write contract, `POST`): it publishes
 the endpoint's contract as the `## UI Contract` section of the slice's feedback-lane markdown node, which the slice export then carries in `slice.json` `notes[]`. Do not restate the format here — the skill owns it
 (a build kit may override it).
 

package/stacks/umadb/templates/.claude/skills/build-state-view/SKILL.md

@@ -330,7 +330,7 @@ events to it in production exactly as it does for the already-verified slices.
 
 ## UI Contract
 
-Once the read endpoint is built, invoke the `ui-contract` skill (read contract, `GET`): it publishes
+**Only when handover is on** (the task's `Handover: on` line, else `"handover": true` in `.eventmodelers/config.json`; with it off, skip this section): once the read endpoint is built, invoke the `ui-contract` skill (read contract, `GET`): it publishes
 the endpoint's contract as the `## UI Contract` section of the slice's feedback-lane markdown node, which the slice export then carries in `slice.json` `notes[]`. Do not restate the format here — the skill owns it
 (a build kit may override it).
 

package/stacks/umadb/templates/build-kit/lib/backend-prompt.md

@@ -36,7 +36,7 @@ You work within **exactly ONE context at a time** — the one named in `.build-k
 10. The slice in the json is always true, the code follows what is defined in the json
 11. slice is only 'Done' if business logic is implemented as defined in the JSON, APIs are implemented, all scenarios in  JSON are implemented in code and it
     fulfills the slice.json. There must be no specification in json, that has no equivalent in code.
-12. Invoke the `ui-contract` skill for STATE_VIEW / STATE_CHANGE slices (publishes the UI Contract section to the slice's feedback-lane markdown node)
+12. Only when `handover` is on (the task's `Handover: on` line), invoke the `ui-contract` skill for STATE_VIEW / STATE_CHANGE slices; with handover off skip this step (publishes the UI Contract section to the slice's feedback-lane markdown node)
 13. Run quality checks — it is enough to run the tests for the slice only, not all tests:
     - Compile: `./mvnw compile -q`
     - Test:    `./mvnw test -Dtest="<SliceName>*" -q`