docs(pm-skill): clause-② CONTENT limb reaches published skills/** — ruled applicability, narrowed criterion - #13746
Merged
Conversation
Records the 2026-08-31 adjudication (第 6 场总监席决裁批 #12, maintainer verbatim 「同意」) in the ruled single source for the review chain: a change to published `skills/**` that makes a FALSIFIABLE operator/contract semantic claim falls under clause ②'s CONTENT limb and goes through the review chain. The criterion is narrowed on purpose — 「可证伪的语义主张」, not 「提到契约」. Pure operator lists, spelling and formatting changes do not trigger it; the yardstick is the measured 10-hits/3-claims split. The line ceiling for the file moves 48 -> 51 by the same ruling; the CEILINGS comment carries the measurement showing the three lines could not be paid in place without re-wrap funding, which is refused. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EnE7G31tqbxN1rqpQmzurT
This was referenced Aug 31, 2026
os-zhuang
approved these changes
Aug 31, 2026
os-zhuang
marked this pull request as ready for review
August 31, 2026 12:35
os-zhuang
enabled auto-merge
August 31, 2026 12:36
This was referenced Aug 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #13588 — half A of the two ruled halves. Half C is reported separately; this PR does not carry it.
⛔ Draft on purpose, and it stays draft.
.claude/**is a governed surface: human merge only. Never flip to ready, never enqueue.What the adjudication says
Maintainer, 2026-08-31, 第 6 场总监席决裁批 #12, verbatim 「同意」. Quoted rather than paraphrased, because the exceptions are the load-bearing half:
The change
One bullet, three lines, at the head of
载体纪律(挂与清)in.claude/skills/pm-dispatch/references/contract-review.md— the ruled single source. It carries all four load-bearing parts of the ruling: the scope (publishedskills/**), the narrowed criterion (可证伪的算子/契约语义主张), the explicit ⛔ negative (not 「提到契约」; operator lists, spelling and formatting do not trigger), and the 10-hits/3-claims yardstick. Provenance is dated in the text.Attach timing is deliberately not restated: the adjacent bullet directly below is the 2026-08-28 不预挂 ruling, which already governs it. One rule, one home.
Why the ceiling moves 48 → 51, and what was tried first
check-skill-line-ratchet.mjsholds this file at 48 lines, headroom 0. Its own discipline: "RAISING one requires a maintainer ruling quoted in the raising PR's body… A protocol change that would cross a ceiling pays its way by moving narrative out (SKILL.md → references/) or compressing in place, instead of raising the roof." The ruling above is that evidence, and here is why neither in-place route was available:dispatch-runbook.mdentry in the same map.state-machine.mdprecedent in the same map (43 → 44, same shape: one ruled addition, no payment available, landed count, headroom 0).The raise lands at the landed count with headroom 0 again, same convention as every neighbouring entry, and the CEILINGS comment carries the measurement so it is checkable without re-deriving it.
Measured, not assumed
wrapLinedid the wrapping). Gate verdict lines, quoted from the gate:✓ check-skill-line-ratchet: .claude/skills/pm-dispatch/references/contract-review.md is 51 lines (ceiling 51; headroom 0).✓ check-skill-line-ratchet: .claude/skills/pm-dispatch/references/contract-review.md: widest table row is 0 bytes (pin 0; headroom 0).skills/**file is touched, so the published-bundle line/token readings do not apply to this diff. The edited skill root is.claude/skills/**, priced in LINES by the ratchet above — which is exactly the reading reported here.Gates
Derived from the REAL diff with
node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstackin a fresh worktree (not from a hand-written path list), and run at the final commitb812c180. 20 commands, exit code captured before any pipe:check:pm-skill-ratchet,check:pm-skill-id-lint,check:skill-frame-sync,check:doc-authoring,check:agent-test-spelling,check:pm-governed-merges,check:pm-dispatch-gates,check:parse-guard,check:entry-guard,check:watch-hint-literal,check:pnpm-filter-targets,check:cli-command-ids,check:bash32-floor,check:cross-package-test-inputs,check:doc-formula-expressions,check-ci-filter-parity,check-cross-package-test-inputs,check-shard-attestation,bare-root-worklist --self-test.node scripts/check-test-completeness.mjsexits 3 withPREREQUISITE NOT MET— it grades a savedturbo run testlog that only CI produces. Its own output states this is "not a red, and there is nothing here to fix". Recorded as NOT MEASURED, not as green and not as red.pnpm check:nul-bytesgreen separately (standing rule for any edit):check-nul-bytes: OK (scanned 7572 text file(s) … no raw ASCII control bytes).check-skill-line-ratchet --self-testpasses (it is the script's test suite — there is no separate*.test.tsfor it). The three other gates in the tree that read this script by name were then enumerated bygit grepand run directly, since the path derivation names only one of them:check:pm-dispatch-gatesexit 0,node scripts/check-published-list-mirrors.mjsexit 0,node scripts/check-skills-token-ratchet.mjsexit 0 (✓ 38 authored bundle file(s) within their ceilings).Changeset
None, deliberately. The diff is
.claude/**+scripts/pm/**only — nothing publishes from any package — so it is on the closedskip-changesetlist, and that label is applied in the same stroke as this PR rather than after a red Check Changeset.One thing this PR does NOT close, reported rather than fixed
The two-limb (双肢) definition itself lives in
pm-dispatch/SKILL.md, which is out of scope for this card (fable-mandated face under its own line ratchet), and its clause-② gate paragraph routes readers here only for 载体纪律、资格与归属、降档保险丝 — applicability is not among the three topics it names. The criterion is reachable in practice, because the operative half of the ruling is an attach rule and 载体纪律 is exactly where an attaching seat lands. But a reader who consults only SKILL.md's 双肢 paragraph will not see theskills/**face named. Closing that gap needs a SKILL.md edit; flagged here for the PM to route, not taken.Generated by Claude Code