@cratis/pi 7.75.0 → 7.76.0

package/package/corpus/skills/cratis-chronicle-reducer/SKILL.md

@@ -234,6 +234,10 @@ event means no observer subscription; assembly membership alone is not event
 membership. Types implementing `IReducer` stay classic even with a self-shaped
 static helper.
 
+Requires Chronicle 19.72.0 for CHR0065 to warn on fold-like methods that are
+misnamed (`Reducer`/`reduce`) or not static and therefore never discovered.
+Check `dotnet list package`; older analyzers can leave those methods silent.
+
 Use the existing generic or Type `RegisterReducer` API for explicit self-model
 nomination too; there is no special self API. A self model cannot share ownership
 with a separate reducer, fluent projection or genuine model-bound mappings in the

package/package/corpus/skills/cratis-multi-service-architecture/SKILL.md

@@ -154,9 +154,15 @@ of tags, and export only the fields consumers need. Read
 ## Versioning contracts
 
 A public event type follows the same generation and migration rules as a private
-one (`cratis-chronicle-event-type-migration`). Kernel subscriptions name event
-types by id and register them as generation 1, and the CLI's `subscriptions add`
-takes ids only. Prefer additive, optional changes to a contract; publish a new
+one (`cratis-chronicle-event-type-migration`). Requires Chronicle 19.66.0 for
+subscription-builder `WithGenerationDelivery(EventGenerationDelivery.Pinned)`
+with typed `WithEventType<TEvent>()` or `WithEventType(id, generation)` to pin
+forwarding into the target inbox. Both stores must register that generation;
+Compatibility remains the default. Read
+../cratis-chronicle-client-dotnet/references/pinned-generation-delivery.md when
+configuring subscription pins and failure behavior. The CLI's `subscriptions add`
+takes ids only; do not invent a generation flag. Prefer additive, optional changes
+to a contract; publish a new
 event type for a breaking change and keep publishing the old one until every
 consumer has moved, rather than adding a generation consumers may not handle.
 Version the contracts package with the contract, and never move a type between

package/package/corpus/skills/cratis-performance-review/SKILL.md

@@ -80,7 +80,10 @@ behavior this file does not already state.
 - Preserve reducer admission and ordering guards when proposing a projection
   conversion; an unconditional setter may resurrect or prematurely create state.
 - Count passive models as inventory, not a smell. Assess history length and read
-  frequency against consistency/security needs. `IMongoCollection<T>` cannot
+  frequency against consistency/security needs. Requires Chronicle 19.77.3 for
+  per-key strongly consistent projection reads to fold from the start each time;
+  repeated reads are O(key history), not incremental cache hits. Prefer a
+  materialized projection for frequent long-history reads when freshness permits. `IMongoCollection<T>` cannot
   read passive computed state; never materialize secrets to make that query work.
 - Distinguish retained `Observe` state and in-memory emissions from explicit
   recompute queries. Narrow source filters and inspect page-refill/membership

package/package/corpus/skills/cratis-screenplay-automations-and-translations/SKILL.md

@@ -42,8 +42,8 @@ Start new models with application-root `reaction batches atomic` (ESM v22 or lat
 Each trigger occurrence's direct productions and each selected refusal branch are
 separate all-or-none batches; invoked commands remain independent. Absence retains
 legacy per-fact behavior even at later versions. Assert no failed-batch facts and
-unchanged views, not only `then error`. Stage refuses v22 (STAGE-ESM-016) and
-atomic mode in admitted v23/v24 models (STAGE-ESM-043); keep the semantics as gap-fill.
+unchanged views, not only `then error`. Requires Stage 4.139.0 for v22 admission
+(older: -016); atomic mode stays STAGE-ESM-043. Keep as gap-fill.
 Read [atomic batches and source mappings](../cratis-screenplay-captures-and-reactions/references/atomic-batches-and-source-mappings.md)
 when choosing these boundaries or mapping an invoked identifier from `$eventSourceId`
 (or `$eventContext.eventSourceId`) instead of copying it into event payload.

package/package/corpus/skills/cratis-screenplay-automations-and-translations/references/realization-and-gap-fill.md

@@ -22,11 +22,19 @@ recovery behavior rather than assuming this handler supplies all-or-nothing sett
 rejected model renderable, and never claim a whole-application V5 from a subset. Choose the route
 with `cratis-screenplay-render-and-gap-fill`.
 
-Application-root `reaction batches atomic` also blocks Stage delivery: v22
-refuses STAGE-ESM-016; mode in admitted v23–v27 refuses STAGE-ESM-043. Preserve the
+Application-root `reaction batches atomic` also blocks Stage delivery with
+STAGE-ESM-043. Requires Stage 4.139.0 for v22 admission; older Stage reports -016. Preserve the
 per-occurrence/selected-branch batch boundary and independent invoked commands.
 Atomic appends do not prove redelivery deduplication or external exactly-once effects.
 
+Requires Stage 4.141.1 for independent event-reaction specifications with `given clock`;
+older executors refuse clocks beside reactions. This supplies `$context.occurred`
+through cascades, invocation arguments and refusal branches, not a scheduler.
+Clock/non-event triggers still refuse `STAGE-ESM-024`. Generated append/redelivery
+clock fixtures retain -024 and context-dependent generated reaction specs retain -011.
+Read [sandbox occurrence boundaries](../../cratis-stage-rendering-and-sandbox/references/sandbox-and-specrunner.md)
+when verifying reaction time in Stage rather than reference execution.
+
 ## Where the pieces go (hand-written)
 | Model element | Realization | Skill |
 |---|---|---|

package/package/corpus/skills/cratis-screenplay-captures-and-reactions/SKILL.md

@@ -29,11 +29,11 @@ Language claims follow Screenplay `reactions.md`, `triggers.md`, `captures.md` a
 The compiler's ESM admission decides, not the slice type. Reactions, triggers and
 captures bind/reference-execute from v6; older compilers refuse them. Read toolchain
 `references/diagnostics.md` when diagnosing skew or false PLAY0285 cascades.
-- **The CLI and Stage** render supported event-triggered Automation, not
-  Translate/captures, non-event triggers or opaque bodies (`-024`). Role/authenticated `runs as`
-  and semantic `from` render; claim/opaque gates, mixed effects and unsupported mappings remain refused;
-  cascade specs remain `-011`. Keep refused scope as gap-fill. Full boundary and source
-  citations: `cratis-stage-rendering-and-sandbox` `references/admission.md`.
+- **Stage realization:** read `cratis-stage-rendering-and-sandbox` `references/admission.md`
+  before claiming rendering. Supported event-triggered Automation renders; captures,
+  Translate, clocks and opaque bodies remain gap-fill (`-024`).
+  Read [sandbox boundaries](../cratis-stage-rendering-and-sandbox/references/sandbox-and-specrunner.md)
+  when checking authored occurrence versus generated-spec limits; a clock fixture is not scheduling.
 
 Name the binding tool. For the automation test, loops and translation boundaries,
 read `cratis-screenplay-automations-and-translations`.
@@ -74,7 +74,7 @@ Start new models with application-root `reaction batches atomic`. One trigger's
 productions, or one selected refusal branch, append all-or-none; invoked commands stay
 separate. Legacy models without opt-in retain per-fact appends even at newer versions.
 Read [atomic batches and source mappings](references/atomic-batches-and-source-mappings.md)
-for batch failure assertions, PLAY0693, Stage STAGE-ESM-016/043 refusals and
+for batch failure assertions, PLAY0693, Stage atomic-mode refusals and
 `invokes` mappings from `$eventSourceId` / `$eventContext.eventSourceId`.
 
 ## Caller-less invokes and unprotected reads
@@ -104,9 +104,9 @@ binding, because its decision dependency cannot be protected. A reaction that on
 command's own reads. Eligible command reads protect under application-root
 `command reads protected` (ESM v25); legacy reads retain PLAY0271. Read command-surface
 [protected reads](../cratis-screenplay-command-surface/references/protected-reads.md)
-for admission and absence/conflict behavior. Stage admits v25 and, from 4.138.0, renders protected reads as Arc read protection (CLI 3.75.0 refuses them with STAGE-ESM-044).
-Semantic Host/executor support is separate; non-Error protected requirements refuse -045,
-including reaction-invoked commands.
+for admission and absence/conflict behavior. Requires Stage 4.138.0 to render
+protected reads; older bundles refuse -044. Semantic Host/executor non-Error
+protected requirements refuse -045.
 `where` over read paths out of scope, and `where` needs
 every operand to resolve from the trigger's declared scalar occurrence shape (listed in
 the input selection or not; nested paths and read aliases fail binding): keep the logic that uses the state in

package/package/corpus/skills/cratis-screenplay-captures-and-reactions/references/atomic-batches-and-source-mappings.md

@@ -36,8 +36,8 @@ batch and unchanged read models with evaluator world/read-model assertions; earl
 accepted work can remain. `then no events` means accepted zero outcomes and cannot
 accompany `then error`. Do not invent a mixed success/error specification form.
 
-Stage refuses ESM v22 with STAGE-ESM-016. Even an admitted v23–v27 model carrying
-atomic mode is refused with STAGE-ESM-043 by renderer, Host and specification executor.
+Requires Stage 4.139.0 for ESM v22 admission; older Stage refuses STAGE-ESM-016.
+Atomic mode is still refused with STAGE-ESM-043 by renderer, Host and specification executor.
 Keep the declaration and report authorized gap-fill; do not promise a render date or
 strip atomicity to lower the version.
 

package/package/corpus/skills/cratis-screenplay-model-authoring/SKILL.md

@@ -26,6 +26,9 @@ Record open modeling questions as `question` notes in committed
 personal data in notes. Read [model notes](references/model-notes.md) when
 listing, recording or resolving questions: `list-model-notes`,
 `propose-model-notes`, `read-proposal view=notes`, refs and orphan review.
+Prefer dotted split-model targets; inspect `substitutions`, also for reanchor,
+and disclose broader owners. The reference covers typed `parts` targets from
+`open-workspace.applicationIdentity`.
 
 ## Choosing a strategy
 
@@ -45,8 +48,7 @@ Use the declared `screenplay` MCP server (for example `open-workspace`).
 Never ask the user which folder to use before trying `open-workspace` without
 arguments; do not invent a root. Read [MCP loop](references/mcp-loop.md) when connecting or switching roots;
 it owns fallback discovery, fixed-root limits and the initialization protocol.
-Discover `tools/list` schemas rather than relying on a remembered count.
-
+Discover `tools/list` schemas.
 
 Look first for the project's existing `.play` files: their folder is the model.
 New models go in `Source/` or `src/`, else root `Screenplay/`, never `.cratis/`
@@ -104,9 +106,8 @@ for handler views: `executableReady` means binding, not an implemented body.
 
 ## Compare models
 
-For a `main` comparison, pass a worktree `path` to `semantic-diff`, not two
-exports. Read [comparison sources](references/mcp-tools.md#semantic-revision-comparison)
-for paging and proposal review.
+Compare with `main` through `semantic-diff` worktree `path`, not two exports.
+Read [comparison sources](references/mcp-tools.md#semantic-revision-comparison) for paging.
 
 ## Make one coherent proposal
 
@@ -191,11 +192,10 @@ Commit `.screenplay/identities.json` with the model; only `apply` writes it. Nev
 
 ## Code attachments
 
-Code bodies and `file` constraints are opaque attachments. Screenplay never compiles or runs them.
-A screen's `file` realizes UI, not an attachment. Read
-[MCP code attachments](references/mcp-tools.md#code-attachments) when resolving
-paths or diagnosing `PLAY0430`-`PLAY0434`; `read-workspace`/`read-proposal`
-`view: "implementation-requirements"` hashes/maps are not behavioral evidence.
+Screenplay never compiles/runs opaque code attachments or `file` constraints;
+a screen's `file` realizes UI instead. Read [MCP code attachments](references/mcp-tools.md#code-attachments)
+for paths, PLAY0430–PLAY0434 and implementation-requirements views; hashes/maps
+are not behavioral evidence.
 
 ## Verify and report honestly
 
@@ -225,7 +225,7 @@ Record screen MCP transcripts in `.ai-work/`; render/runtime checks must use the
 same source, never an app that silently drops authored UI. Use the Screenplay-owned canonical
 corpus fixture path instead of copying available `.play` fixtures here.
 
-Never invent commands, parameters, syntax nodes or downstream capabilities.
+Never invent syntax or capabilities.
 
 ## Route near misses
 

package/package/corpus/skills/cratis-screenplay-model-authoring/references/mcp-tools.md

@@ -555,6 +555,15 @@ row is authored presence, not full coverage, causation or a passing specificatio
 Bare rejections cannot distinguish message-specific rules; syntax-only owners
 retain information-level readiness reasons. Never invent rules from opaque code.
 
+A query's SPEC004 denial matches either `when query <Query>` with `then denied`,
+or a read-only specification with no `when`, exactly one `then query <Query>`
+with `arguments` and no `result`, followed by `then denied`. That read-only denial
+does not meet the returned read model's SPEC006 assertion obligation; add a
+separate state, absence or query-result specification.
+Requires Screenplay 4.212.2 (`screenplay --version`) for this obligation matching;
+older servers miss the read-only denial for SPEC004 and count it for SPEC006.
+Upgrade before treating those rows as a coverage gate.
+
 `find-modeling-smells` asks information-level questions, never changes compilation
 or `--warnaserror`: SMELL001 generic event endings, SMELL002 generic command verbs,
 SMELL003 duplicate nonempty event shapes from different commands, SMELL004 event

package/package/corpus/skills/cratis-screenplay-model-authoring/references/model-notes.md

@@ -5,7 +5,6 @@
 
 ## Contents
 
-- Verified product sources
 - Choose the artifact
 - Anchors and independent state
 - List with bounded, pinned reads
@@ -14,25 +13,8 @@
 - Source proposals can orphan notes
 - Question gate is independent of compilation
 
-## Verified product sources
-
 Requires Screenplay 4.144.0 or later (`screenplay --version`) for model notes; the CLI-bundled MCP can be older.
 
-Sources in `Cratis/Screenplay`:
-
-| Contract | Path |
-| --- | --- |
-| Purpose, anchors, decisions and privacy | `Documentation/screenplay/model-notes.md` |
-| Filters, operations, review and orphan disclosure | `Documentation/screenplay/mcp/reference.md`; `Source/DotNET/Screenplay.Mcp/McpNotesSchemas.cs` |
-| Retained proposals, revision guards and notes review | `Source/DotNET/Screenplay.Mcp/McpWorkspaces.Notes.cs` |
-| Operation fields and resolution evidence | `Source/DotNET/Screenplay.Mcp/McpNotesOperations.cs` |
-| Sidecar bytes, absence and canonical revision | `Source/DotNET/Screenplay/Workspaces/ModelNotesStore.cs` |
-| Standalone question gate | `Source/DotNET/Tool/ModelOpenQuestions.cs`; `Documentation/screenplay/model-notes.md` |
-
-The source-edit and authoring guides remain useful for the ordinary proposal loop:
-`Documentation/screenplay/mcp/edit.md` and `authoring-tools.md`.
-The notes-specific arguments are in the reference and sources above.
-
 ## Choose the artifact
 
 Record an unresolved modeling choice as a `question` note on the affected element,
@@ -60,10 +42,45 @@ Notes live beside the model in committed `.screenplay/notes.json`. An anchor is
 do not derive them from names. Renames and moves keep notes without rewriting the
 sidecar. `lastAddress` is a display hint, never an anchor.
 
-For a syntax-only construct, select its current source handle or address and kind.
-The server substitutes its nearest identified slice, feature, module or application;
-inspect `substitutions` and name the particular construct in the note text.
-Document and authoring-key anchors are unsupported.
+Prefer dotted `{ address, kind }` targets for Module, Feature and Slice notes,
+including split models. Repeated Module/Feature headers at the same logical
+address merge across import placements and explicit headers; genuinely ambiguous
+leaf declarations still refuse. A folder is one application, not a separate note
+namespace per file.
+
+For a typed `{ kind, parts }` target, copy an address from `read-ast` or
+`read-workspace view=semantics`, or build it from names and the exact
+`applicationIdentity` returned by `open-workspace`. This argument template targets
+a Module (replace the Application key with that response's value):
+
+```json
+{
+  "kind": "Module",
+  "parts": [
+    { "kind": "Application", "key": "<applicationIdentity from open-workspace>" },
+    { "kind": "Module", "key": "Library" }
+  ]
+}
+```
+
+A typed address needs an existing catalog identity; it refuses when none exists.
+Use the construct's current source handle instead. A target without an identity
+lands on the nearest identified slice, feature, module or application. On an
+unbound model, even a Slice can lack an identity and fall back to Application;
+opening the workspace does not guarantee container identities.
+
+Always inspect `substitutions` for both `add` and `reanchor`, even when reanchor
+leaves the note unchanged. Each entry has the requested `target`, resolved
+`anchor`, resolved `address` and `reason`. If the note lands on a broader owner,
+say so to the user and name the intended construct in its text; reanchor once
+the intended owner has an identity. Never report the requested anchor as applied
+without checking the actual owner. Document and authoring-key anchors refuse.
+
+Requires Screenplay 4.212.0 (`screenplay --version`) for split dotted-target
+resolution, `open-workspace.applicationIdentity` and complete substitution
+reporting. Older servers can refuse split targets, omit that field or silently
+broaden the anchor; use a catalog address/current handle and inspect the notes
+review's actual anchor, or upgrade before relying on these responses.
 
 Notes do not change source, workspace/catalog/semantic revisions, executable
 model bytes or compiler verdicts. Their own `notesRevision` is `nrev1:` plus the
@@ -141,7 +158,8 @@ revisions just read and an actual declaration address before calling it.
 ```
 
 1. Retain `proposalId`, `afterNotesRevision`, server `addedNotes` IDs and inspect
-   `substitutions`. `changeCount: 0` means no source changes, not no notes change.
+   every `substitutions` entry for the actual owner, also for reanchor.
+   `changeCount: 0` means no source changes, not no notes change.
 2. Read `read-proposal` with `view: "notes"`: before/after notes revisions and
    paged `{ id, before, after }` pairs. On continuation pin **afterNotesRevision**
    as `expectedNotesRevision`, not the disk revision. Review the entire batch.

package/package/corpus/skills/cratis-screenplay-model-authoring/verification.json

@@ -37,6 +37,11 @@
     { "kind": "skill-contains", "value": "never hand-edit `generate` text", "file": "references/mcp-loop.md" },
     { "kind": "skill-contains", "value": "Record open modeling questions as `question` notes" },
     { "kind": "skill-contains", "value": "list-model-notes", "file": "references/model-notes.md" },
+    { "kind": "skill-contains", "value": "`applicationIdentity` returned by `open-workspace`", "file": "references/model-notes.md" },
+    { "kind": "skill-contains", "value": "Repeated Module/Feature headers", "file": "references/model-notes.md" },
+    { "kind": "skill-contains", "value": "Always inspect `substitutions` for both `add` and `reanchor`", "file": "references/model-notes.md" },
+    { "kind": "skill-contains", "value": "even a Slice can lack an identity", "file": "references/model-notes.md" },
+    { "kind": "skill-contains", "value": "older servers miss the read-only denial for SPEC004 and count it for SPEC006", "file": "references/mcp-tools.md" },
     { "kind": "skill-contains", "value": "`anchor`", "file": "references/model-notes.md" },
     { "kind": "skill-contains", "value": "`scope`", "file": "references/model-notes.md" },
     { "kind": "skill-contains", "value": "`state`", "file": "references/model-notes.md" },
@@ -163,11 +168,11 @@
     },
     {
       "kind": "skill-contains",
-      "value": "`view: \"implementation-requirements\"`"
+      "value": "implementation-requirements views"
     },
     {
       "kind": "skill-contains",
-      "value": "Screenplay never compiles or runs them"
+      "value": "Screenplay never compiles/runs opaque code attachments"
     },
     {
       "kind": "skill-contains",
@@ -180,7 +185,7 @@
     },
     {
       "kind": "skill-contains",
-      "value": "schemas rather than relying on a remembered count"
+      "value": "Discover `tools/list` schemas"
     },
     {
       "kind": "skill-contains",

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

@@ -28,11 +28,9 @@ source is the single flow model.
 
 ## Product sources
 
-Screenplay `Documentation/screenplay/projections/` (including `semantic-model.md`, `keys.md`
-and `variants.md`), `readmodels.md`, `diagnostics.md`, `commands.md`, `events.md` and
-`mcp/authoring-tools.md` describe the PDL parser, validator, diagnostics, semantic binder and
-reducer-body binding (`Semantics/`). Every example below compiles with the standalone compiler.
-Reverify before claiming another version behaves the same.
+Consult Screenplay `Documentation/screenplay/projections/` for grammar and semantics,
+`readmodels.md` for targets and `diagnostics.md` for errors. Verify examples with
+the standalone compiler before claiming another version behaves the same.
 
 **Chronicle decides what a projection means.**
 Screenplay owns the grammar; which instance an event affects, what a join may
@@ -81,11 +79,8 @@ Read [observer filters](../cratis-screenplay-toolchain/references/production-rou
 
 ## Projection-level directives
 
-`description "..."` (or a fenced text block) on the projection header (report-only `PLAY0270`; variants
-and nested blocks take none), `no automap`, `sequence <name>`, `file <path>`. `sequence` is a realization
-concern and does not bind to the executable model. A mapping target may end in a dynamic dictionary
-key, `count eventCountByType.$eventContext.eventType.id` (one entry per distinct value); only
-`$eventContext` resolves there, any other `$` text is a literal key with warning `PLAY0299`.
+Read [projection-level directives](references/pdl-grammar.md#projection-level-directives)
+when using descriptions, `sequence`, `file` or dynamic dictionary-key targets.
 
 ⚠️ **Do not write `key` on the projection.** It parses, but neither Chronicle nor
 the executable model routes any event by it, and it is not a default for the
@@ -148,14 +143,26 @@ subscribe to every event type: `all` inside `children` or `nested` behaves as
 `lastUpdatedAt`. The `every` block **inside** a `children` block does not accept
 it — it is already in a children context.
 
+## One event per level
+
+One event type is used once per projection level (`PLAY0801`): two `from` blocks
+cannot update two rows at that level, even with different keys. Combine mappings
+for one row; model a genuine second domain fact as its own event. Never invent
+events only to satisfy the read side. Joins use a separate set; each children,
+nested and variant block starts fresh sets. Read [event scope](references/pdl-grammar.md#event-scope)
+for grouped events, removals and compiler compatibility.
+
 ## Property mapping and AutoMap
 
 ⚠️ **AutoMap is on by default.** Matching property names are copied before your
 explicit mappings run, and explicit mappings win. Turn it off with `no automap` at
 **projection**, `every`/`all`, `join`, `children` or `nested` level — it
 **cannot** be toggled inside an individual `from` block. An `automap`/`no automap`
-under a joined event (`with …`) parses but Chronicle replaces it with the auto-map
-of the level the join sits in (`PLAY0380`).
+under a joined event (`with …`) decides auto-mapping for that event alone;
+without one, the joined event follows its level's auto-map.
+
+Requires Screenplay 4.212.4 (`screenplay --version`) for joined-event auto-map
+overrides in executable binding; older binders replace the setting with the level's.
 
 Mapping sources: a property path (`name`, `contactInfo.email`), a literal
 (`true`, `"Pending"`, `42`, `null`), `$eventSourceId`, and

package/package/corpus/skills/cratis-screenplay-projections/references/pdl-grammar.md

@@ -5,6 +5,8 @@
 - Grammar
 - Parser regexes
 - Diagnostics
+- Event scope
+- Projection-level directives
 - Syntax that parses but means something else
 - Flat composite read-model keys
 - Worked examples
@@ -147,20 +149,53 @@ LiteralKeyword  = "literal", " ", Literal ;   (* parsed at the Expr level *)
 | `PLAY0191` | A read model is built by more than one projection or reducer |
 | `PLAY0192` | A read model is declared more than once |
 | `PLAY0295`–`PLAY0299` | An `$eventContext` path the event-context catalog does not have; `PLAY0299` also warns when a dynamic dictionary key uses a `$` source other than `$eventContext` |
-| `PLAY0380` | Chronicle drops part of a construct: `all` below the top level, or `automap` on a joined event |
+| `PLAY0380` | Only `all` inside `children`/`nested`: loses its subscription to every event type and behaves as `every` |
 | `PLAY0381` | A projection-level `key` routes no event |
 | `PLAY0382`–`PLAY0385` | Variant errors: no `enters on`, shared mapping missing on a variant, duplicate variant name, entering event claimed twice |
 | `PLAY0397` | Inline code uses a language line instead of a tagged fence |
 | `PLAY0398` / `PLAY0399` | A reducer mixes bodied and body-less rules / observes one event twice |
 
+## Event scope
+
+Requires Screenplay 4.212.3 (`screenplay --version`) for the ordinary compilation
+error `PLAY0801` (`DuplicateEventInProjectionScope`) in both compilers; older
+executable binding rejected duplicate uses later with `PLAY0273`.
+
+A level is the projection root, one `children` block, one `nested` block or one
+variant. Within that level, `from` (including each event in `from A, B` lists),
+`remove with`, `remove via join` and `clear with` share one set of event names.
+All `join` events at that level share a separate set: an event may occur once in
+`from` and once in a join, but not twice in either set. Each children, nested and
+variant block starts fresh sets; separate projections are independent.
+
+The check compares authored event names ordinally, without resolving
+qualifications or generations. It reports the second and each later reference;
+identical or different keys do not change the rule. One event cannot update two
+rows of the same level through two `from` blocks with different keys. Combine
+mappings for the same row into one block. Only a genuinely second domain fact
+warrants another event; never invent events only to satisfy the read side.
+These scope checks do not establish executable or renderer admission.
+
+## Projection-level directives
+
+`description "..."` (or a fenced text block) on the projection header (report-only `PLAY0270`; variants
+and nested blocks take none), `no automap`, `sequence <name>`, `file <path>`. `sequence` is a realization
+concern and does not bind to the executable model. A mapping target may end in a dynamic dictionary
+key, `count eventCountByType.$eventContext.eventType.id` (one entry per distinct value); only
+`$eventContext` resolves there, any other `$` text is a literal key with warning `PLAY0299`.
+
 ## Syntax that parses but means something else
 
+An `automap` / `no automap` under a joined event (`with …`) is honored for that
+event alone; without one, it follows its level's auto-map. Requires Screenplay
+4.212.4 (`screenplay --version`) for executable binding; older binders replace the
+joined event's setting with the level's. It does not report `PLAY0380`.
+
 | Syntax | What Chronicle and the executable model do |
 | --- | --- |
 | `key` on the projection | Nothing: events route by the `from` key, then the event source id (`PLAY0381`) |
 | `from X` with no key | Routes by the event source id, never by another `from`'s key |
 | `join … on …` | Updates existing instances only; never creates one; the name after `join` is discarded |
-| `automap` under a joined event | Replaced by the auto-map of the join's level (`PLAY0380`) |
 | `all` inside `children`/`nested` | Behaves as `every` (`PLAY0380`) |
 | `$causedBy.<x>` | Does not bind; use `$eventContext.causedBy.<x>` |
 | Templates in mappings or keys | Do not bind |

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

@@ -9,7 +9,18 @@
     { "kind": "skill-contains", "value": "Look first for the project's existing `.play` files" },
     { "kind": "skill-contains", "value": "`cratis ai install` manages `.cratis/ai/`, never model files" },
     { "kind": "skill-contains", "value": "AutoMap is on by default" },
+    { "kind": "skill-contains", "value": "decides auto-mapping for that event alone" },
+    { "kind": "skill-contains", "value": "without one, the joined event follows its level's auto-map" },
+    { "kind": "skill-contains", "value": "Requires Screenplay 4.212.4" },
+    { "kind": "skill-contains", "value": "| `PLAY0380` | Only `all` inside `children`/`nested`:", "file": "references/pdl-grammar.md" },
+    { "kind": "skill-contains", "value": "It does not report `PLAY0380`.", "file": "references/pdl-grammar.md" },
     { "kind": "skill-contains", "value": "PLAY0191" },
+    { "kind": "skill-contains", "value": "One event type is used once per projection level (`PLAY0801`)" },
+    { "kind": "skill-contains", "value": "cannot update two rows at that level, even with different keys" },
+    { "kind": "skill-contains", "value": "events only to satisfy the read side" },
+    { "kind": "skill-contains", "value": "`clear with` share one set of event names", "file": "references/pdl-grammar.md" },
+    { "kind": "skill-contains", "value": "Each children, nested and\nvariant block starts fresh sets", "file": "references/pdl-grammar.md" },
+    { "kind": "skill-contains", "value": "older\nexecutable binding rejected duplicate uses later with `PLAY0273`", "file": "references/pdl-grammar.md" },
     { "kind": "skill-contains", "value": "every event type in the system" },
     { "kind": "skill-contains", "value": "references/pdl-grammar.md" },
     { "kind": "skill-contains", "value": "Do not write `key` on the projection." },

package/package/corpus/skills/cratis-screenplay-render-and-gap-fill/SKILL.md

@@ -36,24 +36,21 @@ Tool versions are covered in `cratis-screenplay-toolchain` `SKILL.md`; read it b
 
 Read [language admission](../cratis-screenplay-toolchain/references/language-admission.md)
 for v22–v25: Stage rendering refuses atomic batches, described bodies (even Stub mode)
-and protected reads. Semantic Host/executor support is not generated-app protection.
+but renders admitted protected reads in a supporting bundle. Semantic Host/executor
+support is not generated-app protection.
 Preserve contracts; reference success is not target realization.
 
-File/inline command handlers refuse PLAY0800 (`CommandHandlerRequiresAttachment`):
-a permanent requirement for a constrained implementation attachment. Gap-fill the
-slice in code rather than wait for a new ESM version. Hosts identify the command
-through the required typed `arguments.subject`, not message text. Requires
-Screenplay 4.210.0 (`screenplay --version`); older binders use PLAY0268 for these
-handlers. Other PLAY0268 families still mean not representable in a supported ESM
-version yet; triage details: [renderability gate](references/renderability-gate.md).
+File/inline command handlers permanently require constrained attachments: gap-fill
+in code, not by waiting for ESM admission. Requires Screenplay 4.210.0
+(`screenplay --version`) for PLAY0800 and required typed `arguments.subject`;
+older binders use PLAY0268. Read [renderability gate](references/renderability-gate.md)
+when classifying a handler or other binding refusal; never parse message text.
 
 ## Interview phase
-**Skip if** the request names the model root, the application name, the destination and the
-decision on non-renderable scope. Otherwise ask only what is missing:
-Ask only what is missing: the model and accepted version, the application name for `--name` (identical on every re-render), the destination, the decision if admission fails (the three cases below), and the seams (`Customizations/`). Read [references/delivery-protocol.md](references/delivery-protocol.md) ("Interview batch for render delivery") for the defaults.
-
-Unattended: assume visibly (probe destination, default name from the model root folder), never
-assume an answer to 4, and record it as `blocked` for the user.
+Ask only for missing inputs: accepted model/root, stable `--name`, destination,
+non-renderable-scope decision and seams. Read [references/delivery-protocol.md](references/delivery-protocol.md)
+when selecting defaults. Unattended, state probe-name/destination assumptions;
+never assume the non-renderable-scope decision: record it as blocked.
 
 ## The three cases (decide first, say which one applies)
 
@@ -63,36 +60,33 @@ assume an answer to 4, and record it as `blocked` for the user.
 | **B. Generated base plus authorized gap-fill** | an admitted render (whole, or a `--scope` of the admitted slices) exists and the user separately authorized hand-written scope, or a seam the model names needs an adapter | the generated output stays managed and untouched; hand-written code lives in `Customizations/` or a separate project (seam adapters by this skill, business gap-fill by `slice-implementer`), serves named model elements only, never claims render admission, and V5 is reported for the generated base **with its scope stated** |
 | **C. Fully hand-written delivery** | the scope cannot render and no generated base is wanted | `slice-implementer` delivers it with the model as the contract (`references/gap-fill-handoff.md`); V5 is `not run: no render` |
 
-Evolved events are gap-fill too: Stage still refuses any evolved event and its dependent scope with `STAGE-ESM-026`, because it cannot render Chronicle event-type migrations yet (Stage#204). Events at their initial revision still render. Hand-write the evolved events and their migrations per `cratis-chronicle-event-type-migration`, with the model as the contract.
+Evolved events and dependent scope refuse `STAGE-ESM-026`; initial revisions render.
+Gap-fill migrations per `cratis-chronicle-event-type-migration`, preserving the model contract.
 
-Supported UUID/String generation strategies, v15 freshness and scalar/named `returns`
-responses, fixtures and `then returns` render with the CLI and Stage. Unsupported generated
+Supported UUID/String generation, v15 freshness, responses, fixtures and
+`then returns` render. Unsupported generated
 types (`STAGE-ESM-028`) and result combinations (`-038`) still require case A or C:
 preserve the model and its specifications. See Stage's `references/admission.md`.
 Supported event-triggered Automation slices also render as managed Chronicle reactors;
-refused reactions, captures and Translate slices remain gap-fill.
-
-Models with event sources, streams or command routes bind and reference-execute as ESM v8 on the standalone
-tool, so report V3 and V4 from that tool. The CLI/Stage pair
-(`cratis-screenplay-toolchain/references/renderable-subset.md`) reaches v8 route checks
-and construct admission through v27 (Requires Cratis CLI 3.75.0; older bundles stop earlier, v28 is `CLI-RENDER-004`). Public/foreign events and production overrides
-still refuse; semantic reaction/reducer filters and role/authenticated `runs as` render.
-Claim-reading/opaque system gates, legacy actor/filter paths and mixed effects still refuse. Keep refused scope as case A/C,
-never infer target support from binding. Read Stage's `references/admission.md` and
-toolchain `references/sources-and-streams.md`.
-
-**Mixed reaction effects.** A reaction that both `produces` events and `invokes` commands is refused by
-Stage (`STAGE-ESM-037`) although Arc runs one reactor returning events
-and commands (events appended first as one batch, then commands in order, no cross-effect
-transaction; a retry can repeat the events). The scaffold now includes the mixed-result handler,
-but Stage still refuses it because redelivery can duplicate events. `[OnceOnly]` excludes replay,
-not retries. Keep the modeled reaction whole; gap-fill needs a proven retry-safe realization,
-not splitting or dropping effects to get a render. Source: Stage
-`Documentation/reference/reaction-rendering.md`.
-
-Read Stage's `references/admission.md` when checking v17/v19 or query validation:
-primitive query arguments still answer absence, not Screenplay's Validation.
-Query errors need v18 admission; do not delete rules or claim parity.
+refused reactions, captures and Translate slices remain gap-fill. A `given clock` fixture
+in the semantic executor is not support for rendering clock triggers.
+Requires Stage 4.141.0 to render v26 Date/DateTime command comparisons; older renderers
+refuse `STAGE-ESM-046`. Read [rendered date comparisons](../cratis-stage-rendering-and-sandbox/references/date-comparisons.md)
+when delivering dates for remaining refusals and input-binding differences.
+
+Source/stream routes bind and reference-execute as v8; target admission is separate.
+Requires Cratis CLI 3.75.0 for v27 admission; older bundles stop earlier, v28 is
+`CLI-RENDER-004`. Read toolchain `references/renderable-subset.md` and
+`references/sources-and-streams.md` when delivering routes, actor gates or filters.
+Preserve refused public/foreign events, production overrides and opaque gates as A/C.
+
+**Mixed effects (`STAGE-ESM-037`).** Keep the reaction whole: returned events append
+before commands and redelivery can duplicate them. `[OnceOnly]` excludes replay,
+not retries. Read Stage's [admission](../cratis-stage-rendering-and-sandbox/references/admission.md)
+when gap-filling a mixed reaction; prove retry safety, never split or drop effects.
+
+Read Stage's `references/admission.md` when checking v17/v19 or query validation;
+query errors need v18 admission. Preserve rules and test rejection separately from absence.
 
 Two rules hold in every case: a customization never makes a rejected model renderable, and
 a whole-application V5 is never claimed from a subset. `--scope` renders an admitted part (the whole
@@ -114,6 +108,9 @@ model still compiles and binds) and its V5 states the scope.
    (repeatable) to render an admitted part. Classify every
    diagnostic with `references/renderability-gate.md`: model fix in the chosen mode,
    capability gap, permanent implementation-attachment requirement, tool skew or environment. Group by code and count; do not paste the list.
+   Requires Stage 4.146.0 for collecting independent admission refusals in one plan;
+   earlier renderers reveal later batches after earlier fixes. Profile/version failures
+   still stop first. Classify all returned refusals before the next probe.
 3. **When admission fails** (case A) present the options, the user decides:
    (a) keep design mode and record the gaps; (b) narrow to renderable mode, where the modeler
    changes the model for business reasons and **without** removing protection (`pii`,

package/package/corpus/skills/cratis-screenplay-render-and-gap-fill/references/gap-fill-handoff.md

@@ -107,8 +107,9 @@ reaction or drop an effect to dodge rendering.
 
 Preserve declared `reaction batches atomic` boundaries: each trigger occurrence's
 direct productions and each selected refusal branch are separate batches, with
-invoked commands independent. Stage refuses v22 (STAGE-ESM-016) and atomic mode
-in admitted v23–v27 (STAGE-ESM-043); the declaration is not external-effect deduplication.
+invoked commands independent. Atomic mode refuses STAGE-ESM-043.
+Requires Stage 4.139.0 for v22 admission; older Stage reports -016.
+The declaration is not external-effect deduplication.
 For described handlers, hand off only payload computation under the v23 result
 contract; Stage STAGE-IMPL-002 means no stubs, even Stub mode. Protected v25 reads
 render from Stage 4.138.0 (STAGE-ESM-044 from older bundles, or for shapes it cannot