v1.1.0

Added

• runwisp start, plus stop/restart now also accept a task or service target: runwisp start|stop|restart <target...>. A target is a name, a shell-style glob ('*' for everything), or — for stop — a run ID. Multiple targets can be given at once. --url/--password (or RUNWISP_URL/RUNWISP_PASSWORD) dispatch to a remote daemon, same as runwisp run.
• start/stop/restart now work on tasks, not just services: start triggers a run (no-op if one’s already active or queued), stop cancels the active run and drops anything queued, restart does both in sequence. manual_trigger = false now locks all three verbs for tasks too, matching services.
• New POST /api/tasks/{task}/start endpoint.
• The Web UI asks for quick feedback after an hour of uptime, at most once a month: a one-tap rating plus an optional note, sent to the maintainers. It can be dismissed, and check_updates = false turns it off.

Changed

• POST /api/tasks/{task}/stop and .../restart now act on plain tasks instead of returning 400 Bad Request.
• Notification emails now use RunWisp’s colours instead of a generic blue theme.

Fixed

• Subcommand --help output now ends with the pointer to the machine-readable agent docs when it isn’t a terminal.
• A jittered crontab task that RunWisp takes over after the system cron daemon stops now keeps its jitter start-spread instead of firing at the raw tick until the next reload.
• A log stream requested with a negative from larger than the replay limit now replays the newest lines instead of the oldest, so no lines go missing before the live tail.
• Notification durations no longer render as ”60s” or “59m 60s”; they round up to “1m” or “1h”.
• runwisp import cron now warns about a user column on @reboot, @daily and other @-shorthand lines (suggesting --system) instead of importing the username as the command.
• Live output from programs that redraw the screen no longer marks every line after an over-long line as a continuation.