Cloud file sync stops cleanly when an organization's compliance policy forbids it

What

Cloud file sync (copying your project files to a cloud session) now has a dedicated way of ending when your organization's compliance policy does not allow it.

• A 403 response (the server refusing access) whose resource is compliance_restricted or zdr_restricted is now treated as sync being unavailable with the cause compliance_restricted. Before, this case had no special handling and fell through to the generic path.
• Claude Code also checks locally whether your organization has a zero-data-retention (zdr) or ldr policy.
• When this happens, sync stops for the session and the session's sync is marked ended. Scheduled retries of the first-upload withdraw are no longer queued.
• The status line reads that your organization's compliance policy does not allow file sync and that the cloud session keeps whatever files it already has. A running session shows "File sync stopped for this session: your organization's compliance policy does not allow it." A separate notice appears when a session is created.
• A new anchor_unavailable ending covers machines that cannot safely place the session's files into the project.

Why

People at organizations with compliance or zero-data-retention restrictions get a clear reason why file sync does not work, and sync stops instead of behaving as though the service were only temporarily down.