Allow slow CI runners to finish runtime and CLI tests

[aviggiano]

A runtime integration shard was canceled at the 75-minute CI limit after 59 passing tests, with no assertion failures. Identical coverage passed on other runners, but the slow runner took roughly three times as long; its remaining tests project a total of about 86 minutes. The completed local CLI suite also took 76.3 minutes before CI setup time.

Give all four runtime integration shards and the CLI lane a bounded 120-minute budget, matching the existing runtime support lane. Preserve every test, shard, selection rule, validation command, and failure gate. Package and benchmark-history/typecheck lane budgets stay at 45 minutes.

Validation: nine lane-policy tests (70 assertions), frozen dependency installation, strict lint, formatting, and independent review passed. The policy tests cover the budgets and their use in the workflow matrix. Full CI on the final combined main commit will verify completion across every lane.

Confidence Score: 5/5

The PR appears safe to merge; the intended lanes receive the larger bounded budget without weakening coverage or changing unrelated lane budgets.

Summary

This PR increases the bounded timeout for the four sharded runtime integration lanes and the CLI lane from 75 to 120 minutes while preserving the existing lane selection and failure gates.

• Keeps package and benchmark-history/typecheck lanes at 45 minutes.
• Extends the policy test across all runtime lanes and CLI.
• Verifies that the workflow consumes each matrix lane’s configured timeout.

_{Reviews (1) · Last reviewed commit: "Allow complete integration and CLI check..."}