Release v4.59.0

Added

• Specification case tables (Screenplay decision 0046) render as one specification class per case, named from the derived <Specification>_<Case> specification. Two case names that normalize to the same generated file are refused with STAGE-CRATIS-004 instead of overwriting each other. (#256)
• A failing case in a Stage specification run names its case and its effective fixtures, in the same Case '<Case>' of '<Specification>': … Effective fixtures: … form as Screenplay's reference runner, in both the SpecRunner report and the Host's run results. (#256)
• SpecificationExpansion.ExpandAll returns every effective specification of an authored specification, including each case of a table. LoadedSemanticModel.SpecificationOrigins and SemanticSpecificationRunOptions.SpecificationOrigins carry the compiler's case provenance into a specification run. (#256)

Fixed

• The syntax-based CratisRenderer renders every case of a specification table instead of failing on the table. SpecificationRenderer.Render refuses a whole table with an InvalidEventModel that asks for one call per case. (#256)