@cratis/pi 7.32.0 → 7.34.0

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 4.73.1 rendered apps pin Arc 22.68.0 and Chronicle client/kernel
+19.45.0, 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.** Stage 4.73.1 scaffolds Arc 22.68.0
+and Chronicle client/kernel 19.45.0 (not the latest releases). `[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

@@ -27,6 +27,23 @@ compatibility scenarios below first; the identity owner then applies the change
 A test for "generation or new event": a new version must be convertible from the old one
 without inventing facts. If it is not, it is a different event.
 
+## Enum identities are stored contracts
+
+Unnumbered enums use zero-based declaration positions: a reorder or insertion can
+reinterpret stored numbers. Before reordering or removing members, pin each to its
+**existing stored number**, not its new position. `propose-number-enum-members`
+pins an unnumbered enum to current positions; use it before changing order, only
+when those positions match storage. Never renumber or reuse a published member's
+number. Removing a member still needs replay and mixed-reader compatibility decisions.
+
+Numbered members may have sparse or negative unique int32 values, all or none per
+enum. Source authoring shipped in 4.137.0; non-positional numbers bind as ESM v12
+in 4.139.0. Positional pins retain older executable bytes/version. CLI 3.53.1 and
+Stage 4.73.1 bundle 4.137.0 and do not admit v12; keep the pins and report the gap.
+Short-lived input/view-only enums may remain positional. Use opt-in
+`--check enum-pinning` (PLAY0671) to find unnumbered enums used by event properties.
+Syntax/example and source evidence: command-surface [enum numbers](../../cratis-screenplay-command-surface/references/enum-numbers.md).
+
 ## Compatibility scenarios (write before editing)
 For each changed event, answer in the slice `documentation` or `STATE.md`:
 1. **Replay**: does every projection still build from generation 1 facts? Which value do old
@@ -60,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/stream-patterns.md

@@ -216,7 +216,7 @@ Some event stores decide consistency by a query over tagged events instead of on
 check to event types, source type or stream (`concurrency` block, Screenplay
 `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.50.0 reaches Stage construct checks
+Route admission does not make a view read protected. The pinned CLI (toolchain `references/versions.md`) reaches Stage construct checks
 through v10; 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/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

@@ -22,16 +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. For exact diagnostic codes, MCP names/parameters and standalone CLI options, search the large published [references/screenplay-contract.json](references/screenplay-contract.json), pinned by [references/screenplay-contract.version](references/screenplay-contract.version), rather than loading it in full. Locate a diagnostic by its exact `code` (for example `"code": "PLAY0029"`), a tool by its exact `name` (for example `"name": "read-workspace"`), or a command in `cliCommands`; read the matched object for retirement, parameters or options. [references/screenplay-contract-exceptions.json](references/screenplay-contract-exceptions.json) records reasoned exceptions for historical statements; it does not change the current contract.
 
-The standalone pin is Screenplay 4.135.0. CLI 3.50.0 bundles Screenplay 4.131.0,
-Stage 4.67.0 and Cratis.Arc.Screenplay 22.54.0. The single version table records
+The standalone pin is Screenplay 4.139.0.
+CLI and bundled package pins: `references/versions.md`. 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.
 
 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.50.0
-or Screenplay 4.135.0.
+recorded in that vector. These retained results are not a rerun on CLI 3.53.1
+or Screenplay 4.139.0.
 
 ## Ground rules
 
@@ -43,7 +43,8 @@ or Screenplay 4.135.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,10 +65,10 @@ or Screenplay 4.135.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 | CLI 3.50.0 passes through ESM v10 to Stage construct admission; newer versions: `CLI-RENDER-004` |
+| 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` |
 
 Read `references/versions.md` when you need the exact messages, exit codes or the MCP roots bug.
 
@@ -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,17 +100,18 @@ 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.
-  CLI 3.50.0/Stage 4.67.0 reaches construct admission through v10, not blanket
+  The pinned CLI/Stage pair (`references/versions.md`) reaches admission through v10, not blanket
   rendering. Operations and exact numeric source mode remain unadmitted.
   Details: `references/sources-and-streams.md` and `references/versions.md`.
 - **Released v9/v10 and published v11:** public contracts and direction select v9;
@@ -119,6 +121,15 @@ changes with the root folder name.
   `key` binds. Read `references/production-routes-and-filters.md` and read-surface
   `references/named-keys.md`; version freeze and numeric boundaries: `references/versions.md`.
 
+- **Published v12 (4.139.0):** non-positional enum numbers bind; canonical
+  `numbers` parallels `values`. Positional pins preserve earlier executable
+  bytes/version. Specifications still use names. The pinned CLI's compiler accepts source
+  authoring but refuses non-positional numbers at binding (PLAY0268), before
+  renderer admission. Neither its compiler nor Stage reads v12 ESM; upgrading
+  only the compiler would not lift their v10 admission ceiling (`references/versions.md`). Syntax:
+  command-surface `references/enum-numbers.md`; errors PLAY0667–0670 and opt-in
+  `enum-pinning` hint PLAY0671: `references/diagnostics.md`.
+
 - **Caller/compliance metadata** at 4.127.0: `$identity` aliases caller built-ins;
   additional identity details are metadata and executable reads still refuse.
   Bare `pii`/`secret` replace legacy spellings; `pii personal` repeats one marker
@@ -174,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

@@ -21,10 +21,13 @@ PLAY0268 (#599), not v10. Read [named keys](../../cratis-screenplay-read-surface
 Production `stream Source.Stream` overrides and reaction/reducer `from Source[.Stream]`
 select released v10: [routes and filters](production-routes-and-filters.md).
 Qualifying non-route Double literals select published v11 at 4.135.0;
-`numbers exact` does not bind. See `versions.md` for freeze and numeric boundaries.
+`numbers exact` does not bind. Non-positional enum member numbers (`draft = 1`)
+select published v12 at 4.139.0; positional pins keep earlier bytes/version,
+while specifications still use names. The pinned CLI/Stage pair (`versions.md`) does not admit v12.
+Syntax/example: command-surface `references/enum-numbers.md`.
+See `versions.md` for freeze and numeric boundaries.
 
-Current pins: standalone Screenplay 4.135.0 / CLI 3.50.0; `versions.md` is the
-single table. Compile evidence below keeps its historical tool labels.
+Current pins: `versions.md` (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
@@ -84,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/diagnostics.md

@@ -5,6 +5,7 @@
 - Warnings that hide defects (always validate with `--warnings-as-errors`)
 - Source reference and identifier checks
 - Public events and translation direction
+- Explicit enum member numbers
 - Named keys, production routes and observer filters
 - Caller identity, compliance and routes
 - Specification metadata, callers, cases and locators
@@ -53,7 +54,7 @@ Legacy compliance spellings (`@pii`/`@sensitive`) do not evade PLAY0515.
 
 ## Public events and translation direction
 
-Current at Screenplay 4.135.0; all are errors. These constructs bind as released
+Source checked at Screenplay 4.135.0; all are errors. These constructs bind as released
 ESM v9, except public/foreign imports without local shapes (PLAY0268).
 
 | Code | Meaning / fix |
@@ -79,6 +80,24 @@ or non-Translate direction. Repair discovery uses `repair-capabilities`, workspa
 `repairs`, then revision-checked `propose-repair`; do not guess a direction.
 See automations-and-translations `references/public-events-and-direction.md`.
 
+## Explicit enum member numbers
+
+Source errors from Screenplay 4.137.0; ESM v12 admission from 4.139.0:
+
+| Code | Severity | Meaning / fix |
+| --- | --- | --- |
+| PLAY0667 | E | Mixed numbered/unnumbered members; number all or none |
+| PLAY0668 | E | Duplicate enum number; aliases are not supported |
+| PLAY0669 | E | Number outside int32 (-2147483648 through 2147483647) |
+| PLAY0670 | E | Malformed number: decimal digits, optional minus, no leading zero, fraction, exponent or plus |
+| PLAY0671 | I | Opt-in `enum-pinning` completeness hint for an unnumbered enum used by an event property; ordinary compilation does not report it |
+
+Numbering errors have no automatic repair. PLAY0671 suggests the opt-in
+`propose-number-enum-members` refactoring, not a correctness repair. Member names
+remain specification values. Non-positional pins select v12; positional pins keep
+older executable bytes/version. Consumer admission is separate (`versions.md`).
+Source: `v4.139.0:Documentation/screenplay/diagnostics.md`, decision 0065.
+
 ## Named keys, production routes and observer filters
 
 | Code | Severity | Meaning / fix |
@@ -312,7 +331,7 @@ Report each as `code file:line one-line meaning`; never paste more than about 30
 
 ## Render admission (V5): `STAGE-*`, `CLI-RENDER-*`, `STAGE-CRATIS-*`
 Full table with causes: `renderable-subset.md`. The Stage 4.24.x rows below
-retain historical source/probe evidence. Current CLI 3.50.0/Stage 4.67.0 admits
+retain historical source/probe evidence. The pinned CLI/Stage pair (`versions.md`) admits
 through v10 to construct checks; above it is CLI-RENDER-004 (direct Stage:
 STAGE-ESM-016). Publication STAGE-ESM-032, foreign facts/event captures 033,
 reaction identity 034, reaction filters 035 and production overrides 036 remain

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

@@ -1,6 +1,6 @@
 # Documentation contradictions and which side to trust
 
-Current pins are Screenplay 4.135.0 / CLI 3.50.0 (`versions.md`). This is a
+Current pins: `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 admits through
@@ -42,7 +42,7 @@ read from source or documentation.
 | 14 | `$causedBy` | not evaluable (#4119), not ESM | showcase only |
 | 15 | literal keys | `key literal "global"` vs `key "global"` | both compile; prefer `literal` |
 | 16 | query admission | `D/queries.md:74` now says live, filtered, scoped and performer queries are not admitted | the binder also rejects collection queries and a missing `by`, which stay undocumented [probed] |
-| 17 | `@pii` | `D/concepts.md:3,33` "Chronicle applies `@pii` and `@sensitive` rules automatically" | the binder rejects any compliance attribute (PLAY0268); keep it, report V3 blocked. `@sensitive` means an operational secret (`[Encrypted]` + `[NotAudited]`; Screenplay decision 0034); the pinned tools (standalone 4.68.0, bundle 4.66.0) do **not** report `PLAY0515` (`@pii` from 4.69.1, `@sensitive` from 4.84.1): there only Chronicle catches either attribute on an event-source identifier, at build time of the generated code (CHR0034 for `@pii`, CHR0052 for `@sensitive`) |
+| 17 | `@pii` | `D/concepts.md:3,33` "Chronicle applies `@pii` and `@sensitive` rules automatically" | the binder rejects any compliance attribute (PLAY0268); keep it, report V3 blocked. `@sensitive` means an operational secret (`[Encrypted]` + `[NotAudited]`; Screenplay decision 0034); the historically probed tools (standalone 4.68.0, bundle 4.66.0) do **not** report `PLAY0515` (`@pii` from 4.69.1, `@sensitive` from 4.84.1): there only Chronicle catches either attribute on an event-source identifier, at build time of the generated code (CHR0034 for `@pii`, CHR0052 for `@sensitive`) |
 | 18 | read-model identity | `D/readmodels.md:32` "from the keyed query" | at 4.135.0 explicit `key` wins; else single-instance queries agree on one read-model `by` property; only with none and an admitted list query does conventional `*Id` inference run (collection-key exclusions: read-surface `references/named-keys.md`). Queryless views need explicit `key` |
 | 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 |
@@ -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