skills: write the two 2026-08-26 rulings into the PM protocol text — md-content review fork for skills-lane PRs, and the 5-card decision-batch flow as the standing adjudication process

[os-steve]

Filed by the skills seat (session_01JANH3y7qe3MD8aLaLXci8N) recording two maintainer rulings from the 2026-08-26 live PM chat. Reader: the domain:skills execution seat — protocol-text work on the governed face (draft + human merge; clause-① tiering per the skill's own rules). Filed with pm:queue and no lane label — triage confirms routing (domain:skills expected: pm-dispatch SKILL.md is the landing surface).

Ruling 1 — the skills-lane PR review fork keys on .md CONTENT, not on path alone

Maintainer, 2026-08-26, verbatim:

skills 中的pr，只有包含md文件时需要推给我审核，其他代码文件你直接自己审核。

Executable criterion for the protocol text (the ACCEPT-path fork section):

• A skills-lane PR whose diff contains any .md file (SKILL.md, references, os-dev.md, AGENTS.md, CLAUDE.md, published skills/** markdown) → unchanged governed ending: draft, review-requested, human merge is the review record.
• A skills-lane PR whose diff is code only — scripts/pm/**, .claude/hooks/*.sh, .claude/workflows/*.js, .claude/settings*.json, skills/** non-md artifacts — → the skills seat self-reviews (fable-tier, checklist unchanged) and lands it directly (ready → queue), no maintainer review required.
• Scope boundary, stated so the text cannot overreach: this fork applies to the skills lane's own PRs. Other lanes' governed faces (docs/adr/** etc.) keep the standing regime unless the maintainer rules otherwise.

Ruling 2 — today's decision-batch flow becomes the standing adjudication process

Maintainer, 2026-08-26, verbatim:

决裁流程今天这样很好，决策卡5张一组，从业务的角度给我具体解释，说明可选项，并进行四维分析。应该写入技能。

Executable criteria (the 升级与决策 / decision-inbox section, likely with detail in references/decision-analysis.md):

• Decision cards are presented in batches of ≤5, priority-ordered (in-flight-blocked > operational blockers > user-visible > structural).
• Each card carries: a business-angle concrete explanation (what it means for the product/user, not the mechanism), the options with their real costs, the four-axis analysis, and one recommendation.
• One-line batch reply format (「1A 2B …」; 「X, 但…」 = attached conditions ride into execution); after the ruling, the four-piece atomic execution per card (provenance comment with verbatim quote + state transition + Blocked-by liveness + judge-what-is-known) runs without further prompts.
• New inbox arrivals during a batch roll into the next batch; the flow ends only when the inbox reads zero.

Fold note

Same file and same change form as #12227 (repo classes + governance split, already ruled and pm:queue): chain-head fold candidate for one SKILL.md dispatch once PR #12406 reaches MERGED and frees the file. Both cards are ruled; the five fold gates get answered at claim time. Ratchet applies — the compression candidates named on #12227 (five-repo enumeration, 代扫 exception text) plus the ACCEPT-fork paragraph this ruling amends.

[os-steve]

Family-dispatch member (PM loop round R1 W3): this card is folded into the chain headed by #12227. The claim, shared branch claude/issue-12227-skill-governance, worktree and file surface live on the chain head — read the claim there (it quotes this card's authorizing instruction verbatim) before touching this card. Session: session_01JANH3y7qe3MD8aLaLXci8N.

---

Generated by Claude Code