docs(agents): list the open pull requests before you start #735

Merged

coilyco-ops merged 1 commit from docs/list-the-open-pull-requests into main

2026-08-13 21:21:07 +00:00

coilyco-ops commented

2026-08-13 21:19:59 +00:00

Member

The duplicate-work habits name grepping for the function, the file, and the flag. They do not name the one signal that is both strongest and cheapest: an open pull request against the file.

Two duplicates today, mine, same cause

	issue	what I did	what existed
sirens-echo #706	claimed, built, pushed #708	closed unmerged	#707, already merged
deploy #480	claimed, built, pushed #486	closed unmerged	#481, open since 19:33Z

Both issues were unclaimed. Both had work already in flight. I checked the issue for a claim comment and never listed the pull requests.

Why the gap exists

The claim protocol coordinates issue numbers, and issue 552 already records that the collision surface is files. A pull request is where a file gets taken, and the author of a small change often opens one before commenting anywhere. So the strongest signal lives in the place the protocol does not look.

Verified, not assumed

$ aosguard ops forgejo pr list coilyco-bridge deploy --state open
  number: 481
  title: 'fix(reconcile): every skipped service says so, not only the ones pinning a SHA'

One call, and it names the exact duplicate I went on to build.

Acceptance

The duplicate-work habits name listing open pull requests, first.
The command is given in a form that runs.

Next owner

Engineer. Closed by the pull request that lands the change.

ward exec gate PASS on all six steps.

closes #734

The duplicate-work habits name grepping for the function, the file, and the flag. They do not name the one signal that is both strongest and cheapest: **an open pull request against the file.** ## Two duplicates today, mine, same cause | | issue | what I did | what existed | | --- | --- | --- | --- | | sirens-echo [#706](https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/706) | claimed, built, pushed [#708](https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/pulls/708) | closed unmerged | [#707](https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/pulls/707), already merged | | deploy [#480](https://forgejo.coilysiren.me/coilyco-bridge/deploy/issues/480) | claimed, built, pushed [#486](https://forgejo.coilysiren.me/coilyco-bridge/deploy/pulls/486) | closed unmerged | [#481](https://forgejo.coilysiren.me/coilyco-bridge/deploy/pulls/481), open since 19:33Z | Both issues were **unclaimed**. Both had work already in flight. I checked the issue for a claim comment and never listed the pull requests. ## Why the gap exists The claim protocol coordinates issue numbers, and [issue 552](https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/552) already records that the collision surface is files. A pull request is where a file gets taken, and the author of a small change often opens one before commenting anywhere. So the strongest signal lives in the place the protocol does not look. ## Verified, not assumed ``` $ aosguard ops forgejo pr list coilyco-bridge deploy --state open number: 481 title: 'fix(reconcile): every skipped service says so, not only the ones pinning a SHA' ``` One call, and it names the exact duplicate I went on to build. ## Acceptance - The duplicate-work habits name listing open pull requests, first. - The command is given in a form that runs. ## Next owner Engineer. Closed by the pull request that lands the change. `ward exec gate` PASS on all six steps. closes #734

coilyco-ops added 1 commit

2026-08-13 21:19:59 +00:00

docs(agents): list the open pull requests before you start

ci / image-build (pull_request) Successful in 19s

Details

ci / test (pull_request) Successful in 36s

Details

ci / publish-echo-image (pull_request) Has been skipped

Details

ci / publish-observed (pull_request) Has been skipped

Details

031cb806ae

Two duplicates today, both mine, both on unclaimed issues that already had
work in flight: sirens-echo#708 against #707, and deploy#486 against #481. I
checked each issue for a claim comment and never listed the pull requests.

The claim protocol coordinates issue numbers. 552 records that the collision
surface is files, and a pull request is where a file gets taken, so the
strongest signal sits where the protocol does not look.

Verified the command runs and names the duplicate it would have caught.

closes #734

Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>