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

Updated by fix-consistency on 2026-06-30:
  - update .custodian-brief.md for activity-core
This commit is contained in:
2026-06-30 12:36:50 +02:00
parent 92629e7a91
commit bb14d08212

View File

@@ -2,7 +2,7 @@
# Custodian Brief — activity-core # Custodian Brief — activity-core
**Domain:** infotech **Domain:** infotech
**Last synced:** 2026-06-29 23:50 UTC **Last synced:** 2026-06-30 10:36 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)* **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams ## Active Workstreams
@@ -18,24 +18,17 @@ Progress: 0/5 done | workstream_id: `21c73763-9adc-42f6-8fd2-1b8b33c2c770`
- · Task: Verify against current repo and live/degraded sources `5317b532` - · Task: Verify against current repo and live/degraded sources `5317b532`
### LLM Output Robustness & The Producer Trust Boundary ### LLM Output Robustness & The Producer Trust Boundary
Progress: 3/10 done | workstream_id: `4ef0d53b-1777-41ae-80c6-1b69fdb34726` Progress: 4/10 done | workstream_id: `4ef0d53b-1777-41ae-80c6-1b69fdb34726`
**Open tasks:** **Open tasks:**
- ! Reproduce & Root-Cause The Failure `74fd16a5` - ! 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.)* *(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` - ► Tests + calibration re-entry `b7b9e07a`
- ► Schema + Prompt Redesign For Error Locality `ae67ca8c`
- ► Tests + Calibration Re-Entry `c881500b` - ► Tests + Calibration Re-Entry `c881500b`
- · Reproduce & root-cause the 06-26 validation failure `2d3bba00` - · Reproduce & root-cause the 06-26 validation failure `2d3bba00`
- · Schema + prompt redesign for error locality `5da6962c` - · Schema + prompt redesign for error locality `5da6962c`
- · Boundary parser — verify & mitigate with quarantine lane `4c408114` - · Boundary parser — verify & mitigate with quarantine lane `4c408114`
### Post-triage operational hardening
Progress: 7/8 done | workstream_id: `5646e13a-13af-4724-bca6-3c0d86f96733`
**Open tasks:**
- ! Three-Run Calibration Feedback `7cbf0a35`
### Adopt State Hub Beachhead Endpoint ### Adopt State Hub Beachhead Endpoint
Progress: 0/2 done | workstream_id: `bbc07f9e-9323-4b2b-b556-c33b37d0b228` Progress: 0/2 done | workstream_id: `bbc07f9e-9323-4b2b-b556-c33b37d0b228`