Guard coverage: add explicit sub_issue_write read-write classification test

[Copilot]

The GitHub guard coverage check identified a classification gap: the composite MCP operation sub_issue_write was not explicitly covered by guard tests, despite related granular sub-issue operations being covered. This left a blind spot in regression protection for read-write tool classification.

• Guard classification coverage

  • Updated the sub-issue classification test in guards/github-guard/rust-guard/src/tools.rs to include the composite sub_issue_write operation alongside:
    • add_sub_issue
    • remove_sub_issue
    • reprioritize_sub_issue

• Test intent cleanup

  • Renamed the test from test_sub_issue_management_tools_are_read_write_operations to test_sub_issue_tools_are_read_write_operations to reflect composite + granular coverage.

#[test]
fn test_sub_issue_tools_are_read_write_operations() {
    for op in &[
        "sub_issue_write",
        "add_sub_issue",
        "remove_sub_issue",
        "reprioritize_sub_issue",
    ] {
        assert!(is_read_write_operation(op));
        assert!(!is_write_operation(op));
    }
}

[Copilot]

Pull request overview

Adds explicit guard test coverage to ensure the composite MCP operation sub_issue_write remains classified as a read-write (but not write-only) operation, closing a regression gap in the Rust guard tool classification tests.

Changes:

• Extend the existing sub-issue classification test to include the composite sub_issue_write operation alongside the granular sub-issue operations.
• Rename the test to reflect that it now covers both composite + granular sub-issue tools.

Show a summary per file

File	Description
guards/github-guard/rust-guard/src/tools.rs	Updates/renames the sub-issue read-write classification test to explicitly include sub_issue_write.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 1/1 changed files
• Comments generated: 0