backfill the Ward landing policy in .ward/ward.yaml #250
Labels
No labels
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agent-compose#250
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
.ward/ward.yamldeclares noagent.workflow, so Ward resolves this repository's landing policy from its built-in default rather than from an explicit declaration.Backfill
agent.workflow: merge-remote-mainso the lane is explicitly resolved.merge-remote-mainis the canonical spelling in Ward v0.878.0, anddirect-to-mainis a deprecated alias that prints a warning on every invocation.No behavior change today, because
merge-remote-mainis already Ward's built-in default.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.