docs(qa): repair revision/history gap in cli.migrate-duplicates-inventory

[os-elon]

Fixes#11037

check:platform-checklist was red on main: item cli.migrate-duplicates-inventory
in docs/qa/platform-checklist/areas/cli.json carried revision: 3 while its
history array held only two entries, the last at revision 2.

check-platform-checklist: 1 problem(s)
X cli.json - cli.migrate-duplicates-inventory: "revision" (3) must equal the
last history entry's revision (2) -- a semantic edit bumps both

PR #11031 made a genuine semantic edit to the item's contract -- reportVersion
1 -> 2 in the acceptance clause, .runtimeIndexPreflight added to the jq walk
step, a seeding step for the kernel:ready blocker, and a new acceptance
clause carrying a matched control in its verify step -- and bumped revision
to 3, but never appended the matching history entry. This PR repairs the
ledger gap left by #11031: it adds the missing revision-3 history entry
describing what changed, citing #8725 and #11031 as provenance and matching
the sibling entries' shape and voice. revision is NOT reverted -- the
semantic edit is real and the bump is correct.

Scope

Touches exactly one item, cli.migrate-duplicates-inventory, adding one
history entry. No other item, file, or release-notes page is touched.

Verification

Gate before fix (reproduced against origin/main at 2866d5f):

check-platform-checklist: 1 problem(s)
X cli.json - cli.migrate-duplicates-inventory: "revision" (3) must equal the
last history entry's revision (2) -- a semantic edit bumps both
EXIT=1

Gate after fix (this branch):

check-platform-checklist: OK -- 15 areas, 205 items (205 active); coverage: 30
kinds mapped, 0 waived; traps: 19 documented, 19 in use; provisioning: 4 area
recipes, 6 item references resolved (self-checks: 22 trap-vocabulary + 14
provisioning-resolve assertions).
EXIT=0

Item's revision (3) now equals its last history entry's revision (3).

Reverse-verified both directions: entry removed reproduces the exact original
failure above; entry restored passes -- both directions predicted beforehand
and confirmed.

node scripts/pm/dispatch-gates.mjs (no path args, off the merge base) named
check:doc-authoring and check:doc-formula-expressions as the matched local
gates for this diff. pnpm lint was also run per this card's instructions.
Full verdict lines are in the issue report comment (queued behind the shared
verify lock at PR-open time; this draft is opened per this repo's "report at
draft-PR time" convention).

No .changeset/*.md -- this is a docs/QA-ledger-only change (no package code,
no user-facing behavior). Tagged skip-changeset per this repo's convention.

Generated by Claude Code

---

Generated by Claude Code

[github-actions]

⛔ merge queue 构建失败 — 先分诊，再决定要不要重排

队列构建 32576633487 红了。队列跑的是全量套件（PR 侧 CI 只跑 affected 子集），
所以失败的测试可能在本 PR 没碰过的包里 —— 那不是重排能修的。每次盲目重排都会让排在后面的所有 PR 重建一轮。

失败的 job（日志抽取，best effort）：

• Console Pin Gate — 失败步骤: Build the Console SPA at the pinned objectui SHA

  ✗ Build failed in 6.00s
  

↳ 失败原因 是判读的关键：超时（Test timed out in … / Hook timed out in …）多半是负载/时序，不是本 PR 的回归；
断言（AssertionError: …）才指向真实的行为改变。两者的 FAIL 行长得一模一样，只有这一行能区分。

跨 PR 相同签名（24h，按失败测试文件聚合）：

• ⚠️本次没有可用的聚合签名（日志里没有能解析出测试文件名的 FAIL 行）—— 这不是「没有同签名的其他 PR」，是这一轮没测到。跨 PR 聚合本次不可用，请手工比对其他 PR 的同类评论。
• ⚠️ 24h 评论账本没读完（超过 5 页仍未读到窗口尽头），所以上面的「不同 PR 数」是下界，不是全量。

历史信号：

• 本 PR 过去 24h 无队列失败记录（首次）。
• 过去 24h 队列共有 97 个失败构建（不含本次）。

分诊清单：

1. 失败测试在本 PR 改动的包里 → 真回归，修 PR。
2. 失败测试与本 PR 无关 → 看上面的「跨 PR 相同签名」；已有汇总 issue ⇒ flaky/环境问题实锤，去那张 issue 上谈，修好前重排只会再烧一轮全队列。
3. 两者都不是 → 可能与同组 PR 语义冲突；等前面的 PR 落地或失败出队后再重排一次即可，不要连续重排。

---

Generated by Claude Code · merge-queue-triage workflow (#4859)