Find worthwhile work

Read AGENTS.md and the contribution policy in the development guide. Honor the requested scope. For "since the last patch," identify the release timestamp, then look for open issues created or substantively updated afterward. Use a bounded inventory internally; report truncation if it affects coverage.

Start from an inventory, then link each candidate to the PRs that mention it:

gh release list --repo PrefectHQ/fastmcp --limit 1
gh issue list --repo PrefectHQ/fastmcp --state open --limit 30 \
  --json number,title,author,createdAt,updatedAt,labels,comments
gh pr list --repo PrefectHQ/fastmcp --state all --search "<issue-number> in:body" \
  --json number,title,state,author

Where search, GraphQL or --paginate are blocked (cloud sessions), page repo-scoped REST by hand (gh api "repos/PrefectHQ/fastmcp/pulls?state=all&per_page=100&page=N"), dump it once, and join locally.

Pick work with concrete user impact, a supported contract being violated, a tractable causal fix, and a change FastMCP wants to carry. Apply triage and merge decisions before ranking anything: labels and confident diagnoses are claims, and the behavior may already be fixed or decided. Mark each pick want / marginal / don't want. Do not rank solely by recency, comment count, or how small a proposed patch looks. Automated dashboard churn is not itself useful work.

For promising candidates: