docs(pm-dispatch): timestamped readings are the first construct-shaped fix; record the remediation-shape ranking beside it

Every board / tree / queue reading a PM seat states — in a claim, a dispatch
order, a review, a round report, a seat-post segment — carries the UTC moment
it was taken (and the ref or tip when the reading is of a tree). A reading
without its timestamp is malformed, not current: the reader treats it as
untaken. Folded into the reading-validity bullet of 平台读数纪律 beside the
zero-hit control rule, which has the same shape.

Recorded beside it: when a PM-side failure is recorded, the amendment prefers
(a) remove the construct that permits the error, then (b) make the correct
form the only one the protocol spells, then (c) add a check the PM must
remember — (c) recurred, (a) held.

Maintainer ruling 2026-09-02, verbatim: 「其他同意」 (adopting B + A).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LraLgQVGq8egUwfYZpbYt1

Author: claude

.claude/skills/pm-dispatch/SKILL.md

@@ -163,6 +163,12 @@ PR 的会话被读作「清」)。**收班简报 = 前任「不再写」的显
 - **零命中必须用确定存在的邻近词反查**,
   否则零命中不成立;仓不可达同理,⛔ 不因「查不了」
   当「查过了干净」—— 在 issue 上贴出给对应座位的现成命令,等读数回贴再派。
+  **同为成立条件 —— 板面/树/队列读数自带取数时刻**(维护者 2026-09-02 裁「其他同意」):
+  写进认领、派发令、复核、轮次报告、座位贴段落的读数恒带 UTC 时间戳
+  (形如 `2026-09-03T00:21Z`),树读数另带 ref 或 tip;无时间戳的读数是格式错误不是现值,
+  读者按未取处理 —— 改的是键入什么,不是要记住什么。**PM 侧失效的修法按序取**:
+  (a) 删掉容许出错的构造 → (b) 让正确形态成为协议唯一拼写 → (c) 加一条要记住的检查;
+  (c) 型屡复发、(a) 型守住 —— 占位符禁令与本条取数时刻皆 (a) 型。
 - **定时器文本纪律(一切自设定时器适用)**:已删除的定时器仍会投递,
   投递时文本可能落后现实数轮 —— 每一枪**以「幂等 —— 动手前先重读状态」
   开头**,只写关键判据(「若 X 则 Y」),