Release v4.17.0

Scene's navigation host now composes screens recursively through nested outlets, toolbar buttons open their destinations, the components blueprint gains a settings page, and a runnable webview example shows Scene embedded the way VS Code and Event Models embed it.

Added

• A core:outlet component declares a named nested outlet on a screen. A destination into it opens its screen there and keeps the declaring screen on the page, and the opened screen may declare outlets of its own, so composition nests to any depth. A deep link to the innermost level composes every level above it, and back closes the innermost level. See Navigation diagnostics. (part of #74)
• SceneNavigationContextValue exposes primaryScreen and outlets, which say which screen fills the primary region and each nested outlet. (part of #74)
• A SettingsPage screen template in @cratis/scene.blueprint.components: a module's settings as a generated command form with save and discard. (part of #73)
• A descriptor for the Cratis Components toolbar button, so designers configure its label, icon, text, presentation and destination. (part of #74)
• A runnable embedded webview example renders a custom package set with WebViewPackageHost and forwards cratis.scene.* events to VS Code's acquireVsCodeApi or the parent frame. See Package hosting. (part of #75)

Changed

• The Cratis Components toolbar button runs its attached interactions and opens its authored destination - a dialog or a slice screen - through the enclosing navigation host, or announces it with cratis.scene.navigate outside one. (part of #74)
• The business pattern coverage matrix now states its prioritized decisions and the specifications that hold each one. See Business pattern coverage. (part of #73)