[finding] rest-channel :54 still says the REST actor is 「按会话」 claude[bot] or a user — the token class follows the Claude Code account and flipped inside one session twice; one in-place re-key pointing at the fact table #18360

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/rest-channel.md :54 on origin/main 1411cf2c reads, verbatim: 「直合仓 PUT .../pulls/{n}/merge;actor 记通道令牌:REST 按会话为 claude[bot] 或用户,MCP 恒用户。」 — the same 「按会话」 premise PR #18359 retires from platform-readings: the REST token class follows the Claude Code account, not the session, and flipped inside one session with no seat action twice on 2026-09-15/16 (the triage seat claude[bot] → os-sam; this seat claude[bot] → os-zhuang; #18334's table and its carried second measurement). A seat reading :54 records a merged_by actor on a premise the fact table now contradicts.

What is asked

One in-place re-key of rest-channel :54 (≤120 B): the actor is the channel token's class, read from the write's own read-back (user.login / user.type) — 「按 Claude Code 账号」, not 「按会话」 — with a pointer to the fact table rows (platform-readings :126–:132 after PR #18359) rather than a copy. references/rest-channel.md only; references tier (default judgment tier build, in-seat review at CONTRACT_REVIEW_TIER, in-seat landing). Ratchet: rest-channel is 82 / 82 (headroom 0) — in place.

Grading (lane self-triage): p3 · Task · pm:queue · domain:skills. SERIAL behind PR #18359 (the rows it points at must exist on main). Fold candidate with #18337 and #18339 (the same file, the same shape — one write-side line each); decided at claim time by the five gates.

查重词

rest-channel 按会话 · write identity · token class per account · claude[bot] 或用户 · direct-merge actor

Generated by Claude Code