Release v4.165.0

Added

• A repository can declare its Screenplay validation gate in a committed screenplay.json at the model root: the checks, warningsAsErrors, scope and openQuestions the screenplay check command runs, so scripts and CI no longer repeat the options. The model root is the nearest folder at or above the target that holds screenplay.json or .screenplay/. A command-line option overrides only its own value, --no-gate-file ignores the file for one run, and a file with an unknown key or check name is refused with its location rather than ignored. See decision 0076 and the screenplay-v1 JSON schema. (#739)
• The screenplay check command gains --format json, which writes one JSON report with the diagnostics, open questions and the effective gate, and --print-gate, which prints the effective gate and where each value came from without compiling. (#739)
• ScreenplayValidationGate.Read, ValidationGateRoot.Resolve and ValidationGateResolver.Resolve in Cratis.Screenplay let other tools read and apply the same gate. (#739)