pm-dispatch: the wave-checkpoint rule gates the next wave on a maintainer-executed /compact — over-broad for remote sessions; keep the flush, drop the human gate

[yinlianghui]

Filed and claimed by the repo:objectui seat (session session_01RnQd8iMMUwXQEV1crFmQiQ, 2026-08-15) under the maintainer direct-command channel — the maintainer challenged this rule in the live PM session. Verbatim provenance (untranslated, 2026-08-14/15, this session):

「继续，加快进度，最多并发5个子任务」
「哪里来的波次纪律？为什么要等我执行压缩，你乱说的吧？」
「你说你承认"在本环境里执行得过于机械"，以后还会遇到这种问题等我而中断？」

The defect

.claude/skills/pm-dispatch/SKILL.md, section 轮次报告与节奏, sub-section 波次收工点(维护者 2026-08-09 裁定) prescribes: ① 收工点 = 在飞归零 → ② 存档 flush → ③ /compact 由维护者执行 → ④ 压缩后再派下一波,⛔ 不抢派.

Steps ③④ were written for terminal PM sessions, where /compact is human-only and a mid-review auto-compaction can lose in-context judgments. Applied literally in a remote session (auto-summarized, often unattended), they convert a safety checkpoint into an idle stop waiting for a human who is not watching — measured in this seat's session: the seat halted at in-flight-zero on 2026-08-14 until the maintainer asked why it had stopped, twice.

The amendment (direction, for the drafting dev)

• Keep ① and ② unchanged — the in-flight-zero checkpoint and the flush-judgments-to-GitHub obligation are correct everywhere (they are what makes ANY compaction, manual or automatic, lossless).
• Replace ③④: after the flush, the seat proceeds to the next wave immediately. A maintainer-executed /compact at a flush point remains a terminal-session optimization the maintainer may perform, never a dispatch precondition. ⛔ Waiting for it is removed.
• Preserve the existing provenance format: the 2026-08-09 ruling stays cited as superseded-in-part by the 2026-08-14/15 ruling quoted above.

Constraints (binding, from the skill's own guardrails)

• The skill's line-count ratchet (check:pm-skill-ratchet) only goes down — the rewrite must be net non-increasing.
• No issue numbers in operational text (check:pm-skill-id-lint).
• Any card touching .claude/skills/pm-dispatch/** runs on claude-fable-5 (mandatory tiering clause).
• Skills changes are ADR-class: the PR is drafted and pushed by the dev, reviewed by this seat on the card, and left hanging for the maintainer's manual merge — the AI never merges/queues it. That merge is the maintainer's veto window on this very amendment.

[yinlianghui]

Claim: PM loop round 5 (maintainer direct-command channel; provenance quoted in the body)
Session: session_01RnQd8iMMUwXQEV1crFmQiQ
Branch: claude/issue-8830-wave-checkpoint
Worktree: objectstack-issue-8830
Domain: cross-lane exception — .claude/skills/pm-dispatch/** (skills-adjacent; drafted here under the direct command, merge stays human)
File surface: .claude/skills/pm-dispatch/SKILL.md (轮次报告与节奏 section only) (stop on breach; explain in the report)
Container & model: S, mode:subagent, model: fable (mandatory clause for this path)
Serial constraints cleared: no in-flight claim or open PR touches the pm-dispatch skill (checked this round); the four objectui devs in flight are all in the sibling repo.

---

Generated by Claude Code

[yinlianghui]

{
 "issue": 8830,
 "status": "blocked",
 "branch": "claude/issue-8830-wave-checkpoint",
 "pr": null,
 "premise_still_valid": true,
 "summary": "Implementation complete and gate-verified locally; blocked at publish only. The 波次收工点 sub-section of 轮次报告与节奏 was rewritten per the ruling: steps ①② kept (in-flight-zero checkpoint + flush-judgments-to-GitHub), the human gate ③④ removed — after the flush the seat proceeds to the next wave immediately, and a maintainer-executed /compact is demoted to a terminal-session optimization, never a dispatch precondition; the 2026-08-09 ruling is cited as superseded-in-part by the 2026-08-14/15 in-session challenge with verbatim fragment 「为什么要等我执行压缩」. Surgical 5-lines-in/5-lines-out diff, file stays 686 lines, surrounding content byte-identical. BLOCKER: no git-write route from this container. git push fails with exactly: fatal: unable to access 'https://github.com/objectstack-ai/objectstack/': The requested URL returned error: 403 — 8 attempts over ~2h including the PM-directed sequence (retry, then add_repo access:push which returns status already_present without minting git credentials, then 4s/8s/16s backoff). No credential path exists: no credential helper configured, GIT_ASKPASS empty, GH_TOKEN is the proxy placeholder (honored for API Bearer — get_me authenticates — but not for git auth), and the GitHub MCP integration is denied repo writes: create_branch and create_or_update_file both return 403 Resource not accessible by integration (issues-write works — this comment). Auth-layer failure, independent of the change. The commit is durable in the shared object store; the worktree /home/user/objectstack-issue-8830 is left in place (unmerged work, cleanup deferred).",
 "tests": "All at head 5077524ab82517df6ae28c1bb7eba4e94ddb9cbc (git rev-parse from the union run; working tree clean; full union re-run after the final commit): check:pm-skill-ratchet green — 'SKILL.md is 686 lines (ceiling 686; headroom 0)' (self-test 11 cases pass); check:pm-skill-id-lint green — '9 file(s) clean' (self-test 10 pass); check:skill-frame-sync green — '4 copies of the decision frame are structurally isomorphic across 3 files'; check:skill-frame-freshness green — 'the decision frame in this tree is current with origin/main (fetched just now)'; check:nul-bytes green — 'OK (scanned 5842 text file(s) ... no raw ASCII control bytes)', plus a manual control-byte grep of the edited file (clean). Re-derivation via scripts/pm/dispatch-gates.mjs over the changed path added two families beyond the prompt, both run green: check:doc-authoring — '377 files clean — no bare metadata literals'; @objectstack/lint check:doc-formula-expressions — '22 record-scoped formula example(s) across 396 files / 1411 TS blocks judged clean' (self-test 24 pass; required pnpm install and building the lint dependency closure under the shared verify lock). Changeset: none added — .claude/-only change releases nothing; the skip-changeset label is the PR-time step, pending PR creation (the gate's own exemption text: skip-changeset 'declares no release of its own and the changeset check is exempt').",
 "open_questions": [
 {
 "question": "How should the verified commit be published, given this container has no git-write route (anonymous git push 403; MCP integration denied contents/refs write)?",
 "options": [
 "A: an actor with push credentials (PM seat or maintainer) publishes the durable commit from the shared object store: git -C /home/user/objectstack push origin 5077524ab82517df6ae28c1bb7eba4e94ddb9cbc:refs/heads/claude/issue-8830-wave-checkpoint — then opens the draft PR (required body content is in the appendix under this report)",
 "B: escalate this container's credential scope (git push credentials or GitHub App contents:write), then re-wake this session or a fresh dev to push and open the draft PR per the card"
 ],
 "recommendation": "A, because the work is complete and union-verified at the named head — publishing needs only credentials, not a re-run; B only if no reachable actor holds push scope"
 }
 ],
 "out_of_scope_findings": []
}

---

Appendix: the amended sub-section (for review and the maintainer's veto from the card, while the PR cannot yet be opened)

.claude/skills/pm-dispatch/SKILL.md, section 轮次报告与节奏, lines 527-531. Before (origin/main):

**波次收工点(维护者 2026-08-09 裁定)。** 班内节奏:一波处理完 → 收工存档 → `/compact` → 再继续,
⛔ 不跑到被自动压缩。四步有序:① 收工点 = 会话内在飞归零(⛔ 不在复核中途压缩;云卡不挡 —— 热移
交见座位贴协议细则);② 收工存档 = 上下文里的判断 flush 到 GitHub(不过夜义务);③ `/compact` 由维
护者执行;④ 压缩后再派下一波,⛔ 不抢派。同席压缩保全会话绑定(订阅、定时器、座位贴会话 ID),换人
轮换降为班末动作;Routine 座位不适用。前提是 GitHub 恒为唯一权威 —— 失守时压缩即丢判断。

After (commit 5077524ab82517df6ae28c1bb7eba4e94ddb9cbc):

**波次收工点(维护者 2026-08-09 裁定;人闸部分 2026-08-14/15 被同席质疑「为什么要等我执行压缩
」后取代)。** ① 收工点 = 会话内在飞归零(⛔ 不在复核中途压缩;云卡不挡 —— 热移交见座位贴协议
细则);② 收工存档 = 上下文里的判断 flush 到 GitHub(不过夜义务),随后**立即派下一波**,
⛔ 不等人闸。`/compact` 仍由维护者在终端会话择机执行 —— 收工点上的优化项,永远不是派发前提;
①② 令任何压缩(手动或自动)无损,前提是 GitHub 恒为唯一权威 —— 失守时压缩即丢判断。

Dropped alongside ③④ (named here so the veto can weigh it): the same-seat-compaction mechanics sentence (同席压缩保全会话绑定…换人轮换降为班末动作;Routine 座位不适用) — it existed to support the removed gate's rhythm; with /compact demoted to an optional terminal-session optimization it prescribes nothing.

When the branch is published, the draft PR must state: first line Fixes #8830; merged by the maintainer personally (skills changes are ADR-class — no AI merges or queues it); skip-changeset label applies (.claude/-only, releases nothing); title and prose in English.

---

Generated by Claude Code

---

Generated by Claude Code

[yinlianghui]

PM review + blocker escalation (session session_01RnQd8iMMUwFQ… — correction: session_01RnQd8iMMUwXQEV1crFmQiQ`).

Content verdict: ACCEPT. I read the commit's actual diff (not the report): 5077524ab82517df6ae28c1bb7eba4e94ddb9cbc, 5 lines in / 5 out, only the 波次收工点 block touched. It implements the ruling exactly — steps ①② kept, the human /compact gate removed ("随后立即派下一波,⛔ 不等人闸"), /compact demoted to a terminal-session optimization that is never a dispatch precondition, provenance in house style (dates + verbatim fragment, no issue IDs in operational text). The full gate family is green at that head per the dev report above (ratchet 686/686 headroom 0, id-lint, frame-sync, frame-freshness, nul-bytes, doc-authoring, formula-expressions).

Blocked at publish, escalating to the maintainer. This container has no git-write route to this repo: anonymous git push returns 403 (8 attempts over ~2h, including add_repo access:push, which reports already_present without minting git credentials), and the GitHub MCP integration is denied contents/refs writes (create_branch / create_or_update_file → 403 "Resource not accessible by integration"). The PM session hit the identical 403 on an earlier push to this repo, so this is container-level, not dev-specific.

Maintainer action needed (one line, then one click): from any checkout with push credentials that has fetched the shared object store — or directly on the dev container host:

git -C /home/user/objectstack push origin 5077524ab82517df6ae28c1bb7eba4e94ddb9cbc:refs/heads/claude/issue-8830-wave-checkpoint

then open the draft PR from that branch (required body content is in the appendix of the dev report comment above). Per the skills-lane rule the PR itself is also human-merge only, so nothing downstream of this push is automatable from our side anyway.

Worktree /home/user/objectstack-issue-8830 stays in place; card label moved to pm:blocked until the branch is published.

---

Generated by Claude Code

[yinlianghui]

Claim released + lane re-route (maintainer correction, 2026-08-15). Session session_01RnQd8iMMUwXQEV1crFmQiQ (objectui whole-repo PM seat) is releasing this card back to the objectstack lane's own queue.

Why: this card was cross-lane dispatched from the objectui seat because the ruling it implements originated in that seat's chat — that routing was wrong per lane ownership, and it hit a hard wall: the dispatching container has no git-write route to this repo, leaving a finished, gate-verified commit unpublishable. The previous escalation asking the maintainer to push the branch by hand is withdrawn — the correct fix is this re-route, not a manual push.

For whoever picks this up (everything needed is already on this card):

• The dev report comment above carries the exact before/after text of the 5-lines-in/5-lines-out edit to .claude/skills/pm-dispatch/SKILL.md's 波次收工点 block, the full green gate readings (ratchet 686/686 headroom 0, id-lint, frame-sync, frame-freshness, nul-bytes, doc-authoring, formula-expressions), and the ready PR-body requirements in its appendix. Reproducing the edit in a normal objectstack worktree is minutes of work; treat the quoted diff as the spec and re-run the gate family at your own head.
• ⛔ Constraints that travel with the card: pm-dispatch skill edits are fable-model-mandatory for the implementing dev, and the resulting PR is human-merge only (skills lane) — draft it, never auto-merge or queue it.
• The objectui-seat container's local branch (claude/issue-8830-wave-checkpoint, commit 5077524ab82517df6ae28c1bb7eba4e94ddb9cbc) remains as reference only — it is not reachable from other containers and is not the deliverable path.

Label moved pm:blocked → pm:queue; assignee cleared.

---

Generated by Claude Code