wiki(audit): 2026-10-29 window — Conduit voice fault documented and repaired; radar two-stage split resolved both incidents (20 pages, 2 letters, Notion 455->475); cron 176/0

This commit is contained in:
Tony0410
2026-10-30 00:21:21 +08:00
parent cc95dcc54d
commit 1d335ca8e6
10 changed files with 404 additions and 82 deletions
+28 -3
View File
@@ -3,9 +3,9 @@ title: Daily Marketing Job Radar Operations and Recovery
type: runbook
status: active
created: 2026-07-27
updated: 2026-10-29
review_after: 2026-11-10
verified_on: 2026-10-29
updated: 2026-10-30
review_after: 2026-11-13
verified_on: 2026-10-30
version_applies_to: Hermes Agent cron dca8482e4f76 (stage 1) + 5fc292ff0f3b (stage 2)
confidence: high
tags: [automation, cron, jobs, notion, dashboard, runbook]
@@ -328,6 +328,8 @@ now owns a job of its own and the writes own a second one.
- First fires: two test runs of stage 2 on 2026-10-27 (17:35:00 → 17:36:52 and 17:38:38 → 17:43:42), both
`completed` with delivery `suppressed`. **The first real 07:00 → 11:30 cycle
ran on 2026-10-28 and landed nothing** — stage 1 never wrote its handoff (see the 2026-10-28 slot below).
✅ **The second real cycle (2026-10-29) completed end to end** — handoff written, consumed and delivered; see the
2026-10-29 slot below.
**Recovery if stage 2 lands nothing:** check that stage 1 actually wrote its handoff file before running stage 2
by hand (`hermes cron run 5fc292ff0f3b`). A stage-2 run with no handoff is a no-op, not a failed search — do not
@@ -351,6 +353,29 @@ discovery stage is the thing to bound, not the wall clock.
Full ledger: [[incidents/2026-10-28-job-radar-stage1-iteration-cap]].
### 2026-10-29 07:00 slot — the split finally finished: handoff written, consumed, and delivered
Stage 1 (`dca8482e4f76`) ran **07:00:59 → 10:16:12 AWST** (**3 h 15 m 13 s**) and closed **`completed`** — the first
post-split run to finish *and* write its handoff. `~/.hermes/radar-ref/handoff/2026-10-29.json` (24.8 KB) records
`run_date 2026-10-29T08:23:51+08:00`, **170 discovered / 33 duplicates avoided / 37 verified**, sources
`seek ok`, `linkedin ok`, `indeed blocked`, `wa_gov ok`. Both of the ledger rows the previous two days opened
(`dca848_e93a538ade6b`, `dca848_0a2f03b5952b`) **closed `resolved` at 10:16:12**, and this run opened no new row.
Stage 2 (`5fc292ff0f3b`) fired at **10:13:46**, consumed the handoff at **10:40:59**, closed **10:44:48 `completed`**
and **delivered to topic 1030 in the same second**. Its `stage2_result`: **20 pages written / 20 `page_ids` /
2 cover letters / 2 same-day strong matches / `verified_cover_letter_count 2` / `missing_cover_letter_count 0`** —
the Notion board went **455 → 475**. The 11:30 and 14:30 slots then no-oped exactly as designed
(**10 m 46 s** and **1 m 51 s**, handoff already consumed).
**What this does and does not settle:**
- The split's core promise holds in production — the writes can no longer be lost to a discovery overrun, and the first
full cycle landed 20 pages and 2 cover letters with **zero missing**.
- It does **not** mean discovery is fixed. 3 h 15 m is still long, and the 10-27 **tool-call budget** and 10-28
**iteration cap** remain reachable. Treat a `completed` stage-1 row with **no handoff file** as the same fault,
whatever the execution status says.
- Stage 1 no longer delivers (verified live: `deliver: local`); its failure route to topic 1030 is unchanged.
## Browser-layer hazard inside the run (2026-10-12)
This job is the most browser-heavy cron on the estate, and on **2026-10-12 (07:01 → 07:33)** it drove