docs(AGENTS): board tracks issues only, never PRs

[cliffhall]

Closes #1581.

Reconcile a contradiction in the board workflow section of AGENTS.md: line 109 says every board item is a real GitHub issue, but the "created" callout and the add-to-board bullet said "issue or PR."

Now consistent — only issues go on board #28, never PRs. A PR still gets the v2 label but is tracked through its linked issue's card via Closes #N. Also updated the recipe comment/URL placeholder to say "issue" rather than "issue/PR".

🤖 Generated with Claude Code

[cliffhall]

@claude review

[claude]

Claude finished @cliffhall's task in 32s —— View job

---

Code Review — docs(AGENTS): board tracks issues only, never PRs

• Read the diff and surrounding context
• Verify the change resolves the contradiction (docs(AGENTS): board tracks issues only, never PRs #1581)
• Check for any remaining "issue or PR" inconsistencies

Verdict: LGTM ✅ — clean, correct docs-only change that resolves the contradiction cleanly.

What it does

The section already declared "Every board item is a real GitHub issue" (line 109), but two earlier statements said "issue or PR". This PR reconciles them so the whole section says one thing: only issues go on board #28; PRs are tracked via their linked issue's card (Closes #N).

The four edits are internally consistent and match the rest of the section:

• The "created" callout (line 106) now scopes to issues and adds the clarifying sentence about PRs still carrying the v2 label.
• The add-to-board bullet (line 116) is now issue-scoped with the parenthetical about PRs.
• The recipe comment + URL placeholder (lines 149–150) now say issue / <issue-url>.

This aligns with the existing merge-workflow bullets (lines 121–122), which already treat the PR/issue relationship as label + Closes #N linkage, never a board card.

Minor nit (non-blocking)

The generic one-liner at line 163 still uses <url> as its placeholder:

ITEM_ID=$(gh project item-add 28 --owner modelcontextprotocol --url <url> --format json --jq '.id')

For full consistency with the just-updated <issue-url> on line 150, you could make this <issue-url> too. It's genuinely optional — <url> reads as generic and the surrounding prose makes the issues-only intent unambiguous. Fix this →

No functional/code impact (docs only, no tests to run). Nice cleanup.
• branch docs/board-issues-only

[cliffhall]

Thanks! Applied the optional nit in `7ad584fe` — the one-liner recipe now uses `` too, matching the two-step recipe and reinforcing the issues-only rule.

@claude review

[claude]

Claude finished @cliffhall's task in 28s —— View job

---

Re-review — docs(AGENTS): board tracks issues only, never PRs

• Confirm the optional nit was applied in 7ad584fe
• Re-scan the whole board section for any remaining "issue or PR" wording

Verdict: LGTM ✅ — ship it.

The nit is applied correctly. The one-liner recipe (line 163) now reads:

ITEM_ID=$(gh project item-add 28 --owner modelcontextprotocol --url <issue-url> --format json --jq '.id')

matching the <issue-url> placeholder on line 150 and the two-step recipe. All three placeholders in the recipe block are now consistent.

I re-scanned the full board section for stragglers (issue or PR, issue/PR, <url>, <issue-or-pr-url>) — none remain. The only surviving "PR ... issue" phrasing is line 121 ("Link the PR to its issue"), which is the correct linkage bullet, not the contradiction this PR set out to fix.

The section now says one thing end to end: only issues go on board #28; PRs carry the v2 label and are tracked through their linked issue's card via Closes #N. This resolves #1581 cleanly. No code/tests involved.
• branch docs/board-issues-only