readme-pr-check cannot fire on ADDITIONAL.md, so fourteen pull requests sit with no answer #4850

ADDITIONAL.md receives pull requests that no guard can answer, and fourteen of them are queued with zero comments between them.

.github/workflows/readme-pr-check.yml posts the "we are no longer accepting PRs to add new servers" comment and applies the readme: pending label. Two independent things stop it firing on an ADDITIONAL.md pull request:

on:
  pull_request_target:
    paths: ['README.md']

and then, inside the job:

if (files.length !== 1 || files[0].filename !== 'README.md') return;

The trigger filter never matches. The body would return early even if it did.

Measured on 2026-09-26. Fourteen open pull requests touch ADDITIONAL.md: #4836, #4818, #4802, #4779, #4778, #4766, #4751, #4743, #4727, #4699, #4675, #4671, #4664, #4646. All fourteen have zero comments.

Against that, exactly one merged pull request has ever touched the file:

merged PRs touching ADDITIONAL.md: 1
  #4255  2026-05-30T16:44:48Z  Move a list of frameworks and resources to a separate md file

That is #4255, which created the file.

The mismatch matters because ADDITIONAL.md is where a contributor lands after reading that the README is closed. CONTRIBUTING.md says "We don't accept: New server implementations". The pull request template says "We are no longer accepting PRs to add servers to the README". CLAUDE.md says "Not accepted: New server implementations …, README server listing changes". None of that reaches somebody who opens a pull request against the other file, because the one mechanism that says it in the thread covers README.md only.

Two of the fourteen add servers rather than frameworks or resources, and ADDITIONAL.md does not cover servers. Line 3 describes "a curated collection of community-built frameworks and resources that simplify building MCP servers and clients", and its only top-level sections are ## 📚 Frameworks and ## 📚 Resources. The ### For servers heading under Frameworks means frameworks for building servers.

Two ways to close it, and the choice is a maintainer decision rather than a technical one.

Add ADDITIONAL.md to the trigger and relax the filename check, so the same comment and label reach these pull requests. The wording needs a second branch, because the answer for ADDITIONAL.md concerns scope rather than the README being closed.

Or state the inclusion rules in ADDITIONAL.md itself. It carries none today, so a contributor cannot know that a server entry does not belong there until after opening the pull request.

I have no preference between them and no standing to pick. The fourteen-with-zero-comments number is the part worth acting on.