Skip to content

pm-dispatch: batch default back to 3 on the maintainer's ruling 「并发2 还是太慢了,默认恢复3吧」 — SKILL.md :60 + the core-rules mirror (ceiling 5 unchanged) #18125

Description

@claude

Filed by the skills seat (session session_01DAcomhvR9kKizeYgg89Vo8) on the maintainer's ruling in this seat's chat at 2026-09-14T03:4xZ, verbatim, ⛔ not translated: 「并发2 还是太慢了,默认恢复3吧」. Routed and graded through the maintainer's direct-dispatch channel (the audit quote above); p1 by that word. Rules layer (SKILL.md 〈入口与角色〉 batch row + the core-rules mirror) ⇒ fable by dispatch-gates --tier, four-piece, an authorized approval, then the claiming seat lands (ruling C).

Dedupe keywords: batch 默认, 并发, LOCK_DEPTH_HOLD, lock 3, 后续并发降到2, 默认恢复3.

What

Lock 3 (PR #18072 7ef05f997) set SKILL.md's batch default from 3 to 2 and mirrored it in references/core-rules.md. The maintainer now rules the default back to 3; the maintainer ceiling 5 stays. Everything else about lock 3 stays (the write-identity locks 1, 2, 4, 5 are untouched; the verify-lock depth wait LOCK_DEPTH_HOLD and the same-file serial rule stay as they are — they are independent of the default).

Shape

Equal-line edits: SKILL.md 〈入口与角色〉 table row batch:<n> — 默认 3;n 的维护者天花板 5; the core-rules.md mirror line likewise (the two files change in the same PR, per 〈优先级〉 「一条规则在本文与核心条款一处改动,另一处同 PR 同改」). ⛔ No other line; ⛔ no ceiling moved (812/812, 151/151); frame block md5 unchanged; the Routine prompts of the seats are the seats' own to update on landing.

Cross-seat note

The domain:services seat runs at waterline 2 on the maintainer's 2026-09-13T14:5xZ word 「当前任务处理完,后续并发降到2」; this ruling supersedes the default. That seat updates its own Routine on the landed text — the skills seat knocks on #6021 at landing.


Generated by Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions