fix(pm): repair two carriers still spelling the superseded references-tier boundary

Two carriers of the governed-tier rule still stated the 2026-09-13 boundary
(Tier S / "fact layer" = only .claude/skills/pm-dispatch/references/**) that
#19133 (2026-09-18, maintainer "同意改规则。" plus the amendment folding in
.claude/settings.json and .claude/hooks/**) superseded: Tier S is now the
whole .claude/** tree, per the GOVERNED_SURFACES register (id: claude-tree)
and its self-test case skills-agents-and-the-fact-layer-are-Tier-S in
scripts/pm/check-governed-merges.mjs, and per SKILL.md:625-626. Within the
last hour this stale text caused two agents to misclassify a compliant PR.

- .claude/skills/pm-dispatch/references/landing-operations.md:27-28 spelled
  the old boundary as current ("受管路径全在本技能 references/ 者事实层 …
  其余为规则层"), which would tell a dev touching e.g. SKILL.md itself to
  leave the PR in draft awaiting a maintainer approval it does not need.
  Re-keyed to Tier S (.claude/** whole tree) / Tier H (everything else),
  same two-bullet shape, line count and byte ceiling unchanged (69/69).

- scripts/pm/check-governed-queue-guard.mjs's "THIRD leg" header (~268-294)
  reproduced the same narrow 2026-09-13 boundary and concluded "Every other
  governed path is the rules layer and keeps the predicate above
  byte-for-byte" -- false since #19133, and self-contradicting the same
  file's own later "the landing TIER" section, which already records that
  REFERENCES_TIER_PREFIX "is gone". The quoted 2026-09-13 ruling is kept,
  untranslated, as the ruling that started this leg; a new paragraph marks
  it SUPERSEDED by #19133 and points at governedTierFor / the register /
  `check-governed-merges.mjs --test <paths>` instead of a prefix to
  remember. No behavior, constant, or self-test assertion changed.

Tier verdict on this PR's final file list (check-governed-merges.mjs --test):
GOVERNED -- Tier S (landing-operations.md hits the .claude/** register row;
check-governed-queue-guard.mjs is not itself a registered surface).

The card relation to the pre-existing tracking issue is stated once, in the
pull request body, per this repo's own commit-trailer contract.

Co-Authored-By: Claude <noreply@anthropic.com>

Author: claude

.claude/skills/pm-dispatch/references/landing-operations.md

@@ -24,8 +24,8 @@
 - 契约复核 PASS 落地的 PR 到窗口时已 ready 且 auto-merge 在挂,见 `contract-review.md`。
 - 窗口自身权责不变:跟到 MERGED、踢出处置、落地后对账。
 - 转 ready/入队前跑 `check-governed-merges.mjs --pr N`:受管面照两层;>5000 行(含生成物)照规则层。
-- 受管路径全在本技能 `references/` 者事实层:席内达档复核过落地前检三条即转正式入队。
-- 其余为规则层:四件套留 draft 等人批,⛔ 不翻正式不入队;获授权批准后认领席落地。
+- Tier S(`.claude/**` 全树)者:席内达档复核过落地前检三条即转正式入队。
+- Tier H(其余受管面)者:四件套留 draft 等人批,⛔ 不翻正式不入队;获授权批准后认领席落地。
 - ⛔ 两层不由席位批准;清标即落地同受此闸,漏判会被队列守卫在 merge group 里拒收。
 - 再读 `mergeable_state`:`dirty` ⇒ 先 merge `origin/main` 再挂;生成物在面上按 A 的固定序。
 - ready + 全绿 ≠ 已入队:队列从不主动拉 PR,入队是显式动作。

scripts/pm/check-governed-queue-guard.mjs

@@ -279,19 +279,31 @@
  * — answered 「我点头」. The other half of that boundary, the 规则层, is every
  * remaining governed path and is quoted in full on #17950; ⛔ it is NOT excerpted
  * here, because a partial rules-layer list read as the whole one is precisely
- * the under-claim `check-governed-prose` exists to stop. The register is the
- * enumeration; this leg only asks whether a path is under the ONE prefix above. The charter text landed as PR #18018; this leg is what
- * makes it ENFORCED rather than declared, which is the whole of #18020.
+ * the under-claim `check-governed-prose` exists to stop. The charter text landed
+ * as PR #18018; this leg is what made it ENFORCED rather than declared, which is
+ * the whole of #18020 — narrowly, for the one prefix quoted above.
  *
- * So a governed diff whose governed paths ALL lie under
- * `.claude/skills/pm-dispatch/references/` may land on a REVIEW OF RECORD in
- * place of the authorized approval: the `## Contract review` comment — on the
+ * ⭐ SUPERSEDED 2026-09-18 (#19133, ruled 「同意改规则。」 on the skills seat's
+ * proposal; the amendment moved `.claude/settings.json` and `.claude/hooks/**`
+ * over too: 「我觉得这些我也没必要确认」): the quote above is reproduced as the
+ * ruling that STARTED this leg, not as the population it enforces today. #19133
+ * widened that population from the one prefix quoted above to the WHOLE of
+ * `.claude/**` — Tier S, in the register's own words — leaving Tier H as exactly
+ * the register's other rows. The register's `tier` field is the enumeration now;
+ * this leg asks `governedTierFor` for Tier S, never a prefix repeated here — see
+ * the "landing TIER" section below for the enforced definition, and read it live
+ * with `node scripts/pm/check-governed-merges.mjs --test <paths>` rather than
+ * trusting a prefix copied into prose, which is exactly what went stale once.
+ *
+ * So a governed diff whose governed paths are ALL Tier S — today, the whole of
+ * `.claude/**` — may land on a REVIEW OF RECORD in place of the authorized
+ * approval: the `## Contract review` comment — on the
  * PULL REQUEST'S THREAD **or on its CARD'S** — that names the pull request's
  * CURRENT head, carries a `Reviewed-by:` line, and declares a `Served-tier:`
  * reading that STANDS -- its token being the NAME `CONTRACT_REVIEW_TIER`,
  * ⛔ never a model identifier, which `AGENTS.md` lets land in no comment and a
- * record IS one (#18060). Every other governed path is the rules layer and
- * keeps the predicate above byte-for-byte.
+ * record IS one (#18060). Every governed path outside Tier S is Tier H, the
+ * rules layer, and keeps the predicate above byte-for-byte.
  *
  * ⭐ THE TWO CARRIERS ARE ONE DELIVERY, and the location is the governed text's
  * to decide rather than this file's — quoted, untranslated, because it IS the