Fix runtime-error report schedule templates and prepare 1.9.1

[quolu]

Summary

The hourly runtime-error report templates shipped in 1.9.0 started the CLI through its env node shebang. A service manager does not read the login shell's PATH.

• launchd: the default PATH is /usr/bin:/bin:/usr/sbin:/sbin. With Homebrew Node the agent exits 127 (env: node: No such file or directory).
• systemd user unit: with nvm, the unit resolved /usr/bin/node v22.22.1 instead of the installing Node v24.14.1.
• Windows: there was no template, only a README sentence.

Change

• The systemd service and launchd plist take REPLACE_WITH_ABSOLUTE_NODE_PATH and REPLACE_WITH_ABSOLUTE_SPOTTER_SCRIPT_PATH and start Node directly.
• ops/runtime-reporting/windows/install-runtime-errors-task.ps1 registers the hourly spotter-runtime-errors task (interactive logon, hidden console), in the same style as the dashboard installer.
• README.md and README.ja.md describe both. test/runtime-reporting-ops.test.mjs pins the three forms.
• Version 1.9.1 and changelog.

Verification

• The rendered service and plist are byte-identical to the definitions already running under systemd and launchd on three owner terminals (exit 0).
• The Windows installer was run on a Windows 11 terminal under a temporary task name: installer exit 0, task result 0, repeat PT1H.
• npm test: 616 pass, 0 fail, 4 skipped. npm run verify:docs passes.

The sender, its config, credentials, and payload are unchanged.

🤖 Generated with Claude Code