Feature asks driven by real pain points from agent sessions. This file is future-only: implemented items are removed instead of retained as history.
Current state: release_create exists and can create a release with tag/name/body/draft/prerelease plus GitHub-generated notes.
Remaining pain: fedbuild-style workflows still need a second step to upload image + RPM + SBOM + provenance + SHA256SUMS + signatures.
Ask: extend the tool with artifact attachments, changelog-driven notes, and optional verification-block generation.
Current state: workflow_dispatch exists and triggers the event successfully, but GitHub's 204 response means callers still need a follow-up query to find and watch the resulting run.
Ask: add watch, timeoutSec, and final-run resolution so one call can dispatch and observe the workflow outcome.
Current state: pr_create opens a PR once the head branch already exists on GitHub.
Remaining pain: agents still need shell git to push a local branch first and often want the PR body generated from commit history.
Ask: extend the tool with optional branch push, body-from-commits generation, labels, reviewers, and auto-merge knobs.
These change the public JSON contract (output shape) and would require an
MCP_JSON_FORMAT_VERSION bump plus coordinated consumer updates. Held out of the
additive enhancement sweep deliberately; they need an explicit go/no-go.
Current state: repo_status, ecosystem_activity, and pr_preflight accept a LocalOrRemoteRepoSchema[] array (up to MAX_REPOS_PER_REQUEST). changelog_draft and release_readiness extend RepoRefSchema and accept only one repo.
Remaining pain: agents cannot batch a changelog/readiness sweep across an org in one call.
Ask: accept repos[] on the single-repo read tools. Breaking because the top-level result becomes an array (or { repos: [...] }) instead of a single object — decide whether to preserve the single-object shape when exactly one repo is passed, or bump the format version.
Current state: tool-level failures return a top-level { error: {...} }. Bulk tools (repo_status, ecosystem_activity) additionally carry a per-item error inside each repo result. The two patterns are not documented as a single rule.
Ask: ratify and document the convention — top-level error = whole-tool failure; nested error = per-item failure in a bulk result — and align any tool that diverges. Breaking only if any tool's current shape changes.
Current state: pr_comment_batch posts a single review with inline comments on right-side line numbers.
Ask: add support for left-side comments, multi-line ranges, and newer review-comment fields GitHub exposes.
Current state: issue_from_template works well for template files rendered as text with variable substitution.
Ask: support richer GitHub Issue Forms / YAML templates so field names and defaults can be filled structurally instead of as raw text substitution.
Current state: actions_runs_filter filters by workflow, status, conclusion, branch, and limit.
Ask: add a since filter so recent-failure lookups do not require a second client-side timestamp pass.