[BUG] Remote Control: /compact (and other doc-supported commands) missing from the / selector on web/mobile

What happened

In a Remote Control session (steering a running CLI session from the web/mobile UI), typing / opens the slash-command selector, but the list is a curated subset that does not include /compact — even though the Remote Control docs list /compact among the text-output commands supported from mobile and web.

So there's a parity gap between what the docs say is supported and what the / selector actually surfaces. Because /compact isn't a selectable entry, the only way to invoke it remotely is to type it out in full and send it — at which point it's ambiguous whether it executes as a command or gets routed to the model as plain text (see #68252, which documented exactly that routing failure for Remote Control slash commands).

Expected

Any slash command the docs list as Remote-Control-supported (/compact, /clear, /context, /usage, /recap, etc.) should appear in the / selector on web/mobile, so it's discoverable and guaranteed to route as a command rather than plain text.

Actual

• / selector on Remote Control shows only a partial set; /compact is absent.
• No UI affordance confirms a hand-typed /compact will execute vs. be treated as a prompt.

Impact

Users can't reliably compact context from the remote surface — the one place (long-running session on a phone/browser) where hitting the context limit is most likely and least convenient to fix. Falls back to needing terminal access.

Suggested fix

Drive the Remote Control / selector from the same allowlist the docs are generated against, so selector membership == documented support. If a command is intentionally not offered remotely, remove it from the Remote Control docs list to keep the two in sync.

Environment

• Claude Code: 2.1.170
• Platform: macOS 26.5.1 (host CLI); Remote Control via web/mobile
• Related: #68252 (Remote Control slash commands routing to model as plain text)