v0.4.2: Fix standalone monitor dependencies

Fix standalone monitor startup after Pi-managed installation

The monitor in 0.4.1 could fail with ERR_MODULE_NOT_FOUND: @earendil-works/pi-tui. Pi's managed installs disable host peer installation, while the separate Node monitor cannot use Pi's extension module loader.

• Install the monitor's pinned TUI runtime through the pi-intercom-tui npm alias; leave extension host peers provided by Pi.
• Use the same dependency in monitor rendering tests.
• Add an isolated tarball-install regression with --omit=dev --legacy-peer-deps: no host peers, fresh monitor imports and non-TTY CLI validation. Included in Windows/Linux package CI.
• Align the Node requirement to 22.19+, matching the runtime dependency.

Upgrade

Run pi update npm:@comput/pi-intercom and /reload the coordinator/workers. Explicitly update pinned versions. Restart an existing monitor process to load the new display code. An existing failed monitor pane is preserved rather than automatically restarted.

Config-root discovery is unchanged; this patch only addresses monitor dependency packaging. Stop/close safety restrictions remain unchanged.

Validation

Local typecheck, 112 tests and the isolated packaging regression passed. Publication is gated by Windows/Linux CI. Non-TTY import checks do not claim a live Windows/Herdr terminal test.