Align upgrade-review batches with the 30-package backend limit

[jlitola]

Summary

• enforce the deployed maximum of 30 nonblank package upgrades at the shared CLI/MCP request boundary
• advertise the limit in MCP metadata/tool guidance and CLI help
• document the downstream contract and add patch release metadata for both public packages

Blank rows are filtered before capacity is applied. Single-package behavior and the GraphQL query/response path are unchanged.

Validation

• bun test packages/mcp/src/shared/package-upgrade-review-request.test.ts packages/mcp/src/tools/package-upgrade-review.test.ts src/commands/pkg/upgrade-review.test.ts src/tools/package-upgrade-review-parity.test.ts — 27 pass
• bun test — 3,821 pass
• bun run typecheck
• bun run build
• bun run format:check
• bun run lint
• bun run validate:packages
• bun run plugins:generate and bun run plugins:check
• bun run smoke:cli — 93 live steps passed
• bun run smoke:mcp — 50 live steps passed
• targeted descriptor-only package-upgrade agent eval — success/high confidence, 4 MCP calls, no failures or validation violations
• authenticated rich 30-row request against the normal package endpoint — 30 reviews returned
• authenticated rich 30-row request against the development MCP/API/PkgSeer environment — 30 reviews returned
• internal Codex review and Claude Opus review — clean

The GraphQL service file matches the base byte-for-byte. No credential data was inspected or exposed.