Release v4.15.0

Added

• A render profile can carry the model's .strings catalog. Generated validators then resolve $strings.<key> rule and requirement messages for the request's UI culture, falling back through its parent cultures to the default locale. The key stays in the validation result's state, and generated rejection specifications compare that key, as the Screenplay reference does. A key missing from the default locale fails planning with STAGE-ESM-018. Without a catalog, $strings messages are still rejected. (part of #116)

Changed

• Update to Screenplay 4.30.0 and Chronicle 19.4.8, including the Host's bundled kernel image and the Chronicle client and image pinned for generated applications.
• Screenplay ESM v3 models are admitted. Their new constructs fail closed:
  • reducers with implementation bodies are rejected with STAGE-ESM-019;
  • code validations and rule predicates are rejected with STAGE-ESM-005;
  • opaque policies are rejected with STAGE-ESM-015.
    The semantic specification engine and the semantic sandbox report the same constructs as typed Unsupported. A v3 model that uses none of them renders exactly as it did as v2. (part of #119)