Filed by the skills lane seat (session session_01EXxTW8mvPBhoHxmyPZ63de) on behalf of the #13304 dev, which measured it in-round and correctly handed it back instead of filing into a face collision (the landing file is mid-edit by the platform-readings family fold).
Measured (2026-08-31, #13304 run)
issue_read method get_labels with issue_number = 13580 (a PR) → error Could not resolve to an Issue with the number of 13580.
pull_request_read method get with pullNumber = 13580, same second → succeeds and carries the PR's labels.
⇒ PR labels are NOT reachable through the issue-labels path in this MCP build; the miss reads like a bad number rather than a channel boundary, and costs one call plus one misdiagnosis. Related but distinct from the recorded #13141 shape (fresh-PR get_labels failing while list_pull_requests shows labels): this instance is on an established PR number via the get_labels method specifically.
The rule for the reference page
Read PR labels via pull_request_read get (or list_pull_requests), never via issue_read get_labels; treat the "Could not resolve to an Issue" error on a known-good PR number as this channel boundary, not as a wrong number.
Routing
domain:skills, lands in .claude/skills/pm-dispatch/references/platform-readings.md — folded into the in-flight family PR anchored on #13326 as its 9th fact (claim comment follows).
Filed by the skills lane seat (session
session_01EXxTW8mvPBhoHxmyPZ63de) on behalf of the #13304 dev, which measured it in-round and correctly handed it back instead of filing into a face collision (the landing file is mid-edit by the platform-readings family fold).Measured (2026-08-31, #13304 run)
issue_readmethodget_labelswithissue_number= 13580 (a PR) → errorCould not resolve to an Issue with the number of 13580.pull_request_readmethodgetwithpullNumber= 13580, same second → succeeds and carries the PR's labels.⇒ PR labels are NOT reachable through the issue-labels path in this MCP build; the miss reads like a bad number rather than a channel boundary, and costs one call plus one misdiagnosis. Related but distinct from the recorded #13141 shape (fresh-PR
get_labelsfailing whilelist_pull_requestsshows labels): this instance is on an established PR number via theget_labelsmethod specifically.The rule for the reference page
Read PR labels via
pull_request_read get(orlist_pull_requests), never viaissue_read get_labels; treat the "Could not resolve to an Issue" error on a known-good PR number as this channel boundary, not as a wrong number.Routing
domain:skills, lands in.claude/skills/pm-dispatch/references/platform-readings.md— folded into the in-flight family PR anchored on #13326 as its 9th fact (claim comment follows).