diff options
| author | Craig Jennings <c@cjennings.net> | 2026-06-10 15:27:28 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-06-10 15:27:28 -0500 |
| commit | 403f8b891d04780a99859ed7ef64efcc0f4f82f2 (patch) | |
| tree | a903d67d46b2137eac1a95d23a4e517ec829ec80 /scripts/roam-sync.sh | |
| parent | 34c694567b24c7b22b68acb6e4b9860885eefa76 (diff) | |
| download | rulesets-403f8b891d04780a99859ed7ef64efcc0f4f82f2.tar.gz rulesets-403f8b891d04780a99859ed7ef64efcc0f4f82f2.zip | |
feat(triage-intake): loud scan-failure rule + messenger plugin rework
The 2026-06-10 sweep shipped without Signal: a standalone signal-cli receive hung on the account lock while the signel daemon owned it, and the failure looked identical to a quiet source. The engine now renders any failed, hung, or skipped scan in a SCAN FAILED banner at the top of the summary. Quiet means the scan ran and found nothing.
The signal plugin now detects which path owns the account before scanning: when the signel daemon is live it queries chat buffers through Emacs, and the standalone draining receive runs foreground-only when it isn't. The telegram plugin gets an at-a-glance lifecycle (docker-mode launch, scan, send, shutdown only if the scan started the server) and treats a real DM from a work contact as Action.
Diffstat (limited to 'scripts/roam-sync.sh')
0 files changed, 0 insertions, 0 deletions