Admit ESM v16 (stored event names) in cratis render #353

Screenplay 4.152.0 adds ESM v16: an event contract carries storedName when its id pin differs from its name, so a renamed event keeps storing under the name its events already use (Cratis/Screenplay#704). Consumers must admit v16 explicitly.

cratis render admits ESM v1–v15 today. Once the bundled Stage renders stored event names (Cratis/Stage#372), the CLI should:

• bundle Screenplay ≥4.152.0 and the Stage release that admits v16,
• admit v16 in RenderedSemanticVersions (newer versions stay refused with CLI-RENDER-004),
• document the stored-name behavior in the Screenplay reference.

Until then a model with a differing event id pin compiles to v16 and cratis render refuses it with CLI-RENDER-004, which is the safe outcome: rendering it with a v15 renderer would store events under the new name.

Status

State: Done — Released in v3.60.0 (PR #357).
Branch: cli-esm-v16 (#357)
Scope: Prepare Screenplay 4.152.0 bump now (branch cli-esm-v16); admit v16 + Stage bump once Cratis/Stage#372 ships. One minor PR.
Delivered: Nothing yet.
Remaining: To be confirmed.
Follow-ups: None.