pm-dispatch(mailbox): one mailbox PR per seat, a closed doorbell vocabulary (request / notify), alternate-pick for multi-seat lanes, and seat-online / seat-offline notices that wake the sibling seats and triage

Filing gate ③ (maintainer-directed). Filed by the domain:skills#2 seat (os-justin, session_01QSeKYmhU5KEj1nukYhp1Tg, seat post #19287) from a design conversation with the maintainer in that session on 2026-10-28. ⛔ Not a claim; domain:* pre-labelled because every path below is in the skills tree — triage grades.

The maintainer's words (verbatim, in order)

「车道贴为什么不可以直接用 pr，订阅pr可以实时接收消息」 then 「车道之间可以互通」
「我说的车道互通的意思是比如需要分诊紧急处理，没有fable了，需要请分诊复审，分诊审完了需要通知车道。比如main红了，需要协调谁来开发」
「但是也要避免ai互聊信息太多爆炸，我觉得只沟通必要的信息。还有就是同一个车道分在几个不同 Claude code 账户的多个座位上，也是需要协调分工。座位下线的时候也是需要通知」
「分诊席和每个车道通常是长期开着的，只有账户没token了，会切换账户重开」
On the seat's proposal (B: keep the issue registration, make the mailbox PR per seat): 「B方案暂时是不是成本最低的，没有风险的」 → the seat's answer named three measured risks (below) → 「同意信箱改每席一张」, then 「立卡」.

Business reason

Only a PR wakes a session (subscribe_pr_activity); nothing on an issue does. Every cross-seat request today is a PULL: a Contract-review-handoff: line, a cross-seat note on a seat post, a p0 anchor card — read at the receiver's next patrol or summons. PR #26766 waited 9 h for a contract review nobody was woken for. The mailbox PR (pm:mailbox, scripts/pm/mailbox-open.mjs, LEDGER_EXCLUSION, filed by #25412/#25414) already exists as the wake channel, one per PROJECT, and 0 are open today. This card makes it one per SEAT and gives it a closed vocabulary, so the three cases the maintainer named become PUSH without AI-to-AI chatter.

Reader who acts

The domain:skills seat, after #26997 lands (same protocol-text surface; serial). Tier S.

What lands (one PR)

A. One mailbox PR per seat — references/project-forms.md 〈信箱 PR〉: 「每项目至多一个 draft PR」 → one per seat (lane seat, triage seat, director seat), branch mailbox/<login> as today (per ACCOUNT: an account switch opens a new one and closes the old through the relay — the walled account writes nothing, the newcomer announces), labels pm:mailbox + pinned, body first line To: <login>, the seat post's stub carries the mailbox number as its pointer line. Never merged; closed on hand-over or account switch. The seated session subscribes to it (one subscriber per PR is the platform's shape and the wanted one).

B. The closed doorbell vocabulary — the first line of a mailbox comment is one of these keys and nothing else is allowed on a mailbox:

First line	From → to	When
`Request: contract-review · PR #n · head SHA · REASON`	lane → triage	the lane's review tier is unavailable (429 / exhausted); once per head
`Request: urgent-triage · #n · ONE-LINE-CRITERION`	any seat → triage	p0 suspect, main red, deterministic queue red
`Request: main-red · CHECK-NAME · anchor #n · suggested lane X`	the finding seat → triage (director when triage is absent)	the moment the p0 anchor card exists
`Notify: contract-review PASS or FAIL · PR #n · record ID`	triage → lane	the same act that lands the record (not sent when the lane already subscribes to that PR)
`Notify: seat-online · LANE#N · LOGIN · mailbox #m · takes: #a #b …`	the seating session → sibling seats of the lane + triage	the seating act (a takeover's newcomer sends it for the walled account)
`Notify: seat-offline · LANE#N · in-flight: … · stay-behind: … · brief ID`	the signing-off session → sibling seats + triage	the same act as the 收班简报
`Notify: split · LANE#N · takes: … · leaves: …`	a seat of a multi-seat lane → its siblings	at round open, only when the list changed

Hard rules (the anti-chatter half, maintainer's words 3): one event, one line, ≤200 bytes, only keys and numbers — reasons, readings and analysis stay on the card or PR; no acknowledgements (the action is the receipt: the record landed, the claim landed; the sender re-reads GitHub at its own next step, ⛔ never posts 收到/谢谢/请确认); no re-send of the same fact (one Request per head; no nagging — the existing escalation rules take over, e.g. a review a lane has not started in one round goes to triage); anything outside the table is a half-state the half-state patrol reports; ≤5 mailbox comments per seat per round, p0 exempt; every send counts against the write pace. A mailbox comment is a colleague's statement, ⛔ never an authorisation (untrusted-text.md's three sources are unchanged).

C. Multi-seat lanes — references/execution-duties.md 〈候选与批次〉 one line: seats of one lane take candidates by alternate pick over the lane's priority order (seat 1 the 1st, 3rd, 5th …; seat 2 the 2nd, 4th, 6th …), hot-file serial unchanged; a split notice is sent only to break the alternation; the claim timestamp stays the tie-breaker.

D. Online / offline — references/seat-lifecycle.md 〈座位贴协议〉 two lines: seating sends seat-online; the 收班简报 act sends seat-offline; a forced takeover's newcomer sends seat-online for the walled account (it can write nothing). The sentence 「分诊席跑直连会话 … ⛔ 无自醒不常驻」 is corrected to the maintainer's actual form (words 4): seats are long-lived; an account that runs out of tokens is replaced by a new account that reopens the seat and its mailbox.

E. Recogniser — scripts/pm/record-recognisers.mjs parses the seven keys (kind, numbers, sha, login, time) beside the records it already reads, with self-test cases; ⛔ no gate, workflow or queue guard reads a mailbox — coordination, not a merge condition.

F. Workflows ring the doorbell too (maintainer, 2026-10-28 ~06:4xZ, verbatim: 「把这一条补进 #27077」, on the triage seat's point that no seat watches a main push red, so a mailbox only helps if something rings it). The workflows that already file a red card send the matching Request: main-red line to the owning lane's mailbox and to triage's, in the same run that files or refreshes the card:

scheduled-full-run-card.yml (the 4-hourly "red on main" card);
merge-queue-triage.yml (the queue-flake anchor, on its first filing only, not on every refresh);
a main push run that goes red with no anchor open for that check. This is a new step: today nothing files on a push red.
⛔ They write, never read: E's rule that no gate, workflow or queue guard reads a mailbox stands. One line per event, the same ≤200 B closed key. The suggested lane comes from the failing path, by the lane table. .github/workflows/** is Tier H, so F may land as a second PR after A–E, so the Tier S mailbox PR is not held behind a governed approval.

Premises (each with its re-check)

P1 — stale.yml closes a quiet PR: days-before-pr-stale: 30, days-before-pr-close: 7, exempt-pr-labels: 'pinned,security,work-in-progress' (no pm:mailbox). Re-check: git show origin/main:.github/workflows/stale.yml | grep -n -E 'days-before-pr|exempt-pr-labels'. Hence pinned on every mailbox; ⛔ no workflow edit (Tier H, not worth it).
P2 — a PR body edit triggers pr-body-guards.yml (types: [opened, edited, reopened, synchronize]); comments do not. The mailbox body is written once, so B pays nothing per message. Re-check: git show origin/main:.github/workflows/pr-body-guards.yml | grep -n 'types:'.
P3 — one PR wakes one session at a time (platform). A new mailbox per account switch keeps the subscriber unambiguous. Re-check: the subscribe_pr_activity tool text in the session harness; no repo reading.
P4 — the receiver is a resident session (words 4). A Routine seat (cron) cannot be woken; for it the hourly patrol reads the mailbox. Said in the text, not solved here.
P5 — the mailbox tooling exists and is unused: scripts/pm/mailbox-open.mjs present, LEDGER_EXCLUSION appends -label:pm:mailbox, GET /issues?state=open&labels=pm:mailbox → 0 on 2026-10-28T04:3xZ. Re-check: that query plus ls scripts/pm/mailbox-open.mjs.

Relation to queued cards

#27062 (contract-review ownership: the lane reviews its own, triage takes a review nobody is doing, one claim line per head) and #27047 (p0 dispatch rules) are the RULES this channel carries; this card is the CHANNEL. They share record-recognisers.mjs; whichever lands second merges origin/main first. ⛔ This card does not restate their rules.

Acceptance

A reader of project-forms.md alone learns: one mailbox per seat, pinned, the seven keys, the four hard rules, the account-switch flow.
record-recognisers.mjs --self-test parses one example of each key and refuses a free-text mailbox comment.
check:pm-skill-ratchet, check:pm-skill-id-lint, check:pm-governed-prose green; the references pay their lines in place (0 headroom files: measure first).
Clause-②: no · Metadata-protocol: none · Size S · Tier S (.claude/** + scripts/pm/**).

Dedupe (REST list, labels=domain:skills, open 27 + closed 400, grep mailbox|信箱|doorbell|seat-offline|seat-online): open → only seat post #19287 (this conversation's note); closed → #25412, #25414 (the mailbox's birth cards, one per project). New.

Triage: p1 · `domain:skills` · `area:devpath` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-28T04:56Z

⛔ Not a claim.

Read fresh. Maintainer-directed (verbatim on the card): one mailbox PR per seat, a closed doorbell vocabulary (request / notify), alternate-pick for multi-seat lanes, and seat-online / offline notices. Only a PR wakes a session, so today every cross-seat ask is a pull. PR feat(adr-0087): retire a deleted published package whole (PACKAGE#*, D9 amendment) #26766 waited 9 h for a review nobody was woken for.
p1: it is the wake channel that pm-dispatch(contract-review): the lane reviews its own PRs; triage takes only a review nobody is doing, and one claim line per head keeps two reviewers off the same head #27062 (contract-review claim / gap rule), pm-dispatch(p0): a lane's p0 card is dispatched at once — no batch, depth-wait or concurrency cap holds it, and lower-priority dev work pauses to make room; main or merge-queue red is graded p0 at first touch #27047 (p0 dispatch) and pm-dispatch(triage): a lane seat may self-triage (p1/p2) a card that blocks its own in-flight work on clear evidence, then ask the triage seat to review #27061 (lane self-triage review) each lean on. ⚠️ Keep the doorbell vocabulary closed, as the maintainer asked (「只沟通必要的信息」). A claim line, a hand-off, a p0 and a review-done notice are the four requests and notices triage needs.
priority:p1, area:devpath, pm:queue.

Generated by Claude Code

Claim: PM loop round 1 (takeover shift, wave 3 — maintainer's insert) · 2026-10-28T06:33Z
Session: session_01QSeKYmhU5KEj1nukYhp1Tg (seat; implementation by an os-dev subagent of this session, mode:subagent — same session ID, identity by branch)
Account: os-justin (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/issue-27077-mailbox-per-seat-doorbell
Worktree: objectstack-issue-27077
Domain: domain:skills
Seat: domain:skills#2 (seat post #19287)
Take-order provenance (维护者直派插队卡, three parts): who — the maintainer; verbatim — 「27077 这个应该最优先派发」; where — the maintainer's direct cloud session session_01QSeKYmhU5KEj1nukYhp1Tg, 2026-10-28, after triage's first grade 6461033102 (p1).
File surface: .claude/skills/pm-dispatch/references/project-forms.md 〈信箱 PR〉 (L43–48: one mailbox per SEAT, pinned + pm:mailbox, the seven-key closed vocabulary, the four anti-chatter rules, the account-switch flow); .claude/skills/pm-dispatch/references/seat-lifecycle.md 〈座位贴协议〉 (seat-online / seat-offline notices, alternate-pick for multi-seat lanes may instead sit in execution-duties.md 〈候选与批次〉 — the dev picks the line that pays for itself); .claude/skills/pm-dispatch/SKILL.md L74 ONLY (「分诊席跑直连会话、默认判断档;直连会话按召唤跑,⛔ 无自醒不常驻;裁决归总监席」 → seats are long-lived; an account out of tokens is replaced by a new account that reopens the seat and its mailbox); scripts/pm/record-recognisers.mjs (the seven keys parsed beside the records it already reads, with self-test cases); scripts/pm/mailbox-open.mjs only if its refusal ① (one mailbox per login per repo) or Mailbox-of: line must learn the seat name — else untouched. Every .claude/** file here is at its line ceiling (SKILL.md 319, project-forms 54, seat-lifecycle 96, seat-post-protocol 88, coordinator 49; headroom 0): edits IN PLACE, lines paid by deleting content that has a home elsewhere, ⛔ no re-wrap as currency; a ceiling raise is blocked, not a seat act. ⛔ No gate, workflow or queue guard reads a mailbox. Tier S (.claude/** + scripts/pm/**): one draft PR, contract review at CONTRACT_REVIEW_TIER before the seat readies it. (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: CONTRACT_REVIEW_TIER (reason: dispatch-gates --tier --repo objectstack-ai/objectstack .claude/skills/pm-dispatch/SKILL.md at 50b1b7d8 prints Model tier — MANDATORY: claude-fable-5-1 — the one-line edit to SKILL.md L74 is a semantics change (the triage seat's form), not mechanics, so the one-line exit is not taken; the references and script alone print no mandate), effort: xhigh (p1, new protocol vocabulary)
Clause-②: no
Metadata-protocol: none
Responsibility: n/a — not a defect card (filing gate ③, maintainer-directed)
Thread-read: 6461033102
Premise: holds — read on origin/main 50b1b7d8 (this act, 2026-10-28T06:33Z): project-forms.md L46 still reads 「每项目至多一个 draft PR,标签 pm:mailbox,分支 mailbox/<login>」 and L48 「不欠 CI,一切落地与台账查询排除它」; SKILL.md L74 still says the triage seat is summoned, not resident; scripts/pm/mailbox-open.mjs exists (open per login, --close N, refusal ① one mailbox per login per repo, Mailbox-of: body line); record-recognisers.mjs is 2287 lines with --template / --self-test and exports contractReviewHandoff beside reviewFace; stale.yml exempts pinned PRs (the card's P1); 0 open pm:mailbox PRs. Triage's caution 6461033102 binds: keep the vocabulary CLOSED — the four it names (a claim line, a hand-off, a p0, a review-done notice) are inside the card's seven keys.
Serial constraints cleared: open PRs touching SKILL.md — #27082 (this seat, L161/L162/L183, awaiting the maintainer's landing) and #26749 (seat 1, L166) — both region-disjoint from L74; the dev merges origin/main before opening and again if either lands first; no open PR touches project-forms.md, seat-lifecycle.md, seat-post-protocol.md, record-recognisers.mjs or mailbox-open.mjs (file scan of the open PRs in this act, 2026-10-28T06:33Z). Queued, not dispatched, sharing files: #27117 (seat-lifecycle L70, execution-duties L21) and #27062 (record-recognisers.mjs, contract-review.md) — both serialized BEHIND this PR.
Resume-from: none

triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

Scope amendment (maintainer-directed): item F, workflows ring the doorbell · 2026-10-28T06:37Z

⛔ Not a claim. For the claiming seat (os-justin, claim at 06:33Z): the body gains item F.

Maintainer, verbatim: 「把这一条补进 pm-dispatch(mailbox): one mailbox PR per seat, a closed doorbell vocabulary (request / notify), alternate-pick for multi-seat lanes, and seat-online / seat-offline notices that wake the sibling seats and triage #27077」. It answered triage's point that a main push red is seen by no seat. Tonight dogfood: packaged-action-disabled-dispatch-live picks an unordered showcase_task?$top=1; when that seed task is already done, acceptance[0] fails and acceptance[5] cascades (main push red 21:56Z and 22:08Z) #26952 reddened main six times before the hourly triage round read it. So a mailbox helps only if something rings it.
F: the full-run card workflow, the merge-queue-triage workflow (first filing only), and a new step on a red main push with no open anchor each send Request: main-red to the owning lane's mailbox and to triage's. They write and never read (E stands). It uses the same closed key and the same ≤200 B line.
Landing: .github/workflows/** is Tier H. Land F as a second PR after A–E, so the Tier S mailbox PR does not wait on a governed approval. One card, two PRs.
The maintainer also ruled the 30-minute triage check unneeded once the mailbox is live. So the hourly round stays as the backstop, and F is what makes a red reach a seat within minutes.

Generated by Claude Code

os-dev-report

Reported at 2026-10-28T08:10Z · head d82ca53 · PR #27143 · status done · the JSON below is the report the seat parses.

{
  "issue": 27077,
  "status": "done",
  "branch": "claude/issue-27077-mailbox-per-seat-doorbell",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/27143",
  "head": "d82ca533ad474071d25e6ba22d9cf0fa6c695879",
  "session": "session_01QSeKYmhU5KEj1nukYhp1Tg",
  "premise_still_valid": true,
  "summary": "Sections A-E of the card landed in one draft PR (#27143, Tier S, draft, skip-changeset, assignee os-justin). project-forms.md 〈信箱 PR〉 now carries one mailbox PR per seat (pm:mailbox + pinned, body first line To: LOGIN, opened at seating and closed at hand-over or account switch with the successor opening a new one), the seven first-line keys spelled exactly as the card prints them, and the four anti-chatter rules; seat-lifecycle.md 〈座位贴协议〉 carries the seat-online / seat-offline acts and the newcomer-for-walled-account and Routine-patrol clauses; execution-duties.md 〈候选与批次〉 the alternate pick; SKILL.md L74 the maintainer's resident-seat form with 裁决归总监席 kept. record-recognisers.mjs reads the seven keys (readMailboxLine, mailboxEvents, MAILBOX_KEYS; pure, exported beside contractReviewHandoff) with a 21-case battery that also pins every template verbatim in the protocol text; mailbox-open.mjs sends pinned, writes To: LOGIN as the body's first line (retiring the tool's Mailbox-of: dialect for the protocol's spelling) and names the closed vocabulary; refusal ① is unchanged because per-login already equals per-seat (measured: a login holds one seat at a time). Premise re-checked on origin/main 53e0663d and again after merging 07d18e69: every target line was still as the claim read it; neither #27082 nor #26749 had landed, and both are region-disjoint from L74 / execution-duties L37-54. Three mechanical companion edits outside the declared file surface were required by check:pm-dispatch-gates (a new governed self-test read must be declared and registered) and are listed under deviations.",
  "files_changed": [
    ".claude/skills/pm-dispatch/SKILL.md (L74 replaced in place, 114 B to 116 B; 319/319)",
    ".claude/skills/pm-dispatch/references/project-forms.md (〈信箱 PR〉 6 to 16 lines, paid by 10 deletions; 54/54)",
    ".claude/skills/pm-dispatch/references/seat-lifecycle.md (+2 after the 收班 line, paid by L47 and L48; 96/96)",
    ".claude/skills/pm-dispatch/references/execution-duties.md (+1 after the 全序 lines, paid by L37; 188/188)",
    "scripts/pm/record-recognisers.mjs (MAILBOX_KEYS, readMailboxLine, mailboxEvents, the doorbell battery, SELF_TEST_BATTERY_FLOOR 13 to 14, the self-test-reads declaration at line 77)",
    "scripts/pm/mailbox-open.mjs (STALE_EXEMPT_LABEL pinned in PR_LABELS, To: LOGIN body line read and written, the seven-key rule in the body, close comment, two new pins; open-plan battery floor 8 to 9)",
    "scripts/pm/dispatch-gates.data.mjs (GOVERNED_READ_FLOOR fifth row, declared: true, with a docblock paragraph) — outside the claim's declared surface, see deviations",
    "scripts/pm/dispatch-gates.self-test.mjs (live-declaration roster ninth row; eight to nine in the title and the length pin) — outside the claim's declared surface, see deviations"
  ],
  "line_budget": {
    "ceilings_after": "SKILL.md 319/319 · project-forms.md 54/54 · seat-lifecycle.md 96/96 · execution-duties.md 188/188 (check:pm-skill-ratchet exit 0, headroom 0 on all four; every prose line at or under 120 bytes by wc -c)",
    "project-forms.md": {
      "section": "〈信箱 PR〉 heading+blank+4 bullets (6) to heading+blank+14 bullets (16): +10; the fourth old bullet (pm:mailbox PR 不欠 CI…, 67 B) kept verbatim, the other three rewritten in place",
      "new_lines_bytes": "107 · 115 · 115 · 119 · 118 · 120 · 119 · 118 · 116 · 119 · 115 · 118 · 118",
      "deleted": [
        "L9 车道席:认领、派发、PR、跨账号复审;总监席:决策箱与决裁批、发版、日报、总表。 (112 B) → home SKILL.md 入口与角色 table + lanes/director.md 职责一–四",
        "L10 分诊席:只写标签与审计评论;分诊与总监可召进任一项目,⛔ 不绑定项目。 (99 B) → home lanes/triage.md L4 + SKILL.md L55",
        "L11 唯一不变量在账号不在项目:批准账号永不跑席位(SKILL.md 全体座位的不变量);本文不另加。 (120 B) → home SKILL.md L93 (self-declared restatement)",
        "L26 一张也没有 ⇒ 项目闲置;每席恰一条席位线程、恰一车道,一席一贴。 (93 B) → home same file L30 + seat-post-protocol.md L9 + coordinator.md §一",
        "L29 协调者每次开场把指令行与座位贴对照:逐席按 seat-post-protocol.md 坐席或接管。 (106 B) → home coordinator.md §一 L10–L13",
        "L32 总监席只被维护者召唤与 PR 订阅唤醒;摘要与收件箱扫描在召唤内做;见 lanes/director.md。 (118 B) → home lanes/director.md L7, L12, L24 (same file L31 keeps 总监席不建)",
        "L33 并发上限是维护者在该项目定的姿态;⛔ 不是协议常量,本文不写数字。 (95 B) → home coordinator.md §三 L23",
        "L38 撞墙账号写不出任何东西,接管永不等它的注记或简报。 (75 B) → home seat-lifecycle.md L29 + execution-duties.md L83; the section heading keeps the thesis",
        "L39 跨账号 Release: 点名旧会话与出处三件;新 Claim: 带 Resume-from: BRANCH@SHA,新 dev 续旧分支。 (120 B) → home execution-duties.md 认领 ①–④ L84–L86, which L40's pointer names",
        "L54 读自座位贴、标签、assignee 与 PR 查询;生成视图 ⛔ 不手改(cross-repo-coordination.md 规则 5)。 (120 B) → home lanes/director.md L82 + SKILL.md L92"
      ]
    },
    "seat-lifecycle.md": {
      "new_lines_bytes": "115 (坐席发 seat-online、收班简报同一动作发 seat-offline,键见 project-forms.md 〈信箱 PR〉) · 101 (强制接管的新账号代撞墙账号发 seat-online;Routine 席唤不醒,读信箱靠巡查)",
      "deleted": [
        "L47 接管/移交 = 改正文 + 审计评论(只作审计);收尾清单等细则见 references/seat-post-protocol.md。 (119 B) → home seat-post-protocol.md L27, L33 and its 交接收尾清单 section",
        "L48 epic 委托不入座位贴体系;新 packages/spec 工作恒归 spec 座位。 (82 B) → home same file L61 + cross-repo-coordination.md (协议恒归 domain:spec)"
      ]
    },
    "execution-duties.md": {
      "new_lines_bytes": "115 (一车道多席按全序交替取卡:席 1 奇位、席 2 偶位;只为破交替才发 split;认领戳仲裁)",
      "deleted": [
        "L37 文件面不相交只保证文本可合并;跨文件语义耦合由队列 CI 逮住,⛔ 不读作不可能冲突。 (117 B) → home AGENTS.md Multi-agent discipline §10"
      ]
    },
    "SKILL.md": {
      "replaced_in_place": "L74 分诊席跑直连会话、默认判断档;直连会话按召唤跑,⛔ 无自醒不常驻;裁决归总监席。 (114 B) → 分诊席与车道席常驻,断粮即换账号重开该席与信箱;分诊席默认判断档;裁决归总监席。 (116 B); outside the governed-prose and frame-sync regions"
    },
    "no_rewrap_as_currency": "every paid line is a deletion of content with a named home; the 总表 section pays only L54 because the objectstack 置顶 issue fact in L52 has no other home, and project-forms L31 is kept because 分诊席加每小时裸卡轮 has no other home"
  },
  "tests": "node scripts/pm/record-recognisers.mjs --self-test → exit 0 · '✓ record-recognisers self-test: 254 cases pass' (233 + the new 21-case doorbell battery; floor 13 → 14). node scripts/pm/mailbox-open.mjs --self-test → exit 0 · '✓ mailbox-open self-test: 45 cases in 8 batteries pass' (two new pins: pinned read off stale.yml exempt-pr-labels and pm:mailbox not in it; the body opens with To: and names the closed vocabulary). node scripts/pm/check-governed-queue-guard.mjs --self-test → exit 0 · 401 cases (loads the recogniser through the real lazy import). pnpm check:pm-half-states → exit 0 · 5034 cases. No ablation: scripts and protocol text only, no tested product behaviour changed. No package touched, so no build closure, no package test, no changeset (skip-changeset on the create).",
  "gates": "Local subset = node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack on head d82ca533 (no paths; change set 8 paths vs merge base 07d18e69, 0 uncommitted): 41 families, each run in the foreground with exit captured before any pipe (scratch exits.tsv), reconciled by --ran with ' :: exit N' tails → exit 0 · '✓ dispatch-gates --ran: 41 derived famil(ies) accounted for — 40 run, 1 NOT-MEASURED (0 DERIVED from a recorded exit 3, 1 claimed)'. 40 families exit 0, among them: pnpm check:pm-skill-ratchet (four files at ceiling, headroom 0), check:pm-skill-id-lint (104 files clean), check:pm-governed-prose, check:skill-frame-sync, check:pm-record-recognisers, check:pm-dispatch-gates (1935 cases pass on the final head; it was 2-of-1935 red on the first head until the governed read was declared and registered, see deviations), check:nul-bytes, check:doc-authoring, check:scripts-symbol-anchors, check:pm-governed-merges, check:pm-expected-skips, node scripts/pm/check-governed-queue-guard.mjs --self-test. NOT MEASURED: pnpm --filter @objectstack/lint run check:doc-formula-expressions → exit 3 PREREQUISITE NOT MET (@objectstack/lint and @objectstack/formula unbuilt in this worktree; the gate ran no check; CI's Lint & Repo Gates builds them). Local-only: node scripts/check-skill-frame-freshness.mjs --no-fetch → exit 0 (frame unchanged). CI check-runs on PR #27143: in_progress at report time (not waited for); every family CI runs is cited from the PR's check-runs by the seat, not re-run here.",
  "dogfood_battery": "n/a — no `!` in the PR title and no (narrowing) arm",
  "mcp_calls": "0 — no GitHub MCP tool was called, read or write",
  "api_writes": "2 relay writes + 4 git pushes. Relay: pr_create (request fw-20261028T080610Z-352d4f, run 40654413661 success → POST /repos/objectstack-ai/objectstack/pulls and its assignees and labels legs; read-back identical, 19500 bytes, assignees os-justin) and the os-dev-report comment via post-stamped (POST /repos/objectstack-ai/objectstack/issues/27077/comments). git push (not REST): the empty branch probe, then 128ad12c, 2a864ee7 (merge of origin/main 07d18e69), d82ca533.",
  "deviations": [
    "File surface breached by three mechanical companion edits, under the bounded in-place rule (all four conditions hold: the gate's own remedy for this diff, form pinned by the gate's failure text, no open PR holds either file — file scan of the 32 open PRs — and the family check:pm-dispatch-gates is already derived for this card): the self-test-reads declaration line in record-recognisers.mjs (line 77), the GOVERNED_READ_FLOOR row (declared: true) in scripts/pm/dispatch-gates.data.mjs, and the ninth live-declaration roster line (eight to nine) in scripts/pm/dispatch-gates.self-test.mjs. Measured: before, check:pm-dispatch-gates failed 2 of 1935 (unpinned governed read; family not derived for project-forms.md); after, 1935 pass and dispatch-gates --commands over project-forms.md alone derives pnpm check:pm-record-recognisers keyed on the declaration. The seat amends the claim's file surface.",
    "mailbox-open.mjs edited (the order's conditional file): not for refusal ① (per-login equals per-seat, measured, left as is) but for A's ruled shape — pinned on the create and To: LOGIN as the body's first line, replacing the tool's Mailbox-of: dialect; the protocol text has said 正文首行 To: since the mailbox's birth and the tool's header defers to the protocol on that line; 0 pm:mailbox PRs are open, so no stored instance carries the old spelling.",
    "The card's hard rule 'anything outside the table is a half-state the half-state patrol reports' is written as 表外即半态; check-half-states.mjs gained no row (not in the file surface; E forbids a gate reading a mailbox). The reading a patrol takes is mailboxEvents(rows).halfStates.",
    "pnpm --filter @objectstack/lint run check:doc-formula-expressions NOT MEASURED locally (prerequisite build of two packages; the gate's subject is unrelated to this diff; CI runs it).",
    "The seat-online / seat-offline rows in project-forms.md carry only from → to; their when lives in seat-lifecycle.md's two lines (the 120-byte cap did not fit both halves beside the card's exact key spelling). The alternate-pick line omits the words hot-file serial unchanged: that rule stands unedited at execution-duties L26.",
    "test:repo not run (CI's Test Core); no package in the diff."
  ],
  "open_questions": [],
  "out_of_scope_findings": [
    "class: b · reach: exception: maintainer-directed channel (the mailbox text makes pinned mandatory, as ruled) · evidence: GET /repos/objectstack-ai/objectstack/labels/pinned → 404 and labels/work-in-progress → 404 on 2026-10-28 while .github/workflows/stale.yml exempt-pr-labels names pinned,security,work-in-progress (only security exists, 200); the exemption for two of its three names is dead until the labels exist; whether the relay's add-labels POST creates a missing label is a platform reading the first mailbox open takes (a write, not taken here) · carrier: the seat — one line in scripts/pm/ensure-pm-labels.sh is the designed place to create pinned (SKILL.md: a label exists iff it has a named reader; stale.yml is that reader) · dedupe words: pinned, exempt-pr-labels, stale.yml, work-in-progress, ensure-pm-labels",
    "carrier: seat · noted, not filed: #27062 (contract-review ownership rules) and #27047 (p0 dispatch) share record-recognisers.mjs with this PR; whichever lands second merges origin/main first (the card's own instruction). #26749 (open) also edits execution-duties.md L175 and SKILL.md L162 — disjoint from this PR's L37/L54 and L74."
  ]
}

Generated by Claude Code

ACCEPT → PR #27143 comment 6464191702 · domain:skills#2 · 2026-10-28T08:23Z — ⛔ not a claim. Contract review (CONTRACT_REVIEW_TIER) PASS → PR comment 6464123012 on head d82ca533. Tier S (.claude/** + non-gate scripts/pm/**): all 45 check-runs green or expected-skip, mergeable_state: clean; the seat lands it through the relay (pr_ready + automerge_enable) in the next act — if this session's permission classifier refuses that stroke again (as on #27082), the seat stops and reports here. Filed from the dev's class-b finding: #27151 (pinned label absent, ensure-pm-labels.sh to create it). The claim's file surface is amended by the contract review to include the three mechanical companion edits (dispatch-gates.data.mjs, dispatch-gates.self-test.mjs, the declaration line in record-recognisers.mjs). After MERGED: strip pm:dispatched, then #27113 (serialized behind this PR on record-recognisers.mjs) is dispatched.

Generated by Claude Code

Landing stroke refused by the session's permission classifier — the seat stops here

2026-10-28T08:24Z · domain:skills#2 · session_01QSeKYmhU5KEj1nukYhp1Tg. Pre-landing readings were all in: contract review PASS 6464123012, ACCEPT 6464191702, 45 check-runs green or expected-skip on head d82ca533, mergeable_state: clean, check-governed-merges --pr 27143 → Tier S. The seat then ran, bare, from the repo root:

node scripts/pm/fleet-write/dispatch.mjs --repo objectstack-ai/objectstack --actions-file /tmp/…/land-27143.json --json with the file [{"op":"pr_ready","pull":27143},{"op":"automerge_enable","pull":27143}]

Refused before execution by the Claude Code auto-mode classifier with the reason [Merge Without Review] — the same refusal this session met on PR #27082 (card #26997, note 6461164164). Nothing was sent; PR #27143 is still draft with no auto-merge. Per landing-operations.md B (「落地遭分类器拒 ⇒ 停手、报维护者、卡上记命令与拒因;⛔ 不换拼法、不退回 ccr 绕过」) the seat makes no second attempt and no respelling. Reported to the maintainer in the seat's session; the PR waits on the maintainer's hand (ready + auto-merge), a permission rule for that command, or an authorising word the seat can cite.

Generated by Claude Code

Landing stroke sent on the maintainer's word — PR #27143 ready, auto-merge armed, enqueued

2026-10-28T12:20Z · domain:skills#2 · session_01QSeKYmhU5KEj1nukYhp1Tg. The maintainer, in the seat's session: 「你应该按照 pm-dispatch 技能审核并落地pr」. On that word the seat re-sent the same relay stroke (no respelling) that the session's classifier had refused (note 6464224208): node scripts/pm/fleet-write/dispatch.mjs --repo objectstack-ai/objectstack --actions-file land-27143.json --json with [{"op":"pr_ready","pull":27143},{"op":"automerge_enable","pull":27143}] → relay run 40686376753 success. Timeline read back: ready_for_review 2026-10-28T12:16Z, auto_merge_enabled 2026-10-28T12:16Z, added_to_merge_queue 2026-10-28T12:16Z. Pre-landing readings unchanged from the ACCEPT (all checks green or expected-skip, mergeable_state: clean). The seat follows it to MERGED; the landing comment with the two probe readings comes then.

Generated by Claude Code

Landed — PR #27143 merged; card closed by `Fixes #27077`

probe	reading (2026-10-28T12:39Z, `domain:skills#2`)
`git merge-base --is-ancestor d63f24a7 origin/main` after `git fetch origin main`	true — `d63f24a7` `pm-dispatch(mailbox): one mailbox PR per seat with a closed doorbell vocabulary; seat-online/offline notices; alternate pick for multi-seat lanes` is on `origin/main`; `GET pulls/27143` → `merged: true`, `merge_commit_sha d63f24a7`, merged by the queue entry the seat made on the maintainer's word (2026-10-28T12:33Z); `origin/main:SKILL.md` L74 reads 「分诊席与车道席常驻,断粮即换账号重开该席与信箱;分诊席默认判断档;裁决归总监席。」
`GET issues/27077`	`state: closed`, `state_reason: completed` (2026-10-28T12:33Z), closed by the PR body's `Fixes #27077` (the only closing keyword in the body — no other card was closed by it)

State change: pm:dispatched removed from this card in the same act (label-write, read back: tooling, priority:p1, domain:skills, area:devpath remain as ownership). Follow-ups now live: #27151 → PR #27211 (the pinned label rows) merged in the same queue batch; the labels themselves still need one bash scripts/pm/ensure-pm-labels.sh run by a gh-holding account before the first mailbox opens with pinned; #27113 (the signature line, serialized behind this PR on record-recognisers.mjs) is dispatched next. Main's push CI on d63f24a7 is read with the batch's other merges.

Generated by Claude Code

Navigation Menu

Repository navigation

pm-dispatch(mailbox): one mailbox PR per seat, a closed doorbell vocabulary (request / notify), alternate-pick for multi-seat lanes, and seat-online / seat-offline notices that wake the sibling seats and triage #27077

The maintainer's words (verbatim, in order)

Business reason

Reader who acts

What lands (one PR)

Premises (each with its re-check)

Relation to queued cards

Acceptance

Triage: p1 · `domain:skills` · `area:devpath` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-28T04:56Z

Scope amendment (maintainer-directed): item F, workflows ring the doorbell · 2026-10-28T06:37Z

Landing stroke refused by the session's permission classifier — the seat stops here

Landing stroke sent on the maintainer's word — PR #27143 ready, auto-merge armed, enqueued

Landed — PR #27143 merged; card closed by `Fixes #27077`

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

pm-dispatch(mailbox): one mailbox PR per seat, a closed doorbell vocabulary (request / notify), alternate-pick for multi-seat lanes, and seat-online / seat-offline notices that wake the sibling seats and triage #27077

Description

The maintainer's words (verbatim, in order)

Business reason

Reader who acts

What lands (one PR)

Premises (each with its re-check)

Relation to queued cards

Acceptance

Activity

objectstack-fleet commented on Oct 28, 2026

Triage: p1 · domain:skills · area:devpath · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-28T04:56Z

objectstack-fleet commented on Oct 28, 2026

objectstack-fleet commented on Oct 28, 2026

Scope amendment (maintainer-directed): item F, workflows ring the doorbell · 2026-10-28T06:37Z

objectstack-fleet commented on Oct 28, 2026

objectstack-fleet commented on Oct 28, 2026

objectstack-fleet commented on Oct 28, 2026

Landing stroke refused by the session's permission classifier — the seat stops here

objectstack-fleet commented on Oct 28, 2026

Landing stroke sent on the maintainer's word — PR #27143 ready, auto-merge armed, enqueued

objectstack-fleet commented on Oct 28, 2026

Landed — PR #27143 merged; card closed by Fixes #27077

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Triage: p1 · `domain:skills` · `area:devpath` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-28T04:56Z

Landed — PR #27143 merged; card closed by `Fixes #27077`