[cixzhang]

Maintainer impact

• Before: the WebKit interaction proof (pr-interaction-webkit) runs when a pull request touches the press, touch and gesture code it guards. fix(core): one click guard for the menu press model and the gesture host #8360 adds new shared interaction modules: the click guard, the coarse-pointer and input-stream helpers, the flat tree, the selection lock, and the haptic switch style. With the old scope, an edit to any of them would skip the WebKit proof.
• After: the WebKit lane also runs for those paths and for hooks/isRtlElement (the direction read the gesture code uses).
• This lands fix(core): one click guard for the menu press model and the gesture host #8360's CI-scope change on its own, because a fork pull request's .github changes can't run with the repository's workflows. The code change stays in fix(core): one click guard for the menu press model and the gesture host #8360.

Change

• .github/workflows/ci.yml, pr-interaction-webkit scope paths: utils/(…|flatTree|inputStream|clickGuard|selectionLock|coarsePointer), privateAttributes/hapticSwitch.stylex.ts, hooks/(…|isRtlElement).
• .github/scripts/ci-interaction-webkit.test.mjs: the "untouched" example utils/clickGuard.ts, now in scope, becomes utils/focusReturn.ts.
• Both hunks are taken verbatim from fix(core): one click guard for the menu press model and the gesture host #8360, with credit to its author.

Evidence

• On main, the new prefixes match only packages/core/src/hooks/isRtlElement.ts, which already exists. The other eleven matching files are all added by fix(core): one click guard for the menu press model and the gesture host #8360, so they route nothing until it lands.
• ci-interaction-webkit, ci-interaction, workflow-paths and ci-tooling-routing tests pass (59 tests). The existing fix(core): one click guard for the menu press model and the gesture host #8360 routing case (utils/clickGuard.ts runs the lane) already covers the new scope.
• CI impact: no runner-class change (the WebKit lane keeps its standard runner). The WebKit lane also runs for these new paths, plus hooks/isRtlElement.ts, which has changed rarely (last in fix(core): auto-detect RTL for arrow-key navigation in focus hooks #4350). Expected runner-pool change is near zero today; it grows only with pull requests that touch fix(core): one click guard for the menu press model and the gesture host #8360's modules once it lands. No effect on time to green for other pull requests.

Scope

• One change: the WebKit proof's path scope.
• Public text contains no internal Meta context.

[vercel]

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

Project	Deployment	Actions	Updated
astryx	Ready	Preview	Nov 1, 2026 6:15pm UTC

[astracat-bot]

AI review status for this pull request.

Review status	Updated
🟢 Reviewed (for maintainers only)	Nov 1, 2026, 6:15 PM UTC

[github-actions]

PR Analysis Report

🔎 Preview · 8c94a7d

Storybook · Sandbox · built from this PR's head

Package size: no published package changed; no new dependencies.

Not run on this PR: add ci:run-visual, ci:run-a11y or ci:run-rtl to run them.

CI impact: +2.7 job-min per update · pool +3.4% · standard runners · 1 CI action or script file changed (not measured)

	Before	After	Change
Job-minutes per PR update	78.7	81.3	+2.7
Runner pool, runner-minutes a day	36,690	37,932	+1,241 (+3.4%)
Average concurrent jobs	25.5	26.3	+0.9
Time to green (median → this run)	—	11.9 min	—
Runs a day	466	466	0

Changed jobs: pr-interaction-webkit changed: standard

Not measured (the jobs that use these keep their recent minutes above): .github/scripts/ci-interaction-webkit.test.mjs.

Assumptions: before is each job's average over the last 20 pull-request runs; after keeps that for unchanged jobs and uses this run's minutes for added or changed ones, weighted by how often each changed job ran in those runs; runs a day averages the seven whole days before today; time to green compares this run with the median of those runs that ran the same jobs.

---

_{Generated by PR Enrichment workflow | View full report}

[astracat-bot]

This looks ready to merge. The WebKit lane's scope adds seven paths and drops none, so no pull request loses the proof, and the routing tests pass. One optional follow-up: no test pins the new paths, because the #8360 replay still passes on GestureHost.ts alone. Adding them to the "runs for" list in ci-interaction-webkit.test.mjs would catch a later edit that drops one.

[Automated review]

[astracat-bot]

Optional: the seven paths this PR adds to the scope aren't asserted anywhere. This file passes unchanged against the old regex, because the #8360 replay below already runs on GestureHost.ts. Adding packages/core/src/utils/clickGuard.ts, inputStream.ts, coarsePointer.ts, flatTree.ts, selectionLock.ts, packages/core/src/privateAttributes/hapticSwitch.stylex.ts and packages/core/src/hooks/isRtlElement.ts to the "runs for" list above would pin them.