Skip to content

fix(link): verify recorded runtime paths before probing - #840

Closed
luvs01 wants to merge 11 commits into
devfrom
fix/remote-recorded-runtime-trust
Closed

luvs01 wants to merge 11 commits into
devfrom
fix/remote-recorded-runtime-trust

Conversation

@luvs01

@luvs01 luvs01 commented Nov 16, 2026 •

Copy link
Copy Markdown
Owner

Summary

Remote Link treats a recorded runtime path as a discovery hint. Previously its first version probe could execute the recorded binary or package entrypoint before checking who controls that path.

  • Verify the executable and optional entrypoint before any version probe in POSIX discovery, pinned sync, runtime inspection and full-install census.
  • Admit recorded targets on Linux only: require a regular file owned by the SSH account without group/world write bits, and walk original and symlink-target components to check directory replacement authority. Trusted sticky directories remain compatible; traversal is bounded.
  • Preserve the original verified Linux path spelling for package-prefix and entrypoint compatibility. Missing ownership/stat/readlink/platform evidence, symlink loops and ambiguous newline targets skip the record.
  • Skip macOS records as discovery authority before probing that candidate. Mode bits omit ACL grants, and Apple's ls can silently treat an ACL read failure as an absent ACL. Reusing macOS hints needs a native ACL reader that distinguishes those outcomes along the entire path. Existing Desktop, system and PATH discovery continues.
  • Update the owning Remote Link contract and English/Korean operator guidance.

Addresses the Daybreak finding and the macOS ACL review finding.

Historical reviewed checkpoint: base c36793a9336b70cfe5bc3b7f6e6f751e730fb6fc, head b689549a97d0298db567aeb1cfce7c436fc9c83c, independently reviewed tree 487f1b2e00fccaf74574ac5825744347d821a43c. The latest integrated head and its evidence are listed below.

The earlier implementation and verification below used base e87572127d7804216ebfcf0feecaf4c22c181748 and tree 8beec34186cc08bd34d214a233425c5dcfcc5d15.

Compatibility and limits

A macOS installation available only through its runtime record is no longer selected or detected. Add it to the SSH account's PATH or install it in an existing discovery location. Full-install census, including the --require-ephemeral check, can only detect the remaining known install locations on macOS; it may proceed when a record-only full install exists. This change does not execute or remove that undiscovered installation.

This change removes the extra execution authority provided by arbitrary census paths. Existing Desktop/system locations and the SSH account's PATH retain their prior executable/version checks; this PR does not add ownership or ACL validation to those fallback locations. A path rejected through the census can still execute if it is independently selected through one of those locations. A controlled writable-Desktop fixture produces the same calls across all four consumers with and without a census record, confirming that this is an existing fallback policy rather than authority granted by the record.

The checks do not claim protection against root or unrestricted same-account mutation. The shell checks do not bind an opened executable descriptor through execution.

Verification

Current integration — 2026-11-19

Current head: 48a43573170eb6df3d0f0d9f0f28f90ed6e26a3d. It includes integration commit 7f21d442813c8b4779b9367126bb2c505f513849, which normally merges the prior PR head 374867f6a068c50beaa2ec4e17e57876c88c87cc with current dev 80e8952357d11ccf1421b4aa5620e781625dcdb0. The published GitHub tree exactly matches the locally verified tree 709c9f66e746dafba75a253cbc17fac654320f1a.

The actual test-layout conflict was resolved by retaining all 3,340 dev mappings without value changes, plus this PR's one trust-test mapping. Independent source review confirmed that both changed runtime files and all five related regression files are byte-identical to the preceding PR head. The automatically integrated English/Korean documentation retains the same trust contract.

This head also applies the measured-duration refresh from upstream PR #8940. The previous timing table assigned 60 unrecorded completed files only 8.58 seconds although their observed total was about 170.5 seconds. The refreshed table uses completed hosted-file samples and preserves all 20 newer dev timing rows exactly, including the split Link stop tests. Final TSV SHA-256: 2d56880fe64338d36b424bb73178b025078ca1482da5dd4be6e73c6792759be5; Git blob: a07f90e6098082e1452ea5cc075c801271321eca. That data-only refresh preserved the shard count, job limits, assertions, required gates and test selection. The later bounded outer-job budget change is documented separately below.

  • bun test tests/ci-workflows/ci-shard-balance.test.ts tests/ci-workflows/ci-crash-disposition.test.ts tests/clients/link-served-runtime-trust.test.ts tests/clients/link-child-update-launcher.test.ts tests/clients/link-gated-ocx-argv.test.ts tests/clients/link-pinned-sync-argv.test.ts tests/clients/link-ssh-argv-discovery.test.ts tests/test-layout.test.ts tests/test-layout-tooling.test.ts: 244 passed / 19 Windows-related skips / 0 failed / 7,924 assertions.
  • bun run typecheck: 2,625 files, no errors.
  • The earlier policy-only follow-up passed node .github/scripts/release-evidence.cjs policy-check and the exact CI command node --test .github/scripts/release-dispatch-guard.test.cjs .github/scripts/release-evidence.test.cjs .github/scripts/release-history.test.cjs .github/scripts/release-resume.test.cjs .github/workflows/deploy-docs.test.cjs: 69 passed / 0 failed / 0 skipped, including the fixed historical Git trees. The original production-pin mismatch was reproduced before the change.
  • bun run structure:check, bun run privacy:scan, and whitespace checking against dev passed.
  • Documentation build: 793 pages / 121,114 internal links, using isolated Astro/Vite caches.
  • The common timing-data candidate's actual-runner probe preserves all 3,358 general dev test files exactly once across five shards; it records arguments instead of executing assertions, and does not claim a passing suite. This PR's additional trust test remains present and is covered by the focused run and hosted full-lane selection.

Runs used the normal repository preload, its unmodified network guard, isolated temporary filesystems and local fixtures. No live provider, live SSH endpoint or installed application was exercised. The documented focused-validation exception applies because concurrent worktrees share resources. Full local tests, native macOS/Windows acceptance and live-provider acceptance are not claimed.

The earlier policy-only follow-up appends the documented release-evidence fingerprint snapshot for the new TSV. All 26 historical approval records remain unchanged. The new record changes only the TSV hash; the other 26 pins, version and required platform jobs are identical. Independent security review approved policy blob 51c1f898f2bdd69b7a012bd191ac51acb3c1779b. That policy-only change preserved runtime, tests and documentation; the later fixture-only and outer-job budget changes are documented separately below.

Fixture preparation cost follow-up — 99bdab2b

Both attempts of run 44463273114 for preceding head 93eb2c1b failed to complete. In attempt 1, shards 2/5 and 3/5 reached the unchanged 15-minute job limit in batches 60/63 and 57/65. One evidence-based failed-job-only retry was allowed; it again timed out in batches 60/63 and 64/65, with no failed assertion before cancellation. No further retry of that head was started. The release-contract gate and the other three test shards passed, but those successes do not make either attempt green.

Commit 99bdab2b addresses repeated fixture startup cost in one test helper, tests/helpers/codex-cli-apply-fixture.ts. It does not change production runtime, regression assertions, test selection, the TSV, job counts, limits or release policies.

  • The main and backing local package for each version are packed by one real npm process. All four real package archives and the separate real installation remain; fixture setup starts npm three times instead of five. The two local packages in a pair share that command's fresh npm cache. The next version and the installation still start with their own new empty package cache, npm configuration and working directory.
  • Only Node's compiled-code cache is reused within the same fixture-owned root, which is removed by fixture cleanup. No global cache, cache shared with another fixture, package archive cache, install result or readback assertion is introduced or reused. Production isolation helpers are unchanged.

A controlled offline A/B used three independent fixtures per variant on Node 24.22.3. Baseline setup took 4,277 / 3,597 / 3,699 ms, and the new helper took 1,889 / 1,744 / 1,830 ms (median 3,699 → 1,830 ms). All four npm-created archive hashes, the installed version, empty installer trace and independent command workspaces were checked: 30 assertions passed. This measures local preparation cost; it is not a guarantee about hosted job duration.

Focused existing regression command: bun test tests/codex-integration/codex-cli-update-apply.test.ts tests/codex-integration/codex-cli-update-process-fixture.test.ts tests/codex-integration/codex-cli-update-plan.test.ts tests/codex-integration/codex-cli-update-artifacts.test.ts reported 141 passed / 1 platform skip / 1 failed / 800 assertions. The failed management lost-response case stops at waitForDurableAdmission; the same single case was reproduced with the original helper in the same local sandbox, failing at the same point after the same eight assertions. It is not counted as passing. Hosted run 44468943739 at 99bdab2b also passed that same case with the new helper in 11,535.38 ms; that observed result does not erase the local sandbox failure or the hosted job cancellation described below. The actual installer, lease, integrity/readback, argument and production cache-isolation cases passed locally.

The integrated tree also passed bun run typecheck (2,625 files), privacy scanning and whitespace checks. Independent source/security review checked the actual npm implementation's output order, distinct archive names including Windows, all path consumers, cache and cleanup ownership, and unchanged assertions. Reviewed helper blob: 5cf138bef3281035b161f196966044efe8df685c; reviewed patch SHA-256: 407d0022838a1b2a87e85a1c0eb4fbb58490d108961bdfd01af1b51811ba1056.

Bounded outer-job budget follow-up — 48a43573

Run 44468943739 at 99bdab2b remained unsuccessful at the 15-minute outer job limit, even though both cancelled shards emitted their complete test results:

  • Shard 2/5: 672 files / 63 of 63 batches / 13,678 passed / 0 failed. The test step and every post-step completed successfully; the overall job was nevertheless cancelled at finalization.
  • Shard 3/5: 672 files / 65 of 65 batches / 15,303 passed / 0 failed. Its final summary preceded the cancellation line by 0.302 seconds.
  • Shards 1/5, 4/5 and 5/5, the release-contract gate and the Catalog workflow passed. The two cancellations still make the main workflow unsuccessful. No retry of that head was started.

The follow-up changes exactly three files. The full Linux job's bounded outer allowance increases 15 → 18 minutes, including checkout, dependency setup, GUI build and cleanup. All five shards, the default 120-second batch deadline, existing longer per-file deadlines including 300-second conformance cases, assertions, selection and required gates remain intact. No retry-to-green mechanism or trigger, permission, runner-trust or platform-coverage change is introduced. The workflow test still asserts the exact job-owned limit, now 18.

The release evidence policy retains all 27 historical records and appends one reviewed snapshot. Only the workflow fingerprint changes; the other 26 pins, version and 14 Windows jobs stay identical. New policy blob: 7df235ec7904dd19a4b2e588ecfba1da627e9972. The exact three-file common candidate passed 251 CI-contract tests / 9,573 assertions, 69 Node release-contract tests, type checking and policy-check. Independent manual security review verified the complete parsed YAML is otherwise identical, the runner bytes and fail-closed evidence requirements are unchanged, and the historical records remain intact. Review patch SHA-256: 3e18ab649f9766f74859c7eb9ae2f400f1eddbc8d8c4496f77a22fff5f675f7b. No automatic Cloud scan is claimed.

The fixture helper 5cf138be, duration table a07f90e6 and all runtime/security regressions are unchanged by this follow-up. The actual CI merge 07ba0c931f68af0147e324145b2379210621fc35 has the same tree 709c9f66e746dafba75a253cbc17fac654320f1a as the reviewed branch.

Current exact-head main CI 44472490973 and Catalog 44472490959 both completed successfully. The main run passed on attempt 1, with no retry at this head. All five full Linux shards, gates, documentation, structure, storage, API usage, npm, keyring, Docker and the Linux desktop packaging/E2E job succeeded. The final ci aggregator confirmed every job requested by this PR event succeeded at 2026-11-19 06:50:19 UTC.

Full Linux shard Test step Complete job Result
1/5 11m 31s 12m 24s Success
2/5 12m 14s 13m 09s Success
3/5 13m 04s 13m 58s Success
4/5 13m 17s 14m 13s Success
5/5 11m 07s 11m 57s Success

This execution verifies the published tree. All five jobs happened to finish below 15 minutes on these hosts, so the result is not attributed solely to the revised 18-minute ceiling and does not guarantee future runner speed. The earlier failed runs remain recorded above. Native macOS/Windows acceptance and maintainer security approval remain separate requirements; skipped platform jobs are not claimed as executed.

Intermediate hosted evidence — 7f21d442813c8b4779b9367126bb2c505f513849

Run 44461327832 executed the measured-duration table on actual hosted runners. All 3,359 general files / 327 batches completed across the five Ubuntu test jobs, reporting 71,580 passed / 0 failed in aggregate.

Shard Test step Complete job Result
1/5 12m 42s 13m 37s Success
2/5 12m 52s 13m 44s Success
3/5 12m 55s 13m 48s Success
4/5 12m 05s 13m 02s Success
5/5 11m 57s 12m 51s Success

Every job finished within the unchanged 15-minute limit. This is observed execution evidence for the intermediate head, not a guarantee about future runner speeds. Docker, documentation, structure, storage, API-usage and npm-global jobs also passed.

The overall run was not green: its release-contract gate failed because the production policy still pinned the old TSV blob. The final follow-up above fixes that mismatch through the documented snapshot append, preserving the original assertion. This intermediate run was allowed to finish so its actual test outcomes were retained before the new commit was pushed.

Earlier exact-head CI and investigation

At preceding head 374867f6a068c50beaa2ec4e17e57876c88c87cc, main CI 44448708478 concluded cancelled and the aggregate check failed. Shard 2/5 reached the 15-minute job limit in batch 56/61; its first 55 batches reported 0 fail, with no failed assertion before cancellation. Its unfinished batches are not claimed as tested. Shard 3/5 completed all 65/65 batches with 0 fail, but the job was cancelled at finalization. Shards 1/5, 4/5 and 5/5, and Catalog async contracts, passed.

The slow-file investigation found stale timing inputs and runner variation. It did not establish a product timer leak or an unnecessary wait that could safely be removed. The intentionally bounded Lab, scheduler and configuration-lock cases retain their existing contracts. No blind retry of this head was started. Timing replay is an allocation estimate and leaves setup, process-boundary overhead and runner variation to actual CI.

The still earlier head b689549a97d0298db567aeb1cfce7c436fc9c83c had incomplete main CI, attempt 2: shard 2/5 reached the 15-minute job limit in batch 60/63; the other four shards passed. A failed-job retry had already been used. The original 20-case security regression produced 17 failures / 3 compatibility controls on unfixed code, and the subsequent platform correction produced 10 new failures while retaining 20 Linux controls on its preceding version. The local platform checks use Linux fixtures and BSD-format / Darwin shims, not native macOS or Windows execution.

Checklist

  • Scope stays focused and avoids unrelated cleanup.
  • Docs or release notes were updated when needed.
  • Security-sensitive changes were reviewed for secrets, auth, and unsafe defaults.

The last item records implementation and independent source review, not maintainer approval.

Summary by CodeRabbit

  • Security
    • Linux Remote Link uses recorded installations only when it can verify the executable and optional package entrypoint are protected from replacement by other accounts; otherwise, it skips them.
    • macOS and unsupported or unverifiable platforms skip recorded installations. Linux and macOS continue discovering installations through Desktop, system locations, and PATH.
    • On macOS, installations available only through recorded paths must be made discoverable another way. A successful version response alone does not verify ownership.
  • Documentation
    • Updated the Remote Link guides to explain recorded-installation checks and discovery behavior.

@coderabbitai

coderabbitai Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Explain Change →

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • Resume reviews
  • Trigger review

No actionable comments were generated in the recent review.

Walkthrough

The SSH runtime flow now checks recorded runtime paths before use. Linux candidates require verifiable ownership and permissions; macOS and unverified platforms skip recorded candidates. The change also updates CI timeout settings and npm fixture package creation.

Changes: Recorded Runtime Trust

Layer / File(s) Summary
Validate recorded runtime paths
src/link/remote-runtime-trust.ts, src/link/ssh-argv.ts, structure/remote-link.md, docs-site/src/content/docs/guides/remote-link.md, docs-site/src/content/docs/ko/guides/remote-link.md
The shared check validates Linux served paths, including ownership, permissions, path components, and symlink traversal. The SSH runtime flow checks the binary and any supplied package entry before attempting the recorded runtime. Documentation describes platform-specific checks and discovery behavior.
Test trust checks and fallback behavior
tests/clients/link-served-runtime-trust.test.ts, tests/clients/link-*-argv.test.ts, tests/clients/link-child-update-launcher.test.ts, scripts/test-layout/layout-clients.json, tests/fixtures/test-layout-expected.json
Tests cover trusted and untrusted recorded paths, platform-specific skips, and fallback when required tools are unavailable. POSIX fixtures provide Linux-reporting uname commands and path-inspection utilities. The new test is classified in the client layout.

CI Test Timeout

Layer / File(s) Summary
Update the test job budget and evidence
.github/workflows/ci.yml, tests/ci-workflows/ci-workflows.test.ts, .github/scripts/release-evidence-policy.json
The test job timeout changes from 15 to 18 minutes. The workflow test expectation and release-evidence policy entries are updated.

NPM Fixture Setup

Layer / File(s) Summary
Update npm fixture package creation
tests/helpers/codex-cli-apply-fixture.ts
The npm fixture sets NODE_COMPILE_CACHE to a fixture-owned directory. It packs both local packages in one invocation and reads the archives from the fixture root.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Change: Bug fix

Sequence Diagram(s)

sequenceDiagram
  participant SSHRuntime
  participant PathTrustCheck
  participant Discovery
  SSHRuntime->>PathTrustCheck: Validate recorded executable and entry paths
  PathTrustCheck-->>SSHRuntime: Return trusted path or reject
  SSHRuntime->>Discovery: Continue discovery if recorded paths are rejected
Loading

Suggested reviewers: lidge-jun, ingwannu

Merge Risk: Minimal · up to 48a43

Recorded runtime paths are now verified before probing on Linux and skipped on macOS. The sticky-bit concern in the test fixtures is addressed by the current stat format. No concrete merge-blocking risk remains.

Pre-merge checks: Passed 4

Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title "fix(link): verify recorded runtime paths before probing" matches the main change. The PR treats recorded runtime paths as discovery hints and verifies executables and entrypoints (ownership…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Title check

Explanation

The title "fix(link): verify recorded runtime paths before probing" matches the main change. The PR treats recorded runtime paths as discovery hints and verifies executables and entrypoints (ownership, mode, symlink, path-component checks) before any version probe. The title is concise, specific, and follows a conventional commit style. It does not mention the macOS skip or the Linux-only verification, but it does not need to cover every detail.

Finishing Touches

Generate unit tests (beta)

  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

Recent review info

Run configuration

Commits

Reviewing files that changed from the base of the PR and between b689549 and 48a4357.

Files ignored due to path filters: 1

  • scripts/ci/test-durations.tsv is excluded by !**/*.tsv
Files selected for processing: 7

  • .github/scripts/release-evidence-policy.json
  • .github/workflows/ci.yml
  • docs-site/src/content/docs/ko/guides/remote-link.md
  • structure/remote-link.md
  • tests/ci-workflows/ci-workflows.test.ts
  • tests/fixtures/test-layout-expected.json
  • tests/helpers/codex-cli-apply-fixture.ts

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

✅ Deterministic PR hygiene checks passed.

@github-actions github-actions Bot added the bug Something isn't working label Nov 16, 2026
devin-ai-integration[bot]

This comment was marked as resolved.

luvs01 commented Nov 16, 2026

Copy link
Copy Markdown
Owner Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

luvs01 commented Nov 16, 2026

Copy link
Copy Markdown
Owner Author

@coderabbitai review

Please review the latest head cefa181f516c69414f395625128c50c2cc33b95b, including the fail-closed treatment of recorded runtime hints on Darwin and unknown platforms.

@coderabbitai

coderabbitai Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

coderabbitai[bot]

This comment was marked as resolved.

Preserve POSIX recorded-path trust checks and current Windows census and packed-command behavior. Preserve both sides of the test-layout registry without changing its established formatting.

Validation: focused synthetic/loopback coverage, typecheck, structure and privacy checks; file-size gate passed after retaining the upstream registry format. Independent conflict-resolution review found no blocker.
@luvs01

luvs01 commented Nov 17, 2026

Copy link
Copy Markdown
Owner Author

No description provided.

coderabbitai[bot]

This comment was marked as resolved.

@luvs01
luvs01 marked this pull request as ready for review November 18, 2026 00:06
@luvs01

luvs01 commented Nov 18, 2026

Copy link
Copy Markdown
Owner Author

No description provided.

coderabbitai[bot]

This comment was marked as resolved.

Keep the 1007 and 4005 metadata-format assertions without requiring root-only sticky regular-file permissions on Darwin. Restore owner access to the directory before fixture cleanup.

Focused discovery and trust tests: 74 pass, 18 platform skips, 393 assertions. Typecheck, privacy, size and whitespace checks passed; independently reviewed.
@devin-ai-integration

Copy link
Copy Markdown

Review-thread audit: no unresolved Devin Review, CodeRabbit, or Codex connector threads remain on this PR. Fixed on head: the macOS ACL trust-boundary finding, the census fixture trust-tool finding, the BSD stat special-bit finding, and the sticky-bit padding fixture finding. Dismissed: none. No new code changes were needed.

@luvs01

luvs01 commented Nov 18, 2026

Copy link
Copy Markdown
Owner Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Pack each version's two local packages in one real npm invocation and reuse only Node's compiled code within the fixture-owned root. Keep fresh per-command npm config and package caches, the separate real installation, existing readback assertions, and CI budgets unchanged.
Keep all five shards, test deadlines, assertions and required gates intact.
Raise only the full Linux job ceiling to 18 minutes after healthy complete
batch output was cancelled at finalization. Preserve historical release
evidence policies and pin the reviewed workflow snapshot.
@luvs01

luvs01 commented Nov 19, 2026

Copy link
Copy Markdown
Owner Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

luvs01 commented Nov 20, 2026

Copy link
Copy Markdown
Owner Author

Closing this branch in favor of two focused upstream reviews on dev at d61cca122.

  • lidge-jun/opencodex#8981 carries the Remote Link change at f2d38e7dc4ad160763d9f818db4b49354baed12c. All 12 published file blobs match the local integration. The runtime trust helper and its dedicated regression file are byte-identical to this PR's head 48a43573. That PR documents the outstanding Windows test failures.
  • lidge-jun/opencodex#8982 carries the independent npm fixture optimization at fb913faacc2036cf74d303bf0a3f3a8040e79879. Its only file has the same blob as the change here, 5cf138bef3281035b161f196966044efe8df685c.
  • The timing table is already on upstream dev with the same blob, a07f90e6098082e1452ea5cc075c801271321eca. Upstream #8944 set the Linux budget to 20 minutes. Its workflow, regression assertion and evidence pin take precedence over the earlier 18-minute proposal.

Both upstream PRs remain open for review.

@luvs01 luvs01 closed this Nov 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant