Stocktake 2026-11-21: re-verify 5 stale + 2 threshold pages against live state; freshness 0 stale; skills-index 299/67

This commit is contained in:
Tony0410
2026-11-21 03:16:30 +08:00
parent 375d52fa26
commit 95e2cd8357
9 changed files with 100 additions and 27 deletions
@@ -3,9 +3,9 @@ title: Job Radar Stage 1 Exhausted Its Tool-Call Budget on 2026-10-27 — Notion
type: incident
status: resolved
created: 2026-10-28
updated: 2026-10-30
verified_on: 2026-10-30
review_after: 2026-11-13
updated: 2026-11-21
verified_on: 2026-11-21
review_after: 2026-12-21
confidence: high
tags: [automation, cron, jobs, notion, silent-failure, scheduling]
sources: [live-sqlite-cron-executions, live-sqlite-cron-incidents, live-jobs-json, live-notion-api]
@@ -121,6 +121,17 @@ handoff). Stage 1 itself no longer delivers — correct, because stage 2 owns th
The questions this page left open are answered for this run: the handoff **was** written inside budget and
consumed, and **no cover letter went missing on the first real run of the split**.
## Re-verification — 2026-11-21 (stocktake)
Live probe: the split still holds and both stages are healthy — `dca8482e4f76` (Discovery) and
`5fc292ff0f3b` (Write and Letters) are both `enabled: true`, `last_status: ok`, `failure_streak: 0`,
pins unchanged (`custom:omni-101` / `smart-route`). Handoff files are being written every weekday —
latest `~/.hermes/radar-ref/handoff/2026-11-20.json` (7.9 KB), with files present for every weekday
back to 2026-11-13. The cap/budget fault has recurred since this incident (see
[[incidents/2026-11-02-job-radar-stage1-iteration-cap-recurrence]],
[[incidents/2026-11-09-job-radar-stage1-stall-silent-noop]]); both ledger rows this page opened
remain closed `resolved`.
## Related
- [[runbooks/job-radar]] — the two-stage contract, recovery procedure and the 2026-10-26 overrun