Summary
Removes the remote_mcp_issue_fields feature flag and promotes issue field support to always-on. Simultaneously deletes the legacy issue_write write methods that pre-dated issue field support (~572 lines removed from issues.go). The granular issue_write tool (with issue_fields param) is now the only write path.
Files changed: pkg/github/issues.go -572 lines; pkg/github/feature_flags.go -7 lines; pkg/github/issue_fields.go -2; pkg/github/tools.go -2; pkg/github/ui_tools.go -4; removed __toolsnaps__/issue_write_ff_remote_mcp_issue_fields.snap and list_issues_ff_remote_mcp_issue_fields.snap.
Upstream reference
Fork conflict
None. The fork does not extend the legacy issue_write methods or the remote_mcp_issue_fields flag. The fork's issue_graph, set_project_item_status, and add_issue_to_project tools are independent.
Context
The remote_mcp_issue_fields flag was a graduation mechanism for the new granular issue_write tool. Having confirmed stability, upstream removed the flag and the legacy code it guarded. This reduces maintenance surface and eliminates two parallel code paths.
Summary
Removes the
remote_mcp_issue_fieldsfeature flag and promotes issue field support to always-on. Simultaneously deletes the legacyissue_writewrite methods that pre-dated issue field support (~572 lines removed fromissues.go). The granularissue_writetool (withissue_fieldsparam) is now the only write path.Files changed:
pkg/github/issues.go-572 lines;pkg/github/feature_flags.go-7 lines;pkg/github/issue_fields.go-2;pkg/github/tools.go-2;pkg/github/ui_tools.go-4; removed__toolsnaps__/issue_write_ff_remote_mcp_issue_fields.snapandlist_issues_ff_remote_mcp_issue_fields.snap.Upstream reference
Fork conflict
None. The fork does not extend the legacy
issue_writemethods or theremote_mcp_issue_fieldsflag. The fork'sissue_graph,set_project_item_status, andadd_issue_to_projecttools are independent.Context
The
remote_mcp_issue_fieldsflag was a graduation mechanism for the new granularissue_writetool. Having confirmed stability, upstream removed the flag and the legacy code it guarded. This reduces maintenance surface and eliminates two parallel code paths.