Agents incorrectly think "readonly director surface" means that they should not merge #1273

New issue

Open

opened 2026-07-14 10:45:00 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-07-14 10:45:00 +00:00

Owner

They should merge. Coordinating merges is one of the most valuable things a director should be doing.

Release triage

Removed from warded control plane coherence on 2026-07-15. Kai needs a clearer boundary for what belongs in AGENTS.md, seed prompts, generated launch context, and command help before this can be safely implemented.

Prerequisite: ward#1343 should define prompt/seed-text config sources and lightweight variable interpolation. After that lands or is accepted, this issue can be rewritten as a concrete headless prompt/config update.

Chosen doctrine

Read-only director surface means the local clone cannot push. It does not mean the director lacks merge authority. Directors should merge eligible PRs through ward native PR/merge tools when the issue thread and workflow authorize it.

Required shape once prerequisite is resolved:

Update the correct director seed/help/config surface so agents stop interpreting read-only as no-merge.
Make merge authority point at the issue workflow and PR status, not local filesystem writability.
Add a regression test or fixture that a read-only director plan still exposes the merge path for eligible PRs.
Keep direct local git push from the director clone forbidden.

They should merge. Coordinating merges is one of the most valuable things a director should be doing. --- ## Release triage Removed from `warded control plane coherence` on 2026-07-15. Kai needs a clearer boundary for what belongs in AGENTS.md, seed prompts, generated launch context, and command help before this can be safely implemented. Prerequisite: ward#1343 should define prompt/seed-text config sources and lightweight variable interpolation. After that lands or is accepted, this issue can be rewritten as a concrete headless prompt/config update. ## Chosen doctrine Read-only director surface means the local clone cannot push. It does not mean the director lacks merge authority. Directors should merge eligible PRs through ward native PR/merge tools when the issue thread and workflow authorize it. Required shape once prerequisite is resolved: * Update the correct director seed/help/config surface so agents stop interpreting read-only as no-merge. * Make merge authority point at the issue workflow and PR status, not local filesystem writability. * Add a regression test or fixture that a read-only director plan still exposes the merge path for eligible PRs. * Keep direct local git push from the director clone forbidden.

coilysiren changed title from ~~Agents think "readonly director surface" means that they should not merge~~ to Agents incorrectly think "readonly director surface" means that they should not merge

2026-07-14 10:45:12 +00:00

coilysiren commented

2026-07-14 10:45:21 +00:00

Author

Owner

This probably looks like a prompt update

coilysiren referenced this issue

2026-07-14 15:27:09 +00:00

director should emit colorized, space buffered, visually distinct messages about the categories of actions its performing on startup #1283