@cratis/pi 7.20.0 → 7.22.0

package/package/corpus/skills/cratis-screenplay-specifications/SKILL.md

@@ -37,15 +37,12 @@ The update follows `commands.md`, `events.md`, `types.md` and
 `specifications.md` at that main commit (after v4.52.0). This pass compiles the
 changed examples; it does not rerun the reference runner.
 
-**Which tool says what.** The standalone `screenplay` tool 4.68.0 admits ESM v1-v7.
-The `cratis` CLI 3.28.2 and 3.28.3 bundle Screenplay 4.66.0 (ESM v1-v6: generated fixtures and `then returns` report `PLAY0268`). Before `cratis` 3.28.2 the
-bundle was Screenplay 4.60.1, which admitted ESM v1-v5 only and reported a false
-`PLAY0285` on reaction cascades (see "Version skew" in [references/reactions-and-cascades.md](references/reactions-and-cascades.md)). Facts below marked **ESM v6**
-hold for Screenplay 4.61.0 and later: the standalone tool and `cratis` 3.28.2 or later. The full table is in `cratis-screenplay-toolchain`
-(`references/versions.md`; read it before choosing a compiler or interpreting version-dependent binding diagnostics). Neither tool runs specifications: `screenplay` and
-`cratis screenplay validate` parse and check consistency, the MCP server also binds,
-and spec outcomes come only from the reference runner as a library, Stage's
-specification runner or a rendered application's tests.
+Current specification syntax follows Screenplay v4.125.0 `specifications.md`;
+older probes in the table remain historical. Pins: `cratis-screenplay-toolchain`
+`references/versions.md`. Compile commands check source, not reference execution.
+Use `screenplay test` or MCP `run-specifications` for V4; Stage/target tests are
+separate evidence. Unsupported/unbound is never a pass. Typed examples and
+route assertions are in [examples and routes](references/examples-and-routes.md).
 
 Checked against the Screenplay repository at tag `v4.31.0` (commit `355dffb`):
 `Documentation/screenplay/{specifications,policies,constraints,readmodels,diagnostics}.md`.
@@ -95,9 +92,8 @@ target has one normalized behavior to match.
   rejects, the earlier accepted facts and their projections remain.
 
 Unsupported is not passed. Report it as "needs a target", not as green. "Specified"
-and "bound" are never "passing": no command-line tool runs these specifications, so a
-pass is claimed only from the reference runner, Stage's specification runner or a
-rendered application's tests, and named as such.
+and "bound" are never "passing": run the reference CLI/MCP route or the owning
+target tests, and name the engine, version and expected/discovered selection.
 
 ## The vocabulary
 
@@ -184,7 +180,7 @@ Read [references/worked-example.md](references/worked-example.md) when writing o
 
 ## Generated fixtures and return expectations (ESM v7)
 
-Standalone `screenplay` 4.68.0 or later binds and runs generated fixtures (`generated <name> = <value>`, `for` beneath `when`) and `then returns`; the cratis CLI 3.28.3 does not. If execution reaches generation without every generated value supplied, the run is unsupported and never passes.
+Current standalone and bundled compilers bind generated fixtures (`generated <name> = <value>`, `for` beneath `when`) and `then returns` as ESM v7. If execution reaches generation without every generated value supplied, the run is unsupported and never passes.
 Read [references/generated-fixtures.md](references/generated-fixtures.md) when writing generated-value fixtures or scalar and record return expectations for a command.
 
 ## Actions beyond commands
@@ -197,6 +193,18 @@ Read [references/actions-beyond-commands.md](references/actions-beyond-commands.
 From ESM v6 every action sets reactions off and `then` events compare every new fact, the action's and the reactions'. A specification whose action is a command goes in the slice that declares the command. A false `PLAY0285` on a cascade under `cratis` before 3.28.2 is tool skew, not a modeling error: never delete the `then` line to silence it.
 Read [references/reactions-and-cascades.md](references/reactions-and-cascades.md) when a specification's expected events include what a reaction appends, when a cascade, clock tick or invoked command is involved, or when `cratis` reports `PLAY0285` on a model that `screenplay` accepts (it holds the "Version skew: cascades and the false `PLAY0285` (cratis before 3.28.2)" section).
 
+## Reusable fixtures, routes and recovery intent
+
+Use typed `example` declarations for repeated event/command/read-model values;
+step overrides keep the action/outcome visible and carry authored/example/override
+provenance. Event `stream`/`no stream` assertions bind as ESM v8; typed `for` and
+stream ids are not guessed. Read [examples and routes](references/examples-and-routes.md).
+
+`given operation ... fails`, `then operation` and `then compensated` describe
+future external-work behavior. Reaction refusal branches, `when redelivered`
+and `then no events` are also authoring-only: compile them, but report their
+PLAY0268 binding refusal instead of an executed result. Preserve the contract.
+
 ## Rejections and denials say different things
 
 `then error "<message>"` says **rejected, for this reason** — pin it when the
@@ -252,9 +260,9 @@ For view specifications:
 
 ## Verify
 
-- [ ] `screenplay <model> --warnaserror` reports zero errors and zero warnings
-      (standalone 4.68.0 or `cratis` 3.28.2 or later, bundling 4.66.0; under `cratis` before 3.28.2 expect the false
-      `PLAY0285` on reaction cascades and record that it is skew).
+- [ ] Validate the complete root with warnings as errors, naming tool/version.
+      Current standalone pin: 4.125.0. Run specification examples through
+      `screenplay test`; expected unadmitted syntax reports unbound, not passed.
 - [ ] Executable diagnostics are clean too: `PLAY0350`, `PLAY0352`, `PLAY0388`,
       `PLAY0389` and `PLAY0273` are only reported at binding.
 - [ ] Every slice has at least one boundary specification.

package/package/corpus/skills/cratis-screenplay-specifications/references/examples-and-routes.md

@@ -0,0 +1,103 @@
+<!-- Copyright (c) Cratis. All rights reserved. -->
+<!-- Licensed under the MIT license. See LICENSE file in the project root for full license information. -->
+
+# Typed examples, overrides and event routes
+
+## Contents
+
+- Typed examples
+- Effective values
+- Event routes
+- Operation and recovery intent
+
+## Typed examples
+
+`example <Name> : <EventOrCommandOrReadModel>` declares a possibly partial typed
+fixture at document/module/feature/slice scope. Its underlying type resolves in
+the declaration scope, not the use scope. It can state properties, description,
+`for` and command generated fixtures, not callers/clocks or a whole scenario.
+Examples share the type namespace and use the current event generation. They
+cannot inherit from examples or serve as query results/returns/trigger/capture
+fixtures. They are specification data, not operational `seed` events.
+
+This complete example compiled and its two reference scenarios passed on 4.125.0:
+
+```screenplay
+concept ProjectId : Uuid
+module Projects
+  feature Registration
+    example DefaultProject : RegisterProject
+      name = "Default"
+    slice StateChange Register
+      command RegisterProject
+        projectId ProjectId identifier
+        name String
+        produces event ProjectRegistered
+          name String = name
+      specification RegisteringTheDefault
+        when DefaultProject
+          projectId = "3fa85f64-5717-4562-b3fc-2c963f66afa6"
+        then ProjectRegistered
+          for "3fa85f64-5717-4562-b3fc-2c963f66afa6"
+          name = "Default"
+      specification OverridingTheName
+        when DefaultProject name = "Override"
+          projectId = "3fa85f64-5717-4562-b3fc-2c963f66afa6"
+        then ProjectRegistered
+          for "3fa85f64-5717-4562-b3fc-2c963f66afa6"
+          name = "Override"
+```
+
+## Effective values
+
+An example occupies the ordinary name slot in given/event, given readmodel,
+when command, when append, then event or then readmodel. One assignment may be
+inline after the name; more stay indented. There is **no with keyword**.
+Step values override example values by property name; objects/lists replace
+whole values, never recursively merge. Indented `for` replaces its destination;
+generated fixtures merge by name. A new step-only value is authored, not an
+override. Each step/declaration assigns a property once (PLAY0519); malformed
+headers are PLAY0518.
+
+After expansion, required given-event/read-model, command, append and expected
+event fields must be complete (binding PLAY0524); examples can remain partial.
+Read-model assertions retain subset matching unless `exactly` is authored.
+Even unused example values or values overridden at every use are type-checked.
+No default fixture values are invented. A command action must belong to the
+specification's own slice even when a qualified example resolves elsewhere.
+
+MCP `find-fixtures` reports effective authored/example/override origins and
+replaced values. Source-bound runner failures retain that provenance; canonical
+ESM contains merged values only, equivalent to hand-expansion. ESM-only runners
+cannot reconstruct source origins.
+
+## Event routes
+
+Event occurrences in `given`, `when append` and `then` accept `stream Source.Stream`
+with nested scalar `streamId = <literal>` or a complete composite part block.
+These select ESM v8 and reference-execute at 4.125.0; the complete checked model
+is in toolchain `references/sources-and-streams.md`. Command actions take their
+route from the command declaration, never the fixture.
+
+Routed history/appends need typed concrete `for`; routed expectations may omit
+it. `then ... no stream` expects no route; no route in a then is a wildcard.
+`no stream` is invalid on given/appends. Event examples can supply routes, but
+steps replace the entire route, independently of `for`; an inherited route
+cannot be changed back to a wildcard. Literal compatibility/route contradiction
+checks use resolved source/stream types, not guessed text (PLAY0547–PLAY0551).
+CLI 3.41.0 rendering rejects versions above v7 before planning, even though
+source compilation and reference routing pass.
+
+## Operation and recovery intent
+
+Operation failure/request/compensation forms are authoring-only (PLAY0268):
+`given operation <Name> fails`, `then operation <Name>` with a partial input
+subset, and leaf `then compensated <Name>`. See command-surface
+`references/operations.md` for the complete checked authoring fixture.
+
+Refusal selectors, redelivery to one observer and `then no events` likewise
+remain unadmitted; they are not executed append scenarios. Forms, matching,
+acknowledgement and their whole-model refusal boundary are in
+captures-and-reactions `references/refusals-and-redelivery.md`.
+
+Authority: Screenplay `v4.125.0:Documentation/screenplay/specifications.md`.

package/package/corpus/skills/cratis-screenplay-specifications/references/reactions-and-cascades.md

@@ -42,12 +42,11 @@ module Collections
 - A specification whose action is a command goes in the slice that declares that
   command, here `SendInvoice`, not in the `Automation` slice that reacts: a command
   from another slice is `PLAY0273` "command is unresolved in its slice" at binding.
-- A command a reaction `invokes` runs through its full pipeline **with no caller**.
-  A command that needs one rejects, and that rejection ends the scenario. Each
-  invoked command is atomic; the cascade is not, so earlier accepted facts stay.
-  There is no syntax for an identity (Screenplay#383). See
-  `cratis-screenplay-automations-and-translations` and
-  `cratis-screenplay-captures-and-reactions`.
+- A reaction invocation without a declared actor has no caller and a gated
+  command denies. At 4.125.0 reaction `runs as system role "<Role>"` supplies the
+  authenticated system actor (ESM v10); `given caller` does not. Each command is
+  atomic, not the cascade. Checked actor scenario and CLI/Stage limitations:
+  captures-and-reactions `references/invocation-identity.md`.
 - The clock is UTC and exact. An `every` or `at` occurrence fires once when it is
   due after `given clock` and at or before `when clock`; `when clock` needs
   `given clock`, so the same instant twice fires nothing.

package/package/corpus/skills/cratis-screenplay-streams-and-consistency/SKILL.md

@@ -87,10 +87,10 @@ option, mark it `ASSUMED` in the slice or module `description` and in the sessio
    invariant consequences, not names or length. For Chronicle keep event-source identity,
    namespace, process-stream routing and concurrency scope apart
    (`references/chronicle-boundaries.md`). Declared `eventsource`/`stream`/`streamId` and
-   command routes can be authored and validated but not bound, run or rendered today
-   (`PLAY0268`, `STAGE-ESM-016`): keep them as intent and hand-write the routing
-   (`cratis-screenplay-toolchain` `references/sources-and-streams.md`); no supported ESM version
-   admits them. A `generated identifier` (ESM v7, standalone 4.68.0; not rendered by Stage yet) is
+   command/specification routes bind and reference-execute as ESM v8 on 4.125.0.
+   CLI 3.41.0 rendering admits through v7 only (CLI-RENDER-004); keep the routing
+   contract and gap-fill its target realization. Forms/boundaries:
+   toolchain `references/sources-and-streams.md`. A `generated identifier` (ESM v7, standalone 4.68.0; not rendered by Stage yet) is
    generated fresh on every acceptance: it is not a retry identity, and generated values give no
    idempotency, retry or deduplication guarantee. When a retry must find the same stream, the caller
    supplies the identifier before the first attempt.

package/package/corpus/skills/cratis-screenplay-streams-and-consistency/references/stream-patterns.md

@@ -205,8 +205,10 @@ Ask for each stream:
 Some event stores decide consistency by a query over tagged events instead of one stream
 (often called dynamic consistency boundaries). Chronicle's concurrency scopes can narrow a
 check to event types, source type or stream (`concurrency` block, Screenplay
-`commands.md`), and Screenplay has syntax-only event-source/stream declarations (not admitted by any supported ESM version;
-`event-sources.md`). None of this binds on either compiler (`versions.md` in `cratis-screenplay-toolchain`). Model the stream by business
+`commands.md`). Legacy concurrency metadata still fails binding (PLAY0271),
+but sources/streams/routes bind and reference-execute as ESM v8 on 4.125.0.
+Route admission does not make a view read protected. CLI 3.41.0's render boundary
+is v7; see toolchain `references/versions.md`. Model the stream by business
 identity; when a rule truly needs a cross-stream decision, record it (see
 `consistency-and-concurrency.md`) rather than inventing a construct.
 

package/package/corpus/skills/cratis-screenplay-streams-and-consistency/verification.json

@@ -12,9 +12,9 @@
     { "kind": "skill-contains", "value": "CHR0034" },
     { "kind": "skill-contains", "value": "No calculated events" },
     { "kind": "skill-contains", "value": "decision tree and red flags" },
-    { "kind": "skill-contains", "value": "not bound, run or rendered" },
+    { "kind": "skill-contains", "value": "bind and reference-execute as ESM v8" },
     { "kind": "skill-contains", "value": "STAGE-ESM-026" },
     { "kind": "skill-contains", "value": "generated values give no\n   idempotency, retry or deduplication guarantee" },
-    { "kind": "skill-contains", "value": "no supported ESM version\n   admits them" }
+    { "kind": "skill-contains", "value": "CLI-RENDER-004" }
   ]
 }

package/package/corpus/skills/cratis-screenplay-toolchain/SKILL.md

@@ -22,17 +22,16 @@ files is one application: always check the folder, never one file of it.
 
 When choosing or upgrading a tool, or checking version-specific capabilities, read `references/versions.md`; it is the only version table, and other skills point to it.
 
-| Package | Version | Purpose |
-| --- | --- | --- |
-| `Cratis.Screenplay.Tool` | `4.68.0` (`79801bf`) | standalone compiler, binder and MCP server; admits ESM v7 (generated values and responses) |
-| cratis CLI | `3.40.7` (`v3.40.7`, `af9f18e`) | Tag pins Stage 4.51.1 and Screenplay 4.114.0, with `cratis/stage:4.51.1` as the runtime image. The public CLI executed render publication, the browser acceptance run and the real stdio MCP transcript harness (37 tools, `executableReady true`). Reading baselines: 3.40.3, 3.39.0 and 3.28.3 (`8b43fef`) |
-| Screenplay | bundled `4.114.0`; latest language package `4.122.0` | CLI 3.40.7 bundles 4.114.0 and reports `sourceSuccess true`, `semanticSuccess true`, `executableReady true` for the canonical corpus; the repo tool compiles it with `10 file(s) compiled - 0 error(s), 0 warning(s)`. Language features newer than 4.114.0 need the standalone 4.122.0 tool until a CLI bundles them |
-| Stage | `4.51.1` (CLI default; latest package 4.51.3) | Docker image `cratis/stage:4.51.1`; renders the canonical screen corpus with Arc `CommandForm` shells and query bindings, and refuses guarded Close and double-click with `STAGE-SCENE-ACTION-001` / `STAGE-SCENE-INTERACTION-001`. Check generated package sets before claiming exact Scene 4.14 runtime parity |
-| Arc / Chronicle | `22.50.5` / `19.32.0` | code-level facts cited here |
+The standalone pin is Screenplay 4.125.0. CLI 3.41.0 bundles Screenplay 4.114.0,
+Stage 4.51.3 and Cratis.Arc.Screenplay 22.54.0. The single version table records
+released source evidence and historical probes separately; do not relabel an old
+render/browser result as a probe of the current packages.
 
-Facts were read with `git show <tag>:<path>` and probed on the installed tools. Behaviour
-was probed on 4.63.1 and re-checked on 4.66.0 and 4.68.0 (the example gates). 4.65.0 adds command named-rule `implementation` blocks (handlers and operation phases already had the wrapper; it is rejected on concept rules, built-in property rules and whole-command `require`/`validate` bodies); 4.66.0 is editor tooling only. Neither changes execution.
-Re-verify before claiming another version behaves the same.
+Historical screens-release evidence: CLI 3.40.7 / Stage 4.51.1 / bundled
+Screenplay 4.114.0 opened the canonical corpus with `executableReady true`
+and the stdio transcript exposed 37 tools; standalone language 4.122.0 was
+recorded in that vector. These retained results are not a rerun on CLI 3.41.0
+or Screenplay 4.125.0.
 
 ## Ground rules
 
@@ -42,10 +41,10 @@ Re-verify before claiming another version behaves the same.
 2. **Check the folder, warnings as errors.** `screenplay <folder> --warnaserror` or
    `cratis screenplay validate <folder> --warnings-as-errors`. Warnings hide defects:
    PLAY0029 (a misspelt keyword or a `type` inside a slice) drops a construct silently.
-3. **Pick the compiler deliberately and name it.** Standalone `screenplay` for V1 to V3 (file
-   mode follows imports); `cratis` 3.28.2 or later bundles the 4.66.0 compiler (same up to ESM v6, no ESM v7) and is the
-   route for `render`. A cratis before 3.28.2 bundle (4.60.1) rejects ESM v6 and reports a
-   false PLAY0285 on cascades (cli#242). Report tool and version with every verdict.
+3. **Pick the compiler deliberately and name it.** Standalone `screenplay` for
+   current language checks and reference specifications; `cratis` for rendering
+   and generation. Bundled and standalone versions differ. Report both tool and
+   version, rather than transferring a verdict across releases.
 4. **Know the mode** (design, executable, renderable) and write from its subset.
 5. **Capability is not correctness.** The tool you ran decides what is accepted today; the
    domain and the documented semantics decide what is correct. On conflict keep the correct
@@ -62,14 +61,13 @@ Re-verify before claiming another version behaves the same.
 
 ## The two compilers
 
-| | Standalone `screenplay` 4.68.0 | `cratis screenplay ...` 3.28.3 and 3.28.2 (bundle Screenplay 4.66.0) |
+| | Standalone `screenplay` | `cratis screenplay ...` |
 | --- | --- | --- |
-| Check a folder | `screenplay <folder> --warnaserror --no-color` (exit 0 pass, 1 fail; an empty folder also exits 0, so read "N file(s) compiled") | `cratis screenplay validate <folder> --warnings-as-errors -o json-compact` (0 pass, 5 fail, 1 missing path or no files) |
-| ESM admitted | v1 to v7 | v1 to v6 (generated values and responses report `PLAY0268`; before 3.28.2 bundled 4.60.1: v1 to v5) |
-| Automation, Translate, reactions, captures, clocks, triggers | bind | bind (before 3.28.2: PLAY0268 "Slice '<name>' of type '<type>' is not admitted by ESM v1.") |
-| Cascade specs | compile | compile (before 3.28.2: false PLAY0285, cli#242) |
-| File argument | follows imports | ignores imports, false PLAY0165 warnings (cli#244, probed on 3.28.2): validate the folder |
-| MCP | `screenplay mcp <folder>`; 29 tools | `cratis screenplay mcp [root]`; 29 tools; registered by `cratis ai install` |
+| Check root | `screenplay <root> --warnaserror --no-color` | `cratis screenplay validate <root> --warnings-as-errors -o json-compact` |
+| Scope/checks | `--scope <address>`, `--check <names>`; a scoped pass is not whole-application success | Discover installed validation options |
+| Reference execution | `screenplay test <root>` or MCP `run-specifications` | Discover bundled MCP capability; target tests are not V4 |
+| MCP | `screenplay mcp <root>`; discover schemas | `cratis screenplay mcp [root]`; registered by `cratis ai install` |
+| Render version boundary | Binder admission is not Stage admission | CLI 3.41.0 passes up to ESM v7 to Stage; newer versions: `CLI-RENDER-004` |
 
 Read `references/versions.md` when you need the exact messages, exit codes or the MCP roots bug.
 
@@ -84,7 +82,7 @@ Independent results, not a ladder. Read `references/verdicts.md` for the command
 | V1 | authorable (compiles, warnings as errors) | the folder command above |
 | V2 | executable diagnostics read | MCP `open-workspace`, then `read-workspace view=executable-diagnostics` |
 | V3 | binding-ready (binds, no blocking executable diagnostics) | `executableReady` true and no error-severity diagnostic in V2; informational PLAY0269/0270 are reported separately |
-| V4 | reference specifications run | the Screenplay reference execution route only (none ships in the pinned tools: `V4 not run: no route`); rendered Debug tests are V5.tests, never V4 |
+| V4 | reference specifications run | `screenplay test` or MCP `run-specifications`; unsupported/unbound is not a pass; rendered Debug tests are V5.tests, never V4 |
 | V5 | rendered and target-verified | `cratis render`, then Debug build and tests; report admission, publication, build and tests separately |
 
 V2 and V3 need MCP: send `initialize`, then `notifications/initialized`, and start the
@@ -105,12 +103,14 @@ changes with the root folder name.
   only; no handler (PLAY0268, with or without `implementation`/`hint`); `reads` and
   `concurrency` do not bind (PLAY0271); no `@pii`; v6 constructs bind on Screenplay 4.61 or
   later (standalone, and cratis 3.28.2 or later); generated values and `returns` responses bind (ESM v7)
-  only on standalone 4.68.0 or later (`references/generated-responses-example.md`). Read [references/executable-example.md](references/executable-example.md) when you need a small StateChange and StateView model that binds executable, [references/pdl-example.md](references/pdl-example.md) when writing projection forms that bind and run, and [references/automation-translate-example.md](references/automation-translate-example.md) when writing Automation and Translate slices (ESM v6).
-- **Renderable** (V5): `references/renderable-subset.md`. Stage 4.24.2 renders ESM v1 to v4 (evolved events refused, `STAGE-ESM-026`)
-  `StateChange`/`StateView` slices; Automation and Translate are gap-fill (Stage#79), and so are generated values and responses (ESM v7: Stage refuses it with `STAGE-ESM-016`, tracked in Stage#201).
-- **Event sources, streams and command routes** (and operations): authorable and validatable, but never
-  bound (`PLAY0268`: not admitted by any supported ESM version), run or rendered
-  (`STAGE-ESM-016`); gap-fill with the model as contract (`references/sources-and-streams.md`).
+  from Screenplay 4.68.0 (also in the current CLI bundle) (`references/generated-responses-example.md`). Read [references/executable-example.md](references/executable-example.md) when you need a small StateChange and StateView model that binds executable, [references/pdl-example.md](references/pdl-example.md) when writing projection forms that bind and run, and [references/automation-translate-example.md](references/automation-translate-example.md) when writing Automation and Translate slices (ESM v6).
+- **Renderable** (V5): `references/renderable-subset.md` retains explicitly labeled
+  older Stage probes. Current CLI admits v7 to planning, but its v7 corpus gets
+  Stage generated-value/response refusals `STAGE-ESM-028`/`029`, not a blanket
+  compiler refusal. Run admission before claiming a particular model renders.
+- **Event sources, streams and routes** bind as ESM v8 at 4.125.0; CLI 3.41.0
+  render refuses versions above v7 (`CLI-RENDER-004`). Operations and exact numeric
+  mode remain authorable/unadmitted. Details: `references/sources-and-streams.md`.
 
 ## Edit strategy
 
@@ -144,10 +144,12 @@ Read [references/diagnostics.md](references/diagnostics.md) when a PLAY, STAGE o
 2. Write `for <identifier>` on every `produces`.
 3. PLAY0029 is a warning: validate with warnings as errors.
 4. Validate the folder; name the compiler (cli#244, cli#242).
-5. Mappings to undeclared projection targets and undeclared events in `remove with`/capture
-   `append` pass V1 and fail binding (V2/V3, PLAY0273); a declared read-model property that
-   nothing maps is reported by no tool: run V3 and walk field lineage by hand.
-6. A reaction's `invokes` has no caller: a gated command rejects it; keep the gate.
+5. V1 warns on undeclared projection targets (`PLAY0514`) and removal/capture
+   event references (`PLAY0166`). Unmapped declared fields can be reported by
+   opt-in `--check field-origins` (`PLAY0534`); unknown coverage is skipped, so
+   still walk lineage. See diagnostics for editor versus C#-only checks.
+6. Without reaction `runs as` an invoke is caller-less. Declare its trusted role
+   (ESM v10), keep the gate, and reference-test; CLI/Stage support is separate.
 7. Read-model identity is one `query XById => RM optional` with `by xId XId`, and the identifier equal to the
    projection's key (see trap 12); never `identifier` on a read model.
 8. Projection `key` routes only on `from`; joins never create; `all` is per source.

package/package/corpus/skills/cratis-screenplay-toolchain/references/cheat-sheet-example.md

@@ -230,7 +230,7 @@ module Billing
         then InvoiceClosed                            // ESM v6: the Reconciler cascade (amount > 0)
           for "9c858901-8a57-4791-81fe-4c455b099bc9"
 
-module Housekeeping                                   // no gates: a reaction's `invokes` has no caller
+module Housekeeping                                   // no gates: this reaction declares no `runs as`, so its `invokes` has no caller
   description "Background follow-up"
   feature FollowUp
     slice StateChange CloseInvoice

package/package/corpus/skills/cratis-screenplay-toolchain/references/cheat-sheet.md

@@ -1,5 +1,20 @@
 # Screenplay cheat-sheet (tool versions: versions.md)
 
+## Contents
+
+- Samples and preview fixtures
+- Lexical and structural rules
+- Exact numeric source mode
+- Clause order inside a command (canonical)
+- Slice contents (typical)
+- `$context.` paths (command `produces`)
+- `$eventContext.` (projections)
+- PDL quick reference (most forms are compiled in `pdl-example.md` or `cheat-sheet-example.md`; `remove via join` and `$eventContext.occurred` are not)
+- Specification forms
+
+Current pins: standalone Screenplay 4.125.0 / CLI 3.41.0; `versions.md` is the
+single table. Compile evidence below keeps its historical tool labels.
+
 The syntax lives in compiled example files next to this one (each is a Markdown file holding
 one complete `screenplay` fence). Copy shapes from them; do not write a form that none of
 them (or a compiled documentation example) shows. This file holds the prose rules; the
@@ -18,11 +33,31 @@ by `for_Documentation/when_comparing_the_grammar_against_the_parsers.cs`),
 Screenplay CI (`when_compiling_every_example.cs`) against repository main: the standalone
 compiler (4.68.0; `cratis` 3.28.2 or later bundles 4.66.0, which lacks ESM v7); older cratis bundles differ (`versions.md`).
 
+## Samples and preview fixtures
+
+Invoicing is a warning-free syntax showcase, not a runnable whole-language proof.
+The released samples policy excepts these preview families and points to dedicated
+fixtures; do not infer binder admission from the sample's coverage list:
+
+| Family | Screenplay v4.125.0 fixture |
+| --- | --- |
+| Exact numbers | `Source/Screenplay/Compiler/Conformance/exact-named-rule-intent.play` |
+| Sources/streams/command routes | `Documentation/screenplay/fixtures/source-streams.play` |
+| Specification routes | `Source/Screenplay/Compiler/Conformance/specification-streams.play` |
+| Systems/operations/specification steps | `Documentation/screenplay/fixtures/operations.play` |
+| Refusals/redelivery/no-events | `Source/Screenplay/Compiler/Conformance/reaction-refusals-redelivery.play`, `no-events.play` in that directory |
+
+Source: `v4.125.0:.cratis/ai/rules/project/samples.md`. Its preview list retains
+sources/specification routes, but the released binder/runner admits them as v8;
+its old blanket PLAY0268 wording is not the current route verdict. Other rows
+remain unadmitted. Compile and test each relevant fixture with the chosen tool.
+
 ## Lexical and structural rules
 - Spaces only, 2 per level (tabs: PLAY0006 W). Offside rule.
 - Comments: `//` only. `#` is not a comment (PLAY0058 E in a projection) despite doc examples.
-- Order is free (forward references fine) except `domain` first in the file and `description`
-  first in a body.
+- Body directives can appear in any order; singleton `description` still appears
+  at most once. Canonical printing may place it first, but the parser does not
+  require that position. Source preambles precede declarations.
 - Strings: `"..."`, escapes `\" \\ \n \r \t`; other backslashes kept (regex `"^INV-\d{6}$"` works).
 - Structured values: single-line JSON, quoted keys (`[{"sku": "A-1", "quantity": 2}]`).
 - One condition grammar (policy `require`, `produces when`, `require`, reaction `where`): `and`
@@ -40,6 +75,16 @@ compiler (4.68.0; `cratis` 3.28.2 or later bundles 4.66.0, which lacks ESM v7);
   or keyed query argument) or `matches <commandProperty>`; executable; renderable only for
   text-backed targets (Uuid-backed: STAGE-ESM-015).
 
+## Exact numeric source mode
+
+Start each file/import barrel with `numbers exact` to retain bounded decimal
+literals without Double rounding. All assembled files must agree on mode;
+PLAY0508–PLAY0513 diagnose malformed directives, range errors and disagreement.
+Exact mode is authoring-only (`PLAY0268` on binding), not ESM v7 generated values.
+Typed JSON needs consistent `sourceOptions.numericMode: "exact"` on every root
+and `ExactNumber` literal envelopes with canonical fixed-point string values,
+never JSON numbers. Details: model-authoring `references/language-reference.md`.
+
 ## Clause order inside a command (canonical)
 description, properties, `reads`, `authorize`, `validate`, `produces`/`handler`, `concurrency`.
 

package/package/corpus/skills/cratis-screenplay-toolchain/references/diagnostics.md

@@ -3,8 +3,9 @@
 ## Contents
 
 - Warnings that hide defects (always validate with `--warnings-as-errors`)
-- Not caught at V1 (fail binding: V2/V3, PLAY0273)
-- Silent at every level
+- Source reference and identifier checks
+- Structural completeness and timeline checks
+- Editor versus C# verdicts
 - Consistency errors (V1: the model contradicts itself)
 - Binding (V2 and V3) - see `executable-subset.md` for the full table
 - Frequent errors
@@ -33,13 +34,56 @@ then STAGE (V5 admission). Tool differences: `versions.md`.
 | PLAY0455 | quoted import glob matches no file | fix the glob |
 | PLAY0196/0197/0198 | unknown query/screen; ambiguous bare name | declare or qualify `Slice.Name` |
 
-## Not caught at V1 (fail binding: V2/V3, PLAY0273)
-- Projection mapping to a property the read model does not declare.
-- Undeclared event in `remove with` or in a capture `append`.
-(Screenplay v4.66.0 `SemanticModelBinder` `BindMapping`, `LevelEvent`, `BindCaptureAppends`.)
+## Source reference and identifier checks
 
-## Silent at every level
-- A declared read-model property that nothing maps (it stays empty): walk field lineage by hand.
+At Screenplay 4.125.0 these are V1 source checks, not binding-only gaps:
+
+| Code | Severity | Meaning |
+| --- | --- | --- |
+| PLAY0514 | W | Projection mapping, children or nested target absent from the declared read-model/element shape; unknown/imported shapes are not guessed |
+| PLAY0166 | W | Unknown event, including `remove with`, `remove via join on` and capture `append` |
+| PLAY0515 | E | Personal/secret concept in a command identifier, typed `for` destination, event-source identity, stream-id type/part or route mapping source (including nested paths); keep a surrogate identity and protected data in payload |
+
+Legacy compliance spellings (`@pii`/`@sensitive`) do not evade PLAY0515.
+
+## Structural completeness and timeline checks
+
+Opt in with `--check <names>` or MCP diagnostics `checks`, then treat warnings
+as errors if gating. Ordinary compile success does not imply these ran:
+
+| Family | Codes | Checks |
+| --- | --- | --- |
+| data-bindings | PLAY0530/0531 | Conflicting visible bindings; binding/query read-model or cardinality mismatch |
+| input-surfaces | PLAY0532/0533 | Missing command input form/issuing screen; missing reachable issuer |
+| field-origins | PLAY0534 | Missing read-model builder or top-level field origin (AutoMap, identity and variants considered) |
+| query-keys | PLAY0535 | Query argument not representable by known identity/fields |
+| event-consumers | PLAY0536 | Latest local event generation lacks an operational consumer; a terminal fact can legitimately be reported |
+| navigation | PLAY0537 | Unreachable screens; unreachable cycles do not establish an entry point |
+
+Whole-source errors skip completeness checks. Unknown/opaque coverage is not
+invented: report skipped status/coverage and walk field lineage manually.
+
+PLAY0516/0517 are **information**, so never fail `--warnaserror`. They review
+presentation order, not execution: a backward event/read-model dependency or a
+mutually dependent sibling group. A cycle group replaces internal individual
+backward findings. Ordering roots are the sole source document, an importing
+`application.play`, or a unique importing root; without one, folder timeline
+checking is skipped. Safe PLAY0516 repairs move siblings/imports or pin files
+before a retained glob; cycles and own-sub-feature findings have no repair.
+
+## Editor versus C# verdicts
+
+Monaco/VS Code use the TypeScript syntax/authoring compiler. They share projection
+and protected-identifier checks (PLAY0514/0515), typed-example syntax (0518/0519),
+guarded actions (0341–0348), and reaction-refusal syntax/checks (0538–0545).
+A shared catalog code is not proof that a check is implemented in both compilers.
+
+C# CLI/MCP owns whole-application scoped diagnostics, opt-in completeness
+(PLAY0530–0537), semantic binding and PLAY0546 (a negated claim targets optional,
+unavailable-subject or non-text data). The VS Code repair bridge is not a general
+C# validator. A clean editor is not V1 for the complete application, V3 binding
+or V4 execution. Run the CLI or MCP for those verdicts. Authority:
+`v4.125.0:Documentation/screenplay/editor-diagnostics.md`, `diagnostics.md`.
 
 ## Consistency errors (V1: the model contradicts itself)
 | Code | Meaning |
@@ -99,7 +143,11 @@ Fix order: E at V1 -> W at V1 -> silent-gap check -> V2 codes (if the mode needs
 Report each as `code file:line one-line meaning`; never paste more than about 30 lines.
 
 ## Render admission (V5): `STAGE-*`, `CLI-RENDER-*`, `STAGE-CRATIS-*`
-Full table with causes: `renderable-subset.md`. Codes you meet most:
+Full table with causes: `renderable-subset.md`. The Stage 4.24.x rows below
+retain historical source/probe evidence. Current CLI 3.41.0 admits up to ESM v7
+for Stage planning; above that is CLI-RENDER-004. Its v7 corpus is refused by
+STAGE-ESM-028 (generated values) and -029 (responses), not the old v7 version gate.
+Codes in the historical snapshot:
 | Code | Meaning |
 |---|---|
 | STAGE-ESM-016 | model above the admitted ESM schema (v4 on Stage 4.24.2: v5 absence and v6 constructs; 4.24.1 admitted v3, so a v4 model with generations was refused): whole model refused |

package/package/corpus/skills/cratis-screenplay-toolchain/references/doc-contradictions.md

@@ -1,5 +1,10 @@
 # Documentation contradictions and which side to trust
 
+Current pins are Screenplay 4.125.0 / CLI 3.41.0 (`versions.md`). This is a
+**historical** contradiction inventory, not a claim that all listed defects still
+exist. Current grammar documents exact numbers and free description placement;
+sources/routes bind as ESM v8; PLAY0515 is a source error; CLI v7 reaches Stage.
+
 `D/` is Screenplay `Documentation/screenplay/` at **v4.66.0**; line numbers were re-read at
 that tag. Rule: the compiler you ran decides what the tool accepts today; the documentation
 and the domain decide what the model should mean. When they disagree, follow the compiler
@@ -32,7 +37,7 @@ read from source or documentation.
 | 19 | `$strings` constraint messages | `D/constraints.md:31` vs `D/internationalization.md:55` | the compiler keeps the key; realization localizes |
 | 20 | composite key braces | optional in the EBNF; both forms in docs | both fine |
 | 21 | counters list | `D/projections/index.md:54` lists only increment and decrement | `count` exists too [probed] |
-| 22 | ESM version allocation | older text and decisions 0023 and 0024 give exact numbers, operations, streams and reads fixed numbers (v7 to v11) | decision 0025 (accepted 2026-10-06): v7 is generated values and responses (decision 0026, released in 4.68.0); every other feature has no number until its release-ready admission, so say "not admitted by any supported ESM version" |
+| 22 | ESM version allocation | older text and decisions 0023 and 0024 give exact numbers, operations, streams and reads fixed numbers (v7 to v11) | use actual released binder selection: v7 generated values/responses, v8 routing, v10 reaction identity at 4.125.0; operations and exact numbers remain unadmitted. Never infer current admission from older proposed allocations |
 | 23 | claim conditions | the condition grammar lists `==` | claims need `matches` (PLAY0120) [probed] |
 | 24 | `numbers exact` | released in 4.64.0 as syntax only, but absent from `D/grammar.md`; documented only in `D/diagnostics.md` (PLAY0508 to PLAY0513) | the compiler: it parses, never binds (PLAY0268, "not admitted by any supported executable model (ESM) version yet"), PLAY0001 on older compilers [probed] |
 | 25 | command `concurrency` | `D/commands.md:609` says the executable model "does not bind the `concurrency` block yet" | the binder reports PLAY0271 as an **error**, not a silent skip (`SemanticModelBinder.Commands.cs:32-38`) |