Application Lists Refresh as Snapshots

Context

An open tab can outlive licensing or personal-access changes, and Platform itself uses cached authorization data.

Decision

Retain a snapshot, refresh applications after coded refusal or an aged-tab return, and install only results valid for the current workspace ticket. Services remain responsible for request authorization.

Alternatives Considered

Push updates need a delivery channel. Refreshing on every focus adds a request for every window switch without eliminating server-cache delay.

Consequences

Silent failure retains the previous list. Narrow refresh leaves roles and permission rules unchanged. Product still needs to settle the returning-tab refresh scope.