- Extend FeatureFlagEnable/Disable fields from string to []string (AND
semantics for enable, OR semantics for disable) so a tool can require
multiple flags simultaneously.
- Add LegacyIssueWrite: the FeatureFlagIssueFields-disabled variant of
issue_write. It exposes the pre-issue-fields schema (no issue_fields
parameter) and skips the custom field value resolution. Both this and
IssueWrite register under the tool name 'issue_write'; exactly one is
active at a time via mutually exclusive flag annotations.
- Gate IssueWrite (the flag-enabled variant) with FeatureFlagEnable so
it is only served when remote_mcp_issue_fields is on.
- Gate the get_issue field_values enrichment with a runtime
IsFeatureEnabled check so the GraphQL round-trip is skipped when the
flag is off.
- Add issue_write.snap (legacy) and
issue_write_ff_remote_mcp_issue_fields.snap (flag-enabled) toolsnaps
following the convention established by PR #2520.
- Modernise featureFlagAllowed disableFlags loop to slices.ContainsFunc.
Kelsey Myers
ba9930f328