Feature Request - first_locked_order

[wep-v]

I'm requesting a feature/option to be added to broker.toml to enable the prover to prioritize work based on the order, in which, an order is recieved and acquired. I have my broker set to one concurrent order and a peak mhz recommended by the setup wizard. I have started to see up to 10 orders locked at a time on the explorer. There are new orders coming in being fulfilled while old orders stay unfulfilled and lead to slashing. the shortest expiry would work but if you have multiple high volume orders locked that take approx. 10mins to fulfill each, and they each have 30 minutes before they expire, well then you're still bound to have an order or multiple slashed.

If this setting update would direct the prover to prove orders based on the sequence in which they are locked, that would be great.

[linear]

BM-2404

[wep-v]

Config: max_concurrent_proofs = 1, order_commitment_priority = "shortest_expiry", and that you have 48 exec agents (and 8 GPU agents).

Behavior: Many orders “ready for locking/proving” (599), but old locked orders are never chosen to be proved; only newer ones seem to get worked on.

Ask: Whether commitment priority is applied only to “orders we have locked,” and whether there is (or could be) an “oldest locked first” / FIFO option for locked orders.