@cratis/pi 7.75.0 → 7.76.0

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

@@ -0,0 +1,44 @@
+<!-- Copyright (c) Cratis. All rights reserved. -->
+<!-- Licensed under the MIT license. See LICENSE file in the project root for full license information. -->
+
+# Rendering Date and DateTime comparisons
+
+Requires Stage 4.141.0 to render ESM v26 comparisons; older renderers refuse them
+with `STAGE-ESM-046`. Check `cratis --version` and its bundled Stage before rendering;
+a newer standalone Screenplay does not upgrade the CLI renderer.
+
+The Cratis renderer emits comparisons in command `require`, `produces when` and
+command/property validation rules. Date compares calendar days with `DateOnly`;
+DateTime compares UTC instants with `DateTimeOffset` at tick precision, not text
+or millisecond precision. Absence passes validation rules. Date predicates are
+server-side `.Must` rules; no client-side date comparator is extracted.
+
+Every compared DateTime command property carries Arc's `ExplicitOffset` marker:
+input without an offset or `Z` is rejected. A compared DateTime concept binds as
+`DateTimeOffset` and converts back to the concept in events, rules and responses.
+That workaround cannot preserve every shape. `STAGE-ESM-046` names the property for:
+
+- a compared DateTime concept carrying compliance;
+- an optional compared DateTime concept;
+- a compared DateTime property whose name is not camel case.
+
+Keep compliance and optionality: these are gaps, not reasons to change the model.
+Date comparisons from protected-read operands are not rendered. Reaction date
+conditions are not admitted by the language. Legacy engines retain `-046`.
+
+## Input and expectation differences
+
+With a named authorization policy, an unauthorized caller sending an unbindable
+date body receives Validation rather than 403: Arc binds the body before Stage's
+named policy evaluates. Test this boundary; do not claim identical denial ordering.
+Rendered DateTime `then` expectations compare instants, while reference expectations
+remain ordinal text comparisons; the binder requires expected event values to match
+the produced spelling.
+
+## Verify
+
+Run `cratis render <root> --name <App> --destination <out>`, then build and test the
+rendered project in Debug, in separate bounded calls. Admission/publication, build
+and specification outcomes are separate results. Check valid offset inputs,
+offset-less rejections and calendar-day/UTC-instant boundaries; retain any typed
+refusal rather than replacing the comparison with text ordering.

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

@@ -15,6 +15,10 @@ image, Cratis Components, Scene, Fundamentals, Vite and React). The pins belong
 renderer: read them from the rendered `.csproj`, `docker-compose.yml` and `package.json`, never
 from this skill. Moving them is a renderer change, so a re-render
 under a newer Stage is how they change; never bump a managed file.
+Requires Stage 4.144.0 for backend pins derived at build time from Stage's central
+package versions and shared frontend pins following Stage's frontend manifest;
+older renderers use separately maintained scaffold pins. Regeneration updates
+existing applications; it does not float dependencies in an already rendered app.
 
 | Item | Value |
 | --- | --- |
@@ -36,8 +40,10 @@ Consequences: `[ProtectedDecision]` (`Cratis.Arc.Chronicle.ReadModels`) and
 in the scaffold's package set, as is `[ExecuteCommandsAsSystem]`. This is API
 availability, not Stage emission or runtime protection: gap-fill must opt into
 the protected command profile and enroll an admitted projection/key read in the
-active unit of work. The Cratis C# renderer does not turn `.play` `reads`/`require` into protected decisions;
-semantic Host/executor support is separate from generated-application protection.
+active unit of work. Requires Stage 4.138.0 for Cratis C# rendering of admitted
+`.play` protected reads as Arc read protection; older renderers refuse them with
+`STAGE-ESM-044`, as do shapes the renderer cannot preserve. Semantic Host/executor
+support is separate from generated-application protection.
 Hand-written scope that needs a newer dependency can raise its version through
 `Customizations/Dependencies.props` (explicit `Version`, imported last; central management
 is off), but any override must be proven with a restore and build. The compose file binds local ports `27017` and

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

@@ -5,6 +5,7 @@
 - The sandbox: a partial, disposable runtime
 - Protected command reads
 - Date comparisons (v26)
+- Implementation bodies and authored occurrence
 - Refusals shared by both engines
 - The specification runner
 - Choosing between them
@@ -124,10 +125,20 @@ execution. This includes reaction-invoked commands, even a specification expecti
 rejection: the outcome is `Unsupported`, before seeding facts, not a passing refusal.
 Do not change modeled severity to get an executable result.
 
-The semantic Host faults the session on **any outside append** to its event log,
-even an unrelated one, before committing an accepted command. This interim guard
-is stricter than the reference's dependency-scoped decide/commit conflicts; do not
-claim full reference conflict parity or generated-application protection.
+Requires Stage 4.142.0 for decide/commit against outside facts; older Hosts fault
+on any outside append. The Host decides on the session world, reads the outside
+suffix and commits against the extended world. A later fact matching a protected
+read's key and event contracts causes a concurrency conflict without faulting the
+session; unrelated facts remain for commit-time constraints and projections.
+Outside facts do not fire reactions again. Refusals retain their outcome.
+
+The root/reaction batch uses one guarded write against the durable pre-batch tail,
+even for a successful empty batch. A definitive guard loss may retry the same
+decision, preserving generated values, only when settlement invoked no commands.
+An invocation or eight unsuccessful attempts returns a conflict. An unknown write
+outcome or unreadable/unsupported outside history faults the session, never retries
+as success. Legacy custom appenders without these capabilities retain conservative
+checks. These are Host guarantees, not generated-application evidence.
 
 ## Date comparisons (v26)
 
@@ -136,14 +147,54 @@ The semantic Host and specification executor compare `Date` as calendar days and
 `DateTime` as UTC ticks in `require`, `produces when` and validation rules, including
 through concepts. A participating `DateTime` input without an offset or `Z` rejects
 with Validation after authorization and before any rule. `then` stays ordinal. The
-renderer, legacy engines and default sandbox engine refuse these comparisons with
-`STAGE-ESM-046`, naming the property; no date validators or artifacts are emitted.
+Cratis renderer renders these comparisons from Stage 4.141.0; older renderers and
+legacy engines refuse `STAGE-ESM-046`. Read [date comparisons](date-comparisons.md)
+when checking remaining renderer refusals and input-binding differences.
 
 One ordering differs from the reference: the reference checks authorization, then
 offsets, then opaque C# validation, so an offset-less DateTime beside opaque
 validation is a Validation rejection there. The specification executor refuses opaque
-validation at run admission and the Host refuses it before authorization, so both Stage
-paths report `Unsupported`, which never counts as a pass.
+validation when reached at specification admission and the Host refuses a command
+that reaches it before authorization, so both Stage paths report `Unsupported`,
+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:
+
+- command under test and commands invoked by reactions reach command validation;
+- command input and query argument types reach concept rules through composites,
+  collections and optionals;
+- given, appended or produced events reach reducer transitions; read-model assertions
+  and queries reach the corresponding reducer too;
+- potential reaction effects are included without evaluating guards, including effects
+  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`.
+
+Requires Stage 4.141.1 for authored occurrence in event-reaction specifications; older
+executors refuse clocks beside reactions. Independent command, append and named-redelivery
+specifications accept `given clock` at or after the Unix epoch in whole milliseconds.
+Offset-bearing source clocks normalize to UTC; the same instant reaches direct/cascading
+productions, invocation arguments, invoked commands and refusal productions. Redelivery
+uses the scenario clock, not the given event's timestamp.
+
+No authored clock means no reaction occurrence: a reached production using
+`$context.occurred` rejects with `Reaction '<name>' uses $context, which needs the scenario's 'given clock'.`;
+an invocation argument instead rejects as unresolved in its declared root scope.
+A false `where` skips evaluation; the executor never invents wall time. The fixture
+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
+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
 

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

@@ -19,12 +19,16 @@
     { "kind": "skill-contains", "value": "**Render never builds, tests or runs**" },
     { "kind": "skill-contains", "value": "`[ProtectedDecision]`" },
     { "kind": "skill-contains", "value": "`Customizations/`" },
-    { "kind": "skill-contains", "value": "`Stage__Runtime__Engine=semantic`" },
-    { "kind": "skill-contains", "value": "`--engine semantic`" },
+    { "kind": "skill-contains", "value": "`Stage__Runtime__Engine=semantic`", "file": "references/sandbox-and-specrunner.md" },
+    { "kind": "skill-contains", "value": "`--engine semantic`", "file": "references/sandbox-and-specrunner.md" },
     { "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–v21 and v23–v27 pairs" },
+    { "kind": "skill-contains", "value": "exact ESM v1–v27 pairs" },
+    { "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" },
+    { "kind": "skill-contains", "value": "Requires Stage 4.146.0" },
     { "kind": "skill-contains", "value": "STAGE-ESM-044" },
     { "kind": "skill-contains", "value": "STAGE-IMPL-002" },
     { "kind": "skill-contains", "value": "all-Proven rules permit unpinned rendered", "file": "references/admission.md" },

package/package.json

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