A request in flight stays recognised as the workflow grows

When a customer has no project yet, their pages check whether a request they raised is already on its way, and name it instead of offering to raise another. The stages that count as “on its way” used to be written out by hand, so a stage added to the lead workflow later would have been missed and the customer offered a duplicate request. They now come from the workflow itself.

The check also reads less: it looks up only the most recent request and the number in flight, rather than every matching request. What a customer sees today is unchanged.