Release v3.65.0

Added

• cratis screenplay validate reads the validation gate a repository declares in screenplay.json at the model root: the checks, warningsAsErrors, scope and openQuestions the standalone screenplay tool also reads, through the same Screenplay library. A command-line option overrides only its own setting, and a missing file keeps today's defaults. An invalid or unreadable file is refused with its location and exit 1 before anything compiles. See the screenplay.json reference. (#347)
• cratis screenplay validate --print-gate prints the effective gate and where each value came from without compiling, --no-gate-file ignores the file for one run, and the JSON result carries a gate object in the same shape as the standalone tool's. (#347)
• cratis render accepts Screenplay ESM v18 models: a specification that queries with an out-of-rule key or filter value and expects then error renders as a specification asserting the query's validation failure. Shapes Stage cannot reproduce exactly are refused with Stage diagnostics; ESM v20 models are still refused with CLI-RENDER-004.

Changed

• The CLI bundles Stage 4.106.0 and Screenplay 4.170.0; rendered applications use Chronicle 19.64.1 and Arc 22.95.0, rendered queries take concept-typed keys and filter values again so out-of-rule arguments answer with a validation error, and cratis run starts the cratis/stage:4.106.0 image.