#4094 serve daemon enable: add Windows support (service or startup task)

Problem

swamp serve daemon enable (and swamp worker daemon enable) only supports launchd and systemd. On Windows there is no supported way to keep swamp serve running, so workflows with trigger.schedule only fire while a console session happens to be running swamp serve. Scheduled runs are not caught up after serve was down, so a Windows user cannot get reliable scheduled workflows without falling back to the OS task scheduler, which bypasses swamp.

Extensions cannot fill this gap: the extension types (behavior, vault, datastore, report, webhook) cannot add or change CLI subcommands or the daemon installer.

Proposed solution

Add Windows support to swamp serve daemon enable|disable|status (and ideally swamp worker daemon), for example by registering a Windows service or a startup scheduled task. It should keep the existing behavior of setting SWAMP_HOME and SWAMP_CONFIG_DIR, forwarding the serve options, restarting on failure, and reporting state through status.

Alternatives

• Run swamp serve manually or via Task Scheduler (not managed or discoverable by swamp, no restart handling).
• Run the daemon under WSL2/Linux (works, but moves the repo and datastore off the Windows host).
• A community behavior extension that manages a Windows service (possible, but not integrated with swamp serve daemon and duplicates its option handling).

Environment

swamp 20261026.014016.0-sha.7e1aad04, Windows.