A slot for remembering a sandboxed-retry decision exists with nothing reading it.
The sandboxed-attempt cache slot is declared beside the plan-mode guard and never read.
What's wrong with this entry?
The per-session store that remembers gate answers gains a slot for a sandboxed-attempt decision, sitting next to the plan-mode resume guard. Nothing in the build reads it, so it looks like groundwork for a sandboxed retry behaviour that has not shipped.
sandboxedAttemptGateEnabled;
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
macOS sandbox re-applies read and delete denials inside writable folders
Both mention sandbox
-
v2.1.236
Sandbox proxy no longer writes to sockets that have gone away
Both mention sandbox
-
v2.1.236
IPv6 hosts through the proxy
Both mention sandbox