The merge verb cannot acknowledge its own body edits from a sealed seat, so ten correct pull requests sit unmergeable #289

New issue

Open

opened 2026-08-13 22:42:38 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-13 22:42:38 +00:00

Member

Blocked, and filing per the campaign brief's instruction to leave an issue for whoever can unblock it. Angie (ENG, claude seat). Not claiming — this is a build and credential concern, not code.

What I can and cannot do

The merge verb accepts this repository. coilyco-gaming is in the trusted-owner allowlist, unlike coilyco-bridge on coilyco-bridge/deploy#482. So the refusal is not categorical.

ward agent director merge --repo coilyco-gaming/eco-app --dry-run
  merged 0 PR(s), skipped 10

Gate one was mine and is fixed. All ten skipped for "no same-repo closing reference in the PR body", because I wrote each as refs #266 / refs #267 — correctly refusing to claim a slice closes a 25-tool sweep, and incorrectly never filing the slice. AGENTS.md says to do both. Six slice issues later (#283 through #288) that skip reason is gone from all ten.

Gate two is the environment. Repointing a body through the API registers as a manual update, and the verb then wants an acknowledgement it cannot post:

skipping #279: manual close/update snapshot at 22:36:56Z has no newer
               ward acknowledgement yet
ward human-feedback block: could not mirror on coilyco-gaming/eco-app#279:
  resolve Forgejo token: set FORGEJO_TOKEN or launch through a credential broker

So a seat that edits a pull request body can never satisfy the gate that edit creates. Fixing a pull request makes it less mergeable, from here.

Why this is the same family as sirens-echo#483

There the human-feedback gate reads an agent's own claim comment as feedback awaiting acknowledgement. Here it reads an agent's own body edit the same way. Both are the gate working exactly as designed against a class of author it was not designed for.

I am not arguing the gate is wrong. A human-feedback checkpoint that an agent can satisfy by talking to itself would not be a checkpoint.

What would unblock it, cheapest first

Someone with a token runs the verb. Ten pull requests, all gated green, ordering documented on #282 — one stacking constraint (278 on 277) and everything else independent.

Or the seat gets FORGEJO_TOKEN through the credential broker, if an engineer seat acknowledging its own edit is acceptable. That is a policy call and I am not making it.

What is actually waiting

Three are correctness fixes with the narrowest blast radius, and they are the ones I would land first regardless of what happens to the other seven:

279  a treasury of 87,912.99 reported as 0, with health "healthy" derived from it
280  a 401 described as "no currencies have been created or traded yet",
     beside a payload carrying 40 active currencies
271  a cross-check reporting success against a host that does not resolve

Each has a mutation recorded showing its test fails without the fix. None needs a live server.

**Blocked, and filing per the campaign brief's instruction to leave an issue for whoever can unblock it.** Angie (ENG, `claude` seat). Not claiming — this is a build and credential concern, not code. ## What I can and cannot do The merge verb accepts this repository. `coilyco-gaming` is in the trusted-owner allowlist, unlike `coilyco-bridge` on https://forgejo.coilysiren.me/coilyco-bridge/deploy/issues/482. So the refusal is not categorical. ``` ward agent director merge --repo coilyco-gaming/eco-app --dry-run merged 0 PR(s), skipped 10 ``` **Gate one was mine and is fixed.** All ten skipped for *"no same-repo closing reference in the PR body"*, because I wrote each as `refs #266` / `refs #267` — correctly refusing to claim a slice closes a 25-tool sweep, and incorrectly never filing the slice. `AGENTS.md` says to do both. Six slice issues later (https://forgejo.coilysiren.me/coilyco-gaming/eco-app/issues/283 through https://forgejo.coilysiren.me/coilyco-gaming/eco-app/issues/288) that skip reason is gone from all ten. **Gate two is the environment.** Repointing a body through the API registers as a manual update, and the verb then wants an acknowledgement it cannot post: ``` skipping #279: manual close/update snapshot at 22:36:56Z has no newer ward acknowledgement yet ward human-feedback block: could not mirror on coilyco-gaming/eco-app#279: resolve Forgejo token: set FORGEJO_TOKEN or launch through a credential broker ``` So a seat that edits a pull request body can never satisfy the gate that edit creates. **Fixing a pull request makes it less mergeable, from here.** ## Why this is the same family as sirens-echo#483 There the human-feedback gate reads an agent's own claim comment as feedback awaiting acknowledgement. Here it reads an agent's own body edit the same way. Both are the gate working exactly as designed against a class of author it was not designed for. I am not arguing the gate is wrong. A human-feedback checkpoint that an agent can satisfy by talking to itself would not be a checkpoint. ## What would unblock it, cheapest first **Someone with a token runs the verb.** Ten pull requests, all gated green, ordering documented on https://forgejo.coilysiren.me/coilyco-gaming/eco-app/issues/282 — one stacking constraint (278 on 277) and everything else independent. **Or the seat gets `FORGEJO_TOKEN` through the credential broker**, if an engineer seat acknowledging its own edit is acceptable. That is a policy call and I am not making it. ## What is actually waiting Three are correctness fixes with the narrowest blast radius, and they are the ones I would land first regardless of what happens to the other seven: ``` 279 a treasury of 87,912.99 reported as 0, with health "healthy" derived from it 280 a 401 described as "no currencies have been created or traded yet", beside a payload carrying 40 active currencies 271 a cross-check reporting success against a host that does not resolve ``` Each has a mutation recorded showing its test fails without the fix. None needs a live server.

coilyco-ops added the

labels

2026-08-15 21:09:14 +00:00