Repository navigation
[strategist] Agent fleet files duplicate PRs — no cross-agent dedup, ~25% of open queue is redundant #119
Description
Strategic Finding
Type: ecosystem-opportunity / process-gap
Horizon: near-term
As of 2026-08-08 (sweep 6) there are 8 duplicate pairs across 4 repos — up from 3 pairs when first filed. Roughly 1 in 5 open PRs fleet-wide is redundant:
| Pair | Repo | Overlap |
|---|---|---|
| #43 ≡ #112 | endusers | Prince installer SHA-256 verification in pdf.yml |
| #56 ≡ #114 | endusers | centralize NODE_VERSION in import/refresh workflows |
| #103 ≡ #116 | endusers | wire test:unit into CI (partial; #103 also centralizes Node) |
| #29 ≡ #45 | peoplehub | missing getOrgMembers export (build fix, 3 months apart) |
| #41 ≡ #57 | peoplehub | Slack daily summary bot |
| #40 ≡ #56 | peoplehub | vite/esbuild Dependabot bumps |
| #27 ≡ #69 | firehose | Last Week In Cloud Native feed (#27 now CONFLICTING) |
| #120 ≡ #138 | bootc-ecosystem | CNCF Maturity Model self-assessment page (identical titles) |
Resolved since filing: endusers #87 ≡ #107 (#87 closed/merged; #107 still open).
Rationale
Issue #58 established that the agent PR queue outpaces single-human merge capacity (83 mergeable and growing). Duplicates make that worse: every redundant PR burns the same scarce review budget as a real one, and merging one half of a pair silently strands the other (merge conflict or double-apply risk). The fleet currently has no convention for checking existing open PRs before implementing a fix, and no convention for closing a bot PR when an equivalent lands.
Proposed Next Step
- Immediate: close one side of each pair above (keep the newer/better-scoped half; close firehose chore(deps): bump brace-expansion from 1.1.12 to 1.1.18 #27 which is already conflicting).
- Add a fleet dedup convention to AGENTS.md / GOVERNANCE.md: (a) before implementing, agents must search open PRs touching the same files and link or supersede them; (b) when an equivalent change lands, the superseded PR is closed by the triage pass proposed in [strategist] Agent PR queue outpaces single-human merge capacity — 15 open; policy exists, reaping/automerge not operational #58; (c) agents filing fixes that require workflow-file changes should reference the tracking issue instead of opening artifact-patch PRs.
Filed by strategist agent (ACMM L6 — full mode); updated in place 2026-08-08 sweep 6
Activity
docs(governance): add fleet-wide cross-agent duplicate PR prevention …