feat(agents): declare the git workflow in AGENTS.md frontmatter #775

Merged
coilysiren merged 1 commit from aos/claude/mg96-fm into main 2026-08-14 05:17:17 +00:00
Member

Part of the coilysiren/inbox#365 teardown, which deletes .ward/ward.yaml from repos.

Moves agent.workflow into AGENTS.md frontmatter:

---
ward:
  workflow: pull-request-and-merge
---

The lane is doctrine about how this repo is worked, so it belongs beside the doctrine rather than in ward's config. Namespaced under ward: so it does not collide with harness-level frontmatter keys.

This one is not a no-op. Read before merging.

This is a PR-lane repo, one of five declaring pull-request-and-merge. Ward does not read AGENTS.md frontmatter yet, and cmd/ward/agent_workflow.go:32 sets defaultWorkflow = workflowDirectToMain (merge-remote-main).

So between this merging and coilyco-flight-deck/ward#1661 landing, a ward dispatch against this repo would resolve to merge-remote-main and push straight to main with no pull request.

Ward has been inert for weeks, so the hazard is dormant rather than live (Kai's call). ward#1661 is a blocker on ward resuming dispatch. The declaration here is doctrine in the meantime, and .ward/ward.yaml no longer carries the lane.

The 27 non-PR-lane repos in this sweep declared merge-remote-main, which is already the compiled default, so those are true no-ops. Only these five change resolved behavior while ward#1661 is open.

Mechanically checked

The edit refuses to run unless the workflow key is found and removed, the resulting YAML re-parses, commands and catalog are byte-identical afterward, and the new AGENTS.md stays under the 290-line / 26400-char documentation-layout caps counting the frontmatter itself.

Part of the coilysiren/inbox#365 teardown, which deletes `.ward/ward.yaml` from repos. Moves `agent.workflow` into AGENTS.md frontmatter: ```yaml --- ward: workflow: pull-request-and-merge --- ``` The lane is doctrine about how this repo is worked, so it belongs beside the doctrine rather than in ward's config. Namespaced under `ward:` so it does not collide with harness-level frontmatter keys. ## This one is not a no-op. Read before merging. This is a **PR-lane repo**, one of five declaring `pull-request-and-merge`. Ward does not read AGENTS.md frontmatter yet, and `cmd/ward/agent_workflow.go:32` sets `defaultWorkflow = workflowDirectToMain` (`merge-remote-main`). So between this merging and coilyco-flight-deck/ward#1661 landing, a ward dispatch against this repo would resolve to **merge-remote-main** and push straight to `main` with no pull request. Ward has been inert for weeks, so the hazard is dormant rather than live (Kai's call). **ward#1661 is a blocker on ward resuming dispatch.** The declaration here is doctrine in the meantime, and `.ward/ward.yaml` no longer carries the lane. The 27 non-PR-lane repos in this sweep declared `merge-remote-main`, which is already the compiled default, so those are true no-ops. Only these five change resolved behavior while ward#1661 is open. ## Mechanically checked The edit refuses to run unless the workflow key is found and removed, the resulting YAML re-parses, `commands` and `catalog` are byte-identical afterward, and the new AGENTS.md stays under the 290-line / 26400-char documentation-layout caps counting the frontmatter itself.
feat(agents): declare the git workflow in AGENTS.md frontmatter
Some checks failed
ci / image-build (pull_request) Successful in 30s
ci / test (pull_request) Failing after 6m48s
ci / publish-echo-image (pull_request) Has been skipped
ci / publish-observed (pull_request) Has been skipped
7f37680af4
Moves agent.workflow out of .ward/ward.yaml, part of deleting that file
(coilysiren/inbox#365). The lane is doctrine about how this repo is worked,
so it belongs beside the doctrine rather than in ward's config.

Ward does not read the new location yet (ward#1661). It resolves the lane
from ward.yaml and falls back to merge-remote-main when absent.

Refs coilysiren/inbox#365, ward#1661

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
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-gaming/sirens-echo!775
No description provided.