Sandbox tracks new write blocks for claude ssh binaries and symlinked paths

What

The sandbox limits which files commands run by Claude may change. It gains two new write blocks, each controlled by a remotely served (GrowthBook) value:

• A write block on claude ssh binaries, tracked as sshStoreDenyApplied and builtConfigSshStoreDenied.
• A switch that applies write-deny patterns through symlinks (shortcuts that point to another file), tracked as patternWriteDenyTwinsApplied and builtConfigPatternWriteDenyTwins. When the sandbox settings are built, a flag (Q4()) is now passed to the code that builds the write-deny list.

These are recorded for each built sandbox setup, beside the existing host rules and configured denies. The sandbox now watches both remote values and rebuilds its settings during a session when either changes.

Other changes in the same area:

• The settings-file watch list and launch-path helpers now combine two sources of launch paths instead of one.
• The Windows start flag changed from a yes/no value to a start time.
• isOnButNotRunning is now available from the sandbox manager.

Why

Sandboxed commands can be blocked from writing in more places, and a change to these blocks can take effect without restarting Claude Code. Whether either block is applied for you depends on the remotely served values.