fix(ci): drop timeout-minutes from reusable-calling jobs

`jobs.<id>.uses` accepts only with/secrets/needs/if/permissions/strategy/
concurrency. `timeout-minutes` is valid YAML, so every local linter passes
it, but Actions refuses the whole file at parse time — startup_failure with
zero jobs and the workflow listed by path instead of name. That is why these
four workflows have been red on main indefinitely.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: hyperpolymath

.github/workflows/governance.yml

@@ -32,4 +32,3 @@ permissions:
 jobs:
   governance:
     uses: hyperpolymath/standards/.github/workflows/governance-reusable.yml@81dbf2dd854b1444fd6236fa2352474383b2c2b9 # main 2026-06-27
-    timeout-minutes: 30

.github/workflows/hypatia-scan.yml

@@ -32,5 +32,4 @@ jobs:
     # Total caller-side wall-clock cap for the reusable. Matches
     # Hypatia's `missing_timeout_minutes` rule expectation. The scan is
     # typically ~3 min; the cap leaves headroom for slow estate builds.
-    timeout-minutes: 30
 

.github/workflows/mirror.yml

@@ -13,4 +13,3 @@ jobs:
   mirror:
     uses: hyperpolymath/standards/.github/workflows/mirror-reusable.yml@e9c8888769a703924cc3c0d717900960d78aea00
     secrets: inherit
-    timeout-minutes: 60

.github/workflows/secret-scanner.yml

@@ -20,5 +20,4 @@ jobs:
       pull-requests: write
       actions: read
     uses: hyperpolymath/standards/.github/workflows/secret-scanner-reusable.yml@e9c8888769a703924cc3c0d717900960d78aea00
-    secrets: inherit
-    timeout-minutes: 20
+    secrets: inherit