chore(consistency): sync task status from DB [auto]

Updated by fix-consistency on 2026-06-26:
  - update .custodian-brief.md for activity-core

.custodian-brief.md

@@ -2,11 +2,25 @@
 # Custodian Brief — activity-core
 
 **Domain:** infotech  
-**Last synced:** 2026-06-24 10:53 UTC  
+**Last synced:** 2026-06-26 15:52 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: 0/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.)*
+- ► Schema + Prompt Redesign For Error Locality  `ae67ca8c`
+- ► Boundary Parser — Verify & Mitigate (Posture B)  `d65a6281`
+- · 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  `b7136ca9`
+- … and 3 more open tasks
+
 ### Post-triage operational hardening
 Progress: 6/8 done  |  workstream_id: `5646e13a-13af-4724-bca6-3c0d86f96733`