[vjeux]

Review only this PR's change: two lines in the WebKit interaction job's routing. It holds the CI hunks split out of #8342, which adds the Layer module's input hold, so that a maintainer can land them from a branch in this repository.

Maintainer impact

#8342 makes the gesture host ask the input hold (packages/core/src/Layer/inputHold.ts) about each touch, so the gesture specs' fixture bundles that file. The WebKit routing test requires every file the fixture bundles to be in the job's path filter. Without this change, that test fails on #8342, and a change to the hold alone would skip the WebKit proofs.

Intended invariant

Everything the WebKit interaction specs bundle stays in the job's scope, as .github/scripts/ci-interaction-webkit.test.mjs already checks for the gesture, motion and pager bundles.

Change

• .github/workflows/ci.yml: the WebKit interaction job's paths: filter gains packages/core/src/Layer/inputHold\.ts$.
• .github/scripts/ci-interaction-webkit.test.mjs: the in-scope list gains that path.

Evidence

• Failure before the change: on feat(Layer): one input hold, first used by Dialog, Drawer and MobileNav (spec:AST-094 FR35) #8342 without these hunks, "keeps everything packages/core/src/gestures/tests/browser/fixture.ts bundles in scope" and "keeps everything the pager bundle bundles in scope" fail on packages/core/src/Layer/inputHold.ts.
• Success after the change: with this commit merged under feat(Layer): one input hold, first used by Dialog, Drawer and MobileNav (spec:AST-094 FR35) #8342, .github/scripts and the touch bundle test pass (2,539).
• Product/runtime behavior verified unchanged: no product file changes.
• CI impact: none today. packages/core/src/Layer/inputHold.ts does not exist on main until feat(Layer): one input hold, first used by Dialog, Drawer and MobileNav (spec:AST-094 FR35) #8342, so no pull request can touch it, and job-minutes per update, runner-pool usage and time to green are unchanged. After feat(Layer): one input hold, first used by Dialog, Drawer and MobileNav (spec:AST-094 FR35) #8342, a pull request that touches only the hold runs the two pr-interaction-webkit legs instead of skipping them: two ubuntu-latest runners at about 4.4 minutes each (median over the last 9 runs that ran them; at most 6.2), about 9 job-minutes per update instead of 0.2. Both legs run beside the Chromium interaction legs after the Storybook build, so time to green grows only when a WebKit leg is the slowest job. A pull request that already touches another path in the filter sees no change.

Scope

• No intended public API, product behavior, visual direction, or policy change.
• Product changes discovered during the work were removed or split.
• Public text and artifacts contain no internal Meta context.

Testing

pnpm exec vitest run --project node .github/scripts/ci-interaction-webkit.test.mjs passes on this branch (14). Run with #8342 merged on top, .github/scripts and scripts/touch-support-bundle.test.mjs pass; without this commit, the two bundle-scope cases above fail.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
astryx	Ready	Preview	Nov 4, 2026 8:20am UTC

[astracat-bot]

AI review status for this pull request.

Review status	Updated
🟡 Reviewed (for maintainers only)	Nov 4, 2026, 8:22 AM UTC

[github-actions]

PR Analysis Report

Current run: The current CI run concluded skipped. Current analysis is unavailable.

---

_{Generated by PR Enrichment workflow | View current CI run}

[astracat-bot]

Changes requested, for the pull request description only: the routing change itself looks correct.

• The CI impact: line needs job-minutes per update, runner-pool usage and time to green beside the runner class, as AST-030 FR19 requires for a workflow change; for example, that all three are unchanged today because packages/core/src/Layer/inputHold.ts does not exist on main until #8342, and what the two WebKit legs add afterwards for a pull request that touches only the hold.

The new path matches only the hold, and the routing test fails without the ci.yml change, so no code change is needed. CI has not run on this head yet, since it is a draft on a fork branch.

[Automated review]

[vjeux]

Re-landed as #9913 (b87922f).