You'll notice
The startup auth snapshot can carry a gateway token, and a locked-file read failure now retries instead of discarding it.
The background-auth snapshot consumed at startup can now include a gatewayToken field alongside accessToken, read via the internal DCt consumer. If a snapshot read hits a transient failure (EBUSY, EPERM, or EACCES on Windows), the snapshot env var is no longer deleted or unset immediately; the failure is logged instead and a later read is allowed to retry.