Release v3.67.0

cratis render and cratis run now render and run the application shell - navigation regions across modules, toolbar slice dialogs, deep links - on Stage 4.119.1, report their authoring errors with codes before Docker starts, and never ship sample data.

Added

• cratis run reports compiler errors about the application shell - a navigation item that targets nothing or a slot no layout declares (PLAY0747-PLAY0750), a toolbar button that names a slice that is not a State Change slice (PLAY0762), a sample data selection no pack satisfies (PLAY0714) - with their code and file(line,column) location and exit code 5, before it starts Docker. (part of #367)
• The CLI's CI runs an application shell fixture (Integration/Cli/Shell: three modules that inherit, override and extend the sidebar, a toolbar button that opens a State Change slice as a task dialog, a sample data pack) through cratis run on a live Stage and through cratis render, a build and a launch, and drives both with one browser scenario: topbar and sidebar per module, active module and feature, dialog fields from the command schema, cancel posts nothing, submit posts the command, deep link and back navigation, no sample row in anything that ships. (part of #367)
• Documentation for the application shell in the run and screenplay references. (part of #367)

Changed

• The CLI bundles Stage 4.119.1 (built on Screenplay 4.180.1); cratis run starts cratis/stage:4.119.1 by default. Generated applications pin Arc 22.104.0, and validation rules of every severity on generated concepts now render instead of being refused with STAGE-ESM-038 (an unpinned generated value Stage cannot prove still is).

Fixed

• cratis render no longer publishes sample data. The scene.json it writes is a content file of the generated application that the .NET SDK copies to the publish folder, and it carried the authored sample data packs and the profile's selection; it is now written without them (spec SD6: production output never includes sample data).