Pome
Updated just nowruns daily

All components

GitHub 0.1.0

0 of 99 API surfaces match the real GitHub response.

GitHubDegradedWrites not runMCP reads not runNo baseline
Baseline noneLast drift 11 Aug, resolved
3 Aug36 of 38 days matched · 7 unmeasuredToday

1 Responses

Whether this twin's answers match a captured real vendor response.

Read comparison
compared against a committed capture of the real vendor response
Baseline
no committed upstream capture has ever existed for this twin
Write round trip
did not run
MCP read leg
did not run

search_repositories Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/github/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

create_repository Not checked

this row is showing the completion fallback, not a measurement gap: the extended MCP write round trip (sandboxes/github/level2-extended.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

fork_repository Not checked

this row is showing the completion fallback, not a measurement gap: the extended MCP write round trip (sandboxes/github/level2-extended.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

search_code Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/github/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

search_users Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/github/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

get_file_contents Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/github/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

list_commits Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/github/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

create_or_update_file Not checked

this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/github/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

create_branch Not checked

this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/github/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

push_files Not checked

this row is showing the completion fallback, not a measurement gap: the extended MCP write round trip (sandboxes/github/level2-extended.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

issue_read Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/github/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

issue_write Not checked

this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/github/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

search_issues Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/github/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

list_issues Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/github/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

add_issue_comment Not checked

this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/github/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

create_issue Not checked

this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/github/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

list_repository_collaborators Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/github/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

pull_request_read Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/github/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

pull_request_review_write Not checked

this row is showing the completion fallback, not a measurement gap: the extended MCP write round trip (sandboxes/github/level2-extended.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

create_pull_request_review Not checked

this row is showing the completion fallback, not a measurement gap: the extended MCP write round trip (sandboxes/github/level2-extended.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

list_pull_requests Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/github/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

merge_pull_request Not checked

this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/github/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

update_pull_request_branch Not checked

this row is showing the completion fallback, not a measurement gap: the extended MCP write round trip (sandboxes/github/level2-extended.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

create_pull_request Not checked

this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/github/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

list_branches Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/github/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

delete_file Not checked

this row is showing the completion fallback, not a measurement gap: the extended MCP write round trip (sandboxes/github/level2-extended.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

get_commit Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/github/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

update_pull_request Not checked

this row is showing the completion fallback, not a measurement gap: the extended MCP write round trip (sandboxes/github/level2-extended.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

add_reply_to_pull_request_comment Not checked

this row is showing the completion fallback, not a measurement gap: the extended MCP write round trip (sandboxes/github/level2-extended.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

list_tags Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/github/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

list_releases Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/github/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

get_latest_release Not checked

this row is showing the completion fallback, not a measurement gap: the extended MCP write round trip (sandboxes/github/level2-extended.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

get_me Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/github/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

search_commits Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/github/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

get_release_by_tag Not checked

this row is showing the completion fallback, not a measurement gap: the extended MCP write round trip (sandboxes/github/level2-extended.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

get_tag Not checked

this row is showing the completion fallback, not a measurement gap: the extended MCP write round trip (sandboxes/github/level2-extended.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /repos/:owner/:repo Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

POST /user/repos Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

POST /orgs/:owner/repos Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

POST /repos/:owner/:repo/forks Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /repos/:owner/:repo/commits Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

POST /repos/:owner/:repo/git/refs Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /repos/:owner/:repo/issues Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

POST /repos/:owner/:repo/issues Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /repos/:owner/:repo/issues/:number Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

PATCH /repos/:owner/:repo/issues/:number Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /repos/:owner/:repo/issues/:number/comments Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

POST /repos/:owner/:repo/issues/:number/comments Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

PATCH /repos/:owner/:repo/issues/comments/:comment_id Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

DELETE /repos/:owner/:repo/issues/comments/:comment_id Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /repos/:owner/:repo/labels Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

POST /repos/:owner/:repo/labels Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /repos/:owner/:repo/issues/:number/labels Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

POST /repos/:owner/:repo/issues/:number/labels Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

DELETE /repos/:owner/:repo/issues/:number/labels/:name Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

POST /repos/:owner/:repo/issues/:number/assignees Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /repos/:owner/:repo/collaborators Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

GET /repos/:owner/:repo/collaborators/:username Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

PUT /repos/:owner/:repo/collaborators/:username Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /repos/:owner/:repo/pulls Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

POST /repos/:owner/:repo/pulls Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

PATCH /repos/:owner/:repo/pulls/:number Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /repos/:owner/:repo/pulls/:number Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

GET /repos/:owner/:repo/pulls/:number/files Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

GET /repos/:owner/:repo/pulls/:number/reviews Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

POST /repos/:owner/:repo/pulls/:number/reviews Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /repos/:owner/:repo/pulls/:number/comments Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

GET /repos/:owner/:repo/pulls/:number/status Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

PUT /repos/:owner/:repo/pulls/:number/merge Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

PUT /repos/:owner/:repo/pulls/:number/update-branch Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /repos/:owner/:repo/pulls/:number/commits Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

POST /repos/:owner/:repo/pulls/:number/comments Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

POST /repos/:owner/:repo/pulls/:number/comments/:comment_id/replies Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /repos/:owner/:repo/branches Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

GET /repos/:owner/:repo/branches/:branch Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

DELETE /repos/:owner/:repo/git/refs/heads/:branch Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /repos/:owner/:repo/contents/* Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

PUT /repos/:owner/:repo/contents/* Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

DELETE /repos/:owner/:repo/contents/* Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /repos/:owner/:repo/commits/:ref Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

POST /repos/:owner/:repo/statuses/:sha Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /repos/:owner/:repo/commits/:ref/status Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

POST /repos/:owner/:repo/check-runs Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /repos/:owner/:repo/commits/:ref/check-runs Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

GET /repos/:owner/:repo/milestones Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

POST /repos/:owner/:repo/milestones Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

PATCH /repos/:owner/:repo/milestones/:number Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

DELETE /repos/:owner/:repo/milestones/:number Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /repos/:owner/:repo/tags Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

GET /repos/:owner/:repo/releases Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

GET /repos/:owner/:repo/releases/latest Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

GET /repos/:owner/:repo/releases/tags/:tag Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

POST /repos/:owner/:repo/releases Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /user Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

GET /search/repositories Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

GET /search/code Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

GET /search/commits Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/github/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-m1.ts and commit every fixture it writes. It says nothing about parity with real GitHub, which only the L1 upstream lane can answer.

GET /search/issues Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

GET /search/users Not checked

nothing has ever compared this surface against real GitHub. It IS one of the 33 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_GH_TOKEN=… tsx tools/fidelity-watch/capture-m1.ts.

Every surface this twin publishes (99)

MCP · not captured 0 of 36 match

search_repositoriesNot checked
create_repositoryNot checked
fork_repositoryNot checked
search_codeNot checked
search_usersNot checked
get_file_contentsNot checked
list_commitsNot checked
create_or_update_fileNot checked
create_branchNot checked
push_filesNot checked
issue_readNot checked
issue_writeNot checked
search_issuesNot checked
list_issuesNot checked
add_issue_commentNot checked
create_issueNot checked
list_repository_collaboratorsNot checked
pull_request_readNot checked
pull_request_review_writeNot checked
create_pull_request_reviewNot checked
list_pull_requestsNot checked
merge_pull_requestNot checked
update_pull_request_branchNot checked
create_pull_requestNot checked
list_branchesNot checked
delete_fileNot checked
get_commitNot checked
update_pull_requestNot checked
add_reply_to_pull_request_commentNot checked
list_tagsNot checked
list_releasesNot checked
get_latest_releaseNot checked
get_meNot checked
search_commitsNot checked
get_release_by_tagNot checked
get_tagNot checked

REST · not captured 0 of 63 match

GET /repos/:owner/:repoNot checked
POST /user/reposNot checked
POST /orgs/:owner/reposNot checked
POST /repos/:owner/:repo/forksNot checked
GET /repos/:owner/:repo/commitsNot checked
POST /repos/:owner/:repo/git/refsNot checked
GET /repos/:owner/:repo/issuesNot checked
POST /repos/:owner/:repo/issuesNot checked
GET /repos/:owner/:repo/issues/:numberNot checked
PATCH /repos/:owner/:repo/issues/:numberNot checked
GET /repos/:owner/:repo/issues/:number/commentsNot checked
POST /repos/:owner/:repo/issues/:number/commentsNot checked
PATCH /repos/:owner/:repo/issues/comments/:comment_idNot checked
DELETE /repos/:owner/:repo/issues/comments/:comment_idNot checked
GET /repos/:owner/:repo/labelsNot checked
POST /repos/:owner/:repo/labelsNot checked
GET /repos/:owner/:repo/issues/:number/labelsNot checked
POST /repos/:owner/:repo/issues/:number/labelsNot checked
DELETE /repos/:owner/:repo/issues/:number/labels/:nameNot checked
POST /repos/:owner/:repo/issues/:number/assigneesNot checked
GET /repos/:owner/:repo/collaboratorsNot checked
GET /repos/:owner/:repo/collaborators/:usernameNot checked
PUT /repos/:owner/:repo/collaborators/:usernameNot checked
GET /repos/:owner/:repo/pullsNot checked
POST /repos/:owner/:repo/pullsNot checked
PATCH /repos/:owner/:repo/pulls/:numberNot checked
GET /repos/:owner/:repo/pulls/:numberNot checked
GET /repos/:owner/:repo/pulls/:number/filesNot checked
GET /repos/:owner/:repo/pulls/:number/reviewsNot checked
POST /repos/:owner/:repo/pulls/:number/reviewsNot checked
GET /repos/:owner/:repo/pulls/:number/commentsNot checked
GET /repos/:owner/:repo/pulls/:number/statusNot checked
PUT /repos/:owner/:repo/pulls/:number/mergeNot checked
PUT /repos/:owner/:repo/pulls/:number/update-branchNot checked
GET /repos/:owner/:repo/pulls/:number/commitsNot checked
POST /repos/:owner/:repo/pulls/:number/commentsNot checked
POST /repos/:owner/:repo/pulls/:number/comments/:comment_id/repliesNot checked
GET /repos/:owner/:repo/branchesNot checked
GET /repos/:owner/:repo/branches/:branchNot checked
DELETE /repos/:owner/:repo/git/refs/heads/:branchNot checked
GET /repos/:owner/:repo/contents/*Not checked
PUT /repos/:owner/:repo/contents/*Not checked
DELETE /repos/:owner/:repo/contents/*Not checked
GET /repos/:owner/:repo/commits/:refNot checked
POST /repos/:owner/:repo/statuses/:shaNot checked
GET /repos/:owner/:repo/commits/:ref/statusNot checked
POST /repos/:owner/:repo/check-runsNot checked
GET /repos/:owner/:repo/commits/:ref/check-runsNot checked
GET /repos/:owner/:repo/milestonesNot checked
POST /repos/:owner/:repo/milestonesNot checked
PATCH /repos/:owner/:repo/milestones/:numberNot checked
DELETE /repos/:owner/:repo/milestones/:numberNot checked
GET /repos/:owner/:repo/tagsNot checked
GET /repos/:owner/:repo/releasesNot checked
GET /repos/:owner/:repo/releases/latestNot checked
GET /repos/:owner/:repo/releases/tags/:tagNot checked
POST /repos/:owner/:repo/releasesNot checked
GET /userNot checked
GET /search/repositoriesNot checked
GET /search/codeNot checked
GET /search/commitsNot checked
GET /search/issuesNot checked
GET /search/usersNot checked

2 Tool list

Whether this twin offers the same MCP tools the vendor's own server declares. A name-and-contract comparison with no response in it.

GitHub twin36
Vendor tools/list44

34 shared names, on one scale.

This twin serves it and the vendor does not declare it 2

create_issueGITHUB-MCP-001
create_pull_request_reviewGITHUB-MCP-002

Both declare it and the contracts agree 34

add_issue_comment
add_reply_to_pull_request_comment
create_branch
create_or_update_file
create_pull_request
create_repository
delete_file
fork_repository
get_commit
get_file_contents
get_latest_release
get_me
get_release_by_tag
get_tag
issue_read
issue_write
list_branches
list_commits
list_issues
list_pull_requests
list_releases
list_repository_collaborators
list_tags
merge_pull_request
pull_request_read
pull_request_review_write
push_files
search_code
search_commits
search_issues
search_repositories
search_users
update_pull_request
update_pull_request_branch
GITHUB-MCP-001 why this is accepted
Evidence:
GitHub registers create_issue into the issues toolset, which is Default:true, gated on the issues_granular feature flag (pkg/github/issues_granular.go:120 at commit e6e3a4e). That flag is in AllowedFeatureFlags (pkg/github/feature_flags.go), the allowlist of flags a client may enable via the --features CLI flag or the X-MCP-Features HTTP header, so an examinee pointed at https://api.githubcopilot.com/mcp/ — the URL agent-examples/support-triage declares — that sets X-MCP-Features: issues_granular IS served this tool.
Why it is accepted:
The divergence is not that the tool is fictional; it is that the twin serves it unconditionally while GitHub serves it on request, and F-1326's golden was captured with no flags set. Removing it would make the twin refuse a call the vendor answers, which is the false FAILURE this registry's sibling ticket (F-1330) exists to stop, so the twin keeps serving it and the gap is recorded here instead.
What would end this:
  • the twin learns to model X-MCP-Features, at which point it should gate this tool the way GitHub gates it and this entry should be deleted
  • GitHub drops issues_granular from AllowedFeatureFlags or stops registering the tool, at which point it should stop being served
  • the golden is re-captured with the flag set, at which point the tool matches and the lane's own dead-entry check will fail this entry rather than let it stand.
GITHUB-MCP-002 why this is accepted

Same fact, same reasoning, different flag. It is a separate entry rather than a second tool on GITHUB-MCP-001 because the two are gated on DIFFERENT flags: were GitHub to retire one flag and keep the other, a single entry would go on covering both and the registry's dead-entry check would never notice.

Evidence:
GitHub registers create_pull_request_review into the pull_requests toolset, which is Default:true, gated on pull_requests_granular (pkg/github/pullrequests_granular.go:379 at commit e6e3a4e), and that flag is likewise in AllowedFeatureFlags, settable per client via --features or the X-MCP-Features header.
Why it is accepted:
With the flag off, the same capability is reachable as pull_request_review_write method create, which this twin now also serves — so an examinee written against either surface works here, and the only divergence is that this twin does not require the flag.
What would end this:
  • Retired under the same three conditions as GITHUB-MCP-001, read for pull_requests_granular.
Measured against digital-twins e035d34 · the run that produced it · FIDELITY.md · status.json