Cleanup is skipped when server-managed settings can't be read

What

Claude Code periodically cleans up old files in the background, such as past conversation transcripts. Retention cleanup is the part that deletes old ones. It now checks whether server-managed settings (settings an organization pushes from Anthropic's servers) can be known first:

• When the session reads no stored server-managed settings and holds none of its own, retention cleanup stops and returns remote_settings_unknowable. The log reads "Skipping retention cleanup: this session reads no stored server-managed settings". Before, cleanup only looked at user settings and policy settings.
• Background housekeeping waits for that result. When it is remote_settings_unknowable, it does not write the .last-cleanup marker and skips a later cleanup step. Before, it always wrote .last-cleanup.
• Cleanup gains a helper that waits for settings.read hooks before the sweep starts.
• A new check, read by the finding as a test for a session with no disk, makes several disk writes give up: saving remote settings, peer file transfer, file attachments, reading an update result, and writing an inbound attachment.

Why

If a setting that controls how long files are kept could only come from the server and is not available, Claude Code no longer goes ahead and deletes files under rules it can't see.