Cloud sessions on self-hosted runners stop sending your settings' permission mode and effort

What

When Claude Code creates a cloud session (one that runs on another machine, for example with --remote), the request now says where the permission mode (how much Claude may do without asking) and the effort level came from. New fields personAskedForSession, isModeFromSettings and isEffortFromSettings tell an explicit request apart from a value that only came from your settings files.

• Self-hosted runners: if the session runs on a self-hosted runner (a machine your organization runs), a permission mode or effort that came from settings is no longer sent. Before, the permission mode was always sent. The result is marked with settingsModeOnRunner (not_sent or not_pushed), with self_hosted_runner given as the reason.
• Notice: new code compares the mode with and without your settings. If your settings' default permission mode doesn't apply on a self-hosted runner, a notice tells you to relaunch with --permission-mode. It is shown as a warning when the mode is plan. The finder did not locate where this notice is called from.
• Timing: the permission mode notice is now worked out after the session has been created, using the mode the runner reports, rather than only from the decision made before creation.
• Sign-in: attaching to and creating a cloud session now go through an extra authentication step first, and the access token is chosen from your profile (consoleProfileBearer).

Why

The mode shown for a remote session may now match what the runner actually applied. On a self-hosted runner, a default mode in your local settings no longer carries over, so pass --permission-mode on launch if you want a specific mode there.