New connected-session (tengu_violin_maple) and file-sync (tengu_violin_duet) gates for --cloud sessions

What

--cloud (and its deprecated alias --remote) starts a Claude Code session in the cloud. Two new feature gates, switches the server controls, now decide parts of that flow.

• tengu_violin_maple is read by a new isConnectedSessionsEnabled check that is passed into startup checks. It is now another way, besides tengu_remote_backend, to stay attached to a cloud session, and another way, besides tengu_violin_wood, to get trusted-device enrollment and cloud session creation.
• With --attach-serve, the connected-session launch check still uses isViolinWoodEnabled (tengu_violin_wood); otherwise it uses isConnectedSessionsEnabled.
• The offer to sync your directory when creating a session (decideSyncOffer) now needs both tengu_violin_maple and tengu_violin_duet, where before it depended on the tengu_violin_wood check.
• File sync is forced off if either gate is explicitly false from a server payload, an override or a disabled state.
• Both gates are read through a new helper that returns false on error, and returns false straight away, without waiting on the network, when the cached value is not true and came from one of those sources. A built-in fallback only counts when feature values are fresh.
• Session-creation reporting now records whether the connected-session gate was on, off or not yet fetched.

On the readings this site has taken, not under this release, the flag server returned both new gates off for its account and for an anonymous user.

Why

Whether you can stay attached to a cloud session or sync your directory into it now depends on these server-side gates rather than only on the older ones.