Org memory policy check gains a 'held' state while the verdict loads

What

Organization memory lets memory be synced for a team rather than kept only on one machine. The check that decides whether it is allowed used to answer only yes or no. It now has three states: open, closed and held. held means the organization's policy verdict has not arrived yet. open is returned only when the policy permits allow_memory_sync.

• The memory watcher, which starts syncing, now waits for the verdict before it starts. It stays off when HIPAA evidence or another problem means no verdict can be obtained. The allow_memory_sync policy is denied under HIPAA and zero data retention (ZDR) arrangements.
• Memory has a 'tools' mode and a 'files' mode. The choice now also picks tools mode whenever the policy state is anything but closed, including while it is still held. Before, tools mode needed allow_memory_sync up front, so it can now start before the verdict loads. The tengu_linen_orbit switch can still turn tools mode on as before.
• The discovery of synced project memory now returns quietly when the state is held, instead of logging that the gates are closed.

The policy check itself depends on the tengu_haze_glass flag and on CLAUDE_CODE_DISABLE_ORG_MEMORY being unset. CLAUDE_MEMORY_STORES is also part of the discovery chain.

Why

In practice, organizations where synced memory is being rolled out can get tools-based memory without waiting for the policy verdict, and sync does not start until that verdict is known. Setting CLAUDE_CODE_DISABLE_ORG_MEMORY still turns the organization memory check off.