Forwarding your home settings to a cloud session now records your consent separately from permission.
What's wrong with this entry?
--forward-home-settings (used with --cloud or --environment) no longer just flips a boolean. Startup resolves a consent value and passes it through to session creation, so the fact that you consented is tracked separately from whether forwarding is allowed at all, and a settings-upload status feed now sits alongside the existing file-sync one.
- Consent is carried into the create call and reported in telemetry as
home_settings_host_consent; the created session's permission mode is echoed back. - A new refusal reason covers sessions "launched from your home directory (or above it, or inside a checkout rooted there)", which cannot be bound.
- The launch options dropped a settings-plan wait timeout in favour of the consent value, and the consent-surface check can now be short-circuited by the host's answer.
home_settings_host_consent, homeSettingsConsent, replaceHomeSettingsHostConsent, launched from your home directory (or above it, or inside a checkout rooted there)
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.