Raise the Linux validate job timeout from 40 to 60 minutes while the suite stays serial

[seathatflowsinourveins]

Scope

• What this PR changes, in one or two sentences: raises the Linux validate job's timeout-minutes from 40 to 60 and records why in the comment block above it; the workflow's hash is registered again in manifests/evidence.json. No other change.
• Base commit: 4ced2923063db6a6dcafa9f25af5ee05a4153c75
• Lane: lane:foundation
• Owned paths touched: .github/workflows/validate.yml, manifests/evidence.json (registration only, the branch's last commit, per the hot-file protocol in docs/lanes.md)

SOTA sources

• GitHub documentation: workflow syntax, jobs.<job_id>.timeout-minutes (default 360; the job is cancelled when the limit is reached, or earlier at the runner's own execution limit).
• In-repository precedent, same job: the earlier raises of 2026-09-26 (to 20) and 2026-09-29 (to 40, CI: raise the validate and validate-macos timeouts for the #381 tooling tests #512), recorded in the comment block above the line.
• Measurements, read by GET from the Actions jobs API on 2026-10-03: the validate job took 1745 s, 1745 s and 1727 s in runs 37088360538, 37086567708 and 37085570699; the serial arm of hosted trial run 37109532421 ran the unittest step in 1688 s, 1659 s and 1186 s on ubuntu-24.04. The record of that trial, which explains why the job stays serial: Record the failed hosted trial of unittest-parallel on the two required test jobs #652.

Evidence-class table

Claim	Evidence class	Command / receipt
The validate job took 1727 to 1745 s in three production runs, against a 2400 s limit	independent observation of platform records (Actions jobs API, read-only, 2026-10-03)	gh api repos/seathatflowsinourveins/native-agent-stack/actions/runs/<id>/jobs for the three run ids above
The serial unittest step took 1186 to 1688 s in three hosted runs on ubuntu-24.04	native_proven for the hosted run (actual execution on a GitHub-hosted runner); its sanitized receipt is in #652	run 37109532421, arms-linux jobs, step seconds
The suite grew about fourfold in a week (failing validate jobs: 385 s on 2026-09-25, 1787 s on 2026-10-02)	independent observation of platform records, as recorded in the CI measurements receipt of the open records PR	#632
Raising the limit breaks no workflow rule	local_integration	commands below

Local commands run

$ actionlint .github/workflows/validate.yml
exit 0, no output
$ zizmor --no-config --no-ignores --persona regular --strict-collection .
exit 0: No findings to report (offline mode; the online audits run in this PR's own validate job)
$ python3 -m unittest tests.test_workflow_hardening tests.test_workflow_security_coverage tests.test_osv_lockfile_coverage.LockfileInventoryTests.test_every_tracked_lockfile_and_manifest_is_listed tests.test_blind_checkout.RepositoryClassificationTests.test_every_blueprint_value_under_a_label_key_is_classified
Ran 86 tests, OK (skipped=2); exit 0
$ python3 scripts/validate.py ; python3 scripts/validate_convergence.py --all-recorded --root . --json ; python3 scripts/evidence_manifest.py --check ; python3 scripts/component_matrix.py --check ; python3 scripts/new_host_grand_list.py --check
all exit 0 (validate.py: 9,420 hashed files, 187 receipts)

Decision record

No new record: this is the fourth change of the same limit (5 to 10 minutes, then 20 on 2026-09-26, then 40 on 2026-09-29, now 60) and follows the comment convention above the line. The trial that would have shortened the job instead of raising its limit is recorded in #652. Overturn: lower the limit again when the job is shorter than 20 minutes, for example when the suite runs in parallel.

Host evidence

Not applicable: no files under evidence/hosts/ change.

Checklist

• New/changed GitHub Actions are pinned to a full commit SHA with a version comment (no action changes in this PR).
• New/changed workflows declare top-level permissions: contents: read (unchanged).
• No secrets are printed, logged or committed; no new required secret was added.
• No new paid hosting, subscription or billing surface was introduced: the repository is public and its standard-runner minutes are free.
• Peer-owned untracked files and worktrees were preserved (not deleted, moved or overwritten).

Notes for the merger: three open pull requests (#515, #595, #596) also touch validate.yml; this change is one line plus a comment, so a conflict would be trivial. The limit is a hang guard, not a time budget.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-03T11:09:21.013438Z	54160f9	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[seathatflowsinourveins]

ACCEPT — source scope, exact #653 head 54160f929289217c5948c8c4169a8e77a4bf99cb, base 4ced2923063db6a6dcafa9f25af5ee05a4153c75.

The literal workflow delta is five rationale comment lines and timeout-minutes: 40→60. Serial unittest invocation, action pins, permissions, security steps and other job definitions preserve base bytes. GitHub's pinned timeout definition supplies the supported maximum-minutes hang guard and its runner-limit boundary.

Independent original Jobs-API observations support the cited production durations: 37088360538/job1111031802731745s/head8ad5378b160f62d253877b82c3e523d4206a9931; 37086567708/job1110980091841745s/head0e30c3fe3fcdf774f4d0301408b827633fd1ad7a; 37085570699/job1110950293851727s/headfd111e59a7480c7910907e5cdc9a32a9e42ec42e. The retained trial's three serial step11 durations are1688/1659/1186s at full head 1e4bb5ab7c79faa83e4cd8d04cf8dc6d33c7b0de, run37109532421/jobs111164592004,111164592081,111164591986. Those steps record exit status separately; job success alone is not an arm-result verdict. #652's complete failed-trial record remains under separate source review.

The rationale's pickling mechanism has a primary source: unittest-parallel bda5d77dc1a2fa2df90f5f5a7de297ea375e345c main.py:150–164 uses a spawned pool, maps test suites before result aggregation, and does not supply this candidate with a qualified parallel runner. This timeout-only change keeps the current serial job.

Root verified the actual decoded Git payloads: candidate workflow blob 8a2ed348e89d00438625fdccbf6724607fcdb230,38354B/SHA256 91c2f9a7c532d8a2a63a3754adc9053833294fcafa81e0c315dc78030bba9e83; base blob bca1f18b318259ede079011c42cd816675f881d9,37871B/SHA a6ecc9f9f8f5f56d46a3c6c16ae611968bf34db47fa235c6421a1eb576af2089; pinned GitHub docs blob 0953709ba9871623a320aa24b568a8dd51fbdcbf; pinned unittest-parallel blob 8a2d8df5eb30a2cfefba3b1595cc000dce2e668b. Registry blob 9689e383db78879bec65c00b2e6c8d0e54a87eac,2505617B/SHA f635f5a0837c1d5ca201d0f469887f97789d0e9666009244c86e2d73b1033a2f, preserves9420 row membership/order, all9419 foreign rows and187 receipt/26 convergence records; its sole changed row matches this actual workflow payload.

Nine new native GH reads exited0, full JSON originals retained; two additional pinned-source/trial captures were reused and independently verified. The first trial reader expected a JSON object, then a flat list; the actual paginated list of page objects was inspected and recovered. Both processing errors remain retained. Required native CI for this candidate remains a separate gate; no root tests, workflow restart, package adoption, installed-state or model measurement occurred. Integrate against actual current main while preserving all foreign evidence.