[No QA] Replace contributorValidationGate with isAuthorizedContributor action

[roryabraham]

Explanation of Change

Background

contributorValidationGate.yml had four callers:

Workflow	Purpose
claude-review.yml	Gates Claude auto-review on pull_request_target
validateContributorPR.yml	Closes/locks PRs from unauthorized contributors
authorChecklist.yml	Skips the checklist job for unauthorized authors
cla.yml	Skips the CLA signing job for unauthorized authors

What this PR changes

1. Replaces the contributorValidationGate reusable workflow (which unnecessarily spins up a new runner per caller) with a TypeScript isAuthorizedContributor GitHub action built via ncc.
2. Authorization now includes membership in the Expensify contributor-plus org team (via OS_BOTIFY_TOKEN), in addition to existing association, linked-issue assignee, and linked-PR reviewer checks. This is safe for all current use-cases but worht noting - Contributor+ will be able to open pull requests and have them auto-reviewed by Claude.

Fixed Issues

side-quest for #90214

Tests

Automated tests only.

Offline tests

N/A – GitHub Actions only.

QA Steps

N/A – GitHub Actions only.

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I verified there are no new alerts related to the canBeMissing param for useOnyx
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

N/A

[melvin-bot]

@stitesExpensify Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c0b1831a2b

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Restore linked-PR authorization checks for contributors

This change regresses the contributor gate by removing the linked-PR authorization path: isAuthorizedContributor() now only evaluates isAuthorizedViaLinkedIssues(...) after loading the PR body, so external authors who are valid via a linked PR (author/reviewer/requested reviewer) are incorrectly treated as unauthorized. That breaks the prior behavior used by validateContributorPR.yml/claude-review.yml and can cause legitimate contributor PRs to be auto-closed or skipped from downstream workflows.

Useful? React with 👍 / 👎.

[roryabraham]

I intentionally removed this. Here's a snippet from my conversation with Claude:

Rory: What does this function imply? That a contributor can open a pull request because they have another one open? Do we need that for something, or could we just remove it entirely?
...
Claude: The logic implies three separate authorization paths via linked PRs:

1. You authored the linked PR (you've already contributed work)
2. You reviewed the linked PR (you've already done review work)
3. You were requested to review the linked PR (an internal team member nominated you)

The third case (#3 — requested reviewer) is the most defensible: it's essentially "an Expensify employee explicitly invited this person to be involved." But cases #1 and #2 are weak — having authored or reviewed some other PR doesn't really mean you're authorized to open this one.

More importantly, if someone had a PR merged (case #1), they'd already have the CONTRIBUTOR association, which is checked first and would short-circuit before ever reaching this function. So the "you authored a linked PR" path only fires for unmerged PRs — which is even less meaningful as an authorization signal.

The linked issues check is the principled one: being assigned to an issue means someone explicitly tasked you with the work. The linked PR check has no equivalent clear intent.

My recommendation: Remove isAuthorizedViaLinkedPullRequests entirely. The only case worth preserving might be "requested reviewer," but that's a very unusual path and I'd want to know if it was ever actually used before keeping the complexity. Want me to delete the function and update the tests?