Triage the open issue backlog

[cliffhall]

Part of the triage tracker #4875. Blocked by #4857 (2026-07-28 Spec Refactor) and #4858 (agentic software factory). The shared conventions (close labels, close notes, throttling) are in #4875.

Goal

Triage every open issue: about 258 as of 2026-09-26. Each one ends up either kept (labelled, put on the board, milestoned) or closed with a labelled note. Modeled on inspector#1872.

Buckets

Classify every issue. Cheap heuristics first, then hand-check the rest.

1. Server submissions, README listing requests and other spam: close as out of scope and point to the MCP Registry.
2. Archived servers (github, gitlab, gdrive, puppeteer, slack, sqlite, brave-search, …): close and point to servers-archived.
3. Fixed or made obsolete by the refactor (Tracker: 2026-07-28 Spec Refactor #4857): for example SDK v1 import errors, initialize/session behavior, Roots-dependent access, or SSE transport quirks. Close with the refactor close note, and invite a fresh issue if the problem still reproduces on the new release.
4. Legitimate bugs that still reproduce after the refactor: keep. Label v2 and server-*, put on the board in Todo, and set a milestone.
5. Reasonable feature requests in scope under the contribution guidelines (demonstrating MCP features, usability): keep and put on the board. Otherwise close as out of scope, and say why.
6. Security reports: never close as declined. If a report was filed publicly and should be handled privately, move it to Security Advisories. Proposals that would weaken a control (e.g. widening filesystem or git path access, or turning off validation) may get the security-declined label, using the Inspector's three-condition test adapted to these servers.

Tasks

• Take a full snapshot of open issues (gh issue list --state open --limit 1000 --json …) and record the counts per bucket in a comment here before closing anything.
• Create the shared close labels, if the PR pass hasn't already.
• Finalize the close notes, one per bucket, adapted from inspector#1872's notes A and B. Each one references Tracker: Triage the open issue and PR backlog #4875 in the original comment.
• Hand-review everything that falls in buckets 4–6 before closing anything in bulk.
• Run the scripted, throttled closes for buckets 1–3.
• Put every kept issue on the Servers V2 board with a Status, label and milestone.
• Post a final summary here: counts closed per label, counts kept per server, and anything that became new work.

Acceptance criteria

• No open issue is missing the v2 label and a place on the board, or else a close label.
• Every closed issue carries a close label and a note that references Tracker: Triage the open issue and PR backlog #4875.