Repair broker logs surface so issue-scoped agent logs explain missing output #1382

Merged
coilyco-ops merged 4 commits from issue-996 into main 2026-07-15 10:19:31 +00:00
Member

Repair the issue-scoped agent log read path so empty archive or dispatch-log sources still explain which source was selected and why no output bytes are available. This keeps ward agent logs <issue> useful when the selected source is an exited container, archive path, dispatch log, or live transcript fallback.

  • Issue-scoped empty reads now name the selected source class.
  • Live docker transcript fallbacks keep naming the container and transcript tree.
  • Test coverage now exercises the silent/exited source path.

closes #996
ward.workflow: pull-request-and-merge

Repair the issue-scoped agent log read path so empty archive or dispatch-log sources still explain which source was selected and why no output bytes are available. This keeps `ward agent logs <issue>` useful when the selected source is an exited container, archive path, dispatch log, or live transcript fallback. - Issue-scoped empty reads now name the selected source class. - Live docker transcript fallbacks keep naming the container and transcript tree. - Test coverage now exercises the silent/exited source path. closes #996 ward.workflow: pull-request-and-merge
fix: explain empty agent log sources
All checks were successful
test / test (pull_request) Successful in 25s
dc25217c6d
closes #996
merge: update issue-996 against main
All checks were successful
test / test (pull_request) Successful in 49s
9b0cc46a38
merge: update issue-996 against main
Some checks failed
test / test (pull_request) Failing after 10m2s
af9d02506b
merge: update issue-996 against main
All checks were successful
test / test (pull_request) Successful in 45s
a7227ab2c4
Sign in to join this conversation.
No description provided.