@cratis/pi 7.116.1 → 7.118.0

package/package/corpus/skills/cratis-stage-rendering-and-sandbox/references/admission.md

@@ -12,13 +12,15 @@
 - Specification rules (`STAGE-ESM-011`)
 - Refusals seen while drafting a model
 
-Stage admits exact ESM v1–v27 language/semantic pairs, then checks
-constructs. V28 and mixed or unknown pairs report `STAGE-ESM-016`. `cratis render` admits
-ESM v1–v27: Stage plans each model and refuses the constructs it cannot render with typed `STAGE-*`
-codes (atomic batches report `STAGE-ESM-043`; unsupported v26 date shapes `STAGE-ESM-046`; v27 composite
-read-model keys report `STAGE-ESM-048`/`-047`). The CLI refuses
-a bound model above v27 with `CLI-RENDER-004` before planning; a construct its bundled compiler cannot bind
-reports PLAY0268 instead.
+Stage v4.197.0 admits matched language/ESM pairs **1.0–30.0 and 32.0**, then
+checks constructs per target. V31 anonymous conditions, mixed and unknown pairs
+report `STAGE-ESM-016`. CLI v3.100.0 `cratis render` independently admits semantic
+versions through v30 (`CLI-RENDER-004` above it); its bundled Stage then
+checks matched pairs and constructs. V32 needs a direct caller of the reviewed
+Stage baseline. See [CLI bundle details](../../cratis-screenplay-toolchain/references/language-admission.md#stage-admission-and-execution).
+A construct the bundled compiler cannot bind reports PLAY0268 first. Read [current target boundaries](current-boundaries.md)
+for renderer, semantic Host/specification, Translate, atomic, composite-key and
+implementation-gap support before applying the historical minimums below.
 
 Requires Cratis CLI 3.74.0 (`cratis --version`) for v21–v26 rendering and 3.75.0 for v27; CLI 3.66.0–3.73.0 stop at v20 and refuse v21 and
 later with `CLI-RENDER-004`. A construct newer than the CLI's bundled compiler reports that binder's PLAY0268 first.
@@ -40,9 +42,12 @@ always needs pins.
 Requires Stage 4.124.0 for v24 text-rule admission (`cratis --version` identifies the CLI bundle); older renderers refuse v24 with STAGE-ESM-016.
 Requires Stage 4.127.0 for v25 version admission; older renderers refuse v25 with STAGE-ESM-016. Requires Stage 4.138.0 for the Cratis renderer to render protected reads as Arc read protection (`[ReadProtection(On)]`, a nullable read-model `Handle` parameter per read with `[LookUpBy]`, the `<View> '<key>' does not exist.` rejection, requirements evaluated in `Handle` after the reads; generated specifications run in decision mode); `cratis render` gets it from the first CLI that bundles Stage 4.138.0, and earlier bundles (CLI 3.75.0 bundles 4.137.0) refuse every protected read with STAGE-ESM-044. Reads it cannot preserve faithfully stay STAGE-ESM-044 and name the reason: constrained events, read paths in `produces when`, mappings to optional, collection, composite or mistyped event properties, generated-value freshness scopes. See [protected reads](../../cratis-screenplay-command-surface/references/protected-reads.md).
 Requires Stage 4.129.0 for semantic Host/executor protected reads; older engines refuse STAGE-ESM-044. Required absence rejects before requirements or generation; read-backed requirements and produced-event mappings execute. Non-Error protected requirements refuse STAGE-ESM-045, including reaction invocations. See [sandbox boundaries](sandbox-and-specrunner.md#protected-command-reads) for ordering and outside-append commit boundaries.
-Described handlers refuse STAGE-IMPL-002, even Stub mode; atomic mode in an
-admitted pair refuses STAGE-ESM-043. Version admission never implements a body,
-batch or composite-key rendering. Chronological Date/DateTime command comparisons
+Described handlers still refuse STAGE-IMPL-002, even in Stub mode. Query
+performers have a separate implementation-gap contract; gaps are not completed
+behavior. Bounded atomic event production renders; multiple same-event
+production triggers and routed direct productions still refuse STAGE-ESM-043.
+Version admission never implements a body or proves a batch boundary.
+Chronological Date/DateTime command comparisons
 select v26. The semantic Host and specification executor run them.
 Requires Stage 4.139.0 for v22 admission; older Stage refuses v22 with -016.
 Requires Stage 4.141.0 for rendered date comparisons; older renderers and legacy
@@ -52,7 +57,13 @@ rules; never downgrade to ordinal text or millisecond precision.
 
 Requires Stage 4.135.0 for v26 admission; older Stage refuses v26 with STAGE-ESM-016.
 
-Requires Stage 4.137.0 for v27 admission; older Stage refuses v27 with STAGE-ESM-016. The semantic Host runs read models with several key parts end to end (projections keyed by parts, removals, list queries on any part, queries by parts), and composite-keyed read models get no conventional `Get<ReadModel>ById` query. The specification executor refuses specifications over them as unsupported. The renderer and legacy syntax engine refuse a read model with several key parts or a projection keyed by parts with `STAGE-ESM-048`, and the renderer a single-instance query by parts with `STAGE-ESM-047` until Chronicle can look up composite keys (Chronicle#4265); nothing is published.
+Requires Stage 4.137.0 for v27 admission; older Stage refuses v27 with STAGE-ESM-016.
+The reviewed semantic Host runs composite-key read models and key-part
+lookups; specification execution still refuses multi-part keys. The renderer admits bounded scoped composite-key
+projections, not every parts-key shape; unsupported shapes retain STAGE-ESM-048.
+Single-instance query lookup by parts still refuses STAGE-ESM-047 until
+Chronicle#4265. The legacy syntax engine retains STAGE-ESM-048. See
+[current composite-key boundaries](current-boundaries.md#renderer-support-is-bounded).
 
 Binding with the CLI's bundled compiler is a separate
 prerequisite. The exhaustive construct table is `references/renderable-subset.md` in
@@ -159,46 +170,46 @@ Requires Stage 4.90.0 for snapshot/live lists, 4.96.0 for non-text secrets and 4
 
 | Code | Meaning | Usual fix |
 | --- | --- | --- |
-| `STAGE-ESM-001` | Unsupported slice kind; `StateChange`, `StateView` and supported event-triggered `Automation` slices render; Translate is `-024` | Keep the model; gap-fill refused scope |
+| `STAGE-ESM-001` | Unsupported slice kind; `StateChange`, `StateView` and supported event-triggered `Automation` slices render; unsupported Translate shapes are `-024` | Keep the model; gap-fill refused scope |
 | `STAGE-ESM-002`, `-003` | Concept values or validation Stage cannot express; unresolved property type | Simplify the concept; fix the type |
 | `STAGE-ESM-004` | A `StateChange` slice without commands | Add the modeled command; multiple commands render |
 | `STAGE-ESM-005` | Code validation or rule predicate bodies; or a command beyond the first capability (optional event property, event revision other than the first, validation or requirement that cannot be rendered, neither `produces` nor a response) | Use declarative validation; non-initial event generations are not rendered |
 | `STAGE-ESM-006` | `produces` that cannot render without changing its destination or mappings (expression/enum conditions, literal or computed mappings, `for` not a command identifier, mappings not one-to-one with event properties, duplicate tags) | Map properties one to one; supported conditional productions render as guarded events, not separate commands |
 | `STAGE-ESM-007`, `-008`, `-009` | Projection count per read model (exactly one projection or reducer each); unresolvable properties or no single read-model transition (**flat** projections only); affected instance not one, not keyed by an event property, or not the event-source identity (flat projections only) | One projection per read model; see "Projections" below |
-| `STAGE-ESM-010` | A query is neither an optional snapshot lookup by the read-model identifier nor a supported snapshot/observable collection query; each query is checked on its own. Both collection modes render. Concept-typed keys and filters retain Arc validation, including composite members and collection elements; nullable concept keys or optional concept filters with `not empty` cannot preserve null semantics | Keyed `XById => X optional` queries or snapshot/observable lists. Equality filters render on both collections; DateTime filters, required filters after optional ones and unsupported null-validation shapes refuse 010. Filter-name collisions refuse 012. Context/single-result filters, opaque scope and a list-query `by` block remain PLAY0268; a performer query is left out of the model (PLAY0270, Requires Screenplay 4.220.1), so render emits nothing for it and it is a gap-fill item; a read model with several key parts (v27) refuses `STAGE-ESM-048` |
+| `STAGE-ESM-010` | A query is neither an optional snapshot lookup by the read-model identifier nor a supported snapshot/observable collection query; each query is checked on its own. Both collection modes render. Concept-typed keys and filters retain Arc validation, including composite members and collection elements; nullable concept keys or optional concept filters with `not empty` cannot preserve null semantics | Keyed `XById => X optional` queries or snapshot/observable lists. Equality filters render on both collections; DateTime filters, required filters after optional ones and unsupported null-validation shapes refuse 010. Filter-name collisions refuse 012. Context/single-result filters, opaque scope and a list-query `by` block remain PLAY0268; a performer query is left out of the model (PLAY0270, Requires Screenplay 4.220.1), so render emits nothing for it and it is a gap-fill item; unsupported composite-key projection shapes refuse `STAGE-ESM-048`; single-instance lookup by parts remains `-047` |
 | `STAGE-ESM-011` | A specification cannot render (see the rules below) | Reshape it only if the assertion keeps its meaning; otherwise keep the specification, record the gap, and gap-fill with the specification as the oracle. Never weaken or delete it to get a render |
 | `STAGE-ESM-012` | Generated C# names collide (properties, types, namespaces, constraints) | Rename |
 | `STAGE-ESM-013` | An event-context value other than `$context.occurred` mapped in `produces` | Map a command property when that preserves the meaning; otherwise gap-fill |
 | `STAGE-ESM-014` | A constraint Chronicle cannot reproduce (kind, scope, message; multi-claim in one command; optional or composite targets) | A different constraint is a requirement change for the model owner; otherwise gap-fill |
 | `STAGE-ESM-015` | Authorization Stage cannot render exactly: a role-claim URI, an opaque policy nested inside a condition, an unresolved or non-portable policy, no single identifier, an opaque-policy subject that is not text, Uuid, Date or DateTime (a restriction on opaque-policy subjects, separate from declarative claim targets), an unsupported claim artifact. Role-only, authenticated, opaque pure policies, claim conditions with Uuid, Date, DateTime or text targets (numeric and Boolean claim matches render as always false) and `not`/and/or render; roles are read through the identity's `RoleClaimType` | Reshape the policy to a portable condition; otherwise gap-fill |
-| `STAGE-ESM-016` | Model language/semantic pair is not admitted by the installed Stage; exact v1–v27 pairs are admitted, v28 and mixed pairs refused; older Stage also refuses the versions listed in the minimums above. A CLI bundle reports `CLI-RENDER-004` above its ceiling (v27 for CLI 3.75.0) first. v14 filters and v15 generation join v11 numbers, v12 enum numbers and v13 compliance as supported constructs, not blanket construct support | Not fixable by editing: the model needs a newer renderer. Keep the model, record the gap, gap-fill |
-| `STAGE-ESM-017` | Read model or projection cannot render (property names that collide with Chronicle paths or expression syntax, mappings that overwrite the key or child identity, composite keys, unsupported `all` mappings, the refused scope shapes below) | Reshape the projection without changing what it records, or record the gap |
+| `STAGE-ESM-016` | Model language/semantic pair is not admitted by the installed Stage; matched 1.0–30.0 and 32.0 are admitted, not 31.0 or mixed pairs; older Stage also refuses the versions listed in the minimums above. A CLI bundle reports `CLI-RENDER-004` above its ceiling (v27 for CLI 3.75.0) first. v14 filters and v15 generation join v11 numbers, v12 enum numbers and v13 compliance as supported constructs, not blanket construct support | Not fixable by editing: the model needs a newer renderer. Keep the model, record the gap, gap-fill |
+| `STAGE-ESM-017` | Read model or projection cannot render (property names that collide with Chronicle paths or expression syntax, mappings that overwrite the key or child identity, unsupported key/scope shapes and unsupported `all` mappings below) | Reshape the projection without changing what it records, or record the gap |
 | `STAGE-ESM-018` | `$strings.` key missing in the default locale or containing formatting characters | Fix the strings |
 | `STAGE-ESM-019` | Reducer structure or body not admitted (outside a `StateView`, impure, does not compile), or a `generate rule` body that does not compile or produces a compiler warning | An equivalent pure body, or gap-fill |
 | `STAGE-ESM-020` | Implementation body (including a `generate rule` attachment) missing, changed (hash differs) or refused by the loader | Provide the body inside the model root |
 | `STAGE-ESM-021`, `-022` | Reducer typed-context or analysis failure; a construct outside the pure allowlist, or a generated name shadowing a reducer type; also type or namespace shadowing in a `generate rule` body (`-022`) | An equivalent pure body, or gap-fill |
 | `STAGE-ESM-025` | Typed context references an earlier event revision or an earlier property identity; checked before `-026` | Reference the current revision; an earlier reference is not renderable, so gap-fill |
 | `STAGE-ESM-026` | A selected event, or an event a selected slice depends on (producing command, observing projection or reducer, specification, constraint target), is above its initial revision: `Event 'X' has evolved to revision N; Stage does not render event migrations yet.` The whole selection is refused, nothing is emitted | Not fixable by editing without dropping the evolution. Gap-fill the evolved events and hand-write the migrations (`cratis-chronicle-event-type-migration`). A scoped slice of initial events that depends on no evolved event still renders |
-| `STAGE-ESM-024` | Interval, schedule, application, startup and shutdown triggers, opaque reaction bodies, captures, Translate (including directed Translate), and clock/trigger/capture specifications. Event-triggered Automation slices render as Chronicle reactors, subject to `-013` and `-034` to `-040` below | Keep refused scope as gap-fill; do not confuse semantic Host settlement with live reactor delivery |
+| `STAGE-ESM-024` | Unsupported reaction triggers, opaque reaction bodies, Translate shapes or occurrence specifications; bounded source-event captures now render and admitted capture cases have semantic support | Keep refused scope as gap-fill; check [current boundaries](current-boundaries.md), and do not confuse semantic settlement with live delivery |
 | `STAGE-ESM-027` | A specification asserting a read model is absent (`then no readmodel`) is not rendered (the semantic specification engine executes keyed absence) | Keep the specification; verify absence another way and record the gap |
 | `STAGE-ESM-028`, `-029` | Generated values or responses Stage cannot render. Supported scalar UUID/String-concept strategies and Int random, v15 freshness, generation fixtures, scalar/named responses and `then returns` render; unknown strategies, unsupported generated types, and (in the Host and legacy syntax engine) a command generating a `generate rule` value report `-028` | Probe the supported form; preserve refused combinations as gap-fill |
 | `STAGE-ESM-038` | Generated/response results combined with routes, generated-property rules, legacy allocation, non-scalar/non-command response sources or generated-name collisions | Keep the model; gap-fill that command |
 | `STAGE-ESM-039`, `-040` | Reaction conditions, destinations or mappings outside the faithful target subset; protected identity uses (including reaction destinations) and protected enum concepts | See the event-reaction boundary above; never declassify protected values |
 | `STAGE-ESM-030` | Named event-source or stream definition with a reserved stored name; unformattable routed fixtures or command replay routes. The default sandbox engine also reports it for every routed model | Rename the reserved name; render the model with `cratis render`, not `cratis run` |
 | `STAGE-ESM-031` | Whole-number literal outside the C# `int` range below ESM v8 (v8 and later render `long`) | Raise the model to v8 constructs or gap-fill |
-| `STAGE-ESM-032`, `-033` | Public events and event-target projections or reducers (ESM v9); foreign event origins and event-source captures | Gap-fill |
+| `STAGE-ESM-032`, `-033` | Unsupported public/foreign-event uses; the live semantic Host can append public events locally and accept foreign-event seeds, but does not perform external publication or polling | Check [target-specific Translate support](current-boundaries.md#renderer-support-is-bounded); gap-fill refused uses |
 | `STAGE-ESM-034` | Reaction `runs as` invoking claim-reading or opaque authorization; every `runs as` on legacy syntax paths | Keep the gate; gap-fill |
 | `STAGE-ESM-035` | Observer filters on legacy syntax paths; semantic reaction/reducer filters render | Use semantic admission |
 | `STAGE-ESM-036` | Per-production route overrides | Gap-fill |
 | `STAGE-ESM-041` | Older renderers refuse non-text secrets; supported renderers keep their original types | Keep classification; upgrade the renderer, never declassify |
 | `STAGE-ESM-042` | Unknown validation rule kinds; checksum on the legacy syntax path (semantic checksum renders) | Keep the rule; use an admitting semantic renderer or gap-fill |
-| `STAGE-ESM-043` | `reaction batches atomic` in an admitted version pair | Keep the batch boundary; gap-fill without splitting it |
+| `STAGE-ESM-043` | Atomic shapes the renderer cannot preserve: multiple same-event production triggers or routed direct productions; semantic execution supports atomic batches | Keep the batch boundary; gap-fill refused shapes without splitting it |
 | `STAGE-ESM-044` | A protected read the Cratis renderer cannot preserve faithfully, naming the reason (every protected read before Stage 4.138.0); the legacy Host/structural runner refuse the preamble | Keep protection; gap-fill the refused command; semantic Host/executor support is separate from generated-app enforcement |
-| `STAGE-ESM-047`, `-048` | ESM v27 composite read-model keys: `-048` read model with several key parts or projection keyed by parts (also the legacy syntax engine); `-047` single-instance query by parts | Keep the model; gap-fill the composite-keyed scope |
+| `STAGE-ESM-047`, `-048` | `-048` unsupported composite-key projection shape (legacy syntax refuses composite models); `-047` rendered single-instance lookup by parts. Semantic Host supports composite keys and key-part lookups; specification execution still refuses multi-part keys | Keep the model; check [composite boundaries](current-boundaries.md#renderer-support-is-bounded) |
 | `STAGE-ESM-046` | Compared DateTime concept with compliance or optionality, or a non-camel-case compared DateTime property; older renderers and legacy engines refuse all date comparisons | Keep the date rule and protection; see [date comparisons](date-comparisons.md) |
 | `STAGE-ESM-045` | Non-Error requirement on a protected command, including reaction-invoked commands; semantic admission refuses before reads, requirements or facts | Keep the severity contract; record the execution gap, never silently promote or drop the requirement |
-| `STAGE-IMPL-002` | Described command handler, naming command and RequirementId; also refused in Stub mode | Supply authorized implementation outside rendering; no generated stub is emitted |
-| `STAGE-IMPL-003` | Semantic Host/executor reaches a reducer or command/concept validation body; names owner and RequirementId (Requires Stage 4.145.0; older engines refuse unrelated behavior too) | Keep the body; run unaffected scope separately and gap-fill reached behavior. Renderer admission is unchanged |
+| `STAGE-IMPL-002` | Described command handler, naming command and RequirementId; also refused in Stub mode | Supply authorized implementation outside rendering; no described-body stub is emitted |
+| `STAGE-IMPL-003` | Semantic execution reaches a reducer or command/concept validation body it cannot execute, naming owner and RequirementId | Keep the body; run unaffected scope separately and implement reached gaps |
 | `STAGE-PROFILE-001` to `-006` | Profile input cannot be honored: unknown package, missing layout, incompatible packages, missing theme, invalid root template or unresolved blueprint template | Fix the named input without substituting a different shell. Requires Stage 4.143.0 for shared `CratisRendering.ResolveProfileInputs(scene, approvedPackages)` findings; older consumers may have CLI-only checks |
 | `STAGE-ESM-037` | Events and commands from one handler, even across separate triggers on the same event in one reaction. The scaffold's Arc supports mixed results, but appends events before commands; a refused command causes redelivery and duplicate events | **Do not split the modeled reaction or drop an effect.** Gap-fill only with a proven retry-safe implementation; `[OnceOnly]` excludes replay, not retry |
 | `STAGE-ESM-023` | Information: transition bodies analysed | none |
@@ -264,12 +275,13 @@ Stage renders two projection forms; the restrictions differ.
   Every property it leaves unmapped must be optional, text (not an enum) or a single
   composite object so unrelated instances keep it unset, not a value-type default
   Requires Stage 4.93.0 for this check; older renderers can silently materialize defaults.
-- Refused in a scope (`STAGE-ESM-017`): composite keys; empty/literal `all` mappings;
+- Refused in a scope (`STAGE-ESM-017`): empty/literal `all` mappings;
   unmapped `all` properties outside that nullable subset; `every` with
   children included beside children or nested blocks; root `remove via join`; joins,
   children or join removals inside `nested`; a `clear` inside `nested`; recursive children;
   duplicate event contracts among `from`, join or
   removal blocks; event or read-model property names that collide with Chronicle syntax.
+  Composite-key scope admission is separately bounded in [current boundaries](current-boundaries.md#renderer-support-is-bounded).
 - Running totals: `add`, `subtract`, `increment` and `decrement` start from 0 where nothing was set. `add x by 0`
   (or `subtract x by 0`) on a required plain whole number or decimal only makes the total exist and renders as nothing;
   any other constant operand is refused (Chronicle's `Add` takes an event property), and so is a concept total at zero
@@ -298,15 +310,16 @@ context, no directives, no writes to statics, `throw` limited to
 `InvalidOperationException(string)` or `ArgumentException(string)`, LINQ lambdas that are
 pure expressions, and no generated type shadowing a referenced one. Anything else is
 `STAGE-ESM-019`, `-021` or `-022`. A reducer needs a `StateView` slice, its read model in the
-same slice, a required Guid or text identifier and a matching keyed query. Code validation
-(`STAGE-ESM-005`) is refused outright (opaque pure policies render). Attached
+same slice, a required Guid or text identifier and a matching keyed query. Resolved
+C# command/concept rule and iterator validation bodies have pure-gated render
+paths; unsupported body/context shapes still refuse. Attached
 command handlers refuse `PLAY0800` and permanently require constrained implementation
 attachments: gap-fill in code, not by waiting for ESM admission. Requires Screenplay
 4.210.0 (`screenplay --version`); older bundled binders use PLAY0268 for these handlers.
 Read the required typed `arguments.subject` for the command rather than the message.
-A pending handler beside unconditional
-productions binds as a described v23 command, but Stage refuses it with
-`STAGE-IMPL-002`, even in Stub mode.
+A pending handler beside unconditional productions binds as a described v23
+command; rendering still refuses it with STAGE-IMPL-002 even in Stub mode.
+Query-performer gaps are a separate contract: see [bodies and implementation gaps](current-boundaries.md#bodies-and-implementation-gaps).
 
 ## Specification rules (`STAGE-ESM-011`)
 

package/package/corpus/skills/cratis-stage-rendering-and-sandbox/references/current-boundaries.md

@@ -0,0 +1,119 @@
+<!-- Copyright (c) Cratis. All rights reserved. -->
+<!-- Licensed under the MIT license. See LICENSE file in the project root for full license information. -->
+
+# Stage target boundaries
+
+## Contents
+
+- Version admission
+- Renderer support is bounded
+- Semantic Host and specification execution
+- Bodies and implementation gaps
+- Runtime package and reducer migration
+
+Reviewed against Stage v4.197.0. A compiler accepting a model is not proof that a
+renderer, semantic Host, specification runner or CLI accepts it. The product
+inventory owns the review baseline, not a promise that every construct works.
+
+## Version admission
+
+Stage's renderer and semantic Host/specification path admit matched language and
+semantic pairs **1.0–30.0 and 32.0**, not a continuous 1–32 range. V31 anonymous
+conditions, mismatched and unknown future pairs remain refused. V28 adds UUID
+comparisons; v29 includes decimal rules/projection products; v30 carries per-event
+source routes; v32 typed capture identities must not be lost in conversion.
+
+**CLI v3.100.0** `cratis render` independently admits semantic versions through
+**v30**. Its bundled Stage then applies matched-pair and construct
+gates; **v32 needs a direct caller of the reviewed Stage baseline**. The CLI checks only the semantic
+version, not the pair. Do not relabel a newer model to pass it: use a capable
+reviewed caller or report the CLI blocker. The introducing CLI minimums are in
+[the skill's admission prerequisites](../SKILL.md); the exact bundled Stage is in
+[toolchain target boundaries](../../cratis-screenplay-toolchain/references/language-admission.md#stage-admission-and-execution).
+
+## Renderer support is bounded
+
+- **Translate:** supported inbound `source events` captures render inbox reactors
+  with durable per-key capture state. Added, field-change and transition
+  conditions have explicit support; unsupported capture guards still refuse by
+  name. This does not admit source-less captures, polling/webhook scheduling or a
+  Translate slice mixing commands, read models, queries, reducers or reactions.
+- **Outbound:** supported event-target projections in Translate render public
+  contracts and outbox reactors. Public events produced directly by commands or
+  reactions and unsupported foreign-event uses retain their refusals. Generated
+  Translate specifications exercise the generated handlers, not a real external
+  integration.
+- **Atomic reactions:** event-only production can render one event-collection
+  return per trigger occurrence; a selected invocation-refusal branch is its own
+  batch. Multiple production triggers on the same event and routed direct
+  productions retain `STAGE-ESM-043`. Models without the atomic declaration keep
+  their prior behavior.
+- **Composite keys:** required single non-date primitive/concept parts in a
+  scoped projection with complete event-property parts keys for `from`/`remove
+  with` blocks render. Reducers, flat projections, joins, nested/child blocks,
+  partial keys, collisions and protected live queries over that composite shape
+  remain refused. Single-instance lookup by parts remains `STAGE-ESM-047` even
+  though composite projections and equality-filtered lists can render.
+- **Projection products:** required numeric products in supported root/child
+  `from` blocks can lower through a generated event member. Optional/non-numeric
+  factors and unsupported join/`every` product shapes still refuse
+  `STAGE-ESM-050`. This is distinct from Play's Chronicle-definition conversion,
+  which still refuses a factor rather than silently adding only one operand.
+- **Query UI:** default composition supplies an input form only for an optional
+  snapshot single-result lookup with a Text/UUID argument and an eligible scalar
+  result field. It omits list queries, required/unkeyed single-result queries and
+  unsupported arguments; it is not a general query editor. The form submits exact
+  string arguments; draft editing does not execute the query.
+
+## Semantic Host and specification execution
+
+The semantic path is not generated Chronicle code. Atomic reaction batches run
+with per-unit validation in the specification executor; earlier successful units
+remain after a later failure. The live Host is stricter: it rolls back the whole
+initiating command if any unit fails. Invoked commands remain separate units.
+Legacy syntax execution is a separate capability gate.
+
+Semantic specifications fold admitted composite/collection event values,
+composite projection properties and numeric projection products. Composite-key
+models/key-part lookups work in the live Host; specification execution still
+refuses multi-part keys. Recursive composite types still refuse by name; complete
+given-state seeds are not permission to execute partial/null projected seeds or
+opaque reducers. A projection product absent from the run no longer blocks an
+unrelated specification.
+
+Supported `source events` capture specifications execute added/change/transition
+behavior; outbound projections append public events **locally**. The live
+runtime's `BlockingModelFeatures`/`RunsAround` API explains which translation
+constructs it can run around: foreign facts arrive through seeds and captures do
+not poll external sources. Local public appends are not external publication.
+Unsupported translation shapes still refuse by name.
+
+## Bodies and implementation gaps
+
+Resolved C# command/concept validation bodies can render through typed contexts
+and the pure-code gate; context members such as Tenant/CausedBy/Occurred remain
+refused. The semantic Host/executor does not thereby execute opaque validation or
+reducer bodies: reached unsupported bodies retain scoped `STAGE-IMPL-003`.
+Described command handlers still refuse `STAGE-IMPL-002` in rendering, including
+Stub mode; reaching one in semantic execution reports `ImplementationBody` after
+its gates, rather than blocking unrelated behavior application-wide.
+
+A **query performer** is a different contract. Verified supported C# performer
+bodies can render; unsupported/unverifiable performers produce explicit
+implementation gaps and a not-fully-runnable marker. A generated throwing method
+or gap is not a completed implementation or publication approval. Preserve the
+performer's requirement identity, query shape, authorization and reason; do not
+replace missing behavior with an empty success. The `ImplementationGapMode` enum
+alone does not prove a target supports stubbing another role.
+
+## Runtime package and reducer migration
+
+Generated applications consume `@cratis/stage.runtime` pinned to the rendering
+Stage release, rather than copied frontend runtime files. Re-render existing
+applications to migrate; unchanged copies are removed, while edited copies stop
+the render until resolved. Do not hand-edit managed runtime files or dependencies.
+
+Classic-to-self reducer migration is per read model and preserves the previous
+observer id. It needs version-2 configuration, evidence of the existing reducer,
+a publisher that handles `ArtifactRenderPlan.RequiredRemovals`, and publication
+checks against changed files. A new profile alone is not migration evidence.

package/package/corpus/skills/cratis-stage-rendering-and-sandbox/references/rendered-application.md

@@ -3,6 +3,7 @@
 ## Contents
 
 - Scaffold
+- Runtime package migration
 - Lists on screen
 - Reducer layout for new applications
 - What is managed
@@ -51,6 +52,13 @@ is off), but any override must be proven with a restore and build. The compose f
 `35000`, keeps data in the named volumes `chronicle-data` and `chronicle-config`, and
 `docker compose down --volumes` is the only thing that deletes them.
 
+## Runtime package migration
+
+Stage v4.180.0 and later generate a dependency on `@cratis/stage.runtime`, pinned
+to the rendering Stage release, rather than copied frontend runtime files.
+Re-render existing applications: unchanged old copies are removed; edited copies
+stop the migration until resolved. See [runtime and reducer migration](current-boundaries.md#runtime-package-and-reducer-migration).
+
 ## Lists on screen
 
 A `data <ReadModel>[] via query <Query>` list renders from either list-query mode, but
@@ -145,7 +153,7 @@ Every file is optional. Rules that bite:
 
 What the seam does **not** do: it repairs no rejected model and renders nothing.
 Stage renders supported event-triggered Automation slices as managed Chronicle
-reactors; refused reactions, captures and Translate slices remain hand-written gap-fill
+reactors; bounded source-event capture and outbound Translate paths also render. Refused reaction or Translate shapes remain hand-written gap-fill
 with the model as their contract. See [admission.md](admission.md). Keep `Customizations/` under version control: whether a re-render keeps
 it depends on the publisher, and `cratis render` writes only the planned paths and
 refuses unmanaged files at them.

package/package/corpus/skills/cratis-stage-rendering-and-sandbox/references/sandbox-and-specrunner.md

@@ -160,9 +160,10 @@ which never counts as a pass.
 
 ## Implementation bodies and authored occurrence
 
-Requires Stage 4.145.0 for reach-scoped reducer and validation refusals; older semantic
-engines refuse unrelated behavior when any such body exists. Neither Host nor executor
-runs these bodies. `STAGE-IMPL-003` names the reached owner and RequirementId:
+Requires Stage 4.145.0 for reach-scoped reducer and validation refusals; older
+semantic engines refuse unrelated behavior when any such body exists. Neither
+Host nor executor runs these opaque bodies. `STAGE-IMPL-003` names the reached
+owner and RequirementId. Reachability includes:
 
 - command under test and commands invoked by reactions reach command validation;
 - command input and query argument types reach concept rules through composites,
@@ -173,8 +174,10 @@ runs these bodies. `STAGE-IMPL-003` names the reached owner and RequirementId:
   of an action expected to be refused.
 
 Unrelated commands, queries and specifications remain admitted. Reducer refusals use
-Projection capability; validation refusals use Command. This does not relax live-world
-history rebuilding or renderer admission, nor described-handler `STAGE-IMPL-002`.
+Projection capability; validation refusals use Command. This does not relax
+live-world history rebuilding or renderer admission. Described handlers remain
+refused in rendering even in Stub mode; semantic execution reports
+`ImplementationBody` only when reached after their gates. See [current boundaries](current-boundaries.md).
 
 Requires Stage 4.141.1 for authored occurrence in event-reaction specifications; older
 executors refuse clocks beside reactions. Independent command, append and named-redelivery
@@ -190,19 +193,23 @@ A false `where` skips evaluation; the executor never invents wall time. The fixt
 supplies time, not audit identity: `$eventSourceId`/`$eventContext.eventSourceId` and
 `$context.causedBy.*` remain `STAGE-ESM-013`, even under `runs as system`.
 
-Clock/application/startup/shutdown triggers and `when clock`/trigger/capture actions
-remain `STAGE-ESM-024`. **A clock fixture is not a scheduler.** Generated backend
+Clock/application/startup/shutdown triggers and `when clock`/trigger actions
+remain `STAGE-ESM-024`. Admitted `source events` capture specifications now run;
+this does not execute polling or an external integration.
+**A clock fixture is not a scheduler.** Generated backend
 occurrence mappings use `EventContext.Occurred`, but context-dependent generated
 reaction specs retain `-011`; generated append/redelivery clock fixtures retain `-024`.
 Rendered clock fixtures remain command-only.
 
 ## Refusals shared by both engines
 
-Both engines refuse public events (`STAGE-ESM-032`), foreign or source-event captures
-(`-033`), directed Translate slices (`-024`) and reducer observer filters (`-035`). The
-legacy engine also refuses reaction identity and reaction observer filters (`-034`,
-`-035`); per-production route overrides fail `-036` on the semantic engine. Clock,
-application, startup and shutdown triggers and opaque reaction bodies fail `-024`.
+Semantic capture/publication support is target-specific: supported capture
+specifications run and the live Host can run around public/foreign constructs
+using local appends and seeded inbound facts, never real external publication or
+polling. Unsupported Translate reactive/read-side shapes still refuse. Legacy
+syntax admission retains broader refusals, including reaction identity, observer
+filters and routing (`-034`, `-035`, `-036`). Clock, application, startup and shutdown reaction triggers and opaque
+reaction bodies fail `-024`. See [current boundaries](current-boundaries.md).
 
 ## The specification runner
 

package/package/corpus/skills/cratis-stage-rendering-and-sandbox/references/scene-runtime.md

@@ -51,6 +51,10 @@ The scaffold's Scene runtime provides:
   `component.<id>.<output>` via `resolveArgumentSource`. `useBoundQuery` reruns
   on changed arguments, aborts prior runs and discards stale answers; cleared or
   failed bindings remove the previous data.
+- Stage v4.197.0 default composition adds input forms only for eligible optional
+  snapshot single-result lookups with a Text/UUID argument and scalar result field;
+  it omits collections and required/unkeyed single results. Drafts do not execute
+  queries until submit. See [current target boundaries](current-boundaries.md).
 - `core:toolbar` / `core:toolbarItem`: Action items announce the command and
   resolved parameters with `cratis.scene.command`; Navigate/Dialog items use
   the navigation host, or announce navigation outside one. Host wiring is still

package/package/corpus/skills/cratis-stage-rendering-and-sandbox/verification.json

@@ -24,7 +24,15 @@
     { "kind": "skill-contains", "value": "Requires Cratis CLI 3.64.0 for `--engine`", "file": "references/sandbox-and-specrunner.md" },
     { "kind": "skill-contains", "value": "the environment setting below", "file": "references/sandbox-and-specrunner.md" },
     { "kind": "skill-contains", "value": "fresh in-memory Chronicle log per specification", "file": "references/sandbox-and-specrunner.md" },
-    { "kind": "skill-contains", "value": "exact ESM v1–v27 pairs" },
+    { "kind": "skill-contains", "value": "matched language/ESM 1.0–30.0 and 32.0" },
+    { "kind": "skill-contains", "value": "not a continuous 1–32 range", "file": "references/current-boundaries.md" },
+    { "kind": "skill-contains", "value": "admits semantic versions through\n**v30**", "file": "references/current-boundaries.md" },
+    { "kind": "skill-contains", "value": "CLI checks only the semantic\nversion, not the pair", "file": "references/current-boundaries.md" },
+    { "kind": "skill-contains", "value": "v32 needs a direct caller of the reviewed Stage baseline", "file": "references/current-boundaries.md" },
+    { "kind": "skill-contains", "value": "3.81.0 for v28 and 3.86.0 for v29–v30" },
+    { "kind": "skill-contains", "value": "specification execution still\nrefuses multi-part keys", "file": "references/current-boundaries.md" },
+    { "kind": "skill-contains", "value": "including\nStub mode", "file": "references/current-boundaries.md" },
+    { "kind": "skill-contains", "value": "ArtifactRenderPlan.RequiredRemovals", "file": "references/current-boundaries.md" },
     { "kind": "skill-contains", "value": "Requires Stage 4.141.0", "file": "references/date-comparisons.md" },
     { "kind": "skill-contains", "value": "Requires Stage 4.142.0", "file": "references/sandbox-and-specrunner.md" },
     { "kind": "skill-contains", "value": "STAGE-IMPL-003", "file": "references/sandbox-and-specrunner.md" },

package/package/profile-catalog.json

@@ -1155,6 +1155,18 @@
       "languages": [
         "typescript"
       ]
+    },
+    {
+      "id": "cratis/orchestration",
+      "composes": [
+        "cratis/engineering/core"
+      ],
+      "availableTargets": [
+        "cratis-orchestration-lanes"
+      ],
+      "languages": [
+        "language-agnostic"
+      ]
     }
   ]
 }

package/package.json

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