pm-dispatch: fold objectos into the protocol as the fourth triaged repository (Option B)

[os-support-ai]

Fixes#9551

Implements the adjudicated Option B plus the two adopted additions (maintainer 2026-08-18, verbatim, untranslated: 「就按 B,带你补的两条,落地吧」).

What changed

.claude/skills/pm-dispatch/SKILL.md (governed surface — this PR stays draft, human merge only):

1. Fold-in, stated in the multi-repo section: objectos is the fourth coordinated repository (pure docs and site code, outside the runtime dependency chain). Triage sweeps it; execution folds into domain:devx (which already owns content/docs/** + apps/docs); no repo:objectos seat is minted now.
2. Addition 1 — the A-upgrade trigger is written down where the fold-in is stated: either registered scale-out trigger from rule 4 (round duration approaching the fire cycle, or the objectos queue persistently starving under the selection total order) escalates objectos to a full repo:objectos seat — a recorded transition, not a second hole.
3. Addition 2 — objectos agent-instruction files are governed: the governed-face unified definition (ACCEPT path fork) now names the cross-repo extension — objectui, cloud and objectos alike (maintainer 2026-08-18: 「任何对 agents.md 等文件的修改…包括 objectui cloud仓库」→「同意」). Execution routes to devx, but objectos instruction-file PRs stay draft/human-merge. Note: no pre-existing cross-repo clause was found anywhere in SKILL.md or references (grep evidence in the report on [Decision] objectos is a fourth repository with no lane, no seat and no pm labels — which shape should it get? #9551), so the naming is anchored at the unified definition, which the Guardrails bullet already points to — no new section invented.
4. Honest dispatch-expectations notice, one spot where the fold-in is stated: objectos has no changeset flow, no packages/, no merge queue (landing = human merge), and a different CI shape — dispatched agents must not look for machinery that isn't there.

三仓-site inventory (per-site verdicts)

Site	Verdict
Multi-repo intro dependency sentence	stays 三仓 — describes the product runtime topology (spec → objectui/cloud); objectos, a docs/site repo, does not join the chain. The fold-in paragraph is appended right after it.
Rule 4 分诊座位「三仓唯一」	→ 四仓唯一, objectos added to the list
分诊座位职责「对三仓统一执行」	→ 四仓统一执行 (provenance split: 三仓归一 2026-08-16, objectos 并入 2026-08-18); release-board duty marked skip for objectos
路由「读三仓代码定落点」	→ 四仓 — triage routes objectos cards too
Shadow check 「搜两姊妹仓」	→ 各姊妹仓 (count-free; three siblings now)
Release-board health metric「三仓 target:* 之和」	stays 三仓 — objectos has no target:* boards, no changeset/release flow; counting a board that cannot exist would make the zero-condition unreachable in the wrong direction. ensure-pm-labels.sh documents the deliberate exclusion.

Line-ratchet payment table (682 → 682, headroom 0; ⛔ no re-wrap used)

Change	Lines	Content survives at
Fold-in + A-trigger + notice paragraph (multi-repo section)	+4	new (the adjudicated content)
Governed-face cross-repo naming (ACCEPT path fork)	+2	new (the adjudicated content)
分诊职责 provenance split + release-board skip note	+0	in-place edit
Guardrails: PM-writes-no-files exception de-duplicated	−1	全体座位的不变量 bullet 2 (verbatim: 逐 PR 明示授权 / 原话引用在 PR 正文 / 复核需另一座位或 walkthrough / ⛔ 不得自审自合)
Guardrails: release-act list de-duplicated	−2	AGENTS.md release-act paragraph (the binding, seat-universal copy; SKILL.md keeps the ruling date, the Version Packages pin, and the incident-filing rule)
Guardrails: governed ban trio / draft-exit / authoring-open de-duplicated	−2	ACCEPT path fork ②③ (ban trio + draft-only exit, verbatim) and AGENTS.md Prime Directive governed-landing paragraph (authoring-open + reviewed-green-no-override)
Guardrails: duplicated AGENTS.md-wins line deleted	−1	全体座位的不变量 bullet 4 (verbatim)

scripts/pm/ensure-pm-labels.sh: objectos joins the pm state-machine vocabulary loop (pm:queue, pm:dispatched, needs-user-decision, pm:on-hold, pm:blocked, pm:blocking, finding, pm:epic). Deliberately excluded, with comments saying why: the domain-lane loop (lanes are main-repo-only; objectos execution folds into devx) and the target:* loop (no release board). Retired-lane exclusions untouched. Actually running it against objectos is the PM's landing step — this session did not write labels to objectos. No repo:objectos seam label is minted either: it travels with the seat (or with the first real seam card), per the ruling's "no seat now" and startup scope discipline.

Gates (all at head 6a8b11b, after the final commit)

Derived with node scripts/pm/dispatch-gates.mjs (no paths — script-derived changed set, matches the dispatch prompt's list exactly; tier line: clause ① fable-mandatory, satisfied):

• pnpm check:pm-skill-ratchet — exit 0 (SKILL.md 682/682)
• pnpm check:pm-skill-id-lint — exit 0 (9 files clean)
• pnpm check:skill-frame-sync — exit 0 (4 copies isomorphic, 3 axes)
• pnpm check:pm-governed-merges — exit 0 (self-test, 25 assertions)
• pnpm check:doc-authoring — exit 0 (377 files clean)
• pnpm --filter @objectstack/lint run check:doc-formula-expressions — exit 0 (built the @objectstack/lint upstream-dependency closure first)
• node scripts/check-nul-bytes.mjs — exit 0

Open question (not adjudicated here)

The post-claim comment on #9551 raises the objectos landing-shape question (no merge queue; three shapes offered, no recommendation). This PR records only the de-facto status quo as a factual notice (落地 = 人工合并) and does not rule on which shape the protocol adopts — that sub-question remains open on the card.

.claude/ + scripts/ only — publishes nothing; skip-changeset applies.

---

Generated by Claude Code