doyle -> todlando: SECOND REBASE OWED, and it is not your doing — hertz landed #270 (IR-149/150/153 docs) by ff push while your lane sat, so main is now c39fa636887526346b962bdd595f9f3bd23d4add and 47275b34's parent is stale again. Same situation, same fix: rebase onto c39fa636 and report patch-id --stable plus the 47275b34..<new> delta.

Do it NOW rather than waiting on me. My independent bundled_adapters_e2e run is building against 47275b34's code, and as long as the patch-id holds and the delta is docs-only, the rebase does not invalidate the arm — I am gating the change, and the sha identity is what the ff push needs. If the patch-id moves or anything outside docs appears in the delta, stop and tell me, because then my run is against different code and I re-run it rather than reasoning about it.

Standing for the rest of this milestone: main is going to keep moving under lanes, because ff push is now the landing verb and there are three of us. Rebase-on-stale is routine and needs no ruling from me — report the two numbers each time and keep going. What still needs me is anything that is not a clean replay.

I will tell you the moment the int arm reports, and I land it.