@cratis/pi 7.32.0 → 7.34.0

package/package/corpus/agents/screenplay-modeler.md

@@ -62,4 +62,4 @@ Write `.ai-work/screenplay/<model-slug>/STATE.md` (overwrite, untracked) only wh
 
 ## Lineage
 
-The per-run protocol and the corner-cutting self-check (both by pointer to the lifecycle skill) adapt agentic-engineer by Martin Dilger and Nebulit GmbH (https://github.com/Nebulit-GmbH/agentic-engineer, commit `07b0f30648d663cb588d7e2c7aa031af9dfc21f2`; https://nebulit.de), used with their agreement.
+The per-run protocol and the corner-cutting self-check (both by pointer to the lifecycle skill) adapt agentic-engineer by Martin Dilger and Nebulit GmbH (https://github.com/Nebulit-GmbH/agentic-engineer, commit `07b0f30648d663cb588d7e2c7aa031af9dfc21f2`; https://nebulit.de), used with their explicit consent.

package/package/corpus/agents/screenplay-renderer.md

@@ -52,4 +52,4 @@ First line: `Outcome: done | partial (...) | blocked (Qn) | out-of-scope (why)`.
 
 ## Lineage
 
-The delivery discipline adapts the build prompts of agentic-engineer by Martin Dilger and Nebulit GmbH (https://github.com/Nebulit-GmbH/agentic-engineer, commit `07b0f30648d663cb588d7e2c7aa031af9dfc21f2`; https://nebulit.de), used with their agreement.
+The delivery discipline adapts the build prompts of agentic-engineer by Martin Dilger and Nebulit GmbH (https://github.com/Nebulit-GmbH/agentic-engineer, commit `07b0f30648d663cb588d7e2c7aa031af9dfc21f2`; https://nebulit.de), used with their explicit consent.

package/package/corpus/agents/screenplay-reviewer.md

@@ -52,4 +52,4 @@ First line: `Outcome: done | partial (...) | blocked (Qn) | out-of-scope (why)`.
 
 ## Lineage
 
-The business-question lens adapts the "what do you think" (wdyt) skill of agentic-engineer by Martin Dilger and Nebulit GmbH (https://github.com/Nebulit-GmbH/agentic-engineer, commit `07b0f30648d663cb588d7e2c7aa031af9dfc21f2`; https://nebulit.de), used with their agreement.
+The business-question lens adapts the "what do you think" (wdyt) skill of agentic-engineer by Martin Dilger and Nebulit GmbH (https://github.com/Nebulit-GmbH/agentic-engineer, commit `07b0f30648d663cb588d7e2c7aa031af9dfc21f2`; https://nebulit.de), used with their explicit consent.

package/package/corpus/agents/slice-implementer.md

@@ -102,4 +102,4 @@ Proxies now exist. Build React components from the generated proxies (`react.md`
 
 ## Lineage
 
-The re-delivery, specification-oracle and working-discipline items adapt the build prompts of agentic-engineer by Martin Dilger and Nebulit GmbH (https://github.com/Nebulit-GmbH/agentic-engineer, commit `07b0f30648d663cb588d7e2c7aa031af9dfc21f2`; https://nebulit.de), used with their agreement.
+The re-delivery, specification-oracle and working-discipline items adapt the build prompts of agentic-engineer by Martin Dilger and Nebulit GmbH (https://github.com/Nebulit-GmbH/agentic-engineer, commit `07b0f30648d663cb588d7e2c7aa031af9dfc21f2`; https://nebulit.de), used with their explicit consent.

package/package/corpus/rules/profiles.md

@@ -205,6 +205,7 @@ and one phase skill, then the construct skill needed for syntax.
 | `cratis-screenplay-legacy-extraction` | Evidence-led extraction, expert verification and loss report |
 | `cratis-screenplay-toolchain` | Compiler and CLI versions, verdict commands, diagnostics and executable subsets |
 | `cratis-screenplay-render-and-gap-fill` | Admission, publication, target verification and contract-led hand-written delivery |
+| `cratis-screenplay-delivery-planning` | Slice counts by type, dependency waves, issue tracking and estimates from the team's own history |
 
 #### Language
 

package/package/corpus/skills/cratis-application-slice-conformance/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-application-slice-conformance/SKILL.md

@@ -115,6 +115,11 @@ one covers the slice, otherwise the agreed outline).
 Change the code, or return an edit request. Do not touch test files outside the slice unless
 told to.
 
+Where the model is a `.play` and the code is Arc, Marten or Critter Stack, `cratis screenplay
+conform <model-root> --project <path>` (CLI 3.42.0 or later; exit 0/1/2) adds structural drift
+evidence: exact-address comparison of recovered declarations, never behavior or equivalence. It
+runs MSBuild on the project (trusted clone only). It supplements, and never replaces, steps 2 to 4.
+
 ### 5. Delta delivery
 After a model or outline change, the work list is every element and specification that
 changed since the last delivery, including a delivery of only added specifications. Then run

package/package/corpus/skills/cratis-application-slice-conformance/references/checklists.md

@@ -8,6 +8,7 @@
 - Automation and Translation
 - Chronicle runtime guarantees
 - Evidence
+- Final verification: does the code match the contract?
 
 Reconcile in both directions with each list. Moved here from the render workflow; it gives
 the renderer no right to browse managed output or implement rejected semantics.
@@ -105,3 +106,14 @@ none of these. Unsupported semantics remain gap-fill scope, never hidden customi
   route with real configuration. Report runner, configuration and per-specification outcomes
   apart from integration results; skipped and unexecuted cases stay visible.
 - Record deliberate divergences and their approval; never call them equivalent behaviour.
+
+## Final verification: does the code match the contract?
+The last pass before you report a slice done, as a short tick-list. It repeats the checks above in
+the form a closing review uses; every item must hold, and the one that does not is the finding.
+- [ ] Every contracted command field has a field in the code's command, and the command has no other: none invented, none missing
+- [ ] Every contracted event exists with its modeled name, and every payload field is present with the modeled type
+- [ ] Every contracted read-model property exists in the code's read model (and its storage mapping where persisted), and no other does
+- [ ] Every contracted specification maps to an executed specification or specification family
+- [ ] No business rule, default, filter or constraint exists in code that the contract (its documentation or specifications) does not state
+- [ ] No field name was assumed or guessed: a name that is not in the contract is not in the code
+- [ ] Where the contract has a specification family for the lifecycle of one view or one command, each step maps to a specification (no storyline syntax at Screenplay 4.139.0)

package/package/corpus/skills/cratis-application-slice-conformance/references/provenance.md

@@ -5,15 +5,14 @@
   State Change, State View, Chronicle runtime guarantees, evidence. Now `references/checklists.md`;
   the render workflow links here and keeps no second copy. References renamed to the corpus skills.
 
-## 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 |
 |---|---|---|
-| `.claude/skills/build-state-change/SKILL.md`: final verification checklist (commands, events, specifications, nothing invented) | `references/checklists.md` "State Change"; `SKILL.md` steps 2-3 and "Gate" | Adapted closely; slice.json becomes the `.play` slice or agreed outline, emmett types become Arc commands and Chronicle events |
+| `.claude/skills/build-state-change/SKILL.md`: final verification checklist (commands, events, specifications, nothing invented) | `references/checklists.md` "State Change"; `SKILL.md` steps 2-3 and "Gate" | Adapted closely; slice.json becomes the `.play` slice or agreed outline, emmett types become Arc commands and Chronicle events; the six checks are kept as the closing "Final verification" tick-list in `references/checklists.md`. Not adopted: the Emmett decide/evolve structure, `routes.ts` and the state complexity guide |
 | `.claude/skills/build-state-view/SKILL.md`: final checklist (every field has a source, subscribed events equal modeled events, no extra columns, one test per specification) | `references/checklists.md` "State View" | Adapted closely; migration, `canHandle` and Knex items translated to read-model properties, projection sources and storage mapping; Knex connection items not adopted (Emmett specific) |
 | `.claude/skills/build-automation/SKILL.md`: checklist (every processor implemented, command fields map only from the trigger, no invented conditions, idempotency specified, no routes, processor registered in startup and event store bootstrap verified) | `references/checklists.md` "Automation and Translation" including "Real startup participation" | Adapted closely; processor/DLQ items translated to the Chronicle reactor and its failure behavior; startup registration translated to discovery, event store and event sequence checks; `start()`/`stop()`, processor-id and `schema.migrate()` not adopted (Emmett specific) |
 | `.build-kit/lib/backend-prompt.md`: one slice per iteration, planned can be only added specifications, the slice is always true, done criteria, escalating ambiguity, progress report, consolidated patterns, learnings filter | `references/build-prompts.md` sections 3-5; `SKILL.md` steps 4-6 and "Gate" | Restored from #493 and adapted closely; `index.json`, `progress.txt`, board status, `<promise>` sentinels, per-step progress appends, commit and merge steps, and the slice-only done gate not adopted (replaced by the result packet, the completion gate and separate git authorization) |

package/package/corpus/skills/cratis-application-slice-specifications/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-application-slice-specifications/references/provenance.md

@@ -2,11 +2,10 @@
 
 Lineage of the #493 additions to `cratis-application-slice-specifications`. No TrogonStack material was adapted. Nebulit material is credited below.
 
-## 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 |
 |---|---|---|

package/package/corpus/skills/cratis-arc-react-page/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-arc-react-page/references/provenance.md

@@ -7,11 +7,10 @@ No TrogonStack text is adapted in this skill. Nebulit material is credited in th
 | Component APIs, props and hooks | Cratis Components 4.6.0 and Arc, see *Verified product sources* | MIT | original | SKILL.md, references/ |
 | Screenplay and Stage facts in the screen mapping | Cratis/Screenplay v4.66.0 and Cratis/Stage v4.24.0 documentation and source | MIT | original | references/from-screenplay.md |
 
-## 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 |
 |---|---|---|

package/package/corpus/skills/cratis-chronicle-event-modeling/SKILL.md

@@ -37,12 +37,14 @@ and the request is wiring or a narrow fix.
 
 ## Verified product sources
 
-This skill is verified against these exact sources:
+This skill was originally verified against Chronicle 18.3.0 and re-read against Chronicle 19.50.0
+(`Source/Clients/DotNET.CodeAnalysis/DiagnosticIds.cs`, `ProtectedValues/EncryptedAttribute.cs`).
+Current version pins: `cratis-screenplay-toolchain` `references/versions.md`.
 
-| Package | Version | Purpose |
-| --- | --- | --- |
-| `Cratis.Chronicle` | `18.3.0` | event types, event-source identities, subjects, `[PII]` |
-| `Cratis.Chronicle.CodeAnalysis` | `18.3.0` | `CHR0012`, `CHR0026`, `CHR0034`, `CHR0035` |
+| Package | Purpose |
+| --- | --- |
+| `Cratis.Chronicle` | event types, event-source identities, subjects, `[PII]`, `[Encrypted]` |
+| `Cratis.Chronicle.CodeAnalysis` | `CHR0012`, `CHR0026`, `CHR0034`, `CHR0035`, `CHR0052` |
 
 Reverify product sources before claiming support for another version.
 
@@ -132,7 +134,11 @@ operates on the subject and the subject follows the stream.
   already both, and analyzer `CHR0026` says so.
 - Bearer tokens, magic links, and signed URLs are not durable facts. Model a
   keyed hash or an opaque reference, never the secret. Chronicle has no attribute
-  that withholds a value from the log.
+  that withholds a value from the log. Where an operational secret must genuinely be
+  retained (an API key, a signing secret), mark it `[Encrypted]` (encrypted at rest,
+  recoverable, not a PII erasure subject; never on a `[PII]` value or an event-source id)
+  and keep it out of the causation chain with Arc's `[NotAudited]`; see `cratis-arc-command`
+  and `cratis-chronicle-compliance`.
 
 If a subject boundary cannot be made person-level without changing product
 behavior, **stop and surface that trade-off** before implementing.

package/package/corpus/skills/cratis-chronicle-reactor/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-chronicle-reactor/SKILL.md

@@ -322,7 +322,9 @@ public class <ReactorName> : IReactor
 
 A reactor runs with **no principal**; `[ExecuteCommandsAsSystem]` (class-level,
 `Cratis.Arc.Chronicle.Reactors`) supplies one for the **returned** commands only.
-A collection return is executed as commands when every element is a command.
+A collection return is executed as commands when every element is a command. A stable collection mixing registered events and commands (Arc 22.72.0+; Arc 22.68.0's handler needs every element to be a command) appends the events
+first as one batch, then runs the commands in order, with no transaction across them; a retry can
+repeat both. `[ExecuteCommandsAsSystem]` covers only the commands.
 A reactor retry can execute the command's operations again; inline operations
 are not a substitute for reactor/outbox durability (see
 `cratis-arc-command-operation`, verified at Arc v22.48.1).
@@ -408,4 +410,5 @@ scope of these scenario-only guards.
 
 ## Lineage
 
-The specification checklist (field lineage, contract-authorized filtering, repeated delivery) follows an idea from Martin Dilger and Nebulit GmbH's reactor build checklist, credited in `references/provenance.md`. Read `references/provenance.md` when checking checklist attribution or the verification sources for scenario behavior.
+Attribution and verification sources: `references/provenance.md`.
+Read `references/slice-delivery-checklist.md` when delivering a reactor from a slice contract: build order, handler patterns, closing checklist.

package/package/corpus/skills/cratis-chronicle-reactor/references/provenance.md

@@ -1,13 +1,13 @@
 # Provenance
 
-## 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 |
 |---|---|---|
 | `.claude/skills/build-automation/SKILL.md`: reactor checklist: output fields traced to a stated source, skip conditions stated in the contract, repeated-input cases | `SKILL.md` "Specifications" and "Verify" | idea; our own wording kept |
+| `.claude/skills/build-automation/SKILL.md`: read the slice definition first as the source of truth, build the command handler before the processor, single / conditional / multiple-command processor patterns, no route for an automation, closing checklist (no invented mappings, no invented filters, no guessed fields, idempotency of the command) | `references/slice-delivery-checklist.md` | Adapted closely as an `IReactor` delivery checklist: processors became reactor handlers returning commands or events, the storyline-derived test note became a separate reactor mapping specification. Not adopted: the Emmett reactor, `processor.ts`, processor id, lock and retry configuration, the dead-letter store, `schema.migrate()`, Postgres event store bootstrap, and "no dedicated reactor test" (the field mapping is the contract here) |
 
 The `WithStrictEventSubscription()` scope statement and the scenario sequence-number behavior are verified against Chronicle `v19.32.0` source (`Source/Clients/Testing/ReadModels/ReadModelScenario.cs`, `Source/Clients/Testing/Reactors/ReactorScenario.cs`).

package/package/corpus/skills/cratis-chronicle-reactor/references/slice-delivery-checklist.md

@@ -0,0 +1,93 @@
+# Automation slice delivery checklist
+
+## Contents
+
+- Start from the contract
+- Build order
+- Handler patterns
+- What no longer applies
+- Checklist
+- Specifications
+
+Use this when you implement a reactor from an existing contract: an accepted `.play`
+`Automation` slice (a `reaction` with its `when`, `where`, `invokes` or `produces`), or an agreed
+slice outline in a code-first repository. It is the delivery checklist for the code, and it adds
+to the Verify list in `SKILL.md`; it does not replace it. Adapted from Martin Dilger and Nebulit
+GmbH's build-automation (see `provenance.md`), with the event-store, processor and storage
+mechanics replaced by Chronicle and Arc.
+
+## Start from the contract
+Read the slice first. It is the source of truth for three things and nothing else is assumed:
+- which event (or clock or trigger) sets the automation off;
+- which command it invokes, or which events it produces, and from which trigger fields each
+  input is filled;
+- which conditions narrow it (`where`).
+
+If an item the reactor needs is not in the contract, it is not in the code. Ask or record an open
+question; do not guess a mapping or add a filter. Notes in the slice `description` and
+`documentation` are implementation hints: carry them into code comments, validation or
+specifications where they add value, and do not treat them as new requirements.
+
+## Build order
+This checklist covers event-triggered reactions only. Clock and application triggers are not
+`[EventType]`s and do not run through `IReactor` (Chronicle 19.50.0 discovers handlers only for
+registered event types). Route them first to a scheduler or host-signal implementation as
+`cratis-screenplay-render-and-gap-fill/references/gap-fill-handoff.md` describes, then apply the
+remaining steps where they fit.
+
+An automation is a state-change with a trigger in front of it. Build the command side first, then
+wire the reactor.
+1. The command (and its event) exists and works: `cratis-arc-command`, and its specifications
+   (`cratis-application-slice-specifications`). If the automation produces events directly, the
+   `[EventType]` records exist instead.
+2. The trigger event is defined as an `[EventType]` in the contracts project that owns it. A
+   trigger from another module or store is consumed through its public contract, never copied
+   (the cross-service rules in `SKILL.md`).
+3. Write the reactor: one class implementing `IReactor`, one handler per trigger event, no
+   state. It is discovered by the interface; there is no registration step to add.
+4. Add the specifications (below) and run the slice's gate.
+
+The reactor has no route of its own. The invoked model-bound `[Command]` keeps its generated Arc
+HTTP endpoint, so if only the automation should run it, gate it with `[Roles]` or `[Authorize]` and
+give the reactor `[ExecuteCommandsAsSystem]` naming that role.
+
+## Handler patterns
+| Contract says | Handler |
+|---|---|
+| One trigger event, one command | One handler whose first parameter is the trigger event, returning the command built from the trigger's fields. Add `[ExecuteCommandsAsSystem]` only when the command is gated, and `[OnceOnly]` |
+| One trigger event, several commands | Return the commands as a collection: Arc runs them in order, with no transaction across them, and a retry can repeat them (see "Invoking a command from a reactor") |
+| One trigger, events and commands | Return one stable collection mixing registered events and commands (Arc 22.72.0 or later): the events are appended first as one batch, then the commands run in order, with no transaction across them. Add `[OnceOnly]` where a replay must not repeat it. The Stage 4.73.1 scaffold pins Arc 22.68.0, so this needs a proven dependency override; never split the modeled reaction |
+| One trigger event, events produced directly | Return the event or events; `[OnceOnly]` applies (`CHR0022`) |
+| A condition narrows the trigger | Realize exactly the stated `where`. Show it with one specification where it skips and one for the neighboring case where it acts |
+| A fact on another event source | `EventForEventSourceId` with the stated target id |
+| The trigger's fields are not enough | Inject the read model the contract names; do not widen the mapping |
+
+Which return shape expresses "do nothing" for a given handler is established by a scenario that
+runs it, not assumed. Use only the return shapes listed in `SKILL.md`.
+
+## What no longer applies
+Processor identity strings, consumer instance ids, lock and retry configuration, a dead-letter
+store, `schema.migrate()` and a hand-written start and stop call belong to a different runtime.
+Chronicle owns delivery, retry, partition failure and quarantine; see "Failure behavior". Do not
+write a dead-letter table or catch-and-continue around the handler: a swallowed failure is a lost
+fact, not handled (`references/domain-failures.md`).
+
+## Checklist
+- [ ] The slice contract was read first and every trigger, condition, command and field came from it
+- [ ] The trigger event is an `[EventType]` from the owning contracts project
+- [ ] The command (or events) it fires exists and has its own specifications
+- [ ] One handler per trigger event; first parameter is the trigger; no `ReactorSideEffect`, no injected `IEventLog`
+- [ ] Every command or event field is mapped from the trigger, an injected read model or a stated mapping; none invented or defaulted
+- [ ] Every skip condition is the contract's, with a specification on each side of it
+- [ ] Handlers that return events or commands carry `[OnceOnly]`; the effect is idempotent regardless
+- [ ] A gated command has `[ExecuteCommandsAsSystem]` naming the role the command requires
+- [ ] Repeated delivery of the same trigger is specified (what happens when it fires twice)
+- [ ] A modeled slice matches its `.play` contract; the model was not edited to fit the code
+- [ ] The reactor has no route; a command meant only for the automation is gated and the reactor runs it as that role; no processor or lock configuration, no dead-letter store
+- [ ] The build has no `CHR0004`, `CHR0005`, `CHR0008`, `CHR0013`, `CHR0022`, `CHR0031` or `CHR0032` outstanding and the specifications pass
+
+## Specifications
+The trigger-to-command field mapping is part of the contract, so give it its own specification (a
+direct call asserting the returned command, or a `ReactorScenario` where wiring matters). The
+command's own `CommandScenario` covers the command side separately; neither replaces the other.
+Details: `references/specifications.md`.

package/package/corpus/skills/cratis-chronicle-read-model-specifications/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-chronicle-read-model-specifications/SKILL.md

@@ -204,7 +204,7 @@ one, derive it from the projection and say so. Then check each line:
 ## Lineage
 
 Step 6 is adapted in our own words from ideas recorded in `references/provenance.md`.
-Read `references/provenance.md` when checking attribution or the origin of Step 6’s coverage inventory.
+Read `references/view-lifecycle-checks.md` when delivering a read model from a contract: population, update and removal checks per property and event.
 
 ## What breaks
 

package/package/corpus/skills/cratis-chronicle-read-model-specifications/references/provenance.md

@@ -2,14 +2,14 @@
 
 Lineage of the #493 additions to `cratis-chronicle-read-model-specifications`. No TrogonStack material was adapted. Nebulit material is credited below.
 
-## 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 |
 |---|---|---|
 | `.claude/skills/build-state-view/SKILL.md`: checklist: every field asserted, every event covered, empty-list case | `SKILL.md` Step 6 | idea; our own wording kept |
+| `.claude/skills/build-state-view/SKILL.md`: one specification per contract specification, population on the first event, removal on the end event, assertions on the materialized state, optional storyline-derived read-model chain tests | `references/view-lifecycle-checks.md` | Adapted closely as population, update and removal checks over `ReadModelScenario<TReadModel>`; the partial-update and several-instance checks are ours. Not adopted: SQL insert, update and delete operation patterns, Flyway migrations, `PostgreSQLProjectionSpec` with Testcontainers, route creation and wiring; storyline-derived tests wait for storyline syntax (Screenplay#394), lifecycle spec families stand in |
 
 The strict-subscription reconciliation is original to Cratis and verified against Chronicle v18.3.0 and v19.32.0.

package/package/corpus/skills/cratis-chronicle-read-model-specifications/references/view-lifecycle-checks.md

@@ -0,0 +1,79 @@
+# View lifecycle checks
+
+## Contents
+
+- How to use this list
+- Population
+- Update
+- Removal
+- Empty and several-instance cases
+- Closing checklist
+
+Step 6 of `SKILL.md` gives the coverage inventory. This reference expands its three lifecycle
+questions (does the first event populate, does a later event update, does an end event remove)
+into checks you can tick per read model. Use it for each StateView slice you deliver. Adapted from
+Martin Dilger and Nebulit GmbH's build-state-view (see `provenance.md`), with the SQL operations,
+migrations and projection specification harness replaced by `ReadModelScenario<TReadModel>`.
+
+Take the contract first (the `.play` read model, its projection and its specifications, or the
+agreed outline). Write one specification per contract specification, using its example values, and
+add the cases below only where the contract states the behavior; an uncontracted rule found in the
+projection is a proposal for the contract, not silent coverage.
+
+## How to use this list
+For each read model, list its properties and its events in a small table (property, events that
+set it, events that clear it). Walk the three lifecycle stages against it. A cell with no
+specification is a gap to fix or to report.
+
+## Population
+The first event creates the instance with the properties it sets.
+- Seed only that event (`Given.ForEventSource(id).Events(first)`) and assert each property it sets.
+- Assert the key: the instance is the one for that event source (or for the contract's key
+  property). Check the key resolution before the property mapping when `Instance` is `null`.
+- Assert a property the event does not set stays at its default; do not assert a value the
+  contract does not state.
+- Cover every event that can create the instance if the contract has more than one.
+
+## Update
+A later event changes the instance.
+- Seed the first event, then the update event, in that order, and assert the changed property
+  has its new value.
+- Assert every property the update event does **not** set is unchanged. A partial update that
+  clears or overwrites other fields is the common defect; AutoMap can wire an identically named
+  property of another event over an explicit setter, so look at the property the event was not
+  meant to touch.
+- Cover each event that updates the view, with the contract's example value for each.
+- Where several events set the same property, specify the order that matters and the last-writer
+  outcome the contract states.
+- For a child collection, assert the child is added, updated in place, and that siblings stay
+  intact.
+
+## Removal
+An end event removes the instance, or clears a property or a child.
+- Seed the creating event and the removing event, then assert absence: `Instance` is `null`, or
+  the child is gone from the collection. Absence is a result, not a skipped case.
+- Assert a view that must keep ended items does not remove them but sets the contract's status
+  value, and that the removal event does not delete other instances.
+- A suite where every specification only adds is green and untested for removal; add the end
+  event for each removal in the contract.
+
+## Empty and several-instance cases
+- **Empty.** With no matching events `Instance` is `null` (the empty initial state, or the
+  baseline you passed to the scenario). Assert it where "no result" is a behavior the contract
+  states, such as a list with no rows.
+- **Several instances.** Where a view holds one row per source, seed two event sources and use
+  `InstanceForEventSourceId(id)` or `Instances`; a single `Instance` would throw
+  `MultipleInstancesMaterialized`. Assert that one source's events do not touch the other's row.
+- **Subscribed events.** The events your specifications seed, the projection's subscriptions and
+  the contract's events agree in both directions; report any difference to
+  `cratis-application-slice-conformance`.
+
+## Closing checklist
+- [ ] Every read-model property is asserted in at least one specification
+- [ ] Every creating event has a population specification asserting the properties it sets and the key
+- [ ] Every updating event has a specification, and the properties it does not set are asserted unchanged
+- [ ] Every removal or clearing event has a specification asserting absence
+- [ ] The empty case and, where the view holds many rows, a two-source case are specified when the contract states them
+- [ ] Example values and relationships come from the contract; fresh identifiers only where isolation needs them
+- [ ] No property, column or event beyond the contract's read model appears in the code or the specifications
+- [ ] Each new specification was seen to fail once (drop a seeded event, confirm the assertion goes red)

package/package/corpus/skills/cratis-event-model-diagram/LICENSE

@@ -1,2 +1,9 @@
 Copyright (c) Cratis. All rights reserved.
 Licensed under the MIT license. See LICENSE file in the project root for full license information.
+
+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 explicit consent of Martin Dilger and Nebulit GmbH. The adapted
+material remains credited to Martin Dilger and Nebulit GmbH. See references/provenance.md.

package/package/corpus/skills/cratis-event-model-diagram/SKILL.md

@@ -19,8 +19,10 @@ and later). The grammar is owned by Mermaid, and
 file and Mermaid disagree. Confirm the Mermaid version available to the renderer
 before relying on a construct.
 
-The Cratis artifacts a diagram refers to are verified against `Cratis.Chronicle`
-`18.3.0` and the Arc query and command surface it is used with.
+The Cratis artifacts a diagram refers to were originally checked against `Cratis.Chronicle`
+18.3.0 and re-read against Chronicle 19.50.0 and the Arc query and command surface it is used with
+(current pins: `cratis-screenplay-toolchain` `references/versions.md`). The Mermaid claim above is
+external and was not re-verified here.
 
 ## What an event model is
 
@@ -100,6 +102,26 @@ tf 12 evt <EntityName><PastTenseVerb>
 - Several consumers of one read model: declare each consumer `ui` as its own
   `rf` frame with an explicit `->>` back to the `rmo`.
 
+## Connections read forward
+
+A diagram reads left to right, so every connection goes to a later frame, never back to an
+earlier one. In practice:
+
+- Number frames in story order and put elements that belong together next to each other: a
+  persona and the command it issues, a command and the events it produces, an event and the
+  read model that projects it. A read model's `->>` sources are frames that come **before** it.
+- When a later event must change what an earlier read model shows, do not draw an arrow back to
+  that read model. Draw a new `rmo` frame after the later event, sourced from the events that now
+  matter (it is the same read model carried to a later state), and give it its own consumer
+  `ui` frame if a person looks at it. The earlier frame stays as it was: it correctly showed
+  that earlier point in the story. The model itself is unchanged; its projection simply
+  consumes the later event.
+- If the natural place for a frame is already taken, insert it just before or after rather than
+  wiring across the gap.
+
+Adapted from Martin Dilger and Nebulit GmbH's core rules (`references/provenance.md`); their
+board mechanics (columns, cells, linked copies) do not apply to Mermaid frames.
+
 ## The command rules table
 
 Mermaid's eventmodeling grammar has no shape for validation or guards. After the
@@ -166,3 +188,5 @@ language. Include commands that emit no event.
   for a hand-written Chronicle implementation, or
   `cratis-screenplay-event-modeling` when the model is authored as a Screenplay
   `.play` document.
+
+Attribution for adapted method text: `references/provenance.md`.

package/package/corpus/skills/cratis-event-model-diagram/references/provenance.md

@@ -0,0 +1,19 @@
+# Provenance
+
+## 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), used with the explicit consent of Martin Dilger
+and Nebulit GmbH. The notice is in this skill's `LICENSE`.
+
+| Source file | Used in | How |
+|---|---|---|
+| `.claude/skills/eventmodeling-core-rules/SKILL.md`: "Connections Read Forward" and "Updating a Read Model That Already Feeds a Screen" | `SKILL.md` "Connections read forward" | Adapted closely; board columns, cells, linked copies and `link_element` dropped; the later-state read model becomes a later `rmo` frame in the Mermaid diagram |
+
+Not adopted: lanes and the four-row column layout, placement mechanics, single-issuer commands (Mermaid frames
+carry no such rule, and Screenplay commands may have several origins).
+
+## Other lineage
+
+- Mermaid `eventmodeling` diagram type: https://mermaid.js.org/syntax/eventmodeling.html.
+- Event Modeling (Adam Dymitruk) and Martin Dilger, *Understanding Eventsourcing*: the timeline as left-to-right business flow.

package/package/corpus/skills/cratis-screenplay-automations-and-translations/LICENSE

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

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

@@ -28,9 +28,9 @@ identity, effect and pending-work contract at that point; do not postpone it to
 
 ## Tool and realization facts (read before promising anything)
 - Reactions, clocks, triggers, captures and Automation/Translate slices compile (V1) and bind (V3)
-  on Screenplay 4.61 or later: the standalone tool and the cratis CLI 3.28.2 or later (bundled
-  4.66.0). Probed on 3.28.2: the complete examples are `executableReady`. A cratis bundle before 3.28.2
-  (4.60.1) reports PLAY0268 at binding: report "V3 blocked: PLAY0268 (ESM v6)" and
+  on Screenplay 4.61 or later: the standalone tool and the cratis CLI 3.28.2 or later (3.53.1
+  bundles 4.137.0). Probed on 3.28.2: the complete examples are `executableReady`. A cratis bundle before 3.28.2
+  (4.60.1) reported PLAY0268 at binding: report "V3 blocked: PLAY0268 (ESM v6)" and
   name the tool, never remove them.
 - Standalone 4.125.0 runs admitted scenarios through `screenplay test` or MCP
   `run-specifications`; source validation and render publication do not run V4.
@@ -40,8 +40,8 @@ identity, effect and pending-work contract at that point; do not postpone it to
 - Reaction `runs as system role "<Role>"` declares an invocation actor (ESM v10).
   Without it the invoke has no caller. Historical CLI 3.41.0's 4.114.0 compiler
   rejected the syntax (PLAY0137); previous CLI 3.46.1 refused ESM v10
-  at render admission (CLI-RENDER-004). CLI 3.50.0 reaches Stage 4.67.0's
-  construct admission, which still refuses reaction identity (STAGE-ESM-034). Checked model/diagnostics: captures-and-reactions
+  at render admission (CLI-RENDER-004). The pinned CLI/Stage pair (toolchain
+  `references/versions.md`) reaches construct admission, which still refuses reaction identity (STAGE-ESM-034). Checked model/diagnostics: captures-and-reactions
   `references/invocation-identity.md`.
 
 ## Effect guarantees and recovery traps
@@ -71,13 +71,17 @@ even when it blocks binding. Never record bearer tokens, magic links or signed U
 (a keyed hash or reference at most), and never put PII on the event-source id.
 
 ## Verified product sources
+Current pins: toolchain `references/versions.md`. Language claims were re-read at Screenplay v4.139.0,
+renderer claims at Stage v4.73.1 (no Automation, Translate, reaction or capture: `STAGE-ESM-024`), the
+runtime facts at Arc v22.72.0 and Chronicle v19.50.0. Older reads kept as history:
+
 | Package | Version | Used for |
 | --- | --- | --- |
 | Screenplay | v4.66.0 (`c89198b`) | `Documentation/screenplay/{reactions,captures,triggers,specifications,diagnostics}.md`; examples compiled with the standalone tool |
-| cratis CLI | v3.28.3 | bundles Screenplay 4.66.0 and Stage 4.24.2 (before 3.28.2: 4.60.1, which gave PLAY0268 on v6 constructs and a false PLAY0285 on cascades, cli#242) |
-| Stage | v4.24.2 | admits ESM v1 to v4; renders no Automation or Translate slice |
-| Arc | v22.50.5 | `ExecuteCommandsAsSystemAttribute` (since v20.56.0) |
-| Chronicle | v19.32.0 | `OnceOnlyAttribute`, `ReactorDelivery` and `Documentation/reactors/delivery-identity.mdx` |
+| cratis CLI | v3.28.3 | bundled Screenplay 4.66.0 and Stage 4.24.2 (before 3.28.2: 4.60.1, which gave PLAY0268 on v6 constructs and a false PLAY0285 on cascades, cli#242) |
+| Stage | v4.24.2 | admitted ESM v1 to v4; rendered no Automation or Translate slice |
+| Arc | v22.72.0 (read; v22.50.5 earlier) | `ExecuteCommandsAsSystemAttribute` (since v20.56.0); mixed events-and-commands reactor returns (since v22.72.0) |
+| Chronicle | v19.50.0 (read; v19.32.0 earlier) | `OnceOnlyAttribute`, `ReactorDelivery` and `Documentation/reactors/delivery-identity.mdx` |
 
 Read `references/versions.md` in `cratis-screenplay-toolchain` when selecting a tool or checking the full version and capability pins. Reverify before claiming
 another version behaves the same.
@@ -164,8 +168,9 @@ or actor that nobody confirmed. Read `references/worked-integration.md` when you
   separate binder check.
 - A trigger with `reads` that `produces` directly fails binding: decide in a command. `reads` never protects.
 - An authorized command exercised in a spec without `given caller` is PLAY0389 at binding.
-- A list query (`=> Item[]`) and a clock sweep that iterates items do not bind; show them only as marked
-  design-only excerpts (`references/todo-list-example.md`).
+- A list query (`=> Item[]`) binds (Screenplay 4.105.0+; a snapshot list is not rendered, `STAGE-ESM-010`);
+  a clock sweep that iterates items needs a code body the reference does not run
+  (`references/todo-list-example.md`).
 
 **Modeling defaults** (deviate with a recorded reason)
 - A `produces` without `for` lands on the triggering fact's source; clock and trigger occurrences have

package/package/corpus/skills/cratis-screenplay-automations-and-translations/references/audit-format.md

@@ -12,7 +12,7 @@ technique: partial work stays visible and nothing is skipped because it looked r
 Result is `complete` only when every column is filled or says why it does not apply (for example
 "direct effect: immediate, internal, cannot fail"). `open` names the unresolved decision and who
 answers. `blocked` names the actual capability gap with intended behavior. For example,
-CLI 3.50.0 admits ESM v10 to Stage 4.67.0 construct checks, where reaction identity
+the pinned CLI/Stage pair (toolchain `references/versions.md`) admits ESM v10 to construct checks, where reaction identity
 is refused with STAGE-ESM-034. Previous CLI 3.46.1 refused v10 at the version gate
 with CLI-RENDER-004; do not report that historical refusal as the current gap.