@cratis/pi 7.29.1 → 7.31.0

package/package/corpus/skills/cratis-screenplay-slice-design/SKILL.md

@@ -113,10 +113,14 @@ report and slice `documentation`, and continue.
    slice is `read model -> screen -> command -> event`. Pick the builder (declarative projection first, reducer when
    guards cannot be expressed). The query follows the business view: a list where people scan a
    list, a keyed lookup where they open one thing. For **executable or renderable scope**, every
-   read model also needs one unambiguous key: keyed queries `query XById => RM optional` all
-   using the same `by xId XId`. The identifier always equals the projection's effective key;
-   the decision table is in `references/read-model-design.md` and the full rule in
-   `cratis-stage-rendering-and-sandbox` `references/admission.md`. Keep the list query in design mode and record that it blocks V3.
+   read model needs one unambiguous identity: explicit trailing `key` first, else
+   single-instance queries agreeing on `by xId XId`, else conventional `*Id` inference
+   only with an admitted list query and no single-instance identifier. Queryless views
+   need explicit `key`; read-surface `references/named-keys.md` gives the exact fallback.
+   The identifier equals the projection's effective key (decision table in
+   `references/read-model-design.md`; Stage rule in `references/admission.md` of
+   `cratis-stage-rendering-and-sandbox`). Collections and observable delivery bind at
+   4.135.0; check renderer admission separately.
    Whose rows is part of the view; a caller-supplied filter is not access control.
 7. **Screens, Level 1.** `data <RM> via query <Q>` plus `action <Command>` per thing the user
    can do there. Build each slice as read model, screen, command, event. A screen acting on an
@@ -149,11 +153,13 @@ report and slice `documentation`, and continue.
 ### Compiler contracts (the tool enforces these)
 
 - At most one `identifier` per command; never on an event property; never on a read-model
-  property (identity comes from the keyed query's `by`).
+  property (use `key`; otherwise identity comes from single-instance `by`, or
+  conventional `*Id` only with an admitted list query and no single-instance identifier).
+  Queryless read models need explicit `key`.
 - At most one builder (projection or reducer) per read model (`PLAY0191`).
-- A query's `by` goes on its own body line. Only `=> RM optional` with one caller-supplied `by`
-  binds in the executable model; list, observable, filtered or scoped queries are `PLAY0268` at
-  binding but compile.
+- A query's `by` goes on its own body line. At 4.135.0, optional keyed and collection
+  queries bind, including observable delivery; scalar `by` must be caller-supplied.
+  Filtered, scoped, performer-backed and composite-block queries remain `PLAY0268`.
 - A `unique` constraint names a property the event declares directly; the constraint name is
   its identity (renaming starts an empty index).
 - Unauthorized is `then denied`; a broken rule is `then error`; authorization runs first.
@@ -181,6 +187,21 @@ report and slice `documentation`, and continue.
 Ask `references/review-questions.md` (reachability, forms in disguise, secrets, fan-in,
 collections, invariants, who sees which rows); report a finding only with a domain consequence.
 
+## Public boundaries and view identity
+
+Translate crosses an application boundary: inbound consumes foreign public events
+or data and produces private facts; outbound folds private facts into exactly one
+local public event type. Commands never publish public events. Put direction in
+the slice outline and trace every exported field; read automations-and-translations
+`references/public-events-and-direction.md` for the released ESM v9 contract.
+
+Mark view identity with trailing `key`. Use a composite key for independent view
+coordinates (resource + period), a natural single id for one entity's state.
+Supply every named part in single-instance queries and command/trigger reads;
+see read-surface `references/named-keys.md`. Composite view keys remain
+unadmitted at 4.135.0 (PLAY0268, #599), unlike admitted composite stream routes.
+Keep the true identity and report the gap rather than inventing a concatenated id.
+
 ## Identity-affecting edits on an existing model
 
 Classify an edit by whether it changes catalog addresses. When `.screenplay/identities.json`
@@ -203,7 +224,9 @@ Slice design is done when these hold; otherwise report what is open.
 - [ ] Every command has a refusal inventory (success, each refusal with layer and message,
       denied persona); every gated command and query has a `then denied` row.
 - [ ] Every event is past tense, a specific change, and consumed or justified.
-- [ ] Every read model has a consumer and, when the scope is executable, one unambiguous key (keyed queries all using the same `by` property).
+- [ ] Every read model has a consumer and, for executable scope, one identity: explicit
+      `key`, else agreeing single-instance `by`, else unambiguous `*Id` only with an
+      admitted list query and no single-instance identifier. Queryless views use `key`.
 - [ ] Every StateView's `documentation` gives a reason per contributing event; every read-model
       field and screen field is traced; every `from` event sets a field.
 - [ ] No `screen` without `data` or `action`; every acting screen has `data` or a stated

package/package/corpus/skills/cratis-screenplay-slice-design/references/read-model-design.md

@@ -118,21 +118,27 @@ it stays.
 
 | The person... | Design-mode query | Executable/renderable scope |
 |---|---|---|
-| opens one thing | `XById => RM optional` + `by xId XId` | same (the only shape that binds today) |
-| scans a list | `ListX => RM[]` (optionally `observable`, `filter`) | keep the list for design; add the keyed query; record V3 blocked by the list |
-| sees their own rows | list with scope/`from` on the caller | as above; access rules are part of the view, enforced by the target |
+| opens one thing | `XById => RM optional` + `by xId XId` | binds at 4.135.0 with caller-supplied `by`; check target renderer |
+| scans a list | `ListX => RM[]` (optionally `observable`, `filter`) | collection and observable delivery bind at 4.135.0; filters remain PLAY0268; check target renderer |
+| sees their own rows | list with scope/`from` on the caller | scope and context-derived `by` remain PLAY0268; access rules are part of the view, enforced by the target |
 | sees a site-wide figure | singleton read model, `from <Event> key literal "global"` on every `from` (a projection-level `key` routes nothing, PLAY0381; example in Screenplay `projections/keys.md`, "Literal keys") | check the binding (V3, `cratis-screenplay-toolchain`) |
 
 - `observable` when people are expected to see others' or automation's changes while looking
-  (worklists, status awaiting an outside answer); one-shot otherwise. Design mode only
-  (PLAY0268). If access can be revoked mid-session, record that the target re-checks per emission.
+  (worklists, status awaiting an outside answer); one-shot otherwise. Observable delivery
+  binds at 4.135.0; renderer support is separate. If access can be revoked mid-session,
+  record that the target re-checks per emission.
 - Never model paging or page size (no syntax, Screenplay#140). State the order in the query
   `description` ("oldest first"; queries do not accept `documentation`); an unbounded list is a review question.
 - A gated keyed query needs its own denial spec.
 
-Never drop a list query from a design model just to make it bind; record the capability gap.
-The keyed query also defines the read model's identity: its `by` property must be a read-model
-property. The identifier always equals the projection's effective key:
+Never drop a business-required list query to satisfy an old compiler or renderer;
+record any actual capability gap. At 4.135.0, explicit trailing `key` takes precedence
+for read-model identity. Otherwise single-instance queries in the owning slice must
+agree on one `by` property declared on the read model. Only with no single-instance
+identifier and an admitted collection/list query does conventional `*Id` inference
+run; queryless views need explicit `key`. The fallback excludes collection-query key
+candidates when that leaves one identifier (full algorithm: read-surface
+`references/named-keys.md`). The identifier equals the projection's effective key:
 
 | Effective key | Executable model | Renderable model (Stage) |
 |---|---|---|
@@ -182,8 +188,8 @@ has children, not a single value.
 If a view must stop showing cancelled items, use `remove with <Event>` and pin it with
 `then no readmodel <RM> for "<key>"`. If it keeps them, map a status literal from that event
 instead. The slice `description`, the projection and every spec of the view must agree.
-A complete example (marina berths; the `then no readmodel` assertion needs the keyed
-query, which is why the view has one):
+A complete example (marina berths; the keyed query supplies the view's identity
+for the `then no readmodel` assertion; explicit `key` could supply it instead):
 
 ```screenplay
 domain Harbourlight.Berths
@@ -277,7 +283,8 @@ module Berths
 - Every consumer that needs state has its read model (a blank creation form and a direct reaction
   with a documented no-pending-work reason need none); every read model has a consumer.
 - Every field traced (`field-lineage.md`).
-- Executable/renderable scope: one unambiguous key per read model (one or more keyed queries,
-  all with the same `by` property), identifier equal to the projection's key (table above);
-  no list queries.
+- Executable scope: one identity per read model: explicit `key`, else agreeing
+  single-instance `by`, else unambiguous `*Id` only with an admitted list query and
+  no single-instance identifier. Queryless views need explicit `key`. The identifier
+  equals the projection's key (table above); check target renderer admission separately.
 - Design-only shapes listed with the V3 code they cause.

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

@@ -26,16 +26,9 @@ source is the single flow model.
 
 ## Verified product sources
 
-| Package | Version | Purpose |
-| --- | --- | --- |
-| `Cratis.Screenplay` | `4.31.0` | Original parser, binder and reference execution evidence |
-| `Cratis.Screenplay` | main `fd18129` | Inline facts, `optional` and clock spelling; changed examples compiled |
-| `Cratis.Screenplay` | `4.68.0` (`79801bf`) | ESM v7 generated fixtures and `then returns` (decision 0026, `specifications.md` "Generated fixtures and return expectations"): the excerpt matches the compiled example in `cratis-screenplay-toolchain`, whose specifications run in the reference runner |
-| `Cratis.Screenplay` | `4.66.0` (`c89198b`) | ESM v6 specification actions and reaction cascades, `then no readmodel`, `$strings` rejections, `invokes` caller rule; probed with the standalone tool and its MCP server |
+Retained inline-fact update evidence: [source notes](references/source-notes.md).
 
-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.
+The historical parser/binder/reference-runner version table is in the source notes.
 
 Specification syntax was checked against Screenplay v4.127.0 `specifications.md`;
 older probes in the table remain historical. Pins: `cratis-screenplay-toolchain`
@@ -207,6 +200,15 @@ 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).
 
+## Published-event specifications (released ESM v9)
+
+Use `when append <PrivateEvent>` then `then <PublicEvent>` for outbound publication,
+not `then readmodel`. The follow-up event list is exhaustive and ordered. Read
+[publication example and fold cases](../cratis-screenplay-automations-and-translations/references/public-events-and-direction.md).
+Events-source captures and reached opaque event-target reducers return typed
+Unsupported, not a pass. Composite view fixtures need every key part but remain
+unadmitted (PLAY0268, #599); see read-surface `references/named-keys.md`.
+
 ## Reusable fixtures, routes and recovery intent
 
 Use typed `example` declarations for repeated event/command/read-model values;
@@ -278,7 +280,7 @@ For view specifications:
 ## Verify
 
 - [ ] Validate the complete root with warnings as errors, naming tool/version.
-      Current standalone pin: 4.131.0. Run specification examples through
+      Current standalone pin: 4.135.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.

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

@@ -94,8 +94,9 @@ so UUID casing is immaterial. Composite mappings supply each named part once,
 using literals only; encoding escapes `%`/`|` and preserves declaration order.
 Source: v4.127.0 `event-sources.md`, `specifications.md`, `diagnostics.md`.
 
-CLI 3.46.1 rendering rejects versions above v7 before planning, even though
-source compilation and reference routing pass.
+Previous CLI 3.46.1 refused above v7; CLI 3.50.0/Stage 4.67.0 reaches route
+checks through v10. Routed read-model/query replay can still refuse
+STAGE-ESM-030. Source/reference success never establishes target parity.
 
 Command and read-model examples refuse routes (PLAY0526). Effective role and
 `for` checks use the inherited or replaced route: inherited `no stream` on a

package/package/corpus/skills/cratis-screenplay-specifications/references/source-notes.md

@@ -0,0 +1,16 @@
+<!-- Copyright (c) Cratis. All rights reserved. -->
+<!-- Licensed under the MIT license. See LICENSE file in the project root for full license information. -->
+
+# Retained source notes
+
+| Package | Version | Purpose |
+| --- | --- | --- |
+| `Cratis.Screenplay` | `4.31.0` | Original parser, binder and reference execution evidence |
+| `Cratis.Screenplay` | main `fd18129` | Inline facts, `optional` and clock spelling; changed examples compiled |
+| `Cratis.Screenplay` | `4.68.0` (`79801bf`) | ESM v7 generated fixtures and `then returns` (decision 0026, `specifications.md` "Generated fixtures and return expectations"): the excerpt matches the compiled example in `cratis-screenplay-toolchain`, whose specifications run in the reference runner |
+| `Cratis.Screenplay` | `4.66.0` (`c89198b`) | ESM v6 specification actions and reaction cascades, `then no readmodel`, `$strings` rejections, `invokes` caller rule; probed with the standalone tool and its MCP server |
+
+The inline-facts update followed `commands.md`, `events.md`, `types.md` and
+`specifications.md` at main `fd18129` (after v4.52.0). That pass compiled the
+changed examples; it did not rerun the reference runner. Keep this historical
+source evidence distinct from the current source-check gate and V4 execution.

package/package/corpus/skills/cratis-screenplay-specifications/verification.json

@@ -6,12 +6,12 @@
     { "kind": "play-compiles" },
     {
       "kind": "skill-contains",
-      "value": "main `fd18129`"
+      "value": "main `fd18129`", "file": "references/source-notes.md"
     },
     { "kind": "skill-contains", "value": "Generated fixtures and return expectations (ESM v7)" },
     { "kind": "skill-contains", "value": "`then returns` counts as a success outcome but does not relax event comparison", "file": "references/generated-fixtures.md" },
     { "kind": "skill-contains", "value": "`Unsupported(IdentityAllocation)`", "file": "references/generated-fixtures.md" },
-    { "kind": "skill-contains", "value": "4.68.0" },
+    { "kind": "skill-contains", "value": "4.68.0", "file": "references/source-notes.md" },
     {
       "kind": "skill-contains",
       "value": "Inline events are ordinary named facts", "file": "references/worked-example.md"

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

@@ -88,8 +88,8 @@ option, mark it `ASSUMED` in the slice or module `documentation` and in the sess
    namespace, process-stream routing and concurrency scope apart
    (`references/chronicle-boundaries.md`). Declared `eventsource`/`stream`/`streamId` and
    command/specification routes bind and reference-execute as ESM v8 on 4.125.0.
-   CLI 3.46.1 rendering admits through v7 only (CLI-RENDER-004); keep the routing
-   contract and gap-fill its target realization. Forms/boundaries:
+   CLI 3.50.0 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
    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

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

@@ -216,8 +216,8 @@ 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.46.1's render boundary
-is v7; see toolchain `references/versions.md`. Model the stream by business
+Route admission does not make a view read protected. CLI 3.50.0 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/verification.json

@@ -16,6 +16,6 @@
     { "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": "CLI-RENDER-004" }
+    { "kind": "skill-contains", "value": "Stage construct checks through v10" }
   ]
 }

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.131.0. CLI 3.46.1 bundles Screenplay 4.130.0,
-Stage 4.52.0 and Cratis.Arc.Screenplay 22.54.0. The single version table records
+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
 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.46.1
-or Screenplay 4.131.0.
+recorded in that vector. These retained results are not a rerun on CLI 3.50.0
+or Screenplay 4.135.0.
 
 ## Ground rules
 
@@ -67,7 +67,7 @@ or Screenplay 4.131.0.
 | 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.46.1 passes up to ESM v7 to Stage; newer versions: `CLI-RENDER-004` |
+| 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` |
 
 Read `references/versions.md` when you need the exact messages, exit codes or the MCP roots bug.
 
@@ -108,9 +108,16 @@ changes with the root folder name.
   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.46.1
-  render refuses versions above v7 (`CLI-RENDER-004`). Operations and exact numeric
-  mode remain authorable/unadmitted. Details: `references/sources-and-streams.md`.
+- **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
+  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;
+  reaction identity, production overrides and observer filters select frozen v10;
+  qualifying retained non-route Double literals select v11 at 4.135.0.
+  Composite view keys remain authoring-only (PLAY0268, #599), while one explicit
+  `key` binds. Read `references/production-routes-and-filters.md` and read-surface
+  `references/named-keys.md`; version freeze and numeric boundaries: `references/versions.md`.
 
 - **Caller/compliance metadata** at 4.127.0: `$identity` aliases caller built-ins;
   additional identity details are metadata and executable reads still refuse.
@@ -157,8 +164,10 @@ Read [references/diagnostics.md](references/diagnostics.md) when a PLAY, STAGE o
    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.
+7. Mark read-model identity with trailing `key`, not `identifier`. Otherwise single-instance
+   queries must agree on `by`; only with none and an admitted list query can `*Id`
+   inference run. Queryless views need `key` (read-surface `references/named-keys.md`).
+   Align projection keys. Multipart keys remain PLAY0268 (#599).
 8. Projection `key` routes only on `from`; joins never create; `all` is per source.
 9. `null` only for optional read-model properties in specifications.
 10. `then` events are exhaustive and ordered; after `when append` they list only what followed.

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

@@ -12,7 +12,18 @@
 - 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.131.0 / CLI 3.46.1; `versions.md` is the
+Released boundary forms: `public event X`, `event X from "store"`, Translate
+`direction inbound|outbound`, event-target `projection/reducer P => PublicEvent`,
+and capture `source events` with `from ForeignEvent` select v9. Read
+[public contracts](../../cratis-screenplay-automations-and-translations/references/public-events-and-direction.md).
+View properties use trailing `key`; multipart `by` query/read blocks remain
+PLAY0268 (#599), not v10. Read [named keys](../../cratis-screenplay-read-surface/references/named-keys.md).
+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.
+
+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.
 
 The syntax lives in compiled example files next to this one (each is a Markdown file holding

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

@@ -4,6 +4,8 @@
 
 - Warnings that hide defects (always validate with `--warnings-as-errors`)
 - Source reference and identifier checks
+- Public events and translation direction
+- Named keys, production routes and observer filters
 - Caller identity, compliance and routes
 - Specification metadata, callers, cases and locators
 - Guarded interaction diagnostics
@@ -49,6 +51,53 @@ At Screenplay 4.127.0 these are V1 source checks, not binding-only gaps:
 
 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
+ESM v9, except public/foreign imports without local shapes (PLAY0268).
+
+| Code | Meaning / fix |
+| --- | --- |
+| PLAY0607 | A command produces a public event; move publication to outbound Translate |
+| PLAY0608 | Local public production outside explicit outbound Translate |
+| PLAY0609 | Outbound translation has zero or several local public event types; repeated instances of one type count once |
+| PLAY0610 | Foreign public consumption outside explicit inbound Translate |
+| PLAY0611 | Outbound consumes a public or foreign event; consume private local facts |
+| PLAY0612 | Inbound produces a public or foreign event; produce private local facts |
+| PLAY0613 | Foreign public event produced locally; translate to a private event |
+| PLAY0614 | Public metadata without explicit direction; typed repair declares inbound/outbound only when exactly one direction fits |
+| PLAY0615 | Outbound contains an external-data capture |
+| PLAY0616 | Explicit inbound consumes private or local events instead of public foreign events |
+| PLAY0617 | Outbound produces a private event instead of its one local public type |
+| PLAY0618 | Event-target projection/reducer outside explicit outbound Translate |
+| PLAY0619 | `source events` capture outside explicit inbound Translate |
+| PLAY0620 | Missing, malformed or repeated `from <Event>` in `source events` |
+
+Only PLAY0614 in this range has a repair. Legacy directionless translations
+without public metadata stay inbound. PLAY0027 also covers malformed, repeated
+or non-Translate direction. Repair discovery uses `repair-capabilities`, workspace
+`repairs`, then revision-checked `propose-repair`; do not guess a direction.
+See automations-and-translations `references/public-events-and-direction.md`.
+
+## Named keys, production routes and observer filters
+
+| Code | Severity | Meaning / fix |
+| --- | --- | --- |
+| PLAY0660 | E | Invalid top-level read-model key owner/modifier/type; multipart parts must be scalar; no repair |
+| PLAY0661 | E | Missing single-instance lookup parts; repair **command reads only** if every missing part has one same-named compatible source, preserving authored mappings and refusing ambiguity |
+| PLAY0662 | E | Invalid block/shape, duplicate or unknown part, incompatible/optional/collection/literal read source; block needs at least two distinct parts; no repair |
+| PLAY0663 | E | Route on reaction/refusal-branch production; only command event productions override routes |
+| PLAY0664 | W | Override repeats complete command route; typed repair removes the redundant override |
+| PLAY0665 | E | Invalid/duplicate/child-bearing/unresolved source/stream filter or filtered reaction with a non-event trigger |
+| PLAY0666 | W | Filter excludes all statically known effective producer routes; C# only, handlers/foreign origins suppress it |
+
+Queries and trigger reads have no PLAY0661 repair. Composite view keys, query
+blocks and their fixtures remain PLAY0268 (#599), while one explicit key binds
+byte-identically to inference. Fixtures missing any part report PLAY0351.
+Overrides/filters select released ESM v10; malformed routes also use PLAY0504.
+Read read-surface `references/named-keys.md` and
+[production routes and filters](production-routes-and-filters.md).
+
 ## Caller identity, compliance and routes
 
 Source authority: v4.127.0 `diagnostics.md`, `identity.md`, `concepts.md`,
@@ -263,9 +312,12 @@ 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.46.1 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.
+retain historical source/probe evidence. Current CLI 3.50.0/Stage 4.67.0 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
+refused; reducer filters render. Previous CLI 3.46.1 admitted through v7; its
+v7 corpus received STAGE-ESM-028/029, not the older v7 version gate.
 Codes in the historical snapshot:
 | Code | Meaning |
 |---|---|

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

@@ -1,9 +1,12 @@
 # Documentation contradictions and which side to trust
 
-Current pins are Screenplay 4.131.0 / CLI 3.46.1 (`versions.md`). This is a
+Current pins are Screenplay 4.135.0 / CLI 3.50.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.
+sources/routes bind as ESM v8; PLAY0515 is a source error; CLI admits through
+v10 to Stage construct checks. At `v4.135.0:Documentation/screenplay/interoperability.md:133–137`
+v11 is still labeled "claimed, unreleased"; Versions.cs admits it and decision
+0066 freezes it on package publication. The corpus follows source and 0066.
 
 At v4.127.0 `concepts.md` links the shipped purpose declarations/checks/record
 but its final identifier section still calls them later phases. `purposes.md`,
@@ -40,11 +43,11 @@ read from source or documentation.
 | 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`) |
-| 18 | read-model identity | `D/readmodels.md:32` "from the keyed query" | the `by` name must also equal a read-model property (the doc still omits it) |
+| 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 |
 | 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) | 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 |
+| 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 responses, v8 routing, v9 public boundaries, v10 identity/routes/filters, v11 qualifying retained non-route Double literals at 4.135.0; operations and `numbers exact` source mode 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`) |

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

@@ -6,15 +6,17 @@
 - 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
+- Released public boundaries and observer routes
 - Code attachments (what binds, what never does)
 - Refused (code, reason): fix, or record as a mode gap
 - Not refused, but do not rely on it
 - Never do this to reach V3
 
-Current pins are Screenplay 4.131.0 / CLI 3.46.1 (`versions.md`). Detailed
+Current pins are Screenplay 4.135.0 / CLI 3.50.0 (`versions.md`). Detailed
 4.66.0/4.68.0 binder probes below retain their historical labels. Current source
-admits sources/streams/routes as ESM v8 and policy negation as ESM v7; operations,
-exact numbers and reaction refusals/redelivery remain unadmitted. Use the actual
+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
 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
@@ -66,10 +68,15 @@ Authority: v4.127.0 `context.md`, `identity.md`, `concepts.md`, `events.md`, `pu
   <commandProperty>`.
 - `constraint ... unique <prop> on <Event>`. Admission is separate from the open Chronicle
   durability defects (`versions.md`): never treat admission as proof of uniqueness.
-- A `readmodel` with one unambiguous key: one or more keyed queries `query XById => RM optional`
-  in its slice, all using the same `by xId XId` property, whose name equals a read-model
-  property (each with optional `authorize`). Two different `by` properties on one read model are
-  PLAY0268; a list query (`=> RM[]`) is a separate blocker.
+- A `readmodel` with one explicit trailing `key`, or an unambiguous inferred key:
+  single-instance queries in the owning slice agreeing on `by xId XId`; only if
+  none supplies identity and an admitted list query exists does conventional
+  `*Id` inference run (collection-key exclusions: read-surface `references/named-keys.md`).
+  Queryless read models need an explicit `key`. Explicit single keys preserve
+  equivalent inferred ESM bytes. Composite read-model keys, query `by` blocks and
+  their fixtures remain PLAY0268 (#599), not the 4.129.0 authoring delivery's
+  executable admission. Collections and observable delivery bind; filters, scope,
+  performer and context-derived `by` remain separate blockers.
 - One projection per read model: `from`, `every`, `all` (one block per level), `join`,
   `children`, `nested`, `remove with`, `remove via join` (binds; blocks the execution plan at the projection level, see below), `clear with`, counters, `add`,
   `subtract`, `set`, `clear`, variants, and the identifier mapped from the projection's key (`xId = $eventSourceId` only for an event-source key).
@@ -87,7 +94,7 @@ Authority: v4.127.0 `context.md`, `identity.md`, `concepts.md`, `events.md`, `pu
   ...` with an explicit `for`. Without a declared actor, a gated invocation denies.
   On 4.125.0 reaction `runs as system role "<Role>"` supplies the actor and
   selects ESM v10; keep the gate. CLI 3.41.0's older compiler rejected this syntax;
-  current CLI 3.46.1's bundle supports it, but render admission still refuses v10.
+  CLI 3.50.0's bundle supports it, but Stage refuses reaction identity with STAGE-ESM-034.
   Standalone reference execution admits it.
 - Application `trigger` declarations and `when trigger` specifications.
 - `slice Translate` with `capture` (`key`, `map ... translate`, `append ... when x from "a"
@@ -133,6 +140,19 @@ Stage#201), so they bind and run but are not rendered: gap-fill with the model a
 - A reaction-invoked command that reaches generation is `Unsupported(IdentityAllocation)`; response-only commands run
   and discard the response. Generated values give no idempotency, retry or deduplication guarantee.
 
+## Released public boundaries and observer routes
+
+Public/origin events, explicit Translate direction, event-target builders and
+`source events` captures bind as ESM v9 from 4.117.0. Publication folds execute;
+source-event captures and reached opaque event-target reducers return typed
+Unsupported. Public/foreign imports still lack a local shape and refuse PLAY0268.
+See automations-and-translations `references/public-events-and-direction.md`.
+Production overrides and reaction/reducer filters bind and select released v10;
+filters match routed source/stream names only. Read
+[production routes and filters](production-routes-and-filters.md).
+Qualifying retained non-route Double literals bind/reference-execute as v11 on
+4.135.0, unlike `numbers exact`; see `versions.md`.
+
 ## Code attachments (what binds, what never does)
 
 Inline fences (`csharp`, `typescript`, `react`, `html`, `sql`) and `file <path>` attach
@@ -176,7 +196,7 @@ 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 `by` | PLAY0268 | "must declare one caller-supplied 'by' argument" or "must return one optional read model" |
+| `query` returning a collection (`RM[]`), or without exactly one caller-supplied scalar `by` | PLAY0268 | Current 4.135.0 boundary: 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 |
 | `contains` or `starts with` in conditions | PLAY0268 | equality and numeric ordering only |
 | Date or DateTime comparison, `today` | PLAY0268 | no runtime date value |
@@ -198,7 +218,7 @@ bodies still leave their owner non-executable.
 | `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`) |
 | Spec of a gated command or query without `given caller` | PLAY0389 | module and feature gates count |
-| `given` or `then readmodel` missing the key property | PLAY0351 | key is the keyed query's `by` |
+| `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 | |
 | `null` in command or event values | PLAY0350 | Chronicle semantics, not only a binder limit: an optional fact is a separate event (nullable event properties are CHR0012) |
 | `for` with no unambiguous destination type | PLAY0273 | |