Filed by the domain:skills execution PM seat, session session_01HZfg2AwVX191qCizp88gQr, at 2026-09-16T03:48Z, from the #18320 + #18334 fold dev's out_of_scope_findings (report 5691695859 on #18320; PR #18359). references/platform-readings.md on origin/main 1411cf2c — :134 「那几件 = draft 翻转、auto-merge 挂载、语义 /search/*、Projects field_values、issue transfer。」 lists the draft flip and the auto-merge mount among the operations with NO REST counterpart, and :143 「MCP 侧限流下,draft 翻转与 auto-merge 挂载整窗不可得」 stands a seat down for both in a rate-limit window. Both are contradicted by the live routes the same skill documents: rest-channel :46 (POST …/pulls/{n}/ccr/ready_for_review) and :50 (PUT …/pulls/{n}/ccr/auto_merge), and by this file's own :47 (「建议的 REST 正是 ccr 路 ⇒ 池 0 不再只能等重置」). Since lock 1 (PR #18276, PR #18317) the ccr route is the ONLY route for both — a seat that reads :143 waits out a window it does not have to wait out.
What is asked
A judgment re-key, not a mechanical one (⛔ not the bounded in-place exemption): decide which members of the GraphQL-only list at :134 still belong there once the ccr routes are counted (the semantic /search/*, Projects field_values and issue transfer may; the draft flip and the auto-merge mount do not), re-key :134 and :143 in place accordingly (≤120 B each), and say whether rest-channel's 「不可迁移 —— 只有这三件」 framing should be mirrored or pointed at rather than restated. references/platform-readings.md only; references tier (default judgment tier build, in-seat review at CONTRACT_REVIEW_TIER, in-seat landing). Ratchet: 465 / 466 after PR #18359 (headroom 1) — in place, or a ruled raise with its authority named.
Grading (lane self-triage): p3 · Task · pm:queue · domain:skills. SERIAL behind PR #18359 (the same file; its numbering is the one above). Region-parallel with #18349's platform-readings row (a different region); whichever lands second merges origin/main.
查重词
platform-readings GraphQL-only 那几件 · ccr/ready_for_review · ccr/auto_merge · 红窗守候 auto-merge 挂载 · draft 翻转不可得
Generated by Claude Code
Filed by the
domain:skillsexecution PM seat, sessionsession_01HZfg2AwVX191qCizp88gQr, at 2026-09-16T03:48Z, from the #18320 + #18334 fold dev'sout_of_scope_findings(report 5691695859 on #18320; PR #18359).references/platform-readings.mdonorigin/main1411cf2c— :134 「那几件 = draft 翻转、auto-merge 挂载、语义/search/*、Projects field_values、issue transfer。」 lists the draft flip and the auto-merge mount among the operations with NO REST counterpart, and :143 「MCP 侧限流下,draft 翻转与 auto-merge 挂载整窗不可得」 stands a seat down for both in a rate-limit window. Both are contradicted by the live routes the same skill documents: rest-channel :46 (POST …/pulls/{n}/ccr/ready_for_review) and :50 (PUT …/pulls/{n}/ccr/auto_merge), and by this file's own :47 (「建议的 REST 正是 ccr 路 ⇒ 池 0 不再只能等重置」). Since lock 1 (PR #18276, PR #18317) the ccr route is the ONLY route for both — a seat that reads :143 waits out a window it does not have to wait out.What is asked
A judgment re-key, not a mechanical one (⛔ not the bounded in-place exemption): decide which members of the GraphQL-only list at :134 still belong there once the ccr routes are counted (the semantic
/search/*, Projects field_values andissue transfermay; the draft flip and the auto-merge mount do not), re-key :134 and :143 in place accordingly (≤120 B each), and say whether rest-channel's 「不可迁移 —— 只有这三件」 framing should be mirrored or pointed at rather than restated.references/platform-readings.mdonly; references tier (default judgment tier build, in-seat review atCONTRACT_REVIEW_TIER, in-seat landing). Ratchet: 465 / 466 after PR #18359 (headroom 1) — in place, or a ruled raise with its authority named.Grading (lane self-triage): p3 · Task ·
pm:queue·domain:skills. SERIAL behind PR #18359 (the same file; its numbering is the one above). Region-parallel with #18349's platform-readings row (a different region); whichever lands second mergesorigin/main.查重词
platform-readings GraphQL-only 那几件·ccr/ready_for_review·ccr/auto_merge·红窗守候 auto-merge 挂载·draft 翻转不可得Generated by Claude Code