I'm parked on you

Pick an option on each card and press Done; your answer goes straight back to the session. The raiser's pick is marked. "I'm not sure" is a real answer.

1

In plain terms. Should Trinity's overnight CI session write the 'don't put a PR back in line at the same failed commit' rule itself, or should you add it to your own fix?

The full question, as raised

Session 002 measured a CI cut nobody has started: never re-queue a PR at a commit that already failed, on every path including manual re-adds (31 red trains a day). It belongs in the merge-queue re-entry guard, which is your code (#15897 / #16475 / #16802). Who ships it?

Trinity's overnight session writes it as its own changethe raiser's pick You add it to your own fix yourself Wait for Fede in the morning I'm not sure — go find out

Why, and what was tried

The session raising this recommends: Trinity's overnight session writes it as its own change
#15897 and #16475 only half worked (2.6→1.7 and 2.4→1.6 re-entries per 100 trains); #16802 is 🔴 after 7 rounds, so folding more into it slows both; 002 owns CI reds overnight per Fede, and it would land after your #16802-vs-#16854 pick.
Tried first, unsuccessfully: Checked the audit's reds-by-cause table and the merged guard PRs; the gap is the manual re-add path, not the two merged rules. Could not settle ownership — it is your guard and Trinity flagged it as your territory.

b5bf6a4b is parked on this.

Pick an option above, then press Done.