Structured run outcomes and log viewer #806

New Issue

2026-07-22T05:33:04-05:00

jcwalker3 commented

2026-07-22 05:33:04 -05:00

Objective

Implement structured run outcomes and log viewer for multi-LLM workers.

Acceptance criteria

Standardize COMPLETE, NO_WORK, BLOCKED, TIMEOUT, and FAILED.
Preserve the original worker response.
Record start, end, duration, issue/PR, worker identity, and terminal outcome.
Provide safe human-readable logs and machine-readable records.
Redact secrets and sensitive environment data.
Includes parsing and redaction tests.

Parent Epic

Parent: #797

Issue-First & Safety Requirements

Implementation may begin only from an existing open issue.
Author implementation requires canonical routing, a durable issue lock, and a validated author worktree.
Read-after-write verification is required for all mutations.
Wrong-role and ambiguous-ownership operations fail closed.

## Objective Implement structured run outcomes and log viewer for multi-LLM workers. ## Acceptance criteria - Standardize COMPLETE, NO_WORK, BLOCKED, TIMEOUT, and FAILED. - Preserve the original worker response. - Record start, end, duration, issue/PR, worker identity, and terminal outcome. - Provide safe human-readable logs and machine-readable records. - Redact secrets and sensitive environment data. - Includes parsing and redaction tests. ## Parent Epic Parent: #797 ## Issue-First & Safety Requirements - Implementation may begin only from an existing open issue. - Author implementation requires canonical routing, a durable issue lock, and a validated author worktree. - Read-after-write verification is required for all mutations. - Wrong-role and ambiguous-ownership operations fail closed.

jcwalker3 referenced this issue

2026-07-22 06:11:34 -05:00

feat(webui): worker registry and configuration schema (Closes #798) #810

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#806