@cratis/pi 7.31.0 → 7.33.0

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

@@ -13,6 +13,7 @@
 - Identity, compliance and processing views
 - Evidence-pinned production repairs
 - Scoped diagnostics and completeness
+- Property-reference evidence
 - Dependencies and intent inventories
 - Specification obligations and advisory smells
 - Semantic revision comparison
@@ -37,9 +38,9 @@ report unsupported adapters or drift.
 
 After `initialize` and `notifications/initialized`, discover current tools and
 argument schemas with `tools/list`; do not hard-code counts or infer arguments
-from these short descriptions. Screenplay v4.131.0's `McpToolCatalog.cs` has
-37 tools without visualization, 38 with it; older issue counts are not this release.
-The additions below follow its `Documentation/screenplay/mcp/reference.md`.
+from these short descriptions. Additions follow the released
+`Documentation/screenplay/mcp/reference.md`; historical tool counts are not
+current capability evidence.
 The connection procedure, edit routes, identity state and failure handling are in
 the [MCP loop](mcp-loop.md).
 
@@ -50,7 +51,7 @@ the [MCP loop](mcp-loop.md).
 | Source and validation | `diagnostics`, `read-document`, `merged-document`, `syntax-schema` | Read exact source or typed structure and diagnose problems |
 | Workspace inspection | `open-workspace`, `read-workspace`, `read-ast`, `workspace-state`, `export-workspace`, `repair-capabilities` | Obtain current identities, handles, readiness, code attachment requirements, source-map locations, durable-state status and the repair catalog |
 | Visual (MCP-Apps hosts only) | `visualize-model` | Draw the board for the model or a `proposalId`; its `sketch` argument previews a what-if of whole documents. Reads only |
-| Planning | `propose-source`, `propose-ast`, `propose-rename`, `propose-repair`, `propose-extract-inline-event`, `propose`, `recommend-layout`, `expand-layout` | Produce validated, reviewable candidates without writing them |
+| Planning | `propose-source`, `propose-ast`, `propose-rename`, `propose-repair`, `propose-number-enum-members`, `propose-extract-inline-event`, `propose`, `recommend-layout`, `expand-layout` | Produce validated, reviewable candidates without writing them |
 | Review | `read-proposal`, `discard-proposal` | Inspect exact changes, dropped comments and proposed attachments, or abandon a connection-local proposal |
 | Effects | `apply`, `recover-workspace` | Apply an accepted plan or explicitly recover an interrupted write |
 
@@ -146,6 +147,24 @@ then explicitly confirm Apply. Dirty/untitled buffers and evidence drift refuse;
 uncertain Apply outcomes are never retried. Restricted Mode cannot launch it.
 Monaco has no production-repair host bridge. See v4.125.0 `vscode.md`.
 
+### Number enum members (4.137.0)
+
+Find the unnumbered enum's `ConceptSyntax` handle with `read-ast`; pass it as
+`subject` to `propose-number-enum-members` with `expectedRevision`,
+`expectedCatalogRevision` and `formatting: "CanonicalizeTouchedDocuments"`.
+Optional `validation` and `includeContent` follow ordinary proposals. It writes
+`= 0..n-1` in current order, never renumbers numbered/mixed/invalid enums, and
+requires retained comments/catalog assignments and unchanged executable bytes
+when the original binds. Review with `read-proposal`, then `apply` with before
+revisions; proposing writes nothing. Positional pins preserve executable version,
+bytes and revision. Non-positional numbers require v12 (4.139.0) consumer admission.
+
+Opt into `diagnostics` `checks: "enum-pinning"` (or `PLAY0671` or `all`) for an
+Information hint on unnumbered enums used by event properties, including composite
+uses. Ordinary compilation does not report it. This is a refactoring, not a
+correctness repair; PLAY0667–0670 require an author decision, with no automatic repair.
+Source: `v4.139.0:Documentation/screenplay/mcp/authoring-tools.md`.
+
 ## Syntax-only constructs through the MCP
 
 The 4.66.0/4.68.0 negative probes below are historical. At 4.125.0,
@@ -190,9 +209,8 @@ persona/policy and table/case/caseParameter provenance. Neither view executes.
 ## Identity, compliance and processing views
 
 Screenplay v4.127.0 `mcp/reference.md` and `authoring-tools.md` describe these
-additions (checked at 4.127.0); discover installed schemas because current
-Previous CLI 3.46.1 bundled Screenplay 4.130.0; CLI 3.50.0 bundles
-4.131.0, so these source objects are available there too.
+additions (checked at 4.127.0). Discover installed schemas; current compiler
+and bundle pins are in `cratis-screenplay-toolchain/references/versions.md`.
 
 - Identity/detail summaries expose declared sources; `$identity` has its own
   expression node. The block alone stays executable-ready, but executable reads
@@ -248,6 +266,15 @@ They opt into findings, not execution proof. Whole-source errors skip them; repo
 `completenessStatus` as skipped, never passed. `completenessCoverage` states their
 limits. Continue with `expectedSourceRevision`.
 
+## Property-reference evidence
+
+From 4.138.0, `find-references` and `dependencies` accept `kind: "Property"`
+and `Owner.member`, or historical event `Owner.generationN.member`. Before a
+rename/removal, read [property links](property-links.md) for exact query/result
+shapes, roles, direct counterpart traversal, revision paging and `complete: false`
+with `reasons`. Incomplete evidence is never a successful empty list. These tools
+inspect authored links, not code execution or a transitive runtime graph.
+
 ## Dependencies and intent inventories
 
 `dependency-graph` edges point consumer → producer. Views: `edges`, `cycles`,
@@ -326,7 +353,8 @@ the open model as candidate:
 }
 ```
 
-These source objects require Screenplay 4.131.0; CLI 3.50.0 bundles it
+These source objects require Screenplay 4.131.0; compare the bundled compiler
+in `cratis-screenplay-toolchain/references/versions.md` with that minimum
 (previous CLI 3.46.1 bundled 4.130.0).
 Discover installed schemas rather than assuming bundle parity.
 Check that the registered worktree is checked out at the intended commit and

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

@@ -0,0 +1,126 @@
+<!-- Copyright (c) Cratis. All rights reserved. -->
+<!-- Licensed under the MIT license. See LICENSE file in the project root for full license information. -->
+
+# Inspect a property's chain before changing it
+
+## Contents
+
+- Address and query
+- Read evidence, not just a count
+
+Screenplay 4.138.0 released property-path evidence in `find-references` and
+`dependencies`; this guidance was checked against 4.139.0. Discover installed
+`tools/list`: CLI 3.53.1's 4.137.0 bundle predates it. These are read-only
+inspection tools, not a property-change planner.
+
+## Address and query
+
+Use `kind: "Property"`, case-sensitive. Append the member to its owner's exact
+logical address: `Owner.member`. For an event this selects the current generation;
+`Owner.generationN.member` selects a historical shape, whose target details carry
+`historical: true`. Properties are not returned in declaration listings: locate
+the owner and inspect its properties first.
+
+On the command-surface [enum example](../../cratis-screenplay-command-surface/references/enum-numbers.md),
+first inspect the event with `find-references`:
+
+```json
+{
+  "address": "Invoicing.Issuing.SendingInvoice.InvoiceSent",
+  "kind": "Event"
+}
+```
+
+At 4.139.0 this returns two references (`produces`, `thenEvent`), with top-level
+`totalCount: 2`, `references` and empty `ambiguous`, `incomplete`, `wrongKind`
+arrays. The event response has no `complete` field. Query its property separately:
+
+```json
+{
+  "address": "Invoicing.Issuing.SendingInvoice.InvoiceSent.status",
+  "kind": "Property"
+}
+```
+
+Then query direct mapping counterparts with `dependencies`:
+
+```json
+{
+  "address": "Invoicing.Issuing.SendingInvoice.InvoiceSent.status",
+  "kind": "Property",
+  "direction": "outgoing"
+}
+```
+
+Both tools accept `offset`, `limit` and `expectedSourceRevision`; echo the first
+response's `sourceRevision` on continuation pages. `dependencies` additionally
+accepts `direction: "incoming"` (default), `descendants` and `document`. It follows
+**direct mapping counterparts only**, not a transitive property chain or runtime
+impact. Query each resolved counterpart separately when walking a longer chain.
+
+## Read evidence, not just a count
+
+`find-references` returns top-level `references`, `ambiguous`, `incomplete`,
+`complete`, `totalCount`, `offset`, `nextOffset` and `coverage`. Ambiguous/incomplete
+rows contain `reference` and `candidates`. `dependencies` instead has
+`page.items`, each carrying `reference`, `resolution` and `targets`, with paging
+inside `page`; `complete` and `coverage` stay at the top level.
+
+Each property reference retains `owner`, `location`, `role`, `reasons` and
+`otherEnd` (the link's resolved other end, or null). For outgoing dependencies,
+navigate `targets`, not an assumed interpretation of `otherEnd`. Evidence roles are:
+
+| Role | Meaning |
+| --- | --- |
+| `mapping-source`, `mapping-target` | Explicit production, capture append or projection mapping end |
+| `automap` | Derived case-insensitive projection link |
+| `condition` | Declarative condition, including query filters and policy readers |
+| `key` | Lookup/read, projection/join/removal/parent, constraint or stream-id key |
+| `screen-binding` | Screen/form field use |
+| `fixture`, `assertion` | Specification/example assignment or expected value |
+| `response` | Command response property source |
+| `opaque` | Text names the property; code is not resolved |
+| `unclassified` | Conservative backstop found a name occurrence outside classified links |
+
+### Observed result on the compiled example (4.139.0)
+
+The property `find-references` response has `success: true`, `complete: false`,
+`totalCount: 3`, `nextOffset: null`: two resolved references (`mapping-target`
+on the command's `status = status`, and `assertion` on `then InvoiceSent`),
+and one `incomplete` entry. Its `reference.role` is `unclassified`, located at the
+specification's command-input `status` assignment, with `reference.reasons`:
+
+```json
+["Property name occurs in referencing declaration text without a classified link."]
+```
+
+Outgoing `dependencies` also reports `success: true`, `complete: false` and
+`page.totalCount: 1`. Its resolved `page.items[0]` has a `mapping-source`
+reference; `targets[0].address` is
+`Invoicing.Issuing.SendingInvoice.SendInvoice.status`, while the reference's
+`otherEnd.address` is the queried event property. The property's completeness
+covers all indexed evidence even when the chosen direction's page has only a
+resolved link. The workspace had `sourceSuccess: true`, no source diagnostics
+and `readiness.executableReady: true`: compilation success does not imply
+complete property evidence.
+
+**`complete: false` is never a successful empty list.** Inspect every ambiguous
+or incomplete row and its `reasons`/candidates, even when resolved `references`
+is empty. `success` describes compilation, not completeness. Opaque occurrences,
+unresolved counterparts, nested composite paths, legacy command reads and external
+source items can leave incomplete evidence. The backstop counts whole-word names
+case-insensitively in relevant typed source and comments, including quoted text;
+same-named properties in unrelated declarations do not affect completeness.
+External code contents and registrations remain outside coverage even with
+`complete: true`; authored links do not prove executable admission.
+
+Before a rename/removal: pin the revision, inspect incoming readers and outgoing
+counterparts, page to completion, resolve uncertainties, then choose the supported
+identity-safe edit route with the connection owner. Never infer safe deletion from
+zero resolved hits or edit every same-named field. An event-property change still
+needs a persisted-contract evolution decision; the catalog is not storage evidence.
+
+Source/output authority: `v4.139.0:Documentation/screenplay/mcp/reference.md`
+(property links), `Source/DotNET/Screenplay.Mcp/McpPropertyDependencies.cs`,
+`McpToolSchemas.cs`, and decision 0044's released prerequisite index. The planner
+phases in that decision are not release evidence.

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

@@ -148,10 +148,9 @@ Historical verified public vector and executable checks:
   `cratis/stage:4.52.0` and which bundled Screenplay 4.127.0. Published since,
   and not verified by this vector: Scene 4.17.0, Screenplay 4.133.1, Stage 4.64.0,
   previous CLI 3.46.1 (bundling Screenplay 4.130.0, then-default Stage 4.52.0) and
-  Studio 0.152.2. Current pins are CLI 3.50.0 (Screenplay 4.131.0 / Stage 4.67.0)
-  and standalone Screenplay 4.135.0; see toolchain `references/versions.md`.
-  Compiler claims from this `cratis` probe are 4.127.0 claims, not current CLI
-  3.50.0/Screenplay 4.131.0 claims;
+  Studio 0.152.2. Current pins: `cratis-screenplay-toolchain/references/versions.md`.
+  Compiler claims from this `cratis` probe are 4.127.0 claims, not current
+  bundled-compiler claims;
 - fixture root: `Source/DotNET/Screenplay.CanonicalCorpus/Corpus/ScreenComposition/v1/source/folder`
   in the Screenplay repository;
 - Screenplay repo tool (available checkout): `dotnet run --project Source/DotNET/Tool

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

@@ -6,7 +6,7 @@
     { "kind": "play-compiles" },
     {
       "kind": "skill-contains",
-      "value": "Screenplay v4.135.0"
+      "value": "Screenplay v4.139.0"
     },
     {
       "kind": "skill-contains",

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

@@ -31,7 +31,7 @@ adapted to `.play` declarations (`references/provenance.md`).
 |---|---|---|
 | Screenplay | `v4.66.0` (`c89198b`) | MCP catalog (29 tools: `describe-application`, `search-declarations`, `dependencies`, `find-assertion-gaps`, `read-workspace`, `declaration-details`) in `Source/DotNET/Screenplay.Mcp/McpToolCatalog.cs`; diagnostics PLAY0029, PLAY0191, PLAY0268, PLAY0271, PLAY0350, PLAY0381, PLAY0469 in `Source/DotNET/Screenplay/Diagnostics/DiagnosticCodes.cs`; decision 0008 (one data subject per event) |
 | Screenplay | `v4.127.0` | `find-specification-obligations` (SPEC001–SPEC008 authored presence), `find-modeling-smells` (SMELL001–SMELL005 advisory questions); neither proves executed behavior or complete lineage |
-| Screenplay | `v4.131.0` | `semantic-diff` source objects and revision-pinned pages: `Source/DotNET/Screenplay.Mcp/{McpRevisionDiff,McpWorkspaces.Comparison,McpToolCatalog}.cs`, `Documentation/screenplay/mcp/reference.md`; previous CLI 3.46.1 predates these; CLI 3.50.0 bundles them |
+| Screenplay | `v4.131.0` | `semantic-diff` source objects and revision-pinned pages: `Source/DotNET/Screenplay.Mcp/{McpRevisionDiff,McpWorkspaces.Comparison,McpToolCatalog}.cs`, `Documentation/screenplay/mcp/reference.md`; previous CLI 3.46.1 predates these; see pin table below |
 | cratis CLI | `v3.28.3` | bundles Screenplay 4.66.0 and Stage 4.24.2; see the toolchain skill |
 
 The full pin table lives in `cratis-screenplay-toolchain` `references/versions.md`; do not copy

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

@@ -25,9 +25,9 @@ Version pins live once in `cratis-screenplay-toolchain` `references/versions.md`
 
 | Source | Pin | Used for |
 | --- | --- | --- |
-| cratis CLI | `3.50.0` (`v3.50.0`) | Source-checked `Directory.Packages.props`: Stage 4.67.0, Screenplay 4.131.0, `Cratis.Arc.Screenplay` 22.54.0, Chronicle 19.32.0, Fundamentals 7.22.8; default runtime image `cratis/stage:4.67.0`. Previous CLI 3.46.1 used Stage 4.52.0/Screenplay 4.130.0. No new render/browser probe. UI-profile rejection (`CLI-RENDER-007` to `CLI-RENDER-010`) and render-then-recover shipped in 3.41.0 (Cratis/cli#301). Historical screens release vector: 3.40.7 (`af9f18e`) with `cratis/stage:4.51.1`. Reading baselines: 3.40.3, 3.39.0 and 3.28.3 (`8b43fef`) |
-| Stage | `4.67.0` (CLI 3.50.0 default) | Source-checked, not executed as a new vector. Previous Stage 4.52.0 was executed on CLI 3.43.0. Admission (`STAGE-ESM-*`, and `PLAY0268` render refusals surfaced by the CLI), ownership manifest, `Customizations/` seams, Debug-only specifications, guarded actions (`STAGE-SCENE-ACTION-001`) and interactions (`STAGE-SCENE-INTERACTION-001`) were source-checked at 4.51.3. Older baselines: 4.49.5, 4.43.0 and `v4.24.2` (`32dcac4`) |
-| Screenplay | bundled `4.131.0`; standalone `4.135.0` | Standalone compiler for V1 to V3; binding codes `PLAY0268` and code-attachment rules were read at `v4.66.0`. Historical CLI 3.41.0 probes used bundled 4.114.0; current `cratis` compiler claims require checking 4.131.0 |
+| cratis CLI | See `cratis-screenplay-toolchain/references/versions.md` | Historical source check at `v3.50.0:Directory.Packages.props`: Stage 4.67.0, Screenplay 4.131.0, `Cratis.Arc.Screenplay` 22.54.0, Chronicle 19.32.0, Fundamentals 7.22.8; default runtime image `cratis/stage:4.67.0`. Previous CLI 3.46.1 used Stage 4.52.0/Screenplay 4.130.0. No new render/browser probe. UI-profile rejection (`CLI-RENDER-007` to `CLI-RENDER-010`) and render-then-recover shipped in 3.41.0 (Cratis/cli#301). Historical screens release vector: 3.40.7 (`af9f18e`) with `cratis/stage:4.51.1`. Reading baselines: 3.40.3, 3.39.0 and 3.28.3 (`8b43fef`) |
+| Stage | See `cratis-screenplay-toolchain/references/versions.md` | Historical source check: 4.67.0 under CLI 3.50.0, not executed as a new vector. Previous Stage 4.52.0 was executed on CLI 3.43.0. Admission (`STAGE-ESM-*`, and `PLAY0268` render refusals surfaced by the CLI), ownership manifest, `Customizations/` seams, Debug-only specifications, guarded actions (`STAGE-SCENE-ACTION-001`) and interactions (`STAGE-SCENE-INTERACTION-001`) were source-checked at 4.51.3. Older baselines: 4.49.5, 4.43.0 and `v4.24.2` (`32dcac4`) |
+| Screenplay | See `cratis-screenplay-toolchain/references/versions.md` | Standalone compiler for V1 to V3; binding codes `PLAY0268` and code-attachment rules were read at `v4.66.0`. Historical CLI 3.41.0 probes used bundled 4.114.0; check the pinned bundled compiler before making `cratis` claims |
 | Rendered apps (historical check) | Arc `22.50.5`, Chronicle `19.32.0`, Scene packages | Stage 4.51.3 scaffold; `[ProtectedDecision]` / `DecisionRead<T>` available to gap-fill, not emitted enforcement. Embedded reverse extraction disabled; verify generated packages before claiming exact Scene runtime parity |
 
 Historical facts retain their checked tags; current pins are source-checked, not new runtime probes.
@@ -77,8 +77,9 @@ the model, hand-write the command and its response with the model (and its fixtu
 specifications) as the contract, and report V3 from the standalone tool and V5 as `not run: no render`.
 
 Models with event sources, streams or command routes bind and reference-execute as ESM v8 on standalone
-Screenplay 4.125.0, so report V3 and V4 from that tool. Previous CLI 3.46.1 refused above v7 with CLI-RENDER-004. Current CLI 3.50.0/Stage
-4.67.0 reaches v8 route checks and construct admission through v10. Public publication,
+Screenplay 4.125.0, so report V3 and V4 from that tool. Previous CLI 3.46.1 refused above v7 with CLI-RENDER-004. The pinned CLI/Stage pair
+(`cratis-screenplay-toolchain/references/versions.md`) reaches v8 route checks
+and construct admission through v10. Public publication,
 foreign events/event captures and v10 reaction identity/filters/production overrides
 still receive typed refusals; reducer filters render. Keep refused scope as case A/C,
 never infer target support from binding. Read Stage's `references/admission.md` and

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

@@ -77,8 +77,8 @@ not bind a modeled reaction or capture. Case C (no generated application): there
 composition conventions (`rules/vertical-slices.md`, `cratis-chronicle-reactor`).
 Declare the trusted actor with reaction `runs as system role "<Role>"`
 (standalone 4.125.0, ESM v10); `given caller` is not an invocation actor.
-Historical CLI 3.41.0's older compiler rejected the syntax. CLI 3.50.0/Stage 4.67.0
-reaches v10 construct admission but still refuses reaction identity
+Historical CLI 3.41.0's older compiler rejected the syntax. The pinned CLI/Stage pair
+(`cratis-screenplay-toolchain/references/versions.md`) reaches v10 construct admission but still refuses reaction identity
 (STAGE-ESM-034); previous CLI 3.46.1 admitted through v7 only. Gap-fill retains the declared role and uses Arc
 `[ExecuteCommandsAsSystem]` for returned commands. Checked model and diagnostics:
 captures-and-reactions `references/invocation-identity.md`.

package/package/corpus/skills/cratis-screenplay-scenario-coverage/references/spec-forms-by-mode.md

@@ -4,8 +4,8 @@ The subsets themselves (what binds, what renders) are owned by `cratis-screenpla
 (its executable and renderable subset references); version facts by its `references/versions.md`. This file
 says what that means for writing specs. A form outside the chosen mode is never deleted from a
 design model: keep it and record the gap. The detailed Stage 4.24.x rows below
-retain historical admission evidence; current pins are standalone Screenplay
-4.135.0 / CLI 3.50.0 (Screenplay 4.131.0 / Stage 4.67.0). Run actual target admission instead of assuming old restrictions carry over.
+retain historical admission evidence; current pins are in
+`cratis-screenplay-toolchain/references/versions.md`. Run actual target admission instead of assuming old restrictions carry over.
 Typed example/override forms: `cratis-screenplay-specifications`
 `references/examples-and-routes.md`.
 
@@ -23,7 +23,7 @@ Typed example/override forms: `cratis-screenplay-specifications`
 | Command spec listing reaction cascade events | yes (v6 semantics) | false PLAY0285 on a cratis before 3.28.2 bundle only; see SKILL.md "Version skew" | no (no reactions) |
 | `generated <name> = <value>` under `when`, `then returns` (ESM v7) | yes | yes on standalone Screenplay 4.68.0 or later; not on the 4.66.0 bundled in cratis 3.28.x (`PLAY0268`) | historically no at Stage 4.24.x; check current target admission |
 | `then events in any order` | yes | yes | yes |
-| Event `stream` / `no stream`, typed `for` and stream ids | yes | ESM v8 at 4.125.0 | CLI 3.50.0 reaches Stage route checks; routed read-model/query replay can still refuse STAGE-ESM-030 |
+| Event `stream` / `no stream`, typed `for` and stream ids | yes | ESM v8 at 4.125.0 | The pinned CLI reaches Stage route checks (toolchain `references/versions.md`); routed read-model/query replay can still refuse STAGE-ESM-030 |
 | Typed examples and overrides | yes | expanded and type-checked before binding; required fields remain required | depends on expanded contract, not fixture reuse |
 | `given operation ... fails`, `then operation`, `then compensated` | yes | unadmitted PLAY0268 | gap-fill |
 | Refusal branches, `when redelivered`, `then no events` | yes | unadmitted PLAY0268 | gap-fill |

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

@@ -280,7 +280,7 @@ For view specifications:
 ## Verify
 
 - [ ] Validate the complete root with warnings as errors, naming tool/version.
-      Current standalone pin: 4.135.0. Run specification examples through
+      Standalone pin: `cratis-screenplay-toolchain/references/versions.md`. Run specification examples through
       `screenplay test`; expected unadmitted syntax reports unbound, not passed.
 - [ ] Executable diagnostics are clean too: `PLAY0350`, `PLAY0352`, `PLAY0388`,
       `PLAY0389` and `PLAY0273` are only reported at binding.

package/package/corpus/skills/cratis-screenplay-specifications/references/examples-and-routes.md

@@ -94,8 +94,8 @@ so UUID casing is immaterial. Composite mappings supply each named part once,
 using literals only; encoding escapes `%`/`|` and preserves declaration order.
 Source: v4.127.0 `event-sources.md`, `specifications.md`, `diagnostics.md`.
 
-Previous CLI 3.46.1 refused above v7; CLI 3.50.0/Stage 4.67.0 reaches route
-checks through v10. Routed read-model/query replay can still refuse
+Previous CLI 3.46.1 refused above v7; the pinned CLI/Stage pair
+(`cratis-screenplay-toolchain/references/versions.md`) reaches route checks through v10. Routed read-model/query replay can still refuse
 STAGE-ESM-030. Source/reference success never establishes target parity.
 
 Command and read-model examples refuse routes (PLAY0526). Effective role and

package/package/corpus/skills/cratis-screenplay-streams-and-consistency/SKILL.md

@@ -88,7 +88,7 @@ option, mark it `ASSUMED` in the slice or module `documentation` and in the sess
    namespace, process-stream routing and concurrency scope apart
    (`references/chronicle-boundaries.md`). Declared `eventsource`/`stream`/`streamId` and
    command/specification routes bind and reference-execute as ESM v8 on 4.125.0.
-   CLI 3.50.0 reaches Stage construct checks through v10; keep the routing
+   The pinned CLI (toolchain `references/versions.md`) reaches Stage construct checks through v10; keep the routing
    contract when target admission requires gap-fill. Forms/boundaries:
    toolchain `references/sources-and-streams.md`. A `generated identifier` (ESM v7, standalone 4.68.0; not rendered by Stage yet) is
    generated fresh on every acceptance: it is not a retry identity, and generated values give no
@@ -128,7 +128,10 @@ option, mark it `ASSUMED` in the slice or module `documentation` and in the sess
    `references/compliance.md` for allowed types and the policy/encryption distinction.
 5. **Plan evolution** with `references/evolution.md`: classify each event change (additive,
    meaning change, rename, removal, split or merge) and write its compatibility scenarios before
-   editing. Renames and other identity-affecting edits are made by the identity owner (the
+   editing. Pin persisted/public enum member numbers before reordering or removing
+   members; never renumber or reuse a published number. Positional pins preserve
+   executable bytes; non-positional pins need ESM v12 consumer admission.
+   Renames and other identity-affecting edits are made by the identity owner (the
    identity procedure in `cratis-screenplay-modeling-lifecycle`).
 6. **Test ownership and interfaces** with `references/boundaries.md`: ownership interview,
    interface and processor inventory, one real interaction walked across each boundary, coupling

package/package/corpus/skills/cratis-screenplay-streams-and-consistency/references/evolution.md

@@ -27,6 +27,23 @@ compatibility scenarios below first; the identity owner then applies the change
 A test for "generation or new event": a new version must be convertible from the old one
 without inventing facts. If it is not, it is a different event.
 
+## Enum identities are stored contracts
+
+Unnumbered enums use zero-based declaration positions: a reorder or insertion can
+reinterpret stored numbers. Before reordering or removing members, pin each to its
+**existing stored number**, not its new position. `propose-number-enum-members`
+pins an unnumbered enum to current positions; use it before changing order, only
+when those positions match storage. Never renumber or reuse a published member's
+number. Removing a member still needs replay and mixed-reader compatibility decisions.
+
+Numbered members may have sparse or negative unique int32 values, all or none per
+enum. Source authoring shipped in 4.137.0; non-positional numbers bind as ESM v12
+in 4.139.0. Positional pins retain older executable bytes/version. CLI 3.53.1 and
+Stage 4.73.1 bundle 4.137.0 and do not admit v12; keep the pins and report the gap.
+Short-lived input/view-only enums may remain positional. Use opt-in
+`--check enum-pinning` (PLAY0671) to find unnumbered enums used by event properties.
+Syntax/example and source evidence: command-surface [enum numbers](../../cratis-screenplay-command-surface/references/enum-numbers.md).
+
 ## Compatibility scenarios (write before editing)
 For each changed event, answer in the slice `documentation` or `STATE.md`:
 1. **Replay**: does every projection still build from generation 1 facts? Which value do old

package/package/corpus/skills/cratis-screenplay-streams-and-consistency/references/stream-patterns.md

@@ -216,7 +216,7 @@ Some event stores decide consistency by a query over tagged events instead of on
 check to event types, source type or stream (`concurrency` block, Screenplay
 `commands.md`). Legacy concurrency metadata still fails binding (PLAY0271),
 but sources/streams/routes bind and reference-execute as ESM v8 on 4.125.0.
-Route admission does not make a view read protected. CLI 3.50.0 reaches Stage construct checks
+Route admission does not make a view read protected. The pinned CLI (toolchain `references/versions.md`) reaches Stage construct checks
 through v10; see toolchain `references/versions.md`. Model the stream by business
 identity; when a rule truly needs a cross-stream decision, record it (see
 `consistency-and-concurrency.md`) rather than inventing a construct.

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

@@ -22,16 +22,16 @@ files is one application: always check the folder, never one file of it.
 
 When choosing or upgrading a tool, or checking version-specific capabilities, read `references/versions.md`; it is the only version table, and other skills point to it. For exact diagnostic codes, MCP names/parameters and standalone CLI options, search the large published [references/screenplay-contract.json](references/screenplay-contract.json), pinned by [references/screenplay-contract.version](references/screenplay-contract.version), rather than loading it in full. Locate a diagnostic by its exact `code` (for example `"code": "PLAY0029"`), a tool by its exact `name` (for example `"name": "read-workspace"`), or a command in `cliCommands`; read the matched object for retirement, parameters or options. [references/screenplay-contract-exceptions.json](references/screenplay-contract-exceptions.json) records reasoned exceptions for historical statements; it does not change the current contract.
 
-The standalone pin is Screenplay 4.135.0. CLI 3.50.0 bundles Screenplay 4.131.0,
-Stage 4.67.0 and Cratis.Arc.Screenplay 22.54.0. The single version table records
+The standalone pin is Screenplay 4.139.0.
+CLI and bundled package pins: `references/versions.md`. The single version table records
 released source evidence and historical probes separately; do not relabel an old
 render/browser result as a probe of the current packages.
 
 Historical screens-release evidence: CLI 3.40.7 / Stage 4.51.1 / bundled
 Screenplay 4.114.0 opened the canonical corpus with `executableReady true`
 and the stdio transcript exposed 37 tools; standalone language 4.122.0 was
-recorded in that vector. These retained results are not a rerun on CLI 3.50.0
-or Screenplay 4.135.0.
+recorded in that vector. These retained results are not a rerun on CLI 3.53.1
+or Screenplay 4.139.0.
 
 ## Ground rules
 
@@ -67,7 +67,7 @@ or Screenplay 4.135.0.
 | Scope/checks | `--scope <address>`, `--check <names>`; a scoped pass is not whole-application success | Discover installed validation options |
 | Reference execution | `screenplay test <root>` or MCP `run-specifications` | Discover bundled MCP capability; target tests are not V4 |
 | MCP | `screenplay mcp <root>`; discover schemas | `cratis screenplay mcp [root]`; registered by `cratis ai install` |
-| Render version boundary | Binder admission is not Stage admission | CLI 3.50.0 passes through ESM v10 to Stage construct admission; newer versions: `CLI-RENDER-004` |
+| Render version boundary | Binder admission is not Stage admission | Pinned CLI (`versions.md`) passes through ESM v10 to Stage construct admission; bound newer models: `CLI-RENDER-004` |
 
 Read `references/versions.md` when you need the exact messages, exit codes or the MCP roots bug.
 
@@ -109,7 +109,7 @@ changes with the root folder name.
   Stage generated-value/response refusals `STAGE-ESM-028`/`029`, not a blanket
   compiler refusal. Run admission before claiming a particular model renders.
 - **Event sources, streams and routes** bind as ESM v8 at 4.125.0.
-  CLI 3.50.0/Stage 4.67.0 reaches construct admission through v10, not blanket
+  The pinned CLI/Stage pair (`references/versions.md`) reaches admission through v10, not blanket
   rendering. Operations and exact numeric source mode remain unadmitted.
   Details: `references/sources-and-streams.md` and `references/versions.md`.
 - **Released v9/v10 and published v11:** public contracts and direction select v9;
@@ -119,6 +119,15 @@ changes with the root folder name.
   `key` binds. Read `references/production-routes-and-filters.md` and read-surface
   `references/named-keys.md`; version freeze and numeric boundaries: `references/versions.md`.
 
+- **Published v12 (4.139.0):** non-positional enum numbers bind; canonical
+  `numbers` parallels `values`. Positional pins preserve earlier executable
+  bytes/version. Specifications still use names. The pinned CLI's compiler accepts source
+  authoring but refuses non-positional numbers at binding (PLAY0268), before
+  renderer admission. Neither its compiler nor Stage reads v12 ESM; upgrading
+  only the compiler would not lift their v10 admission ceiling (`references/versions.md`). Syntax:
+  command-surface `references/enum-numbers.md`; errors PLAY0667–0670 and opt-in
+  `enum-pinning` hint PLAY0671: `references/diagnostics.md`.
+
 - **Caller/compliance metadata** at 4.127.0: `$identity` aliases caller built-ins;
   additional identity details are metadata and executable reads still refuse.
   Bare `pii`/`secret` replace legacy spellings; `pii personal` repeats one marker

package/package/corpus/skills/cratis-screenplay-toolchain/references/cheat-sheet.md

@@ -21,10 +21,13 @@ PLAY0268 (#599), not v10. Read [named keys](../../cratis-screenplay-read-surface
 Production `stream Source.Stream` overrides and reaction/reducer `from Source[.Stream]`
 select released v10: [routes and filters](production-routes-and-filters.md).
 Qualifying non-route Double literals select published v11 at 4.135.0;
-`numbers exact` does not bind. See `versions.md` for freeze and numeric boundaries.
+`numbers exact` does not bind. Non-positional enum member numbers (`draft = 1`)
+select published v12 at 4.139.0; positional pins keep earlier bytes/version,
+while specifications still use names. The pinned CLI/Stage pair (`versions.md`) does not admit v12.
+Syntax/example: command-surface `references/enum-numbers.md`.
+See `versions.md` for freeze and numeric boundaries.
 
-Current pins: standalone Screenplay 4.135.0 / CLI 3.50.0; `versions.md` is the
-single table. Compile evidence below keeps its historical tool labels.
+Current pins: `versions.md` (the single table). Compile evidence below keeps its historical tool labels.
 
 The syntax lives in compiled example files next to this one (each is a Markdown file holding
 one complete `screenplay` fence). Copy shapes from them; do not write a form that none of

package/package/corpus/skills/cratis-screenplay-toolchain/references/diagnostics.md

@@ -5,6 +5,7 @@
 - Warnings that hide defects (always validate with `--warnings-as-errors`)
 - Source reference and identifier checks
 - Public events and translation direction
+- Explicit enum member numbers
 - Named keys, production routes and observer filters
 - Caller identity, compliance and routes
 - Specification metadata, callers, cases and locators
@@ -53,7 +54,7 @@ Legacy compliance spellings (`@pii`/`@sensitive`) do not evade PLAY0515.
 
 ## Public events and translation direction
 
-Current at Screenplay 4.135.0; all are errors. These constructs bind as released
+Source checked at Screenplay 4.135.0; all are errors. These constructs bind as released
 ESM v9, except public/foreign imports without local shapes (PLAY0268).
 
 | Code | Meaning / fix |
@@ -79,6 +80,24 @@ or non-Translate direction. Repair discovery uses `repair-capabilities`, workspa
 `repairs`, then revision-checked `propose-repair`; do not guess a direction.
 See automations-and-translations `references/public-events-and-direction.md`.
 
+## Explicit enum member numbers
+
+Source errors from Screenplay 4.137.0; ESM v12 admission from 4.139.0:
+
+| Code | Severity | Meaning / fix |
+| --- | --- | --- |
+| PLAY0667 | E | Mixed numbered/unnumbered members; number all or none |
+| PLAY0668 | E | Duplicate enum number; aliases are not supported |
+| PLAY0669 | E | Number outside int32 (-2147483648 through 2147483647) |
+| PLAY0670 | E | Malformed number: decimal digits, optional minus, no leading zero, fraction, exponent or plus |
+| PLAY0671 | I | Opt-in `enum-pinning` completeness hint for an unnumbered enum used by an event property; ordinary compilation does not report it |
+
+Numbering errors have no automatic repair. PLAY0671 suggests the opt-in
+`propose-number-enum-members` refactoring, not a correctness repair. Member names
+remain specification values. Non-positional pins select v12; positional pins keep
+older executable bytes/version. Consumer admission is separate (`versions.md`).
+Source: `v4.139.0:Documentation/screenplay/diagnostics.md`, decision 0065.
+
 ## Named keys, production routes and observer filters
 
 | Code | Severity | Meaning / fix |
@@ -312,7 +331,7 @@ Report each as `code file:line one-line meaning`; never paste more than about 30
 
 ## Render admission (V5): `STAGE-*`, `CLI-RENDER-*`, `STAGE-CRATIS-*`
 Full table with causes: `renderable-subset.md`. The Stage 4.24.x rows below
-retain historical source/probe evidence. Current CLI 3.50.0/Stage 4.67.0 admits
+retain historical source/probe evidence. The pinned CLI/Stage pair (`versions.md`) admits
 through v10 to construct checks; above it is CLI-RENDER-004 (direct Stage:
 STAGE-ESM-016). Publication STAGE-ESM-032, foreign facts/event captures 033,
 reaction identity 034, reaction filters 035 and production overrides 036 remain

package/package/corpus/skills/cratis-screenplay-toolchain/references/doc-contradictions.md

@@ -1,6 +1,6 @@
 # Documentation contradictions and which side to trust
 
-Current pins are Screenplay 4.135.0 / CLI 3.50.0 (`versions.md`). This is a
+Current pins: `versions.md`. This is a
 **historical** contradiction inventory, not a claim that all listed defects still
 exist. Current grammar documents exact numbers and free description placement;
 sources/routes bind as ESM v8; PLAY0515 is a source error; CLI admits through
@@ -42,7 +42,7 @@ read from source or documentation.
 | 14 | `$causedBy` | not evaluable (#4119), not ESM | showcase only |
 | 15 | literal keys | `key literal "global"` vs `key "global"` | both compile; prefer `literal` |
 | 16 | query admission | `D/queries.md:74` now says live, filtered, scoped and performer queries are not admitted | the binder also rejects collection queries and a missing `by`, which stay undocumented [probed] |
-| 17 | `@pii` | `D/concepts.md:3,33` "Chronicle applies `@pii` and `@sensitive` rules automatically" | the binder rejects any compliance attribute (PLAY0268); keep it, report V3 blocked. `@sensitive` means an operational secret (`[Encrypted]` + `[NotAudited]`; Screenplay decision 0034); the pinned tools (standalone 4.68.0, bundle 4.66.0) do **not** report `PLAY0515` (`@pii` from 4.69.1, `@sensitive` from 4.84.1): there only Chronicle catches either attribute on an event-source identifier, at build time of the generated code (CHR0034 for `@pii`, CHR0052 for `@sensitive`) |
+| 17 | `@pii` | `D/concepts.md:3,33` "Chronicle applies `@pii` and `@sensitive` rules automatically" | the binder rejects any compliance attribute (PLAY0268); keep it, report V3 blocked. `@sensitive` means an operational secret (`[Encrypted]` + `[NotAudited]`; Screenplay decision 0034); the historically probed tools (standalone 4.68.0, bundle 4.66.0) do **not** report `PLAY0515` (`@pii` from 4.69.1, `@sensitive` from 4.84.1): there only Chronicle catches either attribute on an event-source identifier, at build time of the generated code (CHR0034 for `@pii`, CHR0052 for `@sensitive`) |
 | 18 | read-model identity | `D/readmodels.md:32` "from the keyed query" | at 4.135.0 explicit `key` wins; else single-instance queries agree on one read-model `by` property; only with none and an admitted list query does conventional `*Id` inference run (collection-key exclusions: read-surface `references/named-keys.md`). Queryless views need explicit `key` |
 | 19 | `$strings` constraint messages | `D/constraints.md:31` vs `D/internationalization.md:55` | the compiler keeps the key; realization localizes |
 | 20 | composite key braces | optional in the EBNF; both forms in docs | both fine |

package/package/corpus/skills/cratis-screenplay-toolchain/references/executable-subset.md

@@ -12,7 +12,7 @@
 - Not refused, but do not rely on it
 - Never do this to reach V3
 
-Current pins are Screenplay 4.135.0 / CLI 3.50.0 (`versions.md`). Detailed
+Current pins: `versions.md`. Detailed
 4.66.0/4.68.0 binder probes below retain their historical labels. Current source
 admits routes as ESM v8, public/direction constructs as v9, identity/overrides/filters
 as v10 and qualifying non-route Double literals as v11. Operations,
@@ -94,7 +94,7 @@ Authority: v4.127.0 `context.md`, `identity.md`, `concepts.md`, `events.md`, `pu
   ...` with an explicit `for`. Without a declared actor, a gated invocation denies.
   On 4.125.0 reaction `runs as system role "<Role>"` supplies the actor and
   selects ESM v10; keep the gate. CLI 3.41.0's older compiler rejected this syntax;
-  CLI 3.50.0's bundle supports it, but Stage refuses reaction identity with STAGE-ESM-034.
+  The pinned CLI bundle (`versions.md`) supports it, but Stage refuses reaction identity with STAGE-ESM-034.
   Standalone reference execution admits it.
 - Application `trigger` declarations and `when trigger` specifications.
 - `slice Translate` with `capture` (`key`, `map ... translate`, `append ... when x from "a"
@@ -153,6 +153,12 @@ filters match routed source/stream names only. Read
 Qualifying retained non-route Double literals bind/reference-execute as v11 on
 4.135.0, unlike `numbers exact`; see `versions.md`.
 
+Non-positional enum member numbers bind as ESM v12 from 4.139.0; positional
+pins preserve the earlier executable version/bytes. The optional canonical last
+`numbers` array parallels `values`; specifications still use member names.
+Consumers must admit v12 explicitly; CLI 3.53.1/Stage 4.73.1 do not. Syntax:
+command-surface `references/enum-numbers.md`; version contract: `versions.md`.
+
 ## Code attachments (what binds, what never does)
 
 Inline fences (`csharp`, `typescript`, `react`, `html`, `sql`) and `file <path>` attach
@@ -196,7 +202,7 @@ bodies still leave their owner non-executable.
 | `Automation` or `Translate` slice, `reaction`, `capture`, `trigger`; `given clock`, `when clock`, `when trigger`, `when capture` | PLAY0268 | **cratis before 3.28.2 bundles only** (4.60.1); messages in `versions.md` |
 | Unquoted `import Other.Contract` | PLAY0268 | external contract import is not bound |
 | `pii` or `secret` on any concept (also alias/legacy markers) | PLAY0268 | Compliance requires portable data-subject semantics; scopes/qualifiers do not admit it. Secret provider mapping is `[Encrypted]` + `[NotAudited]`, not a bind/render claim |
-| `query` returning a collection (`RM[]`), or without exactly one caller-supplied scalar `by` | PLAY0268 | Current 4.135.0 boundary: composite `by` blocks remain unadmitted (#599); optional scalar snapshot lookup binds |
+| `query` returning a collection (`RM[]`), or without exactly one caller-supplied scalar `by` | PLAY0268 | Historical 4.135.0 source check: composite `by` blocks remain unadmitted (#599); optional scalar snapshot lookup binds |
 | `observable`, `filter`, `scoped to`, `performer` queries | PLAY0268 | "uses delivery, filtering, scope, or implementation behavior outside the first ESM v1 vertical." `observable` goes in the return position (`=> observable RM optional`); as a body line it is PLAY0048 |
 | `contains` or `starts with` in conditions | PLAY0268 | equality and numeric ordering only |
 | Date or DateTime comparison, `today` | PLAY0268 | no runtime date value |

package/package/corpus/skills/cratis-screenplay-toolchain/references/production-routes-and-filters.md

@@ -108,7 +108,7 @@ contract. A consumer admitting v10 must include all three, not just identity.
 Composite **read-model** keys are separate and remain unadmitted (PLAY0268, #599).
 
 Previous CLI 3.46.1/Stage 4.52.0 refused versions above v7 before planning.
-CLI 3.50.0/Stage 4.67.0 admits through v10 to construct checks: production overrides
+The pinned CLI/Stage pair (`versions.md`) admits through v10 to construct checks: production overrides
 still refuse STAGE-ESM-036 and reaction filters STAGE-ESM-035; reducer filters render.
 A supported version number alone never proves target support or a passing render.
 

package/package/corpus/skills/cratis-screenplay-toolchain/references/provenance.md

@@ -28,7 +28,7 @@ is adapted with the agreement of Martin Dilger and Nebulit GmbH.
 
 ## Sources read for facts
 
-- Current public/keys/routes/version update: Screenplay `v4.135.0` (`b4e46130`),
+- Historical public/keys/routes/version source check: Screenplay `v4.135.0` (`b4e46130`),
   unchanged release contract, `Semantics/Versions.cs`, `Documentation/screenplay/{events,slices,captures,readmodels,queries,event-sources,diagnostics,interoperability}.md`,
   decisions 0049–0051 and 0060–0066. Composite view keys remain PLAY0268 (#599);
   v11 literal lowering is admitted despite interoperability's unreleased label.