docs(pm-dispatch): cloud-card comms is event-driven by ruling — notes-21 verify-before-toggle, PR subscription as hard step

[os-zhuang]

Fixes#7755

Three validated deltas to .claude/skills/pm-dispatch/SKILL.md from the 2026-08-11 spec-lane shift, executing the maintainer's same-day rulings (「当前事件驱动架构即长期方案」/「云卡通信课题就此收档 … 不再追」/「没有计划 把 PM 席迁到常驻本地机」), plus the bbe056b rider folded in. All three targets were re-located semantically on post-#7766 compressed text (the card body predates the compression); everything verified against origin/main at 2701e95.

The three deltas

1. mode:cloud backend — roster limitation on record. New paragraph after 监控与转向: CCR cloud sessions do not register in the cross-session messaging roster (ListAgents doesn't list them, SendMessage by session ID returns not-reachable; the doc's visibility precondition — sender holds a claude.ai login on the first-party API — is not met by CCR container credentials). Ruling: the event-driven architecture IS the standing solution; ⛔ no roster re-tests, no local-machine migration. Measurement detail in references §「跨会话消息 roster 限制实测」.
2. Operational note 21 — amended in place (no competing entry). The old prescription (toggle when membership reads absent) had a timing defect: the "added to merge queue" webhook can arrive out of order, so a disable fired into the arming window cancels a real enqueue (spec: re-type TenantPlan / sys_environment.plan as an opaque plan identifier #7655; corrected sequence landed feat(spec): rule and enforce submitBehavior.url — relative-only, declared-field interpolation, URL-escaped (#7496) #7657 same day, zero friction). New sequence: ① empty-field return ⇒ verify queue branch first (git ls-remote, ~20–30s allowance); ② branch present ⇒ done, no toggle; ③ absent after wait AND queue visibly churned ⇒ ONE toggle, re-verify by notes 1 criteria; ④ (retained) disable on a settled member doesn't remove membership but clears the auto-merge flag. Hard rule: ⛔ never a disable between an enable and its queue verification. Narrative in references §「spec: re-type TenantPlan / sys_environment.plan as an opaque plan identifier #7655 armed 窗口 disable 撤单实测」.
3. Cloud-card PR subscription — elevated to a hard step. Now numbered lesson 4 of the mode:cloud delivery contract (实测三课 → 实测四课): the moment the cloud card's draft PR exists, subscribe_pr_activity it — an unsubscribed cloud-card PR is a polling liability. A/B evidence: fix(spec): lower equality triples with a $field comparand to {$eq: ref} (#7597) #7672 (unsubscribed, merge found minutes late by polling) vs spec: re-type TenantPlan / sys_environment.plan as an opaque plan identifier #7655/feat(spec): rule and enforce submitBehavior.url — relative-only, declared-field interpolation, URL-escaped (#7496) #7657 (subscribed, second-level delivery, zero polling). The 随行纪律 bullet stays as a pointer; the B-section boundary bullet is rewired to note the non-conflict with the report-time boundary post-[skill] pm-dispatch: 5 lessons from the domain:metadata seat's first term (8 cards MERGED / 0 rework / 4 dev-side falsifications) #6644 L2.

Rider (claude/pm-dispatch-spec-5ls2tr @ bbe056b) — adopted, adapted

Still applicable: its batch-sweep, never-archive-before-merge (#7265/#7325) and unarchive-caveat content was absent from post-#7766 main. Folded into the existing B-section archival bullet rather than as a standalone mode:cloud paragraph — post-#7766, the archival rule's single home is 入队与落地 B (the 随行纪律 bullet already points there), and a second paragraph would have created the competing-entry shape the card forbids. The rider's 6-line original text is preserved verbatim in references §「云卡归档欠账与 dirty 自救实测」 with provenance.

Ratchet discipline (headroom was 0)

MAX_LINES = 2568 and SKILL.md was exactly 2568 lines at origin/main. All additions (~+30 gross) are fully offset within touched paragraphs by the #7766 convention: residual narrative moved verbatim to references/incidents.md (append-only tail, five new sections, each with a 出处 line: #7655 sequence evidence, roster measurement, subscription A/B, #6072 perception-gap tale, archival-debt + rider text) and by reflowing the narrow-wrapped paragraphs already being edited. SKILL.md lands at exactly 2568 lines; MAX_LINES untouched.

Verification

• pnpm check:pm-skill-ratchet ✅ (2568/2568, headroom 0)
• pnpm check:skill-frame-sync ✅ (4 copies isomorphic)
• pnpm check:doc-authoring ✅ (375 files clean)
• pnpm check:nul-bytes ✅
• pnpm --filter @objectstack/lint run check:doc-formula-expressions ✅ (after building the lint dependency closure)
• Every §「…」 pointer in SKILL.md verified to resolve to a real section header in references/*.md (script check, zero missing)

No changeset: .claude/-only change (internal agent tooling), per repo convention — skip-changeset at acceptance.

Landing: skills updates are ADR-class (#7548) — this PR stays draft; ⛔ no auto-merge, no queue entry; the maintainer reviews and merges by hand.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MJrrkG5usF1W3mX6RLyxNA

---

Generated by Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
objectstack	Ignored		Aug 11, 2026 3:06pm

[os-zhuang]

CI note: the Check Changeset red is the expected shape for this PR, not a defect. The diff is .claude/-only (internal agent tooling — no package released), so no changeset file belongs in it; the gate's exemption path is the skip-changeset label, which per the #7755 dispatch card is the PM's act at acceptance (「PM 验收时打 skip-changeset」). Not applying the label from this dev session and not adding a placeholder changeset — the check goes green when the label lands. All other gates were run locally and pass (ratchet 2568/2568, frame-sync, doc-authoring, nul-bytes, doc-formula-expressions).

---

Generated by Claude Code