@cratis/pi 7.103.5 → 7.103.7

package/package/corpus/skills/cratis-engineering-local-cross-repo-verification/scripts/dependency-map.tsv

@@ -1,4 +1,4 @@
-# Reference table of producer/consumer dependencies between Cratis repositories. cratis-local-packages.sh does not read it.
+# Reference table of producer/consumer dependencies between Cratis repositories. cratis-local-packages.sh reads it to derive the pack plan.
 # Tab-separated; # starts a comment; no versions (pins are read live from consumer manifests).
 #   pack  <repo> <eco> <target> [PROP=VAL,...]  pack targets; PROP is a -p:PROP=VAL argument (never an environment variable)
 #   ids   <repo> <eco> <comma-separated expected package IDs>

package/package/corpus/skills/cratis-screenplay-captures-and-reactions/SKILL.md

@@ -14,8 +14,8 @@ Translate slices cross public boundaries; Automation slices cause private follow
 ## Locate the model
 
 Look first for the project's existing `.play` files: their folder is the model.
-For a new model, check `Source/` or `src/`, else use `Screenplay/` at the repository
-root. Never put a model under `.cratis/` or hand-copy it between repositories.
+Reuse existing model/workspace roots; code-only `Source/` or `src/` does not
+qualify. Otherwise use repository-root `Screenplay/` ([discovery/version gates](../cratis-screenplay-event-modeling/references/file-layout.md#locate-the-model)). Never put a model under `.cratis/` or hand-copy it between repositories.
 `cratis ai install` manages `.cratis/ai/`, never model files. Keep explanatory
 Markdown in project documentation; `.play` is the single flow model.
 

package/package/corpus/skills/cratis-screenplay-command-surface/SKILL.md

@@ -15,8 +15,8 @@ they are all built from.
 ## Locate the model
 
 Look first for the project's existing `.play` files: their folder is the model.
-For a new model, check `Source/` or `src/`, else use `Screenplay/` at the repository
-root. Never put a model under `.cratis/` or hand-copy it between repositories.
+Reuse existing model/workspace roots; code-only `Source/` or `src/` does not
+qualify. Otherwise use repository-root `Screenplay/` ([discovery/version gates](../cratis-screenplay-event-modeling/references/file-layout.md#locate-the-model)). Never put a model under `.cratis/` or hand-copy it between repositories.
 `cratis ai install` manages `.cratis/ai/`, never model files. Keep explanatory
 Markdown in project documentation; `.play` is the single flow model.
 

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

@@ -120,7 +120,7 @@ Stage, `cratis render` or Studio refusal as a platform gap rather than waiting f
 
 ## Locate the model
 
-Look first for the project's existing `.play` files: the folder holding them is the model; a new model goes under `Source/` or `src/`, else `Screenplay/`, never under `.cratis/`. Read [references/file-layout.md](references/file-layout.md) (section "Locate the model") when the location is unclear or source might be copied between repositories. `cratis ai install` manages `.cratis/ai/`, never model files.
+Look first for the project's existing `.play` model and workspace state; reuse that root. Code-only `Source/` or `src/` is not a model root; otherwise use repository-root `Screenplay/`, never `.cratis/`. Read [references/file-layout.md](references/file-layout.md) (section "Locate the model") when the location is unclear or source might be copied between repositories. `cratis ai install` manages `.cratis/ai/`, never model files.
 
 ## Verified product sources
 

package/package/corpus/skills/cratis-screenplay-event-modeling/references/file-layout.md

@@ -95,12 +95,21 @@ order of modules, features or slices.
 
 ## Locate the model
 
-Look first for the project's existing `.play` files: the folder holding them is the
-model. A new model goes under the repository's `Source/` or `src/` folder, else in a
-`Screenplay/` folder at the repository root; never under `.cratis/`, which holds
-configuration and the shared AI corpus only. This is the
-conventional home for consumer-owned `.play` source; do not invent another
-location or search the whole repository before checking it.
+Look first for the project's existing `.play` model and Screenplay workspace state;
+reuse that root. `Source/` or `src/` is a model root only when it already holds
+model files or workspace state, not merely because application code lives there.
+With neither, start at repository-root `Screenplay/`, never under `.cratis/`,
+which holds configuration and the shared AI corpus only.
+
+Requires Screenplay 4.236.1 (`screenplay --version`) for standalone MCP discovery.
+Requires Cratis CLI 3.93.1 (`cratis --version`) for CLI discovery. Older tools can select
+a code-only `Source/` or `src/`; inspect the opened root rather than assuming it
+is correct. Existing workspace state can retain the served ancestor of a discovered
+model; do not relocate it or create a second workspace implicitly. Discovery
+selects a path without creating it; the first write creates the directory.
+For fixed-root admission, see [MCP launch and sibling roots](../../cratis-screenplay-model-authoring/references/mcp-tools.md#working-with-the-screenplay-mcp).
+Sources: [MCP discovery](https://github.com/Cratis/Screenplay/blob/main/Source/DotNET/Screenplay.Mcp/McpModelLocation.cs),
+[CLI discovery](https://github.com/Cratis/cli/blob/main/Source/Cli/Commands/Screenplay/ScreenplayModelLocation.cs).
 
 `cratis ai install` manages `.cratis/ai/`, never model files. Never
 hand-copy Screenplay source between repositories. Keep Markdown that explains,

package/package/corpus/skills/cratis-screenplay-event-modeling/verification.json

@@ -3,6 +3,9 @@
   "input": "Facilitate an event modeling session and land the model as .play source.",
   "fixtures": [],
   "assertions": [
+    { "kind": "skill-contains", "value": "Requires Screenplay 4.236.1", "file": "references/file-layout.md" },
+    { "kind": "skill-contains", "value": "Cratis CLI 3.93.1", "file": "references/file-layout.md" },
+    { "kind": "skill-contains", "value": "not merely because application code lives there", "file": "references/file-layout.md" },
     { "kind": "play-compiles" },
     {
       "kind": "skill-contains",
@@ -16,7 +19,7 @@
     },
     {
       "kind": "skill-contains",
-      "value": "Look first for the project's existing `.play` files"
+      "value": "Look first for the project's existing `.play` model and workspace state"
     },
     {
       "kind": "skill-contains",

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

@@ -50,8 +50,9 @@ it owns fallback discovery, fixed-root limits and the initialization protocol.
 Discover `tools/list` schemas.
 
 Look first for the project's existing `.play` files: their folder is the model.
-New models go in `Source/` or `src/`, else root `Screenplay/`, never `.cratis/`
-(configuration/shared corpus only). The source is the single flow model;
+Reuse existing model/workspace roots; code-only `Source/` or `src/` is not a
+model root. Otherwise use repository-root `Screenplay/`, never `.cratis/`
+([root selection and version gates](../cratis-screenplay-event-modeling/references/file-layout.md#locate-the-model)). The source is the single flow model;
 explanatory Markdown belongs in repository documentation.
 
 `cratis ai install` manages `.cratis/ai/`, never model files. Select the
@@ -105,7 +106,10 @@ for handler views: `executableReady` means binding, not an implemented body.
 ## Compare models
 
 Compare with `main` through `semantic-diff` worktree `path`, not two exports.
-Read [comparison sources](references/mcp-tools.md#semantic-revision-comparison) for paging.
+Read [comparison sources](references/mcp-tools.md#semantic-revision-comparison) for paging
+and [enum numeric identity](references/mcp-tools.md#enum-numeric-identity) for
+stored-value risks: implicit reorders can renumber values; stable explicit-number
+reorders do not. Static comparison never proves storage or behavioral compatibility.
 
 ## Make one coherent proposal
 

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

@@ -30,13 +30,21 @@ Without a fixed root, it binds the client's single workspace root, else a launch
 directory holding `.play` files. Only after a no-root or multiple-roots response,
 pass `path`: the folder holding the project's models, otherwise the folder the
 user names. Without a project the server uses `Documents/Screenplay` in the user's
-home; do not invent a location. A fixed root can switch only to the same model
-folder in a registered Git worktree of the same repository.
+home; do not invent a location. A fixed root can switch to the same model
+folder in a registered Git worktree of the same repository. Screenplay 4.236.1
+also admits an explicitly requested sibling from a code-only `Source/` or `src/`
+root, not arbitrary root changes; existing model/workspace state prevents that
+switch. An empty fixed root named `data` still cannot rebind; nested targets,
+links and unrelated nonempty folders remain refused. `semantic-diff` path sources
+share these checks. A Java project with only code in `src` selects
+`<project>/Screenplay`, not `<project>/src`. Read [sibling admission boundaries](mcp-tools.md#working-with-the-screenplay-mcp).
 
 1. Launch with a **fixed root**: `screenplay mcp <model-folder>`, or
    `cratis screenplay mcp <model-folder>`, or `cratis screenplay mcp` inside a
-   project, where the CLI locates the model (the project's `.play` files, else `Source/`
-   or `src/`, else a new `Screenplay/` folder; what the `cratis/screenplay` profile registers). Stdio, newline-delimited
+   project, where the CLI reuses model/workspace roots, else chooses repository-root
+   `Screenplay/`; code-only `Source/` or `src/` does not qualify (Requires Cratis CLI
+   3.93.1; `cratis --version`; older versions can select the code folder).
+   Discovery creates no directory; the first write does. Stdio, newline-delimited
    JSON-RPC, one sequential connection.
 2. Send `initialize`, then the `notifications/initialized` notification, **before
    any tool call**. Earlier calls fail with `-32600` "Initialize and send
@@ -176,6 +184,9 @@ connection. Passing `open-workspace.path` does **not** avoid it, because the err
    move or removal is that approval, also unattended: do not ask again per apply. Then `apply` with the **before**
    revisions. Every old handle and proposal is gone afterwards: re-read at the new
    revision.
+   For a PLAY0516 [wildcard-import repair](repairs.md#timeline-import-order), review
+   that future files will need explicit imports, then rediscover diagnostics and
+   repairs after the apply; never reuse the old ordering proposal.
 9. Verify: compile the whole folder (V1), read `executable-diagnostics` (V2,
    V3), and run `screenplay test <root> --format json` or workspace
    `run-specifications` (V4), naming the tool, version and source revision. A

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

@@ -28,8 +28,12 @@
 The standalone MCP server lists 46 tools from Screenplay 4.228.0 (including the MCP-Apps visualization tool); `tools/list` is the authority for the installed server, and the CLI-bundled MCP (`cratis screenplay mcp`) can be an older Screenplay that lacks newer tools.
 
 The supported CLI launch is `cratis screenplay mcp <model-root>`, or `cratis screenplay mcp`
-alone inside a project, where the CLI locates the model (the project's `.play` files, else
-`Source/` or `src/`, else a new `Screenplay/` folder). The standalone form is `screenplay mcp <model-folder>`. A
+alone inside a project, where the CLI reuses existing model/workspace roots.
+A code-only `Source/` or `src/` is not a model root; without model/workspace state,
+use repository-root `Screenplay/`. Requires Cratis CLI 3.93.1 (`cratis --version`)
+and Screenplay 4.236.1 (`screenplay --version`) for their respective discovery
+paths; older versions can select code-only folders. See [root selection](../../cratis-screenplay-event-modeling/references/file-layout.md#locate-the-model).
+The standalone form is `screenplay mcp <model-folder>`. A
 server started with no root at all binds one on first use from `open-workspace`'s
 `path`, the client's roots, or the working directory; that dynamic form depends on the client supplying roots (see the [MCP loop](mcp-loop.md#dynamic-roots-and-the-workaround)),
 so prefer a fixed root. Without a project the server works in `Documents/Screenplay`. Model files never go under `.cratis/`. AI distribution provides the
@@ -37,6 +41,19 @@ profile-selected declaration and guidance; the CLI owns executable hosting and
 client registration. Installation must preserve user-owned MCP servers and
 report unsupported adapters or drift.
 
+From Screenplay 4.236.1, a fixed root at a code-only `Source/` or `src/` can admit
+an explicitly requested direct sibling model folder via `open-workspace path`. The
+configured code root must have no model or workspace state. The sibling must be
+missing, empty, or already model/workspace-bearing; an unrelated nonempty folder,
+a file or a symlink is refused. Existing model/workspace roots stay protected;
+this is not permission to switch to arbitrary roots. Nested targets are refused;
+an empty fixed root named `data` cannot rebind merely because it is empty.
+`semantic-diff` path sources use the same admission checks. Inspect the returned
+root and reuse its workspace/revisions. Path selection alone creates no directory.
+For example, a Java project `/project` with code in `/project/src` but no model or
+Screenplay state selects `/project/Screenplay`, not `/project/src`.
+Source: [sibling admission](https://github.com/Cratis/Screenplay/blob/v4.236.1/Source/DotNET/Screenplay.Mcp/McpWorkspaces.ModelFolder.cs).
+
 ## Tool groups
 
 After `initialize` and `notifications/initialized`, discover current tools and
@@ -327,7 +344,11 @@ with `view: "diagnostics"`, then `view: "repairs"` at the current revision.
 | `PLAY0688` | Replace a refuted generated-concept rule with the strategy-derived `matches`; review every concept use affected by the changed rule. |
 | `PLAY0683/0684` | Raise NanoID size/bytes count using the concept subject; PLAY0683 also offers uniqueness using the command-property subject. Individual review, canonical formatting, no pinned evidence; see [concept generation](#concept-generation). |
 | `PLAY0664` | Remove an override identical to the command's complete source/stream/id route. |
-| `PLAY0516` | Move a producing sibling declaration/import before its consumer, or pin an already placed file before a retained glob. Preserve catalogs, comments, placement and executable readiness; introduce no timeline findings. Own-sub-feature edges, cycles, unranked members and mixed/different-parent boundaries have no repair. Rediscover after each move; pinned evidence is unsupported. |
+| `PLAY0516` | Move a producing sibling declaration/import before its consumer, pin an already placed file before a retained glob, or, when those cannot safely fix the edge, replace a same-parent wildcard-import span with explicit ordered imports. The last repair changes future inclusion: new files need explicit imports. Preserve catalogs, comments, placement and executable readiness; introduce no timeline findings. Own-sub-feature edges, cycles, unranked members and mixed/different-parent boundaries have no repair. Rediscover after each move; pinned evidence is unsupported. |
+
+Requires Screenplay 4.219.0 (`screenplay --version`) for wildcard-import expansion;
+older tools do not offer that repair. Read [timeline repair](repairs.md#timeline-import-order)
+for the future-import decision and refusal boundaries.
 
 These discoveries verify acceptance before listing a repair. Only compact
 acceptance/conflict verdicts are cached on the immutable snapshot, not diagnostics,
@@ -703,6 +724,31 @@ or transitive/runtime impact. Use `read-proposal` with `view: "semantic-diff"`
 for a retained proposal against its disk baseline without applying it; changed
 baseline bytes or pending recovery refuse that view too.
 
+### Enum numeric identity
+
+Requires Screenplay 4.214.0 (`screenplay --version`); older comparison tools do not
+report these enum-specific changes. Inspect `enum-*` items in `members`, especially
+`stored: true`: the baseline enum is reachable from an event property (including
+nested composite types), not proof that events were persisted. `beforeNumber`,
+`afterNumber`, `beforeNumbering`, `afterNumbering` and `afterMember` expose the
+numeric change; implicit numbers are zero-based declaration positions.
+
+`enum-number-changed`, `enum-member-removed` and `enum-number-reused` are
+contract-breaking. `enum-member-renamed` retains an explicit number on both sides
+and is not breaking for default numeric storage, but renames generated C#/TypeScript
+members and schema metadata; a name-based converter can still break. Explicit
+removal/reuse is indistinguishable from that rename, so review intent. Positional
+renames report number reuse. Appending members, reordering stable explicit numbers,
+or pinning existing positions adds no enum records; structural hashes still change.
+Before reordering a stored positional enum, use `propose-number-enum-members` to pin
+its current values. Never migrate stored numbers automatically.
+
+Duplicate names/numbers or inconsistent member/number counts report
+`EnumerationNotComparable`; absence of enum items is not a clean comparison when
+coverage is incomplete. Neither comparison view proves behavioral compatibility
+or waives the separate release-baseline equality check.
+Source: [model comparison](https://github.com/Cratis/Screenplay/blob/v4.214.0/Documentation/screenplay/model-comparison.md).
+
 Authority: `Source/DotNET/Screenplay.Mcp/{McpRevisionDiff,McpWorkspaces.Comparison,McpToolSchemas,McpToolCatalog}.cs`
 and `Documentation/screenplay/mcp/reference.md`.
 

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

@@ -14,9 +14,10 @@ from silently changing the reviewed candidate.
 
 - `PLAY0166` declares a missing produced event; `PLAY0478` is a routing decision
   (identifier destination, never fix-all); `PLAY0471` removes a redundant name-equal event pin.
-- `PLAY0516` repairs presentation order by moving a sibling or import, or pinning
-  a producer before a glob. It preserves semantics/identities and introduces no
-  new timeline findings; evidence pinning is unsupported for this repair.
+- `PLAY0516` repairs presentation order by moving a sibling or import, pinning
+  a producer before a glob, or replacing wildcard imports with ordered imports
+  ([timeline import order](#timeline-import-order)). It preserves semantics/identities
+  and introduces no new timeline findings; evidence pinning is unsupported for this repair.
 - `PLAY0469` removes an inline identifier payload copy: it **changes the event
   contract**, refuses consumer/opaque impact, has no fix-all, and the catalog does
   not prove events were persisted, so ask about stored contracts first. For a
@@ -31,6 +32,29 @@ from silently changing the reviewed candidate.
 - Generation repairs PLAY0683/0684: [subjects, review and limits](mcp-tools.md#concept-generation).
 - Compliance repairs PLAY0565/0653: [MCP tool guide](mcp-tools.md).
 
+## Timeline import order
+
+Requires Screenplay 4.219.0 (`screenplay --version`) for wildcard-import expansion;
+older tools offer only the earlier safe moves/pins. When those cannot fix the
+edge safely, the discovered repair can replace a same-parent import span
+containing a wildcard with explicit imports in producer-before-consumer order.
+**New files need explicit imports** afterwards: the replaced glob no longer
+includes future files. Review and accept that inclusion-policy change before
+applying; do not manufacture a reorder if discovery offers no repair.
+
+The repair must preserve comments, catalog/identities, document set and placement,
+executable readiness and existing error/warning counts, remove the target finding
+and introduce no new timeline findings. Cycles, own-sub-feature edges, ambiguous
+or duplicate imports, placement mismatches and unproven moves remain refused.
+Rediscover diagnostics and repairs at the new revisions after applying.
+The TypeScript compiler also exposes PLAY0516 as a quick fix (including edits in
+the importing document); Monaco shows it as a code action. VS Code offers it as a
+reviewed saved-file code action with preview, drift checks and recovery. These
+editor routes share the safe repair, not permission to force a reorder.
+Source: [workspace timeline repairs](https://github.com/Cratis/Screenplay/blob/main/Source/DotNET/Screenplay/Workspaces/WorkspaceTimelineRepairs.Expansion.cs).
+
+## Enum numbering and event extraction
+
 `propose-number-enum-members` pins an unnumbered enum to current positions.
 Opt-in MCP `checks: "enum-pinning"` / `--check enum-pinning` (PLAY0671) hints at
 stored enums, not correctness repairs. Arguments/review: `references/mcp-tools.md`.

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

@@ -3,6 +3,20 @@
   "input": "Author and organize a Screenplay model in a repository.",
   "fixtures": [],
   "assertions": [
+    { "kind": "skill-contains", "value": "Monaco shows it as a code action", "file": "references/repairs.md" },
+    { "kind": "skill-contains", "value": "reviewed saved-file code action", "file": "references/repairs.md" },
+    { "kind": "skill-contains", "value": "an empty fixed root named `data` cannot rebind", "file": "references/mcp-tools.md" },
+    { "kind": "skill-contains", "value": "selects `/project/Screenplay`, not `/project/src`", "file": "references/mcp-tools.md" },
+    { "kind": "skill-contains", "value": "`semantic-diff` path sources use the same admission checks", "file": "references/mcp-tools.md" },
+    { "kind": "skill-contains", "value": "Requires Cratis CLI 3.93.1", "file": "references/mcp-tools.md" },
+    { "kind": "skill-contains", "value": "configured code root must have no model or workspace state", "file": "references/mcp-tools.md" },
+    { "kind": "skill-contains", "value": "Path selection alone creates no directory", "file": "references/mcp-tools.md" },
+    { "kind": "skill-contains", "value": "New files need explicit imports", "file": "references/repairs.md" },
+    { "kind": "skill-contains", "value": "Requires Screenplay 4.219.0", "file": "references/repairs.md" },
+    { "kind": "skill-contains", "value": "rediscover diagnostics and", "file": "references/mcp-loop.md" },
+    { "kind": "skill-contains", "value": "enum-number-reused", "file": "references/mcp-tools.md" },
+    { "kind": "skill-contains", "value": "EnumerationNotComparable", "file": "references/mcp-tools.md" },
+    { "kind": "skill-contains", "value": "Requires Screenplay 4.214.0", "file": "references/mcp-tools.md" },
     { "kind": "skill-contains", "value": ".screenplay/release-baseline.json", "file": "references/release-baseline.md" },
     { "kind": "skill-contains", "value": "screenplay baseline admit", "file": "references/release-baseline.md" },
     { "kind": "skill-contains", "value": "screenplay baseline check", "file": "references/release-baseline.md" },

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

@@ -117,6 +117,12 @@ model's behalf.
 
 ## Comparing with a baseline
 For comparison with `main`, use `semantic-diff`; neither it nor `read-proposal view=semantic-diff` proves behavioral equivalence. Read [baseline comparison](references/baseline-comparison.md) for source selection, the baseline worktree check, identity matching and drift refusals.
+Review [enum numeric identity](../cratis-screenplay-model-authoring/references/mcp-tools.md#enum-numeric-identity)
+(Requires Screenplay 4.214.0; `screenplay --version`): inspect `stored: true` items.
+Number change/removal/reuse is breaking; an explicit-number-preserving rename is
+not breaking for numeric storage but renames generated code. Pin stored positional
+enums with `propose-number-enum-members` before reordering. Treat
+`EnumerationNotComparable` as unresolved comparison, never as unchanged.
 
 ## Audit pass (existing or extracted models)
 Read-only. Before the checklist produce the inventory in the fixed shape of

package/package/corpus/skills/cratis-screenplay-model-review/references/checklist.md

@@ -105,7 +105,7 @@ the format in `worked-example.md`.
 | C6 | No secret or bearer values as facts (tokens, magic links, signed URLs): record a keyed hash or a reference | event payloads | D |
 | C7 | No two events of one kind of event source mean the same thing (a shared property set is a signal, not a defect: distinct facts may share a shape and historical generations are exempt; major only when meaning is lost, a rule bypassed or consumers ambiguous); one fact is not recorded twice (aggregate event plus per-item fan-out) | event declarations side by side | D |
 | C8 | Corrections are new facts that name what they correct; redaction and crypto-erasure are compliance tools, not corrections | event names | D |
-| C9 | A changed event contract is a generation or a new event with a recorded reason; no past meaning is reinterpreted through a rename or payload cleanup | `id` pins, generations, documentation | D (major when history changes meaning) |
+| C9 | A changed event contract is a generation or a new event with a recorded reason; no past meaning is reinterpreted through a rename or payload cleanup. For `enum-*` items with `stored: true`, number change/removal/reuse is breaking; explicit-number-preserving renames retain numeric storage compatibility but rename generated code. Pin positional enums before reordering; stable explicit-number reorders add no enum records. `EnumerationNotComparable` is unresolved, not unchanged | `id` pins, generations, documentation; [enum comparison](../../cratis-screenplay-model-authoring/references/mcp-tools.md#enum-numeric-identity) | D (major when history changes meaning) |
 
 ## Phase 6. Events versus views (7 checks, D1-D7)
 | Id | Check | Evidence | Tier |

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

@@ -3,6 +3,8 @@
   "input": "Review the marina berth .play model before we accept it: check the model and report findings, do not change anything.",
   "fixtures": [],
   "assertions": [
+    { "kind": "skill-contains", "value": "EnumerationNotComparable" },
+    { "kind": "skill-contains", "value": "number change/removal/reuse is breaking", "file": "references/checklist.md" },
     { "kind": "skill-contains", "value": "all *known* producers", "file": "references/public-keys-and-routes.md" },
     { "kind": "play-compiles" },
     { "kind": "skill-contains", "value": "A read-only reviewer returns `question` note requests" },

package/package/corpus/skills/cratis-screenplay-modeling-lifecycle/SKILL.md

@@ -25,6 +25,10 @@ an unproven pass.
    A direct user request to model a scope is consent for that scope. A committed model the project marks `modelFirst.frozen` in `.cratis/ai.json` is generated evidence, not opted in (reason `frozen-model`): read it, never regenerate or edit it unless the request names that `.play` path or model; a generic "regenerate all" skips it and says so. Run `scripts/model-first-status.mjs` from the repository with Node.js and Git:
    `node <skill-directory>/scripts/model-first-status.mjs [--root <repository-relative-dir>] [--json]`.
    Read-only roots: `--root`, configuration, then discovery from HEAD project paths (drafts only if none). Discovery prefers legacy `.cratis/screenplay/`, else the common folder, else `Source/`, `src/`, `Screenplay/`. It excludes hidden/build/docs/samples/examples/scratch/test fixtures from discovery and acceptance, including at `.`; explicit roots include everything beneath them.
+   This read-only opt-in detector is not MCP/CLI workspace discovery. For a new
+   workspace use [root selection](../cratis-screenplay-event-modeling/references/file-layout.md#locate-the-model):
+   code-only `Source/` or `src/` does not qualify; absent model/workspace state,
+   use repository-root `Screenplay/`.
    Output: root, reason, frozen marker, file counts, drafts, model changes and the resolved `process` block. Exits: **0 opted in**, **1 not opted in**, **2 could not run** (Git/configuration/arguments). Treat 2 as blocked, not code-first.
    Run `scripts/model-first-status.mjs --self-test` to plant and check verdict fixtures; it executes `scripts/model-first-self-test.mjs` and prints the checked count on success.
    Read `references/opt-in.md` when checking the project configuration mechanism.

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

@@ -15,11 +15,10 @@ text. This is half of every event model, and the half most easily got wrong.
 ## Locate the model
 
 Look first for the project's existing `.play` files: the folder holding them is the
-model. A new model goes under the repository's `Source/` or `src/` folder, else in a
-`Screenplay/` folder at the repository root; never under `.cratis/`, which holds
-configuration and the shared AI corpus only. This is the
-conventional home for consumer-owned `.play` source; do not invent another
-location or search the whole repository before checking it.
+model. Reuse existing model/workspace roots; code-only `Source/` or `src/` does
+not qualify. Otherwise use repository-root `Screenplay/`, never `.cratis/`
+(configuration/shared corpus only). Read [discovery/version gates](../cratis-screenplay-event-modeling/references/file-layout.md#locate-the-model)
+when locating the model; do not invent another location.
 
 `cratis ai install` manages `.cratis/ai/`, never model files. Never
 hand-copy Screenplay source between repositories. Keep Markdown that explains,

package/package/corpus/skills/cratis-screenplay-read-surface/SKILL.md

@@ -14,11 +14,10 @@ shape, the `query` is the entry point, and the `screen` renders it.
 ## Locate the model
 
 Look first for the project's existing `.play` files: the folder holding them is the
-model. A new model goes under the repository's `Source/` or `src/` folder, else in a
-`Screenplay/` folder at the repository root; never under `.cratis/`, which holds
-configuration and the shared AI corpus only. This is the
-conventional home for consumer-owned `.play` source; do not invent another
-location or search the whole repository before checking it.
+model. Reuse existing model/workspace roots; code-only `Source/` or `src/` does
+not qualify. Otherwise use repository-root `Screenplay/`, never `.cratis/`
+(configuration/shared corpus only). Read [discovery/version gates](../cratis-screenplay-event-modeling/references/file-layout.md#locate-the-model)
+when locating the model; do not invent another location.
 
 `cratis ai install` manages `.cratis/ai/`, never model files. Never
 hand-copy Screenplay source between repositories. Keep Markdown that explains,

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

@@ -15,8 +15,8 @@ concrete data.
 ## Locate the model
 
 Look first for the project's existing `.play` files: their folder is the model.
-For a new model, check `Source/` or `src/`, else use `Screenplay/` at the repository
-root. Never put a model under `.cratis/` or hand-copy it between repositories.
+Reuse existing model/workspace roots; code-only `Source/` or `src/` does not
+qualify. Otherwise use repository-root `Screenplay/` ([discovery/version gates](../cratis-screenplay-event-modeling/references/file-layout.md#locate-the-model)). Never put a model under `.cratis/` or hand-copy it between repositories.
 `cratis ai install` manages `.cratis/ai/`, never model files. Keep explanatory
 Markdown in project documentation; `.play` is the single flow model.
 

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

@@ -15,6 +15,8 @@ This skill owns tool selection, verdicts and admission. Modeling method lives in
 
 Decide opt-in per `general.md` "Model first"; where `cratis-screenplay-modeling-lifecycle` is installed, run its `scripts/model-first-status.mjs` to locate the model root. A folder of `.play`
 files is one application: always check the folder, never one file of it.
+MCP/CLI discovery reuses model/workspace roots, not code-only `Source/` or `src/`;
+otherwise use repository-root `Screenplay/` ([version gates and root boundaries](../cratis-screenplay-event-modeling/references/file-layout.md#locate-the-model)).
 
 ## Tool versions and the contract
 
@@ -98,6 +100,10 @@ not the source identity.
 
 Read [observation comparison](references/observation-comparison.md) when asking whether a running namespace holds what the model declares, or when reading a `conform-namespace` verdict. It differs from model comparison (model versus model) and `conform` (model versus code).
 
+PLAY0516 ordering is presentation-only, not execution. For a wildcard-import
+repair, read [timeline diagnostics](references/diagnostics.md): replacing globs
+with ordered imports means future files need explicit imports.
+
 ## Subsets (write from the one your mode needs)
 
 - **Design**: every construct family parses; use it to model first. Compiled shapes:

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

@@ -12,6 +12,7 @@
 - `$eventContext.` (projections)
 - PDL quick reference (most forms are compiled in `pdl-example.md` or `cheat-sheet-example.md`; `remove via join` and `$eventContext.occurred` are not)
 - Generated values and proofs
+- UI profile theme references
 - Specification forms
 
 Released boundary forms: `public event X`, `event X from "store"`, Translate
@@ -213,6 +214,18 @@ for v21 admission, all-Proven unpinned specs and the separate prerequisites for
 warning/info rules, checksum validation and pattern/random rendering.
 `generate rule` renders from Stage 4.136.0 (STAGE-ESM-028 in the Host). Reference binding is not rendering.
 
+## UI profile theme references
+
+Inside `ui profile`, write `theme "Scene Default Light"` for a package theme's
+display name. Requires Screenplay 4.227.0 (`screenplay --version`); older compilers
+reject quoted references. Escapes resolve to the name. Undeclared quoted names
+refer to package themes without `PLAY0231`; quoted names matching declarations
+receive `PLAY0232` compatibility checks. Bare `theme Nordic` is unchanged.
+Empty, blank or unterminated quoted names are `PLAY0229`; duplicates are `PLAY0230`.
+Declaration headers remain identifiers, not quoted names. Package compatibility
+is unchanged; parse acceptance does not prove rendering support. See [profile
+examples](../../cratis-screenplay-ui-composition/references/ui-profile-and-theme.md#ui-profile-and-theme).
+
 ## Specification forms
 Full list with semantics: `Documentation/screenplay/specifications.md`. Compiled in the
 examples: `given caller` (+`authenticated`, `role`), `given clock`, `given <Event> for`,

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

@@ -348,8 +348,16 @@ presentation order, not execution: a backward event/read-model dependency or a
 mutually dependent sibling group. A cycle group replaces internal individual
 backward findings. Ordering roots are the sole source document, an importing
 `application.play`, or a unique importing root; without one, folder timeline
-checking is skipped. Safe PLAY0516 repairs move siblings/imports or pin files
-before a retained glob; cycles and own-sub-feature findings have no repair.
+checking is skipped. Safe PLAY0516 repairs move siblings/imports, pin files
+before a retained glob, or replace a same-parent wildcard-import span with explicit
+ordered imports when earlier moves cannot safely fix it (Requires Screenplay
+4.219.0; `screenplay --version`). **New files need explicit imports** after that
+replacement. Review comments, identities, placement and readiness preservation,
+and no new timeline findings; cycles, own-sub-feature edges and ambiguous imports
+remain refused. Use the [timeline repair loop](../../cratis-screenplay-model-authoring/references/repairs.md#timeline-import-order),
+not a hand-written reorder; rediscover after applying. In the same release the
+TypeScript compiler/Monaco expose the PLAY0516 quick fix, and VS Code provides a
+reviewed saved-file code action (preview, drift checks and recovery).
 
 ## Editor versus C# verdicts
 

package/package/corpus/skills/cratis-screenplay-toolchain/verification.json

@@ -3,6 +3,9 @@
   "input": "Check a Screenplay model folder: which compiler should I run, what do V1 to V3 mean, and what does the cratis CLI do with my Automation slice?",
   "fixtures": [],
   "assertions": [
+    { "kind": "skill-contains", "value": "Requires Screenplay 4.227.0", "file": "references/cheat-sheet.md" },
+    { "kind": "skill-contains", "value": "New files need explicit imports", "file": "references/diagnostics.md" },
+    { "kind": "skill-contains", "value": "cycles, own-sub-feature edges and ambiguous imports", "file": "references/diagnostics.md" },
     { "kind": "skill-contains", "value": "Uuid equality in command conditions (ESM v28)", "file": "references/executable-subset.md" },
     { "kind": "skill-contains", "value": "screenplay baseline check", "file": "references/verdicts.md" },
     { "kind": "skill-contains", "value": "independent of V1–V5", "file": "references/verdicts.md" },

package/package/corpus/skills/cratis-screenplay-ui-composition/SKILL.md

@@ -20,8 +20,8 @@ a trigger value named `file` is written `@file`.
 ## Locate the model
 
 Look first for the project's existing `.play` files: their folder is the model.
-For a new model, check `Source/` or `src/`, else use `Screenplay/` at the repository
-root. Never put a model under `.cratis/` or hand-copy it between repositories.
+Reuse existing model/workspace roots; code-only `Source/` or `src/` does not
+qualify. Otherwise use repository-root `Screenplay/` ([discovery/version gates](../cratis-screenplay-event-modeling/references/file-layout.md#locate-the-model)). Never put a model under `.cratis/` or hand-copy it between repositories.
 `cratis ai install` manages `.cratis/ai/`, never model files. Keep explanatory
 Markdown in project documentation; `.play` is the single flow model.
 
@@ -268,6 +268,12 @@ precedence, PLAY0485 and examples.
 
 ## `ui profile` and `theme`
 
+Requires Screenplay 4.227.0 (`screenplay --version`) for a quoted profile reference
+such as `theme "Scene Default Light"`: an undeclared quoted name selects a package
+theme without PLAY0231; a declared one gets PLAY0232 compatibility checks. Bare
+`theme Nordic` still works; declaration headers stay identifier-only. See the
+reference below for escaping and PLAY0229 malformed/blank-name refusals.
+
 A `ui profile` selects the application shell with `root template` (an own layout or application-scope screen template, or `blueprint <B> <Name>` with an optional `version` pin), its shell `option` lines, an `appearance` block (`color scheme`, `accent`), the template new screens start from (`new screens use template`), the theme and the `packages`, listed in override-priority order (a later package shadows an earlier one); `target platform` and `target size` accept any identifier, so a typo is silent. The legacy `layout <Name>` line inside a profile still reads but warns `PLAY0791`: write `root template`. `PLAY0790` to `PLAY0799` check the shell. Read [references/ui-profile-and-theme.md](references/ui-profile-and-theme.md) when writing a profile or theme, or fixing a shell diagnostic.
 
 ## A deliverable app declares its identity, titles and labels

package/package/corpus/skills/cratis-screenplay-ui-composition/references/ui-profile-and-theme.md

@@ -148,6 +148,34 @@ theme Nordic
   compatible with Cratis.Components
 ```
 
+A profile can select a package theme by its quoted display name, or quote a
+locally declared name:
+
+```screenplay excerpt
+ui profile PackageTheme
+  theme "Scene Default Light"
+
+ui profile DesktopQuoted
+  root template AppShell
+  theme "Nordic"
+  packages
+    Cratis.Components
+```
+
+Requires Screenplay 4.227.0 (`screenplay --version`) for quoted references; older
+compilers reject them. Escapes resolve to the theme name. A quoted name not
+declared in the document refers to a package theme and gets no unknown-theme
+`PLAY0231`; do not invent an identifier alias for `"Scene Default Light"`. A
+quoted name matching a declared theme resolves to it and receives the `PLAY0232`
+package compatibility check, like the bare reference `theme Nordic`.
+
+Empty, blank or unterminated quoted names are `PLAY0229`. Repeating a profile's
+`theme` selection remains `PLAY0230`. This changes only references inside
+`ui profile`; declaration headers remain identifiers (`theme Nordic`), not
+`theme "Nordic"`. Package selection/compatibility rules are unchanged, and
+parse acceptance does not prove that an installed package provides the theme.
+Source: [UI profile parser](https://github.com/Cratis/Screenplay/blob/main/Source/DotNET/Screenplay/Parsing/UiProfileParser.cs).
+
 - `target platform` takes a comma-separated list. `web`, `ios` and `android` are
   the documented examples; ⚠️ **the parser accepts any identifier** — there is no
   enforced list, so a typo is silent.

package/package/corpus/skills/cratis-screenplay-ui-composition/verification.json

@@ -3,6 +3,10 @@
   "input": "Declare the application shell, a screen template and a command form.",
   "fixtures": [],
   "assertions": [
+    { "kind": "skill-contains", "value": "Requires Screenplay 4.227.0", "file": "references/ui-profile-and-theme.md" },
+    { "kind": "skill-contains", "value": "theme \"Scene Default Light\"", "file": "references/ui-profile-and-theme.md" },
+    { "kind": "skill-contains", "value": "Empty, blank or unterminated quoted names are `PLAY0229`", "file": "references/ui-profile-and-theme.md" },
+    { "kind": "skill-contains", "value": "package compatibility check", "file": "references/ui-profile-and-theme.md" },
     {
       "kind": "skill-contains",
       "value": "PLAY0685",