Harden WSJF triage report recovery
This commit is contained in:
parent
20d4f26166
commit
42e373aba1
10 changed files with 223 additions and 8 deletions
|
|
@ -8,7 +8,7 @@ status: active
|
|||
owner: codex
|
||||
topic_slug: custodian
|
||||
created: "2026-06-03"
|
||||
updated: "2026-06-04"
|
||||
updated: "2026-06-05"
|
||||
state_hub_workstream_id: "5646e13a-13af-4724-bca6-3c0d86f96733"
|
||||
---
|
||||
|
||||
|
|
@ -84,6 +84,11 @@ live modes, plus `tests/test_daily_triage_verifier.py`. `docs/runbook.md` now
|
|||
covers Temporal schedule/workflow checks, `activity_runs`, State Hub progress,
|
||||
working-memory notes, missed-run `skip` behavior, and LLM timeout budget.
|
||||
|
||||
2026-06-05: Follow-up hardening after the scheduled WSJF triage ran but emitted
|
||||
no report because the live schema required `wsjf` fields and the stale DB prompt
|
||||
did not request them. The verifier default and runbook now point at the live
|
||||
working-memory sink path, `/home/worsch/the-custodian/memory/working`.
|
||||
|
||||
## Three-Run Calibration Feedback
|
||||
|
||||
```task
|
||||
|
|
@ -166,6 +171,12 @@ failure behavior, LLM timeout/retry behavior, and page/note/next-session
|
|||
classification. Task emission sink failures now raise from `emit_tasks`, making
|
||||
them visible to Temporal retries instead of warning-only logs.
|
||||
|
||||
2026-06-05: Added instruction-output robustness for report-sink instructions:
|
||||
after retry exhaustion, schema-invalid model output now produces a durable
|
||||
validation-failure report containing bounded partial output instead of a silent
|
||||
empty result. Report sinks include validation metadata in working-memory
|
||||
frontmatter and State Hub progress detail.
|
||||
|
||||
## Issue-Core Emission Boundary Verification
|
||||
|
||||
```task
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue