[bug] SchedulerWatch and CloudPager text only through Relay (sendOwnText) #2780

What happened

SchedulerWatch and CloudPager text only through Relay (sendOwnText). On an install without Relay every alarm fails with 'no own number in bridge config', which appears only as an error line in pulse-stderr.log, so the principal never learns that an alarm fired or that the alarm path is dead. Expected: Doctor flags the pager as having no delivery channel, and a failed own-line send is surfaced somewhere the principal reads (a Vigil event or the Pulse dashboard), or a second own-line channel is supported.

Summary

LIFEOS/TOOLS/SchedulerWatch.ts sendOwnText() is the only own-line sender for both pager legs that pulse.ts runs every 5 minutes (SchedulerWatch.ts heal and CloudPager.ts once). It reads the Relay bridge config and, when there is no own number, returns { ok: false, reason: "no own number in bridge config" }. The pager then exits non-zero and Pulse writes one error line to PULSE/logs/pulse-stderr.log. Nothing else records it: Doctor reports the install healthy, no Vigil event is emitted, and the dashboard shows nothing.

On a macOS 8.761.0 install without Relay, heal detected a freeze and the text failed twice ("texted":false,"textResult":"no own number in bridge config"). That freeze turned out to be the post-reboot false positive from #2537, but a real one would have been silent in the same way.

Expected, any of: Doctor names the pager as having no delivery channel; a failed own-line send becomes a Vigil event or a dashboard line; or a second own-line channel can be configured.

Details

• Kind: bug
• LifeOS version: 8.761.0

Filed with the LifeOS /feedback command. The reporter approved this exact text before it was sent; paths, secrets and personal details were stripped locally.