backfill the Ward landing policy in .ward/ward.yaml #1651

Closed
opened 2026-08-08 15:49:08 +00:00 by coilyco-ops · 0 comments
Owner

.ward/ward.yaml declares no agent.workflow, so Ward resolves this repository's landing policy from its built-in default rather than from an explicit declaration.

Backfill agent.workflow: pull-request-and-merge so the lane is explicitly resolved.

This repository reaches beyond its own tree, so it takes the director merge lane rather than landing straight on main. That is a real change from the built-in merge-remote-main default it was silently inheriting.

The lane stops being an unstated fallback, which is the precondition for coilyco-flight-deck/agentic-os#972 (unassigned work defaults to pull-request).

Fleet rollout tracked in coilysiren/inbox#340.

`.ward/ward.yaml` declares no `agent.workflow`, so Ward resolves this repository's landing policy from its built-in default rather than from an explicit declaration. Backfill `agent.workflow: pull-request-and-merge` so the lane is explicitly resolved. This repository reaches beyond its own tree, so it takes the director merge lane rather than landing straight on main. That is a real change from the built-in `merge-remote-main` default it was silently inheriting. The lane stops being an unstated fallback, which is the precondition for coilyco-flight-deck/agentic-os#972 (unassigned work defaults to `pull-request`). Fleet rollout tracked in coilysiren/inbox#340.
Commenting is not possible because the repository is archived.
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/ward#1651
No description provided.