@cratis/pi 7.33.0 → 7.34.1

package/package/corpus/skills/cratis-screenplay-specifications/references/persona-callers-and-cases.md

@@ -37,6 +37,9 @@ denial still uses `then denied`; a visitor persona is not an anonymous caller.
 
 ## Case tables
 
+Two diagnostics to know: `PLAY0588` (warning) for a declared parameter no step references, and `PLAY0585`
+(error) when an optional parameter feeds a required target.
+
 Use tables for validation matrices whose steps stay the same. Rows are **cases**,
 not examples: `example` means a named typed fixture. This complete model's five
 expanded specifications pass in the 4.127.0 reference runner:

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

@@ -53,8 +53,9 @@ module Collections
 - A reached reaction with a code body (`file` or inline) returns unsupported, as
   does a reaction that never settles. The reference stops at 1,000 new facts per
   scenario and 10,000 due occurrences per clock advance.
-- A model that uses these forms selects ESM v6 (`schemaVersion: 6`). Stage 4.24.2
-  admits ESM v1-v4 and renders no `Automation` or `Translate` slice, so the whole
+- A model that uses these forms selects ESM v6 (`schemaVersion: 6`). Stage 4.73.1
+  admits ESM v1-v10 by version but renders no `Automation` or `Translate` slice and no reaction
+  (`STAGE-ESM-024`; `-034` runsAs, `-035` filters, `-037` mixed effects), so the whole
   automation is gap-fill against this contract: `cratis-screenplay-render-and-gap-fill`.
 
 ### Version skew: cascades and the false `PLAY0285` (cratis before 3.28.2)

package/package/corpus/skills/cratis-screenplay-streams-and-consistency/LICENSE

@@ -34,5 +34,5 @@ SOFTWARE.
 
 This skill also adapts material from agentic-engineer by Martin Dilger and Nebulit GmbH
 (https://github.com/Nebulit-GmbH/agentic-engineer, commit 07b0f30648d663cb588d7e2c7aa031af9dfc21f2;
-https://nebulit.de), used with the agreement of Martin Dilger and Nebulit GmbH. That repository
-carries no licence file; the adapted material remains credited to Martin Dilger and Nebulit GmbH.
+https://nebulit.de), used with the explicit consent of Martin Dilger and Nebulit GmbH. The adapted
+material remains credited to Martin Dilger and Nebulit GmbH.

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

@@ -12,7 +12,7 @@ which it only records, and what a retry, a race or a replay does. Grammar lives
 skills; this skill owns the decisions. The `.play` model is the source of truth: a rule that
 lives only in code, or only in a description, is a finding, not a solution.
 
-**First append into a scope (Chronicle v19.32.0, version-qualified).** The default optimistic
+**First append into a scope (Chronicle v19.50.0, version-qualified).** The default optimistic
 strategy compares the scope's tail sequence number. When nothing matches the scope yet (the
 first event on a new event source, or the first event of a new source type, stream type or
 stream id), there is no tail and the append is **not checked**: two writers opening the same
@@ -28,17 +28,17 @@ Require target evidence that the check ran: a concurrent first-append scenario a
 Chronicle, asserting one append wins, one is rejected, and `IAppendResult.ConcurrencyCheckPerformed`
 is `true` (a skipped check and a passing one look identical otherwise; a current client against
 an older kernel always reads `false`). This was source- and documentation-inspected, not
-concurrency-tested here. The historically checked Stage 4.51.3 scaffold pins Chronicle client/kernel 19.32.0
-and Arc 22.50.5; the APIs exist for gap-fill, not as automatically rendered enforcement.
+concurrency-tested here. The Stage scaffold pins Chronicle client/kernel and Arc releases (see `cratis-stage-rendering-and-sandbox` `references/rendered-application.md`;
+the CLI bundle's Chronicle is in `cratis-screenplay-toolchain` `references/versions.md`); the APIs exist for gap-fill, not as automatically rendered enforcement.
 
 ## Verified product sources
 
 | Product | Pin | Used for |
 | --- | --- | --- |
 | Screenplay | v4.68.0 (`79801bf`) | ESM v7 generated values (`generated identifier`, decision 0026) and decision 0025's numbering; the diagnostics below were read at v4.66.0 (`c89198b`): `identifier`, `for`, constraints, generations, `id` pins, diagnostics PLAY0019/0135/0268/0271/0273/0391-0393/0446-0449/0469/0471 |
-| Chronicle | v19.32.0 (`f17a2ff`) | CHR0012, CHR0034; open defects #3744, #4123, #4131 |
-| Arc | v22.50.5 | `[ProtectedDecision]` and `DecisionRead<T>` (since v22.39.0) |
-| Stage (historical source check) | v4.51.3 | rendered apps pin Arc 22.50.5 and Chronicle client/kernel 19.32.0; protected-read APIs available to gap-fill. Historical 4.24.2 admission probe: ESM v4, evolved events refused with `STAGE-ESM-026` |
+| Chronicle | v19.50.0 (read; first read at v19.32.0 `f17a2ff`) | CHR0012, CHR0034; open defects #3744, #4123, #4131 (still open) |
+| Arc | v22.72.0 | `[ProtectedDecision]` and `DecisionRead<T>` (since v22.39.0) |
+| Stage | v4.73.1 | rendered apps pin the Arc and Chronicle client/kernel listed in the Stage skill's `references/rendered-application.md`; protected-read APIs available to gap-fill. Historical 4.24.2 admission probe: ESM v4, evolved events refused with `STAGE-ESM-026` |
 
 Full pin table: `references/versions.md` in `cratis-screenplay-toolchain`. Re-check the three
 Chronicle issues before relying on a constraint in a later release.
@@ -90,7 +90,7 @@ option, mark it `ASSUMED` in the slice or module `documentation` and in the sess
    command/specification routes bind and reference-execute as ESM v8 on 4.125.0.
    The pinned CLI (toolchain `references/versions.md`) reaches Stage construct checks through v10; keep the routing
    contract when target admission requires gap-fill. Forms/boundaries:
-   toolchain `references/sources-and-streams.md`. A `generated identifier` (ESM v7, standalone 4.68.0; not rendered by Stage yet) is
+   toolchain `references/sources-and-streams.md`. A `generated identifier` (ESM v7, standalone 4.68.0 and later; Stage 4.73.1 refuses it, STAGE-ESM-028) 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.
@@ -166,10 +166,10 @@ option, mark it `ASSUMED` in the slice or module `documentation` and in the sess
   complete named mappings and canonical comparison, not guessed legacy splits.
   Stored key-schema changes require a new stream identity or migration; see
   toolchain `references/sources-and-streams.md`.
-- Chronicle (open at v19.32.0): the SQL and InMemory providers do not settle unique claims
+- Chronicle (open at v19.50.0): the SQL and InMemory providers do not settle unique claims
   (#3744); index updates run after commit and may fail silently (#4123); composite values can
   collide on the separator (#4131). A declared constraint is a declaration, not a runtime test.
-- `[ProtectedDecision]` is available in Arc v22.39.0 or later, including Stage 4.51.3's
+- `[ProtectedDecision]` is available in Arc v22.39.0 or later, including Stage 4.73.1's
   rendered package set. It is not emitted protection: gap-fill must enroll an admitted
   decision read, or redesign the stream/identity when the shape is refused
   (`references/consistency-and-concurrency.md`, section 3).

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

@@ -3,6 +3,7 @@
 ## Contents
 
 - Establish the boundary, not an organizational formula
+- Ownership by design (optional lens)
 - Ownership interview
 - Ownership and interface inventory
 - Cross-boundary walkthrough
@@ -29,6 +30,28 @@ decision visible in the session `STATE.md`; never report independence as establi
 splitting a boundary revisit every invariant that needs information from both sides: an event
 exchange does not make that decision atomic.
 
+## Ownership by design (optional lens)
+Conway's observation is that systems come to mirror the teams that build them. Use it as a
+deliberate lens when you shape boundaries, not as a law: decide the ownership you want and let the
+boundaries follow it, instead of discovering later that the org chart set them.
+
+- When one team will own a boundary end to end, treat the module as that team's system: it owns
+  its commands, the events it produces, the read models it maintains and the systems it calls.
+  Other teams interact only through its public events and its capture contracts, so each side can
+  be built, scaled and released on its own, coordinating through events rather than meetings.
+- A system this process integrates with is, by definition, owned by someone else. Record that
+  owner next to the public fact or capture contract; it is the person you ask before changing it.
+- Treat "team = system" as a hypothesis to test with the interview answers, not as a default. One
+  team may own several modules, a module may be shared during a transition, and a team boundary
+  does not make a decision atomic across it (see above). Write down which the model follows.
+
+**Indirect producers.** When a fact reaches a receiver through an intermediate boundary (the
+booking system's `BerthBooked` drives billing, whose `StayInvoiceDue` then reaches the harbour
+office), attribute each public event to the boundary that decides it, and name the original
+producer in the consumer's description as the indirect source. Ownership of the public contract
+stays with the boundary that decides the fact; the indirect source tells a reader whom a change
+upstream will surprise.
+
 ## Ownership interview
 Run it when ownership, autonomy or integration decisions are missing; skip it when the user or
 the model already states all three. Ask one question at a time, offer the options, and follow
@@ -136,14 +159,19 @@ integration support.
   internal step.
 - Treat a public event like a published API: evolution follows `evolution.md` with the
   consumers named, and breaking changes become new events.
-- Screenplay has no public/internal marker. Record the classification in the event's
-  `documentation`, and keep the list in `STATE.md`.
+- Events are private by default. Mark a public contract with `public event X` (ESM v9, released in
+  Screenplay 4.117.0); declare a foreign public event's shape locally with `event X from "store"`.
+  A command never produces a public event (PLAY0607/0613); crossing the boundary is a `Translate`
+  slice with an explicit direction (`cratis-screenplay-automations-and-translations`
+  `references/public-events-and-direction.md`). Nothing checks that the foreign shape matches the
+  other store, so also name the consumers in the event's `documentation` and keep the list in
+  `STATE.md`. Stage 4.73.1 refuses public events (`STAGE-ESM-032`).
 
 ## Crossing a boundary in Screenplay
 | Situation | Construct |
 |---|---|
 | another module in the same application | reference the event by name (cross-module resolution works within one application) |
-| another bounded context's contract | unquoted `import Context.Event` (foreign contract; does not bind on either compiler, PLAY0268; see `versions.md` in `cratis-screenplay-toolchain`) |
+| another bounded context's contract | `event X from "store"` (shape declared locally, ESM v9); an unquoted `import Context.Event` or `import Q.X from "store"` has no local shape and stays PLAY0268 (see `versions.md` in `cratis-screenplay-toolchain`) |
 | my own files | quoted `import "glob"` |
 | outside data entering | `Translate` slice: `capture`, or a translator `reaction` over an imported event (`cratis-screenplay-automations-and-translations`) |
 | our fact another context needs | a public summary event; the other side translates it into its own language |

package/package/corpus/skills/cratis-screenplay-streams-and-consistency/references/chronicle-boundaries.md

@@ -5,16 +5,16 @@ target facts; the `.play` model declares only part of them (`versions.md` in
 `cratis-screenplay-toolchain`).
 
 ## Pins
-Chronicle **v19.32.0** (`f17a2ff`): CHR0012 (nullable event properties) and CHR0034 (PII on an
-event-source id) are present. Three runtime defects are **open at v19.32.0**: #3744 (SQL and
+Chronicle **v19.50.0** (first read at v19.32.0 `f17a2ff`): CHR0012 (nullable event properties) and CHR0034 (PII on an
+event-source id) are present. Three runtime defects are **open at v19.50.0**: #3744 (SQL and
 InMemory providers do not settle unique claims), #4123 (constraint index updates run after commit
 and fail silently) and #4131 (composite unique constraints collide when a component contains the
-separator). Arc **v22.50.5** has `[ProtectedDecision]` (since v22.39.0, needs Chronicle 19.23 or
-later); Stage 4.51.3 rendered apps pin Arc 22.50.5 and Chronicle client/kernel
-19.32.0, so the APIs are available to gap-fill, not automatically emitted or
+separator). Arc **v22.72.0** has `[ProtectedDecision]` (since v22.39.0, needs Chronicle 19.23 or
+later); Stage-rendered apps pin an Arc and Chronicle client/kernel release
+(see the Stage skill's `references/rendered-application.md`) that include them, so the APIs are available to gap-fill, not automatically emitted or
 protected (see `consistency-and-concurrency.md` section 3). Re-check the issues before relying on a
 constraint in a new release.
-A concurrency scope's first append is unchecked by default at v19.32.0; see
+A concurrency scope's first append is unchecked by default at v19.50.0 (the default is planned to become checked in the next major, `Documentation/events/concurrency.mdx`); see
 SKILL.md, ‘First append into a scope’.
 
 ## Identity, routing and claims

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

@@ -64,7 +64,7 @@ observed legacy check from verified atomic protection.
 Never accept the caller's copy of the state: `currentStatus Status` on the command with
 `require currentStatus == "approved"` protects nothing, and neither does a boolean attestation
 input (`confirmsX == true`) standing in for the rule. Never move the rule into `handler` or
-`implementation hint` prose; a description is not rendered (Stage#178), so prose alone leaves
+`implementation hint` prose; a description renders only as an XML doc comment (Stage#178), so prose alone leaves
 the rule unenforced in rendered scope.
 
 Right: write the rule as stated intent and mark it unenforced.
@@ -74,7 +74,7 @@ Right: write the rule as stated intent and mark it unenforced.
 - Slice `description`: one short marker per rule, `NOT enforced in the model today; target: <mechanism>`.
 - Slice fenced `documentation`, one block per rule:
   - Requirement: the business rule in business words.
-  - Status: NOT enforced in the model today (Screenplay#129, #209).
+  - Status: NOT enforced in the model today (Screenplay#129).
   - Decision inputs: the authoritative facts or state.
   - Missing guarantee: why the construct does not protect the decision.
   - Race consequence: what two individually plausible commands could jointly violate.
@@ -106,11 +106,11 @@ empty or `$eventSourceId`). Reducers, joins, children, nested sources and **even
 routing** (fan-in from many streams by a payload reference) are refused, and a concurrency scope
 on the referenced source does not see appends made on other sources. A rule over such a view, for
 example a course capacity computed from enrolment streams, needs option a or b: write the
-deciding fact on the source that owns the state, or give each scarce item its own identity. Sources: Arc `v22.50.5:Documentation/backend/csharp/chronicle/read-models/injecting-into-commands.md`;
+deciding fact on the source that owns the state, or give each scarce item its own identity. Sources: Arc `v22.72.0:Documentation/backend/csharp/chronicle/read-models/injecting-into-commands.md` (limits unchanged since v22.50.5);
 `chronicle-boundaries.md`.
 
-**Availability in Stage-rendered applications.** Stage v4.51.3 scaffolds Arc 22.50.5
-and Chronicle client/kernel 19.32.0. `[ProtectedDecision]` and `DecisionRead<T>` /
+**Availability in Stage-rendered applications.** The Stage scaffold pins Arc and Chronicle client/kernel
+releases (not the latest). `[ProtectedDecision]` and `DecisionRead<T>` /
 `IDecisionReads` exist in that package set; source checks are in
 `cratis-stage-rendering-and-sandbox` `references/rendered-application.md`.
 This does not mean Stage emits protected decisions. Gap-fill must opt into the
@@ -119,7 +119,7 @@ read in the active unit of work. For refused shapes choose option a/b (state on
 its owning stream or one identity per scarce item), or agreed compensation c.
 Keep the rule **NOT enforced in the model today** with its race consequence.
 Never infer protection from `.play` `reads` + `require`, weaken the rule to render,
-or edit managed dependency files. Older Stage 4.24.x scaffolds predate these APIs.
+or edit managed dependency files. Older Stage 4.24.x scaffolds predate these APIs. Arc 22.72.0 and Chronicle 19.50.0 are the latest releases; the scaffold does not move with them.
 
 ## 4. Concurrency scenarios
 For each enforced or recorded rule write three short scenarios:
@@ -185,11 +185,12 @@ behaviour. Write the answer in the slice `documentation`.
   date views and rules use. Constraints and reactions still see record order.
 
 ## 10. Specification limits (no local spec engine)
-- A spec can show a source re-claiming its own value and a `unique event` violation. Whether
-  it can show a collision between two different sources is contested in the docs:
-  `constraints.md` says not yet, `specifications.md` says `for` on `given` events allows it. Treat
-  such a spec as parsed (V1), not proven; spec outcomes come only from a reference run (V4) or
-  rendered tests. See `cratis-screenplay-scenario-coverage`.
+- A spec can show a source re-claiming its own value, a `unique event` violation and a collision
+  between two different sources: `for` on `given` events (ESM v2) establishes a claim on one source
+  and attempts the same value on another (`specifications.md`; `streams-example.md` uses it). It is a
+  sequential history, not a race proof. The `constraints.md` sentence that it "cannot yet show a
+  collision between two event sources" is stale (`cratis-screenplay-toolchain` `references/doc-contradictions.md`).
+  Spec outcomes come only from a reference run (V4) or rendered tests. See `cratis-screenplay-scenario-coverage`.
 - Constraint violation messages are fixed strings: copy them exactly into `then error`.
 - For every value constraint write a competing-claim spec (one source owns the value, a
   different source attempts it) using `when <Command>` with the earlier fact as `given`.

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

@@ -77,7 +77,7 @@ Procedure and ownership: the identity procedure in `cratis-screenplay-modeling-l
 owning session, or a brief that asks for the rename, applies it; a subagent without MCP returns
 the catalog-changing request to the owner; never leave a requested change silently unapplied).
 - Several generations select ESM v4; that binds executably on both tools (compiled
-  with `evolution-example.md`). Stage 4.24.2 admits v4 but refuses any evolved event and its
+  with `evolution-example.md`). Stage (still, at 4.73.1) admits v4 but refuses any evolved event and its
   dependent scope with `STAGE-ESM-026` (it cannot render event-type migrations yet, Stage#204,
   which depends on Screenplay#71), and its runtime still refuses evolved events: the evolved
   events are gap-fill, with migrations hand-written per `cratis-chronicle-event-type-migration`.

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

@@ -11,11 +11,10 @@
 
 Event Modeling practice is by Adam Dymitruk and Martin Dilger, cited as practice; no text taken.
 
-## Adapted closely (Martin Dilger and Nebulit GmbH, with agreement)
+## Adapted closely (Martin Dilger and Nebulit GmbH)
 
 Source: https://github.com/Nebulit-GmbH/agentic-engineer at commit `07b0f30648d663cb588d7e2c7aa031af9dfc21f2`,
-by Martin Dilger and Nebulit GmbH (https://nebulit.de). The repository carries no licence file; this material
-is adapted with the agreement of Martin Dilger and Nebulit GmbH.
+by Martin Dilger and Nebulit GmbH (https://nebulit.de), used with the explicit consent of Martin Dilger and Nebulit GmbH.
 
 | Source file | Used in | How |
 |---|---|---|
@@ -23,5 +22,6 @@ is adapted with the agreement of Martin Dilger and Nebulit GmbH.
 | `.claude/skills/eventmodeling-optimizing-stream-design`, patterns reference: decision tree, red flags 2-4, composite and collection and log patterns | `references/stream-patterns.md` "Boundary decision tree", "Red flags", "Boundary patterns by domain" | adapted closely, restored from #493; red flag 1 ("no natural end") dropped because it contradicts long-lived identities; event-granularity tip dropped (generic update events are a defect here) |
 | `.claude/skills/eventmodeling-optimizing-stream-design`, domain-patterns reference: per-domain identity entries | `references/stream-patterns.md` "Boundary patterns by domain" | translated to invoicing, marina, memberships, enrolment and hire; lifetimes and archival splits dropped |
 | `.claude/skills/eventmodeling-applying-conways-law/SKILL.md`: interview questions with follow-up triggers, six-step ownership workflow, quality checklist | `references/boundaries.md` "Ownership interview", "Ownership and interface inventory", "Responsibility matrix and ownership timeline", "Boundary checklist" | adapted closely; "team = system" absolutes deliberately not adopted, kept "not by law" |
-| `.claude/skills/eventmodeling-applying-conways-law`, examples reference: responsibility matrix, swimlane timeline, inter-system communication | `references/boundaries.md` "Responsibility matrix and ownership timeline", "Worked walkthrough" | translated to marina and invoicing; Martin Dilger and Nebulit GmbH's indirect-producer attribution not copied |
+| `.claude/skills/eventmodeling-applying-conways-law`, examples reference: responsibility matrix, swimlane timeline, inter-system communication | `references/boundaries.md` "Responsibility matrix and ownership timeline", "Worked walkthrough" | translated to marina and invoicing (see the next row for the indirect-producer attribution) |
 | `.claude/skills/eventmodeling-core-rules/SKILL.md`: immutability, calculated-event anti-pattern, causality, open question versus decided failure, "left chair" fan-out, offline-first | `references/stream-patterns.md` "Core rules that bear on stream design", `SKILL.md` modeling defaults | adapted closely, translated to Screenplay constructs; board lanes, linked copies and role catalog not adopted here (other skills own them) |
+| `.claude/skills/eventmodeling-applying-conways-law/SKILL.md`, examples reference: team and system boundary as one, indirect-producer attribution | `references/boundaries.md` "Ownership by design (optional lens)" | Adapted closely as an optional lens with the "team = system" claim kept as a hypothesis to test; indirect-producer attribution adopted for public events, with ownership staying with the deciding boundary |

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

@@ -164,7 +164,7 @@ module Courses
         then denied
 
     slice StateChange EnrolMember
-      description "Atomic here: one active enrolment per member and course (composite unique constraint, released by withdrawal), and one MemberEnrolled per enrolment stream, so a retry with the same enrolment id after a lost reply cannot enrol twice (the composite constraint alone lets a source re-claim its own value). NOT enforced in the model today: 'enrolments never exceed the course capacity'. The rule depends on other streams' state: `reads` is PLAY0271 and `require` over a view is PLAY0268 at binding (Screenplay#129/#209). The enrolment-to-course fan-in cannot be protected as modeled (see the CourseAvailability slice): concurrent enrolments can overbook. Target enforcement is an open decision (consistency-and-concurrency.md section 3); the model stays as stated intent, recorded in STATE.md."
+      description "Atomic here: one active enrolment per member and course (composite unique constraint, released by withdrawal), and one MemberEnrolled per enrolment stream, so a retry with the same enrolment id after a lost reply cannot enrol twice (the composite constraint alone lets a source re-claim its own value). NOT enforced in the model today: 'enrolments never exceed the course capacity'. The rule depends on other streams' state: `reads` is PLAY0271 and `require` over a view is PLAY0268 at binding (Screenplay#129). The enrolment-to-course fan-in cannot be protected as modeled (see the CourseAvailability slice): concurrent enrolments can overbook. Target enforcement is an open decision (consistency-and-concurrency.md section 3); the model stays as stated intent, recorded in STATE.md."
       command EnrolMember
         enrolmentId EnrolmentId identifier
         courseId    CourseId

package/package/corpus/skills/cratis-screenplay-toolchain/LICENSE

@@ -5,5 +5,5 @@ Third-party notices
 
 This skill adapts material from agentic-engineer by Martin Dilger and Nebulit GmbH
 (https://github.com/Nebulit-GmbH/agentic-engineer, commit 07b0f30648d663cb588d7e2c7aa031af9dfc21f2;
-https://nebulit.de), used with the agreement of Martin Dilger and Nebulit GmbH. That repository
-carries no licence file; the adapted material remains credited to Martin Dilger and Nebulit GmbH.
+https://nebulit.de), used with the explicit consent of Martin Dilger and Nebulit GmbH. The adapted
+material remains credited to Martin Dilger and Nebulit GmbH.

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

@@ -43,7 +43,8 @@ or Screenplay 4.139.0.
    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
    current language checks and reference specifications; `cratis` for rendering
-   and generation. Bundled and standalone versions differ. Report both tool and
+   and generation. Bundled and standalone versions differ (CLI 3.53.1 bundles 4.137.0;
+   the standalone pin is 4.139.0). 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
@@ -64,7 +65,7 @@ or Screenplay 4.139.0.
 | | Standalone `screenplay` | `cratis screenplay ...` |
 | --- | --- | --- |
 | 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 |
+| Scope/checks | `--scope <address>`, `--check <names>`; a scoped pass is not whole-application success | `validate --executable` (bundled binder, no write), `--check <names>`, `--scope`; `render --scope`/`--check`; `cratis screenplay conform` |
 | 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 | Pinned CLI (`versions.md`) passes through ESM v10 to Stage construct admission; bound newer models: `CLI-RENDER-004` |
@@ -85,12 +86,12 @@ Independent results, not a ladder. Read `references/verdicts.md` for the command
 | 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
+V2 and V3 need MCP (V3 alone can also be read from `cratis screenplay validate --executable <root>`, labeled as the bundled compiler): send `initialize`, then `notifications/initialized`, and start the
 server with a fixed root when the tool is older than 4.63.2 (the roots bug hit 4.63.1 and the
 4.60.1 bundled by cratis before 3.28.2; 4.66.0 and later and cratis 3.28.2 are fine). A subagent without MCP reports "V2 not run: no MCP in this agent".
 
-One line per verdict, tool first, for example `V1 pass (screenplay 4.68.0, 3 files)` and
-`V3 blocked: PLAY0268 x3 (list query, pii)`. Name the source identity (commit plus the digest from
+One line per verdict, tool first, for example `V1 pass (screenplay 4.139.0, 3 files)` and
+`V3 blocked: PLAY0268 x3 (filter query, pii)`. Name the source identity (commit plus the digest from
 the source-identity helper (`cratis-screenplay-modeling-lifecycle` `references/verdicts-and-modes.md` "Source identity")) the verdict ran on; keep it apart from the MCP
 `modelRevision`, which is semantic and, without `.screenplay/identities.json`,
 changes with the root folder name.
@@ -99,15 +100,16 @@ changes with the root folder name.
 
 - **Design**: every construct family parses; use it to model first. Compiled shapes:
   `references/cheat-sheet.md`. Read [references/cheat-sheet-example.md](references/cheat-sheet-example.md) when you need one complete design-mode document with every construct family.
-- **Executable** (binds, V3): `references/executable-subset.md`. Keyed optional queries
-  only; no handler (PLAY0268, with or without `implementation`/`hint`); `reads` and
+- **Executable** (binds, V3): `references/executable-subset.md`. Optional keyed lookups, unfiltered
+  lists and lists narrowed by one `by` key (observable too); `filter`, `scoped to`, `performer` and composite `by` do not bind; no handler (PLAY0268, with or without `implementation`/`hint`); `reads` and
   `concurrency` do not bind (PLAY0271); no compliance markers (`pii`/`secret`); 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)
   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.
+- **Renderable** (V5): `references/renderable-subset.md` has the current Stage 4.73.1 table and
+  explicitly labeled older probes. The CLI admits through v10 to Stage construct checks; generated
+  values and responses get `STAGE-ESM-028`/`029`, not a blanket compiler refusal. Run admission
+  before claiming a particular model renders (`cratis render --scope` for an admitted part, `--check`
+  for no-write planning).
 - **Event sources, streams and routes** bind as ESM v8 at 4.125.0.
   The pinned CLI/Stage pair (`references/versions.md`) reaches admission through v10, not blanket
   rendering. Operations and exact numeric source mode remain unadmitted.
@@ -183,7 +185,7 @@ Read [references/diagnostics.md](references/diagnostics.md) when a PLAY, STAGE o
 11. Declare an event once, in its producing slice.
 12. Quoted `import "glob"` is your own files; unquoted `import Ctx.Event` is a foreign
     contract and does not bind.
-13. A handler never binds; `numbers exact` never binds; descriptions are never rendered.
+13. A handler never binds; `numbers exact` never binds; descriptions render only as XML doc comments, never as behavior.
 
 ## Gate
 

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

@@ -2,7 +2,7 @@
 
 One complete document with every construct family. Design mode, not executable. Prose rules: [cheat-sheet.md](cheat-sheet.md); tool versions: [versions.md](versions.md); what binds: [executable-subset.md](executable-subset.md).
 
-Binding blockers: unquoted import, `pii`, `reads` (PLAY0271), `starts with`, observable/list/filter query. Executable shapes are in the sibling examples. The bare-marker fence compiles warning-free on standalone 4.127.0; the earlier legacy-marker version compiled on 4.66.0 and CLI 3.28.2. `RecordingAPayment` lists the `InvoiceClosed` cascade, which the cratis 3.27.1 bundle (4.60.1) rejected with a false PLAY0285 ("outcome cannot be produced by 'RecordPayment'"); 3.28.2 accepts it.
+Binding blockers: unquoted import, `pii`, `reads` (PLAY0271), `starts with`, a `filter` query (lists and observable lists bind). Executable shapes are in the sibling examples. The bare-marker fence compiles warning-free on standalone 4.127.0; the earlier legacy-marker version compiled on 4.66.0 and CLI 3.28.2. `RecordingAPayment` lists the `InvoiceClosed` cascade, which the cratis 3.27.1 bundle (4.60.1) rejected with a false PLAY0285 ("outcome cannot be produced by 'RecordPayment'"); 3.28.2 accepts it.
 
 ```screenplay test=unbound
 // Design-mode cheat-sheet: every construct family; compiles warning-free on the standalone tool.
@@ -153,9 +153,9 @@ module Billing
       readmodel InvoiceRow
         invoiceId InvoiceId
         number    String
-      query InvoiceById => InvoiceRow optional        // keyed: the only executable query shape
+      query InvoiceById => InvoiceRow optional        // keyed optional lookup (unfiltered lists bind too)
         by invoiceId InvoiceId
-      query ListInvoices => observable InvoiceRow[]   // design mode only (PLAY0268 at binding)
+      query ListInvoices => observable InvoiceRow[]   // design mode only: the `filter` below is PLAY0268 at binding
         filter number String optional
       projection InvoiceList => InvoiceRow
         from InvoiceRegistered

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

@@ -87,7 +87,7 @@ remain unadmitted. Compile and test each relevant fixture with the chosen tool.
   generated identifier` (PLAY0484); legacy `?` is PLAY0479 (information).
 - Ownership policies: `require claim "ownerId" matches subject` (subject = command identifier
   or keyed query argument) or `matches <commandProperty>`; executable; renderable only for
-  text-backed targets (Uuid-backed: STAGE-ESM-015).
+  text-backed targets at the 4.24-era Stage; Stage 4.73.1 also renders Uuid and Date claim targets (see `renderable-subset.md`; unsupported subjects: STAGE-ESM-015).
 
 ## Exact numeric source mode
 

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

@@ -55,8 +55,10 @@ read from source or documentation.
 | 27 | decision index | `decisions/README.md` row 0020 shows stage `none` while v5 is implemented | the code: v5 `then no readmodel` binds |
 | 28 | `visualize-model` kind | the tool filters on the kind "Reactor" (`McpVisualization.cs:21`) although the construct is a Reaction; its added/removed summary never counts reactions (Screenplay#379, open) | the model, not the summary |
 | 29 | bodied reducers in Stage | cli `Documentation/reference/screenplay.md:38` says bodied reducers are unsupported (STAGE-ESM-019) | Stage 4.24 code admits pure allowlisted reducer bodies (`PureTransitionAdmission.cs`); trust the code |
-| 30 | `cratis screenplay validate <file>` | the command reads as a document validator | file mode ignores the file's imports and reports false unknown-name warnings (cli#244, open): validate the folder [probed] |
+| 30 | `cratis screenplay validate <file>` | the command reads as a document validator | file mode ignored the file's imports and reported false unknown-name warnings on CLI 3.28.2 (cli#244, closed by PR #258: later releases compile the file with its imports); validate the folder anyway [probed on 3.28.2] |
 | 31 | cli false PLAY0285 | `D/diagnostics.md:640` defines PLAY0285 as a contradiction against every possible producer | cratis before 3.28.2 reported it falsely on reaction cascades (cli#242); not reproduced on cratis 3.28.2 [probed] |
+| 32 | competing-claim specification | `D/constraints.md` says a specification "cannot yet show a collision between two event sources" | `D/specifications.md`: `for` on `given` events establishes a claim on one source and attempts the same value on another; the specification page and the tool decide (checked at v4.139.0) |
+| 33 | descriptions in rendered code | Stage `Documentation/reference/render-plans.md` says the cratis CLI does not yet call `WithAuthoringMetadata` | the CLI calls it since 3.51.0 (`CratisRenderTarget.cs`): descriptions and documentation render as XML doc comments; `CLI-RENDER-006` when skipped (checked at cli v3.53.1) |
 
 Rows 0 to 12, 14 to 21 and 23 were re-read at the v4.66.0 line numbers above; rows 14, 15,
 19, 20 and 23 are properties of the language rather than documentation defects and were

package/package/corpus/skills/cratis-screenplay-toolchain/references/executable-subset.md

@@ -5,7 +5,7 @@
 - Caller and compliance boundary (4.127.0)
 - Admitted on both compilers
 - Admitted from Screenplay 4.61 (ESM v6): standalone tool and cratis 3.28.2 or later
-- Generated values and responses (ESM v7): standalone 4.68.0 or later only
+- Generated values and responses (ESM v7): standalone 4.68.0 or later; the cratis 3.53.1 bundle binds them too
 - Released public boundaries and observer routes
 - Code attachments (what binds, what never does)
 - Refused (code, reason): fix, or record as a mode gap
@@ -15,25 +15,30 @@
 Current pins: `versions.md`. Detailed
 4.66.0/4.68.0 binder probes below retain their historical labels. Current source
 admits routes as ESM v8, public/direction constructs as v9, identity/overrides/filters
-as v10 and qualifying non-route Double literals as v11. Operations,
-`numbers exact` source mode and reaction refusals/redelivery remain unadmitted. Use the actual
+as v10, qualifying non-route Double literals as v11 (exact lowering of Double-mode literals)
+and non-positional enum numbers as v12. Operations, the `numbers exact` **source mode** (PLAY0268) and
+reaction refusals/redelivery remain unadmitted. Use the actual
 binder before promoting an older probe to a current capability claim.
 
 What the binder admits, and what it refuses with which code. The answer depends on the
-compiler version: standalone Screenplay 4.68.0 admits ESM v1 to v7; the 4.66.0 compiler bundled in
-cratis 3.28.2 and 3.28.3 admits v1 to v6; the 4.60.1 compiler bundled in cratis before 3.28.2 admits v1 to v5.
+compiler version: the standalone tool (4.139.0) binds through v12; the compiler bundled in cratis
+3.53.1 (4.137.0) binds ESM through v10 for rendering and refuses non-positional enum numbers at
+binding; older bundles (4.66.0 in cratis 3.28.x, admitting v1 to v6; 4.60.1 before 3.28.2, v1 to v5)
+are history.
 Tool facts and the exact v6 messages: `versions.md`. Always name
 the tool with a V2 or V3 result. When tool and documentation disagree, the tool decides
 current capability; the documentation and the domain decide intended correctness. Record
 the gap, never strip the model to pass.
 
-Binding is observed only through MCP (`read-workspace view=executable-diagnostics`) or a
-render. `screenplay <folder>` and `cratis screenplay validate` never bind (`verdicts.md`).
+Binding is observed through MCP (`read-workspace view=executable-diagnostics`), a render, or
+`cratis screenplay validate --executable <root>` (bundled compiler; binding errors only, writes
+nothing; exit 5 when it does not bind). `screenplay <folder>` and plain `cratis screenplay validate`
+never bind (`verdicts.md`).
 
 Complete examples that bind live in `executable-example.md` (both compilers),
 `pdl-example.md` (projections, both compilers) and `automation-translate-example.md`
 (ESM v6; standalone tool and cratis 3.28.2 or later) and `generated-responses-example.md`
-(ESM v7; standalone tool 4.68.0 or later only).
+(ESM v7; standalone tool 4.68.0 or later, and the cratis 3.53.1 bundle).
 
 ## Caller and compliance boundary (4.127.0)
 
@@ -106,13 +111,15 @@ Authority: v4.127.0 `context.md`, `identity.md`, `concepts.md`, `events.md`, `pu
 - Command specifications that list reaction cascades (no false PLAY0285).
 - In a `then` list after `when append`, only what followed the appended event.
 
-## Generated values and responses (ESM v7): standalone 4.68.0 or later only
+## Generated values and responses (ESM v7): standalone 4.68.0 or later; the cratis 3.53.1 bundle binds them too
 
 Facts read at `v4.68.0`: decision 0026 and `Documentation/screenplay/{commands,specifications,interoperability}.md`.
 A model selects ESM v7 only when it uses a generated property, a response, a generated fixture or a `then returns`
 expectation; every other model keeps its version, bytes and revision. The cratis CLI 3.28.3 (bundled 4.66.0)
-reports `PLAY0268` for these constructs, and Stage 4.24.2 refuses ESM v7 with `STAGE-ESM-016` (tracked in
-Stage#201), so they bind and run but are not rendered: gap-fill with the model as contract. Complete example:
+reported `PLAY0268` for these constructs (history). The current CLI (3.53.1, bundled 4.137.0) binds them
+and reaches Stage planning, where Stage 4.73.1 refuses generated values with `STAGE-ESM-028` and
+responses with `STAGE-ESM-029` (Stage#175), so they bind and run but are not rendered: gap-fill with the
+model as contract. Complete example:
 `generated-responses-example.md`.
 
 - A generated property is command-only, required, scalar and a concept backed by `Uuid`; bare `Uuid`, optional and collection
@@ -187,8 +194,9 @@ bodies still leave their owner non-executable.
   `require`/`validate` bodies (`v4.66.0:Documentation/screenplay/commands.md`, `context.md`).
 - A handler therefore makes the slice non-executable and non-renderable: it is gap-fill
   with the model as the contract.
-- Stage 4.24 admits only pure reducer bodies (Roslyn allowlist, STAGE-ESM-019 and 022);
-  code validation (STAGE-ESM-005) and opaque policies (STAGE-ESM-015) are refused.
+- Stage admits only pure reducer bodies (Roslyn allowlist, STAGE-ESM-019 and 022);
+  code validation is refused (STAGE-ESM-005). Opaque pure policies render at Stage 4.73.1 (4.24
+  refused them with STAGE-ESM-015).
 - The reference runner returns Unsupported for the opaque bodies that do bind (rule and
   policy predicates, code validation, reducer transitions); a specification that needs one
   never passes. Handlers, file constraints and query performers (and reaction effects on a trigger with
@@ -202,8 +210,8 @@ bodies still leave their owner non-executable.
 | `Automation` or `Translate` slice, `reaction`, `capture`, `trigger`; `given clock`, `when clock`, `when trigger`, `when capture` | PLAY0268 | **cratis before 3.28.2 bundles only** (4.60.1); messages in `versions.md` |
 | Unquoted `import Other.Contract` | PLAY0268 | external contract import is not bound |
 | `pii` or `secret` on any concept (also alias/legacy markers) | PLAY0268 | Compliance requires portable data-subject semantics; scopes/qualifiers do not admit it. Secret provider mapping is `[Encrypted]` + `[NotAudited]`, not a bind/render claim |
-| `query` returning a collection (`RM[]`), or without exactly one caller-supplied scalar `by` | PLAY0268 | Historical 4.135.0 source check: composite `by` blocks remain unadmitted (#599); optional scalar snapshot lookup binds |
-| `observable`, `filter`, `scoped to`, `performer` queries | PLAY0268 | "uses delivery, filtering, scope, or implementation behavior outside the first ESM v1 vertical." `observable` goes in the return position (`=> observable RM optional`); as a body line it is PLAY0048 |
+| `query` with a composite `by` block, or `by ... from` context-derived arguments | PLAY0268 | composite `by` blocks remain unadmitted (#599). An optional scalar snapshot lookup, an unfiltered list (`RM[]`) and a list narrowed by one caller-supplied `by` key bind, in their `observable` form too (since 4.105.0) |
+| `filter`, `scoped to`, `performer` queries | PLAY0268 | "uses delivery, filtering, scope, or implementation behavior outside the first ESM v1 vertical." `observable` is not the blocker: it goes in the return position (`=> observable RM[]`); as a body line it is PLAY0048 |
 | `contains` or `starts with` in conditions | PLAY0268 | equality and numeric ordering only |
 | Date or DateTime comparison, `today` | PLAY0268 | no runtime date value |
 | Rule on a nested path (`lines.qty all > 0`) | PLAY0268 | put the rule on the nested value's concept |
@@ -222,7 +230,7 @@ bodies still leave their owner non-executable.
 | `$eventContext.occurred.Week` | PLAY0273 | derived value |
 | Projection `parent p` where `p` is not on the child event | PLAY0273 | "Event property not found" |
 | `generated` or `returns` on a compiler before 4.68.0 (4.66.0 and 4.67.0 refuse; 4.66.0 is bundled in cratis 3.28.x) | PLAY0268 | admitted from standalone 4.68.0 (ESM v7), see above |
-| Operations or systems, `numbers exact`, reaction refusals/redelivery | PLAY0268 | not admitted by any supported ESM version; one such construct leaves the **whole** application without an executable model. Event sources/streams/routes instead bind as ESM v8 on the current compiler (`sources-and-streams.md`) |
+| Operations or systems, `numbers exact` source mode, reaction refusals/redelivery | PLAY0268 | not admitted by any supported ESM version; one such construct leaves the **whole** application without an executable model. Event sources/streams/routes instead bind as ESM v8 on the current compiler (`sources-and-streams.md`) |
 | Spec of a gated command or query without `given caller` | PLAY0389 | module and feature gates count |
 | `given` or `then readmodel` missing key parts | PLAY0351 | explicit `key` marks replace inference; composite fixtures need every part but remain unadmitted (#599) |
 | When-less spec asserting events or errors | PLAY0352 | |

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

@@ -14,11 +14,10 @@ the file that holds it.
 | --- | --- | --- |
 | TrogonStack/agentskills `7b249d3ee42d8b7e11fa564141ebd5fbc37aadf1` (MIT, Copyright (c) 2025 Straw Hat, LLC) | none: no passage of this skill is adapted from it | no third-party notice needed in `LICENSE` |
 
-## Adapted closely (Martin Dilger and Nebulit GmbH, with agreement)
+## Adapted closely (Martin Dilger and Nebulit GmbH)
 
 Source: https://github.com/Nebulit-GmbH/agentic-engineer at commit `07b0f30648d663cb588d7e2c7aa031af9dfc21f2`,
-by Martin Dilger and Nebulit GmbH (https://nebulit.de). The repository carries no licence file; this material
-is adapted with the agreement of Martin Dilger and Nebulit GmbH.
+by Martin Dilger and Nebulit GmbH (https://nebulit.de), used with the explicit consent of Martin Dilger and Nebulit GmbH.
 
 | Source file | Used in | How |
 |---|---|---|