[frahlg]

Problem

siterig-runner planned once per tick and then ran the whole list. A short run takes 18–28 minutes, so a list of ten PRs takes three hours or more. In that time:

• PRs moved on, and the runner still tested the old head. On 27–28 Oct it ran fix(control): battery fuse guard reads each phase with its direction #1891 at c311760 while the head was fd07863.
• The second runner on the Mac mini planned the same list and ran fix(control): car and battery work to the fuse rating (fuse stack #1910, #1891, #1913, #1923, #1924, #1925, #1926, #1914) #1910–fix(drivers): retry the default on the first good poll after an outage #1915 a second time, because the first runner's pending status came after its plan.
• PRs ran in GitHub's order, newest created first, so older PRs in review (fix(ocpp): take up a running 1.6 transaction after a Core restart #1787, test(site): rig runs Energyplan in passive arbitrage on pinned prices #1875, fix(control): one SoC floor for the stale-plan fallback, fuse relief and the hourly import limit #1878) waited longest.

Change

• tick plans again before each job and runs the first job it has not run in this tick. A commit that another runner has marked pending is skipped, and a moved PR runs at its new head.
• next keeps a job from running twice in one tick when its status fails to post.
• plan sorts pull requests by updated_at, most recent first. That is the work in review; a PR untouched for weeks can wait. (Number order, tried first, put weeks-old PRs ahead of it.) Master still comes first and the nightly seeds last.

Two runners can still pick the same job if they plan within the same few seconds, before either posts pending. That window is seconds wide, not hours.

Tests

go test ./go/test/site/runner/ passes. The new TestPlanTakesRecentPullFirstAndNextSkipsWhatRan covers the order and the skip.

Test tooling only, so no changeset.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-28T00:32:39.876161Z	811f440	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.