Release v4.48.0

Added

• A complianceDetails render option renders Screenplay concept compliance metadata: personal data gets [ComplianceDetails] with its GDPR Art. 9(1) special category or Art. 10 criminal-offence prefix followed by the authored reason, and secrets get [Encrypted] with their encryption scope and reason. The option is off by default, so existing models render unchanged until it is settled whether a details change counts as an event schema change (Cratis/Chronicle#4660). (#250)

Changed

• Event-source routes from Screenplay 4.101 are refused with STAGE-ESM-030 on every rendering and admission path, including the legacy renderer and specification runs, instead of being dropped. (part of #250)
• Screen navigation routes and parameters and dialog-template outlets are refused with STAGE-SCENE-UI-001 instead of being silently dropped, and a semantic or legacy Stage host reports these scene refusals as unsupported instead of failing at startup. (part of #250)