fix: persist and retry run alerts and honor notification modes
This commit is contained in:
+15
@@ -574,6 +574,21 @@ Everything else is free-form and preserved under the step's `markdown` output.
|
||||
the run. Artifacts are served from `/artifacts/<run>/<step>/<name>`; shared files
|
||||
appear with a `public/` prefix.
|
||||
|
||||
### Run notification modes and receipts
|
||||
|
||||
`--notify auto|on|off` records `notify_mode` on the run (also returned in
|
||||
summaries and `run_event` frames). Auto retains stage policies and run-level
|
||||
waiting/failure defaults. On also alerts terminal success without requiring a
|
||||
stage hook. Off suppresses stage, run-level system and browser tray alerts.
|
||||
|
||||
`inspect --json` / `get_run` includes top-level `notifications` receipts with
|
||||
`sequence`, `event`, `channel`, `status`, `attempts`, and optional `diagnostic`
|
||||
and `message_id`. Status is pending, sending, sent, failed, or covered (already
|
||||
published by the stage). Run-level system alerts persist and retry at most three
|
||||
times, recovering pending work after restart. A publisher acknowledgement is not
|
||||
proof of reception; a crash before saving it can duplicate a message. See
|
||||
[`notes/audit-notifications.md`](notes/audit-notifications.md) for limits.
|
||||
|
||||
## Investigating runs with a configured harness
|
||||
|
||||
On the runs list or inspector, press `D` or use `:debug`; CLI equivalent:
|
||||
|
||||
Reference in New Issue
Block a user