Published Apps reuse validated language catalogs for the same tenant, user session, execution, frontend revision and language. Routine authorization refreshes no longer download an unchanged catalog; updates and identity changes select a new cache entry.
Runtime authorization still runs before cached translations are used. No SDK, App image or database migration is required. The PHP SDK guide now documents public Actor identifiers and unlinked Party handling.
Upgrade migration evidence accepts up to 2 MiB within the existing 3 MiB completion envelope, so multi-table fresh/baseline/upgrade reports are recorded without dropping observations. All schema, identity, integrity and pass/fail checks remain mandatory.