From ec66e06066ad8a296dfbca6d11ff736a21e4bee8 Mon Sep 17 00:00:00 2001 From: tegwick Date: Sat, 27 Jun 2026 08:00:51 +0200 Subject: [PATCH] chore(consistency): sync task status from DB [auto] Updated by fix-consistency on 2026-06-27: - update .custodian-brief.md for activity-core --- .custodian-brief.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/.custodian-brief.md b/.custodian-brief.md index 02d62a1..f436da1 100644 --- a/.custodian-brief.md +++ b/.custodian-brief.md @@ -2,24 +2,23 @@ # Custodian Brief — activity-core **Domain:** infotech -**Last synced:** 2026-06-26 16:20 UTC +**Last synced:** 2026-06-27 06:00 UTC **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)* ## Active Workstreams ### LLM Output Robustness & The Producer Trust Boundary -Progress: 2/10 done | workstream_id: `4ef0d53b-1777-41ae-80c6-1b69fdb34726` +Progress: 3/10 done | workstream_id: `4ef0d53b-1777-41ae-80c6-1b69fdb34726` **Open tasks:** - ! Reproduce & Root-Cause The Failure `74fd16a5` *(wait: Local analysis complete: mechanism is the unbounded ~1-per-workstream recommendation list (16 active workstreams; break at char 5268 ~rank 8-9); both first attempt and retry failed. Exact token + finish_reason are unrecoverable from activity-core (complete() drops finish_reason; report cap 4000 < 5268; log cap 2000). Remaining: pull llm-connect producer-side logs on railiance01 (cluster/operator-owned). Does NOT block T02/T03 — mitigation is identical regardless.)* - ► Tests + calibration re-entry `b7b9e07a` - ► Schema + Prompt Redesign For Error Locality `ae67ca8c` +- ► Tests + Calibration Re-Entry `c881500b` - · Reproduce & root-cause the 06-26 validation failure `2d3bba00` - · Schema + prompt redesign for error locality `5da6962c` - · Boundary parser — verify & mitigate with quarantine lane `4c408114` -- · Producer Guardrails + ADR-004 `f5c3af5b` -- … and 1 more open tasks ### Post-triage operational hardening Progress: 6/8 done | workstream_id: `5646e13a-13af-4724-bca6-3c0d86f96733`