Release v2.22.2

Changed

• Attested invitation completion reports bounded, value-free diagnostic reasons so operators can distinguish failed completion checks without exposing invitation or identity data. Duplicate-subject refusals are logged consistently on both invitation paths. (#118)

Fixed

• Attested invitations display the unavailable-email page when the provider supplies no usable address, and the email-mismatch page when the address differs or is not explicitly verified, rather than collapsing these outcomes into a generic invalid-link page. The documentation distinguishes strict attested verification from the unchanged legacy unsigned exchange. (#118)
• OIDC providers can complete attested invitations using the already-validated canonical session identity instead of failing because the protocol's authentication-type value differs from the configured scheme. (#122)
• Attested completion retains the invited recipient captured before authentication is awaited. Reloading invitation configuration during completion cannot relax the verified-email requirement or switch the recipient being matched. (#118)