Finish before starting: an approved pull with a conflict is brought up to date before any new issue is picked #3682

Probe 2026-10-20 21:55Z: tick approved="38 approved: queued=21 conflict=17" - 17 reviewed, approved pulls blocked by conflicts with main, while builders were full (did=full, active=9) picking new issues; the forge log shows no conflict-resolution or bring-up-to-date activity for 60 min. Every one of those 17 is nearly done work that lands in minutes once updated; each new pick adds more open pulls that will conflict.

Done: in the autonomy tick, a slot freed goes first to an approved pull with conflicts (its author, else any builder; the resolver #2039 brief: merge main, resolve keeping both intents, re-run the check), then to a changes-requested pull, then to a new issue; the tick line shows finishing=N and conflict=N waiting. A pull that fails to update twice is handed to a person on /review (#3247) instead of retried forever. Measure: approved-to-landed minutes and conflict count on /boards before and after. Test: with 1 slot, an approved conflicted pull and a ready issue - the pull is updated first.

Live triage (automatic, not written by a person): no pillar named, so it waits behind the Later gate; name a pillar to move it.