[BUG] Remote Control startup fails with "disabled by your organization's policy" on a personal account; manual retry connects

Remote Control failed to connect at session startup with:

```
Remote Control disconnected — disabled by your organization's policy
```

Running `/remote-control` manually printed the same thing:

```
Remote Control is disabled by your organization's policy. Contact your organization admin for access.
```

I enabled it again a minute later and it connected fine. No config change, same account, same machine, same session.

Two problems:

1. The gate check is returning a false denial intermittently. Same account passes on retry.
2. The error message is wrong. This is a personal account with no organisation attached, so "contact your organization admin" points at someone who does not exist. Looks like the org-policy string is being used as the catch-all for any entitlement denial.

**Environment**

- Claude Code 2.1.257
- macOS 26.5.2 (darwin)
- Personal account, no org, no managed settings file (`/Library/Application Support/ClaudeCode/managed-settings.json` does not exist)
- `~/.claude/settings.json` has `"remoteControlAtStartup": true`

**Expected**

Either the entitlement check succeeds consistently, or a transient failure says so and retries. A denial that clears on retry should not be reported as a policy block.

If the denial is genuinely policy-based, the message should name which policy source produced it - managed settings, org membership or server-side gate - so it can be checked.

Start with the /remote-control entry point and compare its startup path with a manual retry. Check ~/.claude/settings.json and the absent /Library/Application Support/ClaudeCode/managed-settings.json while tracing how the entitlement denial is classified. Done means transient failures are distinguishable from policy blocks and personal accounts receive an applicable message.

Escrito por el modelo de indexación a partir del texto del issue.