@@ -65,7 +65,7 @@ model: opus
    - 就地修欠两样:认领申报的文件面同轮增补;PR 正文点名该修复并附证据。
    - 优先扩展一个守卫关掉整个类;任一条不成立 ⇒ 回默认:无 assignee 立单、列出、不碰。
    - 本轮改动令其变假或触碰的已发布缺陷必修;其余立卡并记明已发布面,PR 照常落地。
-4. ⛔ 永不编辑 `content/docs/releases/`、force-push、推 `main`、合并任何东西。
+4. ⛔ 永不编辑 `content/docs/releases/`、推 `main`、合并任何东西;force-push 只按 AGENTS.md §3。
    - 用户可见的改动需要 `.changeset/*.md`。
 5. **Contract-first。** 修复若诱使你在消费端加宽容回退(`??` 别名、宽松解析),缺陷在上游。
    - 去生产者或 spec 修,或返回 `needs_decision`。
 
@@ -119,7 +119,7 @@
 - 二、派发词必带自驱条款:云会话回合一结束即停摆等 poke。
 - ⛔ 不为提问或中期汇报结束回合;开放选择按裁决与评估轴自裁,记入终报 `open_questions`。
 - 合法回合终点只有两个:推送完成加终报,或硬阻塞详报。
-- 三、交付通道:dev 自开 draft PR(`Fixes #<n>`,正文含验证记录)。
+- 三、交付通道:dev 自开 draft PR(`Fixes #<n>` 只写正文,`partof-closing-keyword` RULE 2,含验证记录)。
 - 终报以 issue 评论交付,带 `os-dev-report` 标记。
 - 未 attach 的姊妹仓够不着,跨仓跟进卡由 PM 代立。
 - trigger 定时会话维持降级通道:推送 outcome branch,终报走最后一条会话消息,PM 代开 draft PR。
 
@@ -467,8 +467,14 @@ Even inside your own worktree, operate defensively:
    pays a rebuild lap per landing; and a breaking changeset's ADR-0087 disposition is base-relative, so a stacked card's
    two bases demand contradictory markers. A multi-card change uses a **trunk branch**: correct the trunk's disposition
    to `registered` before it merges, and pay the rebase laps. ⛔ No gate or merge-policy change is made for it.
-3. **Never `git push --force` / `--force-with-lease`, and never push `main`.** A
-   force-push can clobber a parallel agent's work; `main` is shared — land all via PR.
+3. **Never force-push a *shared* branch, and never push `main`.** A force-push can
+   clobber a parallel agent's work; `main` is shared — land all via PR. A branch is
+   unshared, and `--force-with-lease` allowed, only while ALL FIVE hold: ① it is named
+   `claude/issue-*`; ② this worktree created it; ③ nobody else has ever pushed it (the
+   author and committer sets of `git log origin/<branch>` are you alone); ④ no open PR
+   on it carries a reviewer or an approval (one does ⇒ a new branch and a fresh PR
+   instead); ⑤ the push spells `--force-with-lease=<branch>:<sha you last pushed>` —
+   ⛔ never bare `--force`. One criterion failing ⇒ the branch is shared.
 4. **Verify the current branch before every commit/push**
    (`git rev-parse --abbrev-ref HEAD`). HEAD may have been switched by another agent —
    if it isn't your feature branch, stop and re-checkout before pushing.
 
@@ -1052,7 +1052,21 @@ export const CEILINGS = new Map([
   // bullet is already typeset at the surrounding block's 90-byte prose width, and
   // AGENTS.md is not a CROSS_FILE_MOVES destination, so no `ruledRaises` record
   // applies. Landed count, headroom 0, same convention.
-  ['AGENTS.md', 1068],
+  //
+  // 1068 → 1074 (card #16851): Multi-agent discipline §3 narrowed from an
+  // unconditional force-push ban to "never force-push a SHARED branch", plus the
+  // five criteria that make a branch provably unshared before `--force-with-lease`
+  // is allowed — the ban's own rationale (a parallel agent's work) was already
+  // scoped that way, and check-partof-closing-keyword RULE 2 can only be satisfied
+  // by rewriting a commit message, so the unconditional wording had already been
+  // broken once in practice. +6 lines, exactly the ruled budget: two lines cannot
+  // carry five criteria, and the item measures 0 lossless rewrap headroom at the
+  // list's ~90-byte prose width. Maintainer ruling, verbatim and untranslated:
+  // 「其他同意」 (decision batch #111 item 4, 2026-09-10, on analysis 5615846806
+  // option A; recorded by the director on #16851 comment 5617189215, which also
+  // rules the net budget of 6). AGENTS.md is not a CROSS_FILE_MOVES destination,
+  // so no `ruledRaises` record applies. Landed count, headroom 0, same convention.
+  ['AGENTS.md', 1074],
   // #9965: root CLAUDE.md is the other repo-root instruction file — same read
   // path (every seat session), same governance (Prime Directive #14). It is
   // structurally growth-prone in the way the ratchet is built for: it exists to