UK qualify job times out at 120 minutes since the household route runs, so no candidate finishes its gates #659

Since 17 October around 14:30Z, no UK candidate has finished its local gates. Every qualify job hits its 120-minute timeout-minutes ("The job has exceeded the maximum execution time of 2h0m0s", run 39145419501). The next scheduled catch-up re-stages the attempt, and the cycle repeats: 2.135.6 (pair f5aac48f…) has been staged seven times.

Why now:

• Through 17 October 03:59Z, gates finished in about 1h20m (e.g. 81958192: staged 02:39, gates 03:59). Every wrapper.household contract row errored at once then, because policyengine.uk was None (The Budget reform contract's household route errors in the qualification gate: policyengine.uk is None #650).
• Import the UK model module directly in the contract's household route #651 (merged 17 Oct 13:25Z) fixed that, so those rows now run the household calculator. With contract 2.0.0 (Check statutory resumption after a freeze: Budget reform contract 2.0.0 (cos d1344) #627) adding 2034/2035 checks, the gates step passes two hours. The cancelled log shows active computation in both the candidate and previous-pair environments up to the cut-off.

Fix: raise the qualify job's timeout-minutes to 330, under the 360-minute ceiling for GitHub-hosted jobs. The job's concurrency group (uk-candidate-<pair>, cancel-in-progress: false) already stops a later run from cancelling it. Speeding up the household route, for example by running household cases in parallel, is a separate follow-up.