Release v4.105.0

Added

• A slice that declares screens now gets its own Screens.scene.json in its folder, listing that slice as its source, so a consumer such as Studio's slice Preview can show a slice's screens. The application's scene.json is assembled from the same fragments and stays byte-identical. Slice- and feature-scoped plans emit the selected slices' fragments, byte-identical to an application plan, and leave out the application-wide Scene files with an informational diagnostic, so a scoped write never leaves them partial. Screen ownership supplied by a caller is checked against the compiled model: an owner that doesn't declare the screen, or a stale screen payload, fails planning. (#400)