chore(agents): move sirens-echo onto the pull-request-and-merge lane #319
No reviewers
Labels
No labels
move-to-repo
coilyco-bridge-deploy
move-to-repo
coilyco-flight-deck-agent-compose
move-to-repo
coilyco-gaming-eco-app
move-to-repo
coilysiren-inbox
move-to-repo
unknown
🔒⚠️📦⚠️🔒 SANDBOXED 🔒⚠️📦⚠️🔒
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
c#
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-gaming/sirens-echo!319
Loading…
Reference in a new issue
No description provided.
Delete branch "pr-lane-318"
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?
Moves sirens-echo from
merge-remote-mainto the PR lane the other repos in this class run..ward/ward.yaml:agent.workflowbecomespull-request-and-merge.AGENTS.md: the direct-to-main sentence under## Agent rulesbecomes the PR-lane block agentic-os, deploy, infrastructure, and ward carry.The block asserts byte-identity across the PR-lane repos, so its enumeration goes from four to five and names sirens-echo. Verified byte-for-byte against the existing four, with only that enumeration differing. Companion one-line pull requests carry the same edit into the other four.
No server-side change rides along. Branch protection already covers
coilyco-gamingthrough the fleet converge, which blocks force-push and deletion and does not gate the PR lane. Merge settings already match deploy and infrastructure. Required status contexts stay unset, matching deploy and infrastructure rather than agentic-os and ward. CI already triggers onpull_request.ward exec gatepasses: build, policy-check, vet, test, test-skips, pre-commit.closes #318