Upstream report from a peer workspace (owner-directed, 2026-09-17; deduped against the porch board — #1235's arbitrary-worktree resolution and #1229's terminal-state gaps are adjacent family, neither covers this). The reporting workspace closes its local tracker as tracked-upstream here; low priority by their own calibration.
Defect
Porch's project listing keys on the bare issue number, so same-numbered projects across protocols collide. Observed in the field 2026-07-23: codev/projects/3179-* (a PIR lane) vs bugfix-3179-* — with both present, porch pending never listed the bugfix-3179 builder, leaving no porch-native gate-state visibility for that lane (gates still functioned; they were just invisible to the listing).
Same-number-different-protocol is not exotic: any issue that gets a bugfix attempt after a protocol lane (or vice versa) collides.
Related known gap (fold in or split at the lane's judgment)
porch pending also omits bugfix-* projects generally — the collision above is the acute case of a broader listing bias toward unprefixed project ids.
Likely fix
Key listings (and any other bare-number lookups) on the full protocol-qualified project id (bugfix-3179-... as distinct from 3179-...), which is already the directory-name reality under codev/projects/.
Upstream report from a peer workspace (owner-directed, 2026-09-17; deduped against the porch board — #1235's arbitrary-worktree resolution and #1229's terminal-state gaps are adjacent family, neither covers this). The reporting workspace closes its local tracker as tracked-upstream here; low priority by their own calibration.
Defect
Porch's project listing keys on the bare issue number, so same-numbered projects across protocols collide. Observed in the field 2026-07-23:
codev/projects/3179-*(a PIR lane) vsbugfix-3179-*— with both present,porch pendingnever listed the bugfix-3179 builder, leaving no porch-native gate-state visibility for that lane (gates still functioned; they were just invisible to the listing).Same-number-different-protocol is not exotic: any issue that gets a bugfix attempt after a protocol lane (or vice versa) collides.
Related known gap (fold in or split at the lane's judgment)
porch pendingalso omitsbugfix-*projects generally — the collision above is the acute case of a broader listing bias toward unprefixed project ids.Likely fix
Key listings (and any other bare-number lookups) on the full protocol-qualified project id (
bugfix-3179-...as distinct from3179-...), which is already the directory-name reality undercodev/projects/.