#307 The required check's checks job may run 25 minutes, not 15

The Maintainer raised the checks job's timeout from 15 to 25 minutes.

Why

On 2026-10-21, make verify on the runner (its simulators on 300 seeds) took 11 to 14.5 minutes in the runs that finished. Six runs were cancelled at 15:00 with the tests still running:

• #301 (four times);
• adapters/acceptance;
• kernel/unidentified-run-alert.

The mutation shards run the same suite on 40 seeds and pass, so the cancelled runs are slow, not broken.

What changes

• .github/workflows/verify.yml: checks gets timeout-minutes: 25. The head comment gains one line with the measured times.
• examples/workflows/verify.yml and the first yaml block of docs/standards/workflows.md change the same way. They hold the workflow word for word, and tools/check_workflows.py and tools/check_context.py compare them.
• tests/test_tools.py: the tests that removed or changed timeout-minutes: 15 to make a drift or a fault now use 25. Each still fails loudly if its replacement stops matching.

Nothing else changes: no permission, trigger, secret, pin or step.

Gates

• PATH=/usr/bin:/bin SIM_SEEDS=40 make verify: 973 tests, OK.
• Claude review with a security pass: no blockers or majors. Its two wording nits are fixed in 0c5bf91.
• Argon (AGY, gemini-4-argon-high): no findings.
• Muse: not run (Maintainer, 2026-10-20: Kernel/hook only).
• No decision record, by the Maintainer's instruction.

🤖 Generated with Claude Code