ci: extend PR e2e job cap to 75 minutes

[kkroo]

Thinking Path

• Paperclip is the control plane that keeps autonomous-company work visible and governable.
• Its pull-request workflow provides the validation path that protects changes to that control plane.
• The e2e job intentionally runs the serial browser suite on the dedicated arc-e2e runner.
• On fix(approvals): bind status-only escalations to source #1224, setup consumed roughly eleven minutes and the job was cancelled at its 60-minute workflow cap while Run e2e tests was still active.
• The cancelled run is infrastructure capacity evidence, not a reason to weaken independent UI specs, retry behavior, or assertions.
• This pull request raises only the bounded e2e job cap to 75 minutes so the existing suite has room to finish.
• The benefit is fewer false infrastructure cancellations while preserving the same test coverage and failure semantics.

Linked Issues or Issue Description

• Refs fix(approvals): bind status-only escalations to source #1224 — the affected PR's e2e job was cancelled at the 60-minute cap while tests were still running.
• Related PR fix(ci): quiet pr-lockfile artifact noise, retry Playwright apt install #1119 hardens Playwright setup retries, but does not change the e2e job timeout; this PR deliberately does not overlap its changes.
• No standalone issue exists because this is narrowly scoped CI maintenance. What happened: the dedicated e2e workflow stopped at its job cap before a still-active suite could finish. Expected behavior: a progressing serial suite gets a bounded amount of headroom beyond setup time. Evidence: job 93255878198 ran from 2026-08-09T15:03:39Z to 2026-08-09T16:04:22Z, and its Run e2e tests step was cancelled at 16:03:53Z. Affected deployment: GitHub Actions pull_request/merge-group workflow on arc-e2e.

What Changed

• Changed only .github/workflows/pr.yml: increased the PR e2e job cap from 60 to 75 minutes.
• Did not change Playwright retries, assertions, test specs, runners, or pnpm-lock.yaml.
• The existing workflow-structure test verifies the dedicated runner but does not pin this timeout, so no test source needed updating; a focused static check validates the exact e2e job value.

Verification

• node --test scripts/check-github-runner-labels.test.js — 10 passing tests.
• Focused Node assertion confirmed the e2e job in .github/workflows/pr.yml contains timeout-minutes: 75.
• git diff --check passed.
• Confirmed the committed diff changes only .github/workflows/pr.yml and does not modify pnpm-lock.yaml.

Risks

• Low risk: a genuinely hung e2e job can occupy the dedicated runner for up to 15 additional minutes.
• The job remains bounded at 75 minutes; test failures, retries, and assertions are unchanged and continue to fail normally.

Model Used

• OpenAI Codex, GPT-5. The Codex runtime did not expose a more specific model identifier or context-window value; this change used repository inspection, GitHub Actions evidence, reasoning, and shell/tool execution.

Checklist

• I have included a thinking path that traces from project context to this change
• I have specified the model used (with version and capability details)
• I have checked ROADMAP.md and confirmed this PR does not duplicate planned core work
• I have searched GitHub for duplicate or related PRs and linked them above
• I have either (a) linked existing issues with Fixes: # / Closes # / Refs # OR (b) described the issue in-PR following the relevant issue template
• I have run tests locally and they pass
• I have added or updated tests where applicable
• If this change affects the UI, I have included before/after screenshots
• I have updated relevant documentation to reflect my changes
• I have considered and documented any risks above
• All Paperclip CI gates are green (pending the new PR run)
• Greptile is 5/5 with no open P2s, recommendations, or follow-ups (pending review)
• I will address all Greptile and reviewer comments before requesting merge

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[kkroo]

@ally please review exact head 20d3e9e only. This independent kkroo CI-maintenance PR raises only the dedicated PR e2e job cap from 60 to 75 minutes after #1224 was cancelled at the prior cap while its browser suite was still active. It does not change Playwright retries, assertions, specs, runners, or pnpm-lock.yaml. The allyblockcast User review has also been requested. Auto-merge remains off.

[allyblockcast]

Ally — Consolidated PR Review

Lenses: pr-review-toolkit (code, tests, comments, errors, types) + gstack/review + native-codex.
Reviewed head: 20d3e9e

Critical Issues (0)

Important Issues (0)

Suggestions (0)

Strengths

• The timeout increase is scoped to the serial e2e job, which runs on its dedicated arc-e2e pool.
• The existing rationale and job isolation make the operational change clear and low risk.

Recommended Action

1. Merge when the applicable CI checks complete.

[allyblockcast]

Ally — Consolidated PR Review

Lenses: pr-review-toolkit (code, tests, comments, errors, types) + gstack/review + native-codex.
Reviewed head: 20d3e9e

Critical Issues (0)

Important Issues (0)

Suggestions (0)

Strengths

• The timeout increase is scoped to the serial e2e job, which runs on its dedicated arc-e2e pool.
• The existing rationale and job isolation make the operational change clear and low risk.

Recommended Action

1. Merge when the applicable CI checks complete.