Remote Control servers under claude daemon split out from the rest of the daemon

What

claude daemon manages a background service that runs Claude Code work for you. Its subcommands were all refused behind one switch. Remote Control now has its own path.

• claude daemon remote-control now has a separate availability check. It can pass when the remote flag tengu_radiant_heron is on. list, scheduled and hub still exit with "is not available in this environment".
• claude daemon help gains a Remote Control servers section, shown only when Remote Control is allowed. It lists:
  • remote-control list [--json]
  • remote-control add [--dir <path>] [--name <n>] [--spawn-mode same-dir|worktree]
  • remote-control remove <name-or-dir>
• The help notes that add and remove require the service to be installed.
• The remote-control server command now runs an extra check before it resolves --dir and checks whether the folder is trusted. If that check returns a reason, the command exits with it, except under one condition.
• claude daemon status prints extra lines about served folders, and worker status reports a servedFolder with its folder and session count.

Why

Remote Control under the daemon can now be switched on without the rest of the daemon. The commands for adding and removing Remote Control servers are documented in the help. The server command may now refuse earlier than before, with a new reason.