Session storage adapter inconsistency during authentication timeout handling in Zend\Auth

Context

Zend\Auth (Laminas\Authentication) delegates session persistence to interchangeable storage adapters such as Session, NonPersistent, and custom implementations. The framework does not prescribe a unified timeout strategy; each adapter interprets session lifetime and garbage-collection settings independently.

Problem

When an authentication timeout occurs, the resulting identity clearance behaves differently depending on the active storage adapter. A Session adapter may retain the identity until the PHP session expires, while a NonPersistent adapter clears it immediately. Custom adapters that wrap Redis or database-backed stores introduce additional variance because their TTL logic is external to PHP's session handler. This inconsistency makes it difficult to guarantee that a least-privilege enforcement layer (e.g., Laminas\Permissions\Acl) sees a revoked identity at the same moment across all deployment configurations.

Goal

Determine whether a single, adapter-agnostic event or interface exists that reliably signals authentication expiration so that downstream authorization checks can react uniformly.

Specific questions:

1. Does Laminas\Authentication emit a standard event when any storage adapter discards an identity due to timeout?
2. If not, what is the recommended extension point for injecting a consistent revocation callback across all built-in adapters?
3. Are there version-specific changes in Laminas 3.x that address this divergence?