Windows schedules create JSON parsing and interval mismatch

[agent-zhang-beihai]

What happens

On Windows PowerShell, schedules create rejected valid header JSON and then exited with a libuv UV_HANDLE_CLOSING assertion. The documented '1 minute' interval was also rejected although the scheduling guidance allows minute interval syntax.

Command

insforge schedules create --headers <json> --cron 1 minute

Error

Invalid JSON for --headers; Assertion failed: UV_HANDLE_CLOSING; cronSchedule invalid

Expected

Accept valid JSON passed as one argument and documented minute interval syntax without crashing.

Workaround

Used PowerShell stop-parsing with escaped JSON and a five-field cron expression: * * * * *.

Triage finding

CLI --cron help still advertises "5 minutes" in published 0.2.8, but backend #1159 shipped seconds-only (/^\s*(\d+)\s+seconds?\s*$/i) and rejects minutes by design — fix the help string in schedules/create.ts:17 and update.ts, not the skill doc (that one is already correct); the --headers failure is PowerShell quote-stripping (docs-only), and the untracked UV_HANDLE_CLOSING crash likely comes from handleError's hard process.exit() racing the awaited PostHog/undici teardown.

· win32 10.0.26200

Filed automatically from user feedback.