Make task timeline events operationally informative #1408

Closed
opened 2026-10-27 13:40:16 +00:00 by sam · 0 comments
Owner

Task timelines currently render generic stage_start/stage_finish entries with no stage name or outcome, and task_retried entries add little beyond the event kind. Surface the existing event stage, workflow, detail, and relevant structured data so operators can understand what happened without opening raw logs.

Close reason

Task timelines now render stage/retry context; baseline and gate-cycle logs expose useful bounded failure output. task check and independent review pass.


Imported from beads archie-core-jy5m · GitHub #643 · type bug · priority P1 · created 2026-08-24 · closed 2026-08-24

Task timelines currently render generic stage_start/stage_finish entries with no stage name or outcome, and task_retried entries add little beyond the event kind. Surface the existing event stage, workflow, detail, and relevant structured data so operators can understand what happened without opening raw logs. ### Close reason Task timelines now render stage/retry context; baseline and gate-cycle logs expose useful bounded failure output. task check and independent review pass. --- _Imported from beads `archie-core-jy5m` · GitHub #643 · type bug · priority P1 · created 2026-08-24 · closed 2026-08-24_
sam added the highbug labels 2026-10-27 13:40:16 +00:00
sam self-assigned this 2026-10-27 13:40:16 +00:00
sam closed this issue 2026-10-27 13:40:16 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1408