docs(pm): base the REST draft-flip row on a probe, not the docs (#17597)

* docs(pm): base the REST draft-flip row on a probe, not the docs

`rest-channel.md` 不可迁移 item 1 recorded the draft-to-ready flip as
REST-unsupported on documentation — its own words, 「与第 5 条同批核对官方
文档,未逐个实调」. It is measured now, and the measurement is stronger than
the doc implied: REST `PATCH /pulls/{n}` with `{"draft": false}` answers
HTTP 200 and changes nothing (read-back still `draft = true`, body
untouched). A success code therefore proves nothing and the read-back is
the only tell — the failure mode a documented *absence* does not warn
about, because a reader pictures an error they would notice.

The verdict is unchanged (GraphQL-only mutation; the egress proxy serves
only the pinned PR-review GraphQL set) and the 断粮出路 stays; only the
basis moves, and the working channel is now named rather than implied.

Two lines rewritten in place, net 0 lines (82/82 on the line ratchet),
each line within the 120-byte cap.

Claude-Session: https://claude.ai/code/session_01YKEjmbYNvYWJvWGSWx26zK
Co-authored-by: Claude <noreply@anthropic.com>

* docs(pm): keep the documentary-basis disclosure on 不可迁移 item 5

The parenthetical the previous commit deleted from item 1 was the only
place in `rest-channel.md` disclosing that item 5 — `issue transfer` as
GraphQL-only — also rests on a documentation check rather than a probe.
Item 5 did not say so itself, so that disclosure would otherwise exist
nowhere in the file. It now sits on item 5, where a reader of item 5 will
actually meet it.

One line, one token wider: line 61 goes 82 to 105 bytes, the file stays
82 lines at ceiling 82, and every other line — item 5's continuation
included — is byte-identical.

Claude-Session: https://claude.ai/code/session_01YKEjmbYNvYWJvWGSWx26zK
Co-authored-by: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>

Author: os-litant

.claude/skills/pm-dispatch/references/rest-channel.md

@@ -51,14 +51,14 @@
 红窗守候规则住 `platform-readings.md` 配额段。
 
 1. draft 转 ready 翻转:GraphQL-only mutation;出口代理只放钉住的 PR-review GraphQL 集。
-   判据 = REST update-a-pull-request 只收 `title`/`body`/`state`/`base`/`maintainer_can_modify`,无 `draft`
-   (与第 5 条同批核对官方文档,未逐个实调)。断粮出路:等 MCP 恢复,或人工点一下。
+   判据 = 2026-09-11 实调:REST `PATCH /pulls/{n}` 带 `{"draft": false}` 回 200 且什么都没改,读回仍 draft
+   ⇒ 状态码不作数,读回才作数。通道 = MCP `update_pull_request`;断粮:等它恢复或人工点一下。
 2. auto-merge 与入队挂载:GraphQL mutation,即 MCP `enable_pr_auto_merge`。
    走合并队列的仓落地必经它 ⇒ 配额红窗无退路;直合仓有退路 `PUT .../pulls/{n}/merge`。
 3. 语义搜索:`/search/*` 被出口代理按设计拒绝。退路 = REST 列表端点加本地 grep。
    REST 也被会话门关掉的席位 = 一次定向 MCP `search_issues`,⛔ 不宽表扫。
 4. Projects field_values:GraphQL-only —— 舰队并不需要它;MCP 服务器端无条件抓它才是漏点。
-5. `issue transfer`:issues 端点表无 transfer 路由 ⇒ 同为 GraphQL-only。
+5. `issue transfer`:issues 端点表无 transfer 路由(核对文档,未实调)⇒ 同为 GraphQL-only。
    拿不到时当轮改走在目的仓重建配方,配方住 `platform-readings.md`。
 
 ## 第三桶 —— git 零配额等价物