From 10272ccf2275782c8cfe9423158f352dd2843dd0 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 22 Sep 2026 08:39:11 +0000 Subject: [PATCH] docs(pm): arm-time drift re-measurement becomes standing in landing-operations B MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The ruled fourth bullet of the pure-regeneration ruling: the generated-artefact drift reading is taken in the SAME act that arms auto-merge, and an earlier zero is never reused — a zero that was true when read goes false the moment a sibling PR lands, which is how a PASSed PR gets kicked out of the queue two minutes after it was armed. A non-zero reading routes back to section A's fixed sequence. Placed in B beside the existing arm-act re-read of `mergeable_state`, which already routes a generated-artefact hit into A's sequence: both readings of the arm act now sit adjacent. Section A is what to DO once drift is found, not when to measure it. Paid at the ratchet ceiling (69 / 69, headroom 0) by retiring the duplicate `⛔ 不得要求 baseRev == merge-base`: it and the line above it were ONE sentence until the rules-only rewrite split a comma-clause into its own bullet, the surviving line already states that a lagging `baseRev` is allowed and is not an error (so the equality cannot be required) and names the same 相等, and the only content the retired line ever had of its own — that the equality is not any gate's criterion — is held by the line naming `check:authorable-surface` green as the criterion. No gate reads the equality. Claude-Session: https://claude.ai/code/session_01Wnstp2kTth7sGXfr8fXypc Co-authored-by: Claude --- .claude/skills/pm-dispatch/references/landing-operations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.claude/skills/pm-dispatch/references/landing-operations.md b/.claude/skills/pm-dispatch/references/landing-operations.md index b0bd927ccfe..2c0cdec626d 100644 --- a/.claude/skills/pm-dispatch/references/landing-operations.md +++ b/.claude/skills/pm-dispatch/references/landing-operations.md @@ -12,7 +12,6 @@ - 更硬的旁证是查上一单的实现体完好:`git grep` 带引号精确名对 `origin/main` 与实现文件。 - 锚点断言的正确措辞:断言 `pnpm --filter @objectstack/spec check:authorable-surface` 绿即可。 - `baseRev` 允许滞后,是一行提示不是错误;⛔ 禁为凑相等手改锚点。 -- ⛔ 不得要求 `baseRev == merge-base`。 ## B. 跟到 MERGED 为止;入队后的看护归车道 PM 落地窗口 @@ -28,6 +27,7 @@ - Tier H(其余受管面)者:四件套留 draft 等人批,⛔ 不翻正式不入队;获授权批准后认领席落地。 - ⛔ 两层不由席位批准;清标即落地同受此闸,漏判会被队列守卫在 merge group 里拒收。 - 再读 `mergeable_state`:`dirty` ⇒ 先 merge `origin/main` 再挂;生成物在面上按 A 的固定序。 +- 挂 auto-merge 的同一动作里重测生成物漂移,⛔ 不复用更早的零;非零 ⇒ 按 A 的固定序。 - ready + 全绿 ≠ 已入队:队列从不主动拉 PR,入队是显式动作。 - 零 `enqueued` 事件按序查三条:① `mergeable_state` 是否 `dirty`。 - ② enable-auto-merge 调用根本没落地,重发与效果验证序列见 `platform-readings.md`。