Remote managed settings: a payload with nothing usable keeps the previous settings

What

Remote managed settings are policies an organisation's admins push to Claude Code from a server. When a payload arrives but no key in it can be applied as written, the result is now called ruled_empty instead of the old invalid_settings:

• Nothing from that payload is applied, and nothing is reset.
• If settings were accepted earlier, they stay in force (logged as ruled_empty_kept_previous). If there were none, nothing is applied (logged as ruled_empty_nothing_kept).
• The failure carries a ruling for each key, which is shown to the user, and is marked so it is not retried.
• The status text now reads "no setting in the server response could be applied as written" or "no setting in the gateway's response could be applied as written", replacing "the gateway's response was not valid managed settings".
• The background check for new settings treats ruled_empty like a successful fetch when deciding whether to re-apply settings.

A payload where only some entries are bad still applies the valid ones.

Why

If an admin pushes a payload where every key is broken, Claude Code keeps the policy it already had instead of treating it as an ordinary failure and trying again.