Add regression coverage for pull_request_read DIFC labeling#10735
Conversation
Co-authored-by: lpcox <15877973+lpcox@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Adds regression coverage for DIFC labeling parity between pull_request_read and get_pull_request.
Changes:
- Compares both tools’ labels and descriptors.
- Verifies the PR descriptor format.
Show a summary per file
| File | Description |
|---|---|
guards/github-guard/rust-guard/src/labels/mod.rs |
Adds the labeling parity regression test. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Balanced
|
|
||
| #[test] | ||
| fn test_apply_tool_labels_pull_request_read_matches_get_pull_request() { | ||
| let ctx = default_ctx(); |
🔒 mcpg Read-Only Stress — defaultSurface coverage: MCP tool calls + proxied CLI (REST) + GraphQL mutations
Overall: PASS Gateway exposes 22 read-only MCP tools; all 7 write attempts returned References: §31037394048
|
🔒 mcpg Read-Only Stress — docker-sbxSurface coverage: MCP tool calls + proxied CLI (REST) + GraphQL mutations
Overall: PASS Full ReportPart B — MCP Write Errors
Write tools are absent from the gateway tool registry — gateway enforcement, not backend config. Parts D & E: References: §31037394527
|
🔒 mcpg Read-Only Stress — gVisorSurface coverage: MCP tool calls + proxied CLI (REST) + GraphQL mutations
Overall: PASS
References: §31037393770
|
pull_request_readis a canonical PR read surface and must retain the same repo-scoped secrecy and PR-aware integrity handling asget_pull_request.pull_request_readproduces identical labels and descriptor toget_pull_request.apply_tool_labelsPR match arm from future inventory or refactoring drift.