Overview
dsh-notify
README / EN
Package documentation
Registry summary
dsh.pub verifies the pinned bundle contract, runtime facts, and distribution semantics. The complete README remains in the source repository.
Read the full README on GitHubLIMITATIONS
Known limitations
- **SMTP not implemented**: email notifications go through an MCP mail bridge (see the example above — any mail MCP server's send tool). - **SAPI unavailable in non-interactive sessions**: System.Speech needs a desktop interactive session (Windows Session 0 services or SSH sessions have no audio device); use webhook/A2A/MCP channels there. - **A2A is one-way `message/send` only**: no SSE subscription, no task polling — accepted means sent; use a full A2A client if you need to read task results. - **MCP is a minimal implementation**: SSE responses parse only the first frame; an expired session makes the next call fail into the retry/failover chain (the retry re-handshakes, so it self-heals). - Notifications are not persisted: dispose flushes only 2 s, the rest is dropped. - `askUserQuestion: 'auto'` treats the `webServer` service as “has a web layer”; a third-party frontend that doesn't register that service looks like headless — set `'on'` to force. - After an escalation fires, that session's pending table is cleared, so later resolution signals no longer trigger “confirmed” (avoids duplicate noise).