Managed settings are re-checked after remote settings load at startup

What

Managed settings are settings an organization's administrator controls, and some of them arrive from a remote server when Claude Code starts. Two startup checks now make sure those values actually take effect.

• Login restriction: the check that pins sign-in to an organization now refreshes the managed settings first, and runs a follow-up step if the refresh reports something new. It then reads forceLoginOrgUUID and forceLoginMethod from the refreshed settings, falling back to the earlier reading when the refreshed value is missing. Before, the settings were read once with no refresh.
• Inconsistent reads: when, after the remote settings load, one read of a settings file finds settings and another finds none, Claude Code logs "Settings: after the remote settings load, one read of a settings file found settings and another found none, so the settings are applied again", clears its held-back change notice, and applies the managed settings again.

Why

A managed setting delivered remotely is now honoured during the same startup instead of possibly being missed. For an organization pinning logins with forceLoginOrgUUID or forceLoginMethod, that means the restriction applies on the first launch after it is delivered.