docs(pm-dispatch): correct rest-channel header's quoted default read order (#13022)

The header cites references/platform-readings.md by name and quotes its
default read order, but quoted the three-tier form git -> REST -> MCP/GraphQL.
The named source has carried the four-tier order git -> payload -> REST ->
MCP/GraphQL since 2026-08-25, when the zero-quota public-repo payload tier was
added. The omitted tier sits above REST precisely for seats whose repo-scoped
REST probe returns 403, for whom the stale header silently degraded the ladder
to git then MCP/GraphQL -- skipping the only tier that costs no quota.

Pointer-style: the spelling is matched to the source; no tier mechanics are
copied here (platform-readings.md stays the single home).

Net 0 lines (87/87, ceiling unchanged). The insertion costs 12 bytes on a line
already at 118 of 120, so the three-line paragraph is re-wrapped to the
canonical wrapLine form. No content cut.

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

Author: os-litant

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

@@ -1,8 +1,8 @@
 # REST 通道操作对照表(references —— 按需加载)
 
-出处:`platform-readings.md` API 配额段(**默认读序 git → REST → MCP/GraphQL** 的策略住那里,本表是
-逐操作的通道归属)。做一件事之前查一行:它有没有 REST 对应物。⛔ 不引用 issue 编号 ——
-每行自含边界与日期。
+出处:`platform-readings.md` API 配额段(**默认读序 git → payload → REST → MCP/GraphQL** 的策略住那
+里,本表是逐操作的通道归属)。做一件事之前查一行:它有没有 REST 对应物。⛔ 不引用 issue
+编号 —— 每行自含边界与日期。
 
 **通道边界**:容器 curl = App installation token,REST core 15,000/时、与 GraphQL 池独立计;出口代理按设
 计只放 **repo-scoped 路径**(`/repos/{o}/{r}/...`)加 `/rate_limit`,org 级端点未实测。⚠️ **✓ 按席位