Release v4.17.0

Added

• Render inputs can carry a Screenplay model's implementation attachments: the compiler's requirements and each resolved body, keyed by requirement id. Inline bodies come from the source; file bodies are loaded through Screenplay's AttachmentFiles from the model root. LoadedSemanticModel exposes the requirements, the bodies and the loader's attachment diagnostics, and new CratisRendering.Plan overloads accept them.
• Planning verifies every supplied body against its requirement's content hash. A body the model references that is missing, refused by the loader, or changed since compilation fails with STAGE-ESM-020, which names the requirement and the loader's reason (PLAY0430–PLAY0434), and no artifacts are produced.

Changed

• Code validation, reducers with bodies and code policies are still rejected, and their diagnostics now name only what is still missing: Arc does not supply the received-at time for RuleContext.Occurred or PolicyContext.Occurred, Stage does not yet enforce the pure capability, and reducers wait for Screenplay's typed context descriptor.
• The renderer guide describes the attachment envelope, what planning verifies, and that a single-file model's root is its folder.