Bundle Stage 4.79.1 and Screenplay 4.145.1: admit ESM v11–v13, model notes, empty scopes, Copilot adapters

[woksin]

The CLI catches up with the current Stage and Screenplay releases: cratis render admits models up to ESM v13, the embedded Screenplay MCP server carries model notes, and Copilot loads the Cratis AI instructions natively.

Added

• cratis render admits ESM v11 (lossless Double-mode number literals), v12 (explicit enum member numbers) and v13 (concept compliance markers such as pii and secret). ESM v14 query filters stay refused with CLI-RENDER-004 until the bundled renderer admits them. (Admit Screenplay ESM v11 in cratis render once Stage supports it #332)
• cratis screenplay mcp serves the model-notes tools from Screenplay 4.144: list-model-notes, propose-model-notes, read-proposal with view: "notes", and run-specifications with a proposalId to run a retained proposal's candidate model before apply. The reference explains that .screenplay/notes.json is owned by the server, committed with the model, and never blocks opening a model, and shows where to gate on open questions with screenplay check --open-questions report|fail. (Bundle Screenplay model notes: list-model-notes, propose-model-notes, --open-questions #340)

Changed

• Bundles Stage 4.79.1 and Screenplay 4.145.1, and runs cratis/stage:4.79.1 by default. Server-generated UUID values, scalar and named command responses, and event-triggered reactions now render instead of being refused.
• cratis ai install and cratis ai update link .github/instructions to the corpus's generated Copilot adapters (.cratis/ai/harnesses/copilot/instructions), so Copilot applies the Cratis rules by path. An older corpus without those adapters keeps the link to .cratis/ai/rules, and cratis ai update relinks existing installs. (cratis ai: link Copilot path instructions to the generated harnesses/copilot/instructions adapters #341)

Fixed

• cratis render --scope on a module or feature whose slices were all removed now checks only application-level declarations, so errors in unrelated slices no longer block removing the scope's previously rendered files. Application-level errors still refuse the render and leave the published output untouched. (Compile empty render scopes without unrelated slice admission failures #334)

[woksin]

Reviewer notes (not release notes):

• Pins: Stage 4.73.1 → 4.79.1, Screenplay 4.137.0 → 4.145.1 (approved by woksin in-session; Directory.Packages.props only these two lines).
• cli#333 was already delivered by Move the CLI to Stage 4.73.0 and render navigation metadata and toolbars #336 (v3.53.0) and is closed; Stage 4.79.1's ContributionConverter still carries navigation id/icon/presentation/group/destination.
• cli#340: no cratis screenplay validate --open-questions. Screenplay 4.145.1 exposes ModelNotesStore/ModelNotesAnchors publicly, but the root-aware loader that resolves persisted identities and scope (McpState, ModelOpenQuestions) is internal; reimplementing it would duplicate the notes format. The issue's documented alternative applies: the reference points to screenplay check --open-questions report|fail.
• Stage 4.74 renders server-generated UUID concepts, so the scope-isolation spec's unselected-slice refusal moved from STAGE-ESM-028 to STAGE-ESM-038.
• --engine (semantic execution for cratis run) stays in cli#324, gated on Move the live Stage runtime path to the Screenplay executable semantic model Stage#23.
• Local gates (mirroring build.yml): Release build (0 warnings), whole dotnet test Release (4111 passed, 6 Windows-only skips), Markdown docs gate, sentinel pack, packaged Screenplay placement, rendered React application (5/5 assertions). CI's Windows/macOS workspace-admission matrix and native linux-x64 placement were not run locally.
• Review: cross-provider review (Opus 5.5 + GPT-6.1 Sol), round 1 found one doc inaccuracy about ESM v11 (numbers exact still does not bind) — fixed in 7bc1b48; round 2 delta review on that fix.