Wire Windows scheduler helper to cursor, hermes, and generic hosts

Context

PR #546 added the reusable Windows Task Scheduler helper and wired it only to claude_code first. The next Windows gap is to reuse the same helper for host adapters that also rely on OS-level scheduling and do not have a native scheduler: cursor, hermes, and generic.

codex, openclaw, and workbuddy should remain out of scope because they use host-native scheduling systems.

Scope

• Add schedule_command wiring for cursor and hermes using their headless commands.
• Add a generic path where the command is provided/configured by the user.
• Ensure schedule {install,uninstall,status,verify} is exposed only for the hosts that set schedule_command.
• Update install/bridging/uninstall docs for these hosts with Windows Task Scheduler instructions.
• Add focused tests matching the claude_code coverage pattern from #546.

Acceptance Criteria

• On Windows, cursor/hermes/generic have deterministic install/uninstall/status/verify behavior through the shared scheduler helper.
• The task name follows memu-bridging-<host> consistently.
• Hosts with native schedulers still do not expose the shared schedule verb.
• Existing cron/launchd behavior is unchanged.

Planning

Priority: P2 Size: M Schedule: Next Owner: @ankaisen

Related: #546, #539, #538