"drain" logs of previous? current? director runs on init of new directors

coilysiren commented

2026-07-15 02:09:02 +00:00

Owner

This is a bit vague - but I think the idea is that the action of logs drain should always pair writing to disk, the redaction / filtering we already do, then pushing those logs to a collector. Director drains just skip that first step since they are already on disk, and then past that point they are just another warded agent drain

Decision for headless carry

Implement this as log-pipeline normalization, not a new policy decision. Director logs are already on disk, so their drain starts after the write-to-disk step that normal agent logs perform.

Required shape:

Reuse the existing redaction and filtering path before any collector upload.
Treat previous and current director run logs as sources in the same drain pipeline as warded agent logs.
If no collector is configured, still produce the local drained artifact and a clear no-op status.
Add tests around source selection and redaction reuse.
Do not invent a new collector in this issue.

This is a bit vague - but I think the idea is that the action of logs drain should always pair writing to disk, the redaction / filtering we already do, then pushing those logs to a collector. Director drains just skip that first step since they are already on disk, and then past that point they are just another warded agent drain --- ## Decision for headless carry Implement this as log-pipeline normalization, not a new policy decision. Director logs are already on disk, so their drain starts after the write-to-disk step that normal agent logs perform. Required shape: * Reuse the existing redaction and filtering path before any collector upload. * Treat previous and current director run logs as sources in the same drain pipeline as warded agent logs. * If no collector is configured, still produce the local drained artifact and a clear no-op status. * Add tests around source selection and redaction reuse. * Do not invent a new collector in this issue.

coilyco-ops added the

labels

2026-07-15 04:51:14 +00:00

coilyco-ops added this to the warded control plane coherence milestone

2026-07-15 05:14:48 +00:00

coilyco-ops added

and removed

labels

2026-07-15 06:03:35 +00:00

coilyco-ops commented

2026-07-15 07:16:39 +00:00

Owner

WARD-TRIAGE: warded control plane coherence milestone

This issue is part of the warded control plane coherence sprint. The release thesis is to make warded feel like one dependable control plane for agent work: higher safe parallelism, coherent config defaults, reliable broker/container behavior, human-feedback gates, and enough structured evidence for the next actor after a paused or failed run.

For this sprint, headless means an engineer should be able to carry the issue from current issue context to a merged change without new human decisions. If the issue discovers a missing decision, split or demote the unclear part instead of guessing.

WARD-TRIAGE: warded control plane coherence milestone This issue is part of the `warded control plane coherence` sprint. The release thesis is to make `warded` feel like one dependable control plane for agent work: higher safe parallelism, coherent config defaults, reliable broker/container behavior, human-feedback gates, and enough structured evidence for the next actor after a paused or failed run. For this sprint, `headless` means an engineer should be able to carry the issue from current issue context to a merged change without new human decisions. If the issue discovers a missing decision, split or demote the unclear part instead of guessing.

coilyco-ops referenced this issue

2026-07-15 13:09:25 +00:00

Resolve PR #1442 merge conflict after main advanced #1444

coilyco-ops referenced this issue from a commit

2026-07-15 13:14:50 +00:00

cmd/ward: include director runs in issue log drains

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-15 13:15:22 +00:00

Include director runs in issue log drains #1448

coilyco-ops commented

2026-07-15 13:20:32 +00:00

Owner

WARDED_WORKFLOW: #1448

details

workflow: pull-request-and-merge; review summary: skipped (in-container review gate intentionally skipped because temporary ward default pending brokered QA)
felt: surgical and contained
confidence: high
surprises: the widened issue lookup needed the shared Docker test double to answer ward.role
follow-ups: none

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1448 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped (in-container review gate intentionally skipped because temporary ward default pending brokered QA) felt: surgical and contained confidence: high surprises: the widened issue lookup needed the shared Docker test double to answer `ward.role` follow-ups: none </details>

coilyco-ops referenced this issue

2026-07-15 13:23:17 +00:00

Retrigger PR #1448 after runner context-canceled job stayed pending #1449

coilyco-ops commented

2026-07-15 13:30:49 +00:00

Owner

DISPATCH-DEFERRED: PR #1448 failed after the first engineer exited. Evidence: run 8585 (#2295) failure test.yml pull_request #1448 "cmd/ward: include director runs in issue log drains"; ward agent pr status coilyco-flight-deck/ward#1448 reports combined status failure. Attempted warded engineer coilyco-flight-deck/ward#1301 --harness codex --workflow pull-request-and-merge from the director surface at 2026-07-15T13:30Z, but Ward rejected it because coilyco-flight-deck/ward already has 3 active engineers at the repo limit. Dispatch log: /Users/kai/.ward/agent-logs/dispatch/20260715T133022Z-director-codex-md65-coilyco-flight-deck-ward-1301.log. Retry as soon as a slot opens.

DISPATCH-DEFERRED: PR #1448 failed after the first engineer exited. Evidence: `run 8585 (#2295) failure test.yml pull_request #1448 "cmd/ward: include director runs in issue log drains"`; `ward agent pr status coilyco-flight-deck/ward#1448` reports combined status failure. Attempted `warded engineer coilyco-flight-deck/ward#1301 --harness codex --workflow pull-request-and-merge` from the director surface at 2026-07-15T13:30Z, but Ward rejected it because coilyco-flight-deck/ward already has 3 active engineers at the repo limit. Dispatch log: /Users/kai/.ward/agent-logs/dispatch/20260715T133022Z-director-codex-md65-coilyco-flight-deck-ward-1301.log. Retry as soon as a slot opens.

coilyco-ops closed this issue

2026-07-15 13:38:25 +00:00

coilyco-ops referenced this issue

2026-07-15 13:42:53 +00:00

Repair failed promote run after PR #1448 #1454

Rows
Columns

"drain" logs of previous? current? director runs on init of new directors #1301

Decision for headless carry