ci: allow snapshot harness more time

Two hosted snapshot runs completed setup normally and kept passing cases until GitHub cancelled each job at the exact 60-minute ceiling. The suite had reached its late curated Clippy cases, so the cancellation did not identify a compiler or snapshot failure.\n\nRaise only the snapshot shard ceiling to 90 minutes and update the focused workflow contract to prevent an accidental reduction below the newly observed requirement. The harness stages, six-worker parallelism, cleanup policy, and test coverage remain unchanged.\n\nVerified with the focused CI workflow contract, JavaScript syntax checking, and git diff validation. Hosted CI on this branch provides the final full-suite proof.

Author: fullofcaffeine

.github/workflows/ci.yml

@@ -250,7 +250,7 @@ jobs:
   harness-snapshots:
     name: Harness / snapshots
     runs-on: ubuntu-latest
-    timeout-minutes: 60
+    timeout-minutes: 90
     steps:
       - name: Checkout
         uses: actions/checkout@v5

test/scripts/ci-harness-workflow.test.js

@@ -19,7 +19,7 @@ const timeout = snapshots.match(/^    timeout-minutes: (\d+)$/m)
 
 assert(timeout, 'snapshot harness job must have an explicit timeout')
 assert(
-  Number(timeout[1]) >= 60,
+  Number(timeout[1]) >= 90,
   `snapshot harness timeout must cover the observed full-suite runtime; found ${timeout[1]} minutes`
 )
 assert.match(