## Why
Running threads need to pick up changes to approval requirements and
Guardian policy when users reload configuration, sign in, or sign out.
## What changed
Refresh Guardian policy after publishing local config layers so the first
reload uses updated policy fallbacks. Attempt the refresh even if unrelated
user configuration fails to load.
Refresh policy after login while the account owner is still current, and
after logout. If reading account details fails after login, report the
error in the login completion notification and still send the account
update.
## Testing
Extend coverage for changing and removing Guardian policy requirements,
applying requirements despite a config load error, and picking up local
fallbacks on the first reload. Verify that a late low-risk score cannot
release a pending adaptive approval while stricter requirements apply.
GitOrigin-RevId: 95453807a06a0d3c39dcfd9a0f66fd63f41294b9