Release v22.98.0

Added

• The Screenplay generator states a command specification asserting result.ShouldNotBeAuthorized() as then denied when the denial is explained by the stated authorization: the command has an emitted authorize gate with exactly recovered roles or policies, the scenario has an exactly recovered given caller, the pinned Screenplay reference runner denies that caller, and no other outcome is asserted. See Generating a Screenplay. (#3185)

Changed

• Denial specifications that cannot be stated truthfully stay reported with SP0039, and the warning now names the reason: caller not recovered, policy not recovered exactly, the stated caller satisfies the stated authorization, the denial cannot be decided from the stated caller, the denial is combined with another outcome, no stated policy explains it, or the command's own code can return an authorization denial. (#3185)