Release v22.128.0

Changed

• With command read protection enabled, a missing required read model now rejects the command with reason rule and the message <ReadModel> '<key>' does not exist., instead of dependencyUnavailable. Nullable parameters still receive null when the model is missing, and unprotected reads retain their existing behavior. (#3347)

Fixed

• Protected command reads reject empty, whitespace-only, wildcard (*), hash-containing and whitespace-padded keys, including invalid composite key parts, before accessing the store. These failures use the same validation outcome as a missing read model rather than an unhandled server error. Composite key parts are checked through the AOT-safe protected-key accessors, so with ProtectedReadModelKeyOptions.Strict (or under native AOT) a composite key type without registered accessors fails with ProtectedReadModelKeyAccessorMissing instead of being read. (#3347)