@cratis/pi 7.86.0 → 7.87.1

package/package/corpus/harnesses/copilot/instructions/github-actions.instructions.md

@@ -72,7 +72,11 @@ paths:
 - A bot's pre-push verification build must match the strictest configuration any CI in
   the organization applies to the same commit (build `Release` when consumers enforce
   analyzers there). Do not add `[skip ci]` to bot commits as a load optimization: the
-  downstream CI run is the only check that sees the merged result.
+  downstream CI run is the only check that sees the merged result. One exception: a
+  bootstrap commit that changes **only** bootstrapped wrapper workflow files, whose
+  content the source repository's CI verified before the rollout, may carry
+  `[skip ci]` once the same wrapper content has landed with CI running in one canary
+  repository. Package-update bots, and any commit touching another file, keep normal CI.
 - Comment-triggered agent workflows must gate on the trigger phrase in the job's `if:`
   (for example `contains(github.event.comment.body, '@claude')`) so a runner only
   starts when the agent is actually addressed.

package/package/corpus/rules/github-actions.md

@@ -71,7 +71,11 @@ paths:
 - A bot's pre-push verification build must match the strictest configuration any CI in
   the organization applies to the same commit (build `Release` when consumers enforce
   analyzers there). Do not add `[skip ci]` to bot commits as a load optimization: the
-  downstream CI run is the only check that sees the merged result.
+  downstream CI run is the only check that sees the merged result. One exception: a
+  bootstrap commit that changes **only** bootstrapped wrapper workflow files, whose
+  content the source repository's CI verified before the rollout, may carry
+  `[skip ci]` once the same wrapper content has landed with CI running in one canary
+  repository. Package-update bots, and any commit touching another file, keep normal CI.
 - Comment-triggered agent workflows must gate on the trigger phrase in the job's `if:`
   (for example `contains(github.event.comment.body, '@claude')`) so a runner only
   starts when the agent is actually addressed.

package/package/corpus/skills/cratis-screenplay-captures-and-reactions/references/record-capture-specifications.md

@@ -9,6 +9,11 @@ For `source api`, webhook, poll and other record sources, a first record of a ty
 
 This applies independently to each child identity in its parent's previous collection and each nested record: a missing/null previous nested value is new, and every child of a new parent is new. Expression guards still evaluate the mapped current record on first sight; maps and unguarded appends keep their meaning. These record fixtures are not valid for `source events`: use typed events instead (automations-and-translations [public event captures](../../cratis-screenplay-automations-and-translations/references/public-events-and-direction.md)).
 
+A capture **over events** carries a public event's list across the boundary two ways (decision 0098, no new ESM version): `lines = $.lines`
+copies the whole list into a list property of the same shape (matched by property name), and `children lines identified by sku` with an
+`append ... when added` makes one private event per element, so a repeated delivery appends nothing and one with an extra line appends only
+that line. `nested <object>` scopes into an object the same way.
+
 The complete model separates a new observation, an update and an unchanged repeat:
 
 ```screenplay

package/package/corpus/skills/cratis-screenplay-command-surface/references/constraints-produces-concurrency.md

@@ -68,8 +68,9 @@ to the routed scope. This does not make command `reads` protected.
   computed expressions parse but block binding (`PLAY0268`).
 - **`for <identifier>`** on an indented line names the event source the event is
   appended to. At most one per `produces`. To bind, it must name the command's
-  `identifier` property (`PLAY0273` otherwise; a `generated identifier` command, ESM v7, may name another required scalar property); fanning out to another event
-  source parses but does not run today.
+  `identifier` property (`PLAY0273` otherwise; a `generated identifier` command, ESM v7, may name another required scalar property). From ESM v30 (decision 0098)
+  a command may append to several event sources: each `produces` may name any required scalar command property, and the events of one accepted command are appended
+  together. Optional and collection properties still cannot be destinations. A model using it selects v30; state each destination with `for` on the matching `then` event.
 - **`tag`** lines apply literal tags to this append. Tags also exist on the
   `event` declaration, where they apply to every append of that type.
 - **Several unconditional `produces` blocks** are allowed — that is co-production,

package/package/corpus/skills/cratis-screenplay-command-surface/references/validate-rules.md

@@ -13,6 +13,7 @@
 | `matches "<regex>"` | Portable linear dialect; any substring unless anchored `^…$`; invalid syntax PLAY0367, refused constructs PLAY0699 |
 | `contains "<text>"` / `not contains "<text>"` | Ordinal substring presence/absence on scalar non-enum text |
 | `starts with "<text>"` / `ends with "<text>"` | Ordinal prefix/suffix; quoted literal operands, not conditions |
+| `decimals <= <n>` | `price decimals <= 2`; a `Decimal` property or concept only, `<n>` a whole number 0 to 28, trailing zeros do not count; ESM v29 (decision 0098) |
 | `all > <v>` / `all >= <v>` | `lines.quantity all > 0` |
 | `rule <Name>` | `orgNumber rule BeAValidOrganizationNumber` |
 | `checksum luhn|mod11|mod97` | String concept `validate checksum luhn`; validates supplied/stored values too |

package/package/corpus/skills/cratis-screenplay-projections/references/joins.md

@@ -35,7 +35,8 @@ A join cannot declare its own key or trigger removal — that is
 | `increment <prop>` | +1, expressing *modifying state* |
 | `decrement <prop>` | −1 |
 | `add <prop> by <expr>` | += expression |
-| `subtract <prop> by <expr>` | −= expression |
+| `add <prop> by <a> * <b>` | += the exact product of two values (ESM v29, decision 0098); only after `by`, one `*` |
+| `subtract <prop> by <expr>` | −= expression (also `by <a> * <b>`) |
 
 `count` and `increment` behave identically; the difference is intent. The target
 must be numeric.

package/package/corpus/skills/cratis-screenplay-specifications/references/generated-fixtures.md

@@ -66,6 +66,10 @@ specification RegistersWithPinnedValues
   differences in response field order. An absent optional source yields `Null`; arrays compare in order.
 - `then returns` counts as a success outcome but does not relax event comparison: a command specification with
   no expected events still asserts that no facts were produced.
+- A command that a **reaction** invokes takes its generated values from `given generated <Command>.<property> = <value>` lines
+  before the `when` (ESM v30, decision 0098). Each invocation takes the next value pinned for that
+  command and property in authored order; two invocations need two lines. The property must be `generated`; the value is a
+  concrete literal.
 - If execution reaches generation without every generated value supplied, the run is `Unsupported(IdentityAllocation)` and
   the specification never passes; nothing is invented. A denial or validation failure happens before generation and
   keeps its own outcome.

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

@@ -59,6 +59,13 @@ module Collections
   or mixed effects (`-037`). Single-hop reaction append specs render; deeper appends and
   command specs cascading into reactions remain `-011`. Keep refused scope as gap-fill against this contract: `cratis-screenplay-render-and-gap-fill`.
 
+### A command specification states the public event its slice publishes
+
+When an outbound Translate slice publishes an event from the private events a command produces, the command's specification
+lists the public event after the private ones (`then ProductPriceChanged` after `then ProductPriceSet`). `PLAY0285` follows the
+outbound projection (decision 0098); the accepted path is proven where the command is. An exact fact count
+fails without it.
+
 ### Version skew: cascades and the false `PLAY0285`
 
 `PLAY0285` (a specification's expected event contradicts every producer of its

package/package/corpus/skills/cratis-screenplay-toolchain/references/language-admission.md

@@ -16,6 +16,10 @@ exact language/semantic pairs; binding, reference execution and rendering are se
 | v26 | Chronological command Date/DateTime comparisons | Same-primitive `==`, `!=`, `>`, `>=`, `<`, `<=`; DateTime UTC ticks and pre-rule offset validation | v26 admitted; Host/executor run it; renderer supports admitted shapes with remaining STAGE-ESM-046 refusals; legacy engines refuse -046 |
 | v27 | A read model with two or more `key` marks | Untyped projection `key` blocks, equality-filter lists, single-instance `by` blocks, per-part fixtures | v27 admitted; Host runs it, renderer refuses STAGE-ESM-048/-047, executor refuses specs over it |
 | v28 | `==`/`!=` between Uuid values in command `require` and `produces when` | Uuid properties, Uuid concepts and identities, canonical literals; protected read paths in `require` only | v28 refused STAGE-ESM-016 |
+| v29 | `decimals <= N`; `add`/`subtract` by `a * b`; a concept mapped to another concept over the same primitive (decision 0098) | Decimal-places rule on a Decimal concept or property; the exact decimal product; the conversion is admitted only when the target declares no rule or compliance the source does not, never for enums, composites or optional into required | v29 refused until Stage admits it |
+| v30 | A command `produces ... for <required scalar property>` (several event sources); a specification `given generated <Command>.<property> = <value>` (decision 0098) | Several sources in one accepted command; pinned generated values for reaction-invoked commands, taken in authored order | v30 refused until Stage admits it |
+
+Constructs of decision 0098 with no executable-model content need no version: application-level toolbar buttons in the layout's `navigation topbar` region (`button <id> title "..." slice <Slice>` with an optional indented `authorize <Policy>`), a command specification that states the public event its outbound Translate slice publishes (no more false `PLAY0285`), and a capture over events that copies a list (`lines = $.lines`) or fans out with `children lines identified by sku`. Check `screenplay --version` against the release that admitted v29 and v30 before relying on them.
 
 Requires Screenplay 4.181.0 or later (`screenplay --version`) for atomic batches; older compilers cannot admit the preamble.
 

package/package/corpus/skills/cratis-screenplay-ui-composition/references/application-shell.md

@@ -166,6 +166,25 @@ own.
 - `item` entries (`action`, `navigate to`, `dialog`) stay valid beside buttons. Use `button` to start a slice, and
   `item ... navigate to` to go to a screen.
 
+### Application-level buttons
+
+A layout's `navigation topbar` region takes the same `button` line once for the whole application, so an action stays at hand
+whichever page the user is on. An indented `authorize <Policy>` line under a button limits who sees it. A module's
+`navigation topbar extends|overrides|inherits` governs the buttons as it does the items. A button in `navigation sidebar` is
+`PLAY0741`. The slice rules above (`PLAY0761`-`PLAY0765`) apply unchanged (decision 0098).
+
+```text
+layout AppShell
+  category application
+  topbar
+  navigation contributes Navigation
+  content
+  navigation topbar
+    item shop title "Shop" target Shop
+    button newProduct title "New product" slice Merchandising.Products.DraftProduct emphasis primary icon plus
+      authorize CanCurateCatalog
+```
+
 ⚠️ When a screen uses a `template`, put the `toolbar` inside a slot body (`body` above). Stage refuses a screen that
 mixes a top-level `template` directive with other top-level directives.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cratis/pi",
-  "version": "7.86.0",
+  "version": "7.87.1",
   "description": "Configuration-aware Cratis AI integration for Pi",
   "type": "module",
   "files": [