feat(source-control): pr_body_required_sections accepts none (no required sections)

[kyle-sexton]

Closes #1138

Summary

pr_body_required_sections now accepts the literal keyword none — "this repo requires no PR-body sections" as a stated convention, previously unstatable (absence yields the portable default, the opposite of what a deliberately empty-body repo wants). Parallel to the sibling keys trailer_policy and pr_body_attribution: a resolved none means /pull-request create drafts no section scaffold and the §2.4.2.2 pre-create gate requires nothing. The §2.4.2.1 closing-keyword check is independent and unchanged; ad hoc ## Related content from real refs is still never dropped. none participates in per-key layering as a resolved value, not an absence — a layer declaring it overrides a lower layer's list wholesale, while a key unset in every layer still falls through to the portable default (Summary, Test plan).

Surfaces updated: reference/config-resolution.md (value grammar + layering semantics), docs/conventions/pr-body-convention/README.md (owner doc — new "none: no required sections" section with the consumer-evidence rationale), pull-request/reference/create.md (§2.4.1 resolve step, template build, §2.4.2.2 vacuous pass), setup/SKILL.md (check-report rendering none (no required sections), interview offer, config template). source-control 0.19.0 → 0.20.0 + CHANGELOG.

Test plan

• jq -e validates both edited evals.json files and plugin.json.
• Both eval files conform to the skill-quality evals.schema.json (required id+prompt, kebab-case name, no extra fields).
• New model-graded evals cover the resolution contract: pull-request eval 19 (team-layer none → empty scaffold, gate passes vacuously, closing-keyword check still enforced; fixture source-control-required-none.md), eval 20 (none wins the per-key override across all three layers; absence vs none distinguished), setup eval 16 (check report renders resolved none distinctly from unset).
• typos clean over the touched trees.

Related

• Sibling none precedents: trailer_policy, pr_body_attribution (config-resolution.md).
• Issue chain: source-control: pr_body_required_sections accepts 'none' (no required sections) #1138 → source-control: setup inference reads a configurable year-scale consensus window, not git log -50 #1139 → source-control: setup SKILL.md skill-quality gate pass (lint per repo config, Gotchas surface) #1140 → source-control: neutral tool-agnostic convention SSOT — author-directed reopen of #913 #1141 (source-control convention SSOT series).

🤖 Generated with Claude Code

[claude]

Claude encountered an error after 1s —— View job

---

I'll analyze this and get back to you.

[claude]

Claude encountered an error after 0s —— View job

---

I'll analyze this and get back to you.

[github-actions]

Warning

Automated review did not complete — this is an infrastructure failure, not a review verdict.

Treat any Claude comment on this PR (including a placeholder like "I'll analyze this and get back to you") as incomplete, not "no findings."

• Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/30003717683
• Last SDK result: {"subtype":"success","is_error":true,"num_turns":1,"duration_ms":516,"total_cost_usd":0}

Re-running the job, or pushing a new commit, will retry the review.

[github-actions]

Warning

Automated security review did not complete — this is an infrastructure failure, not a review verdict.

Treat any Claude comment on this PR (including a placeholder like "I'll analyze this and get back to you") as incomplete, not "no findings."

• Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/30003717561
• Last SDK result: {"subtype":"success","is_error":true,"num_turns":1,"duration_ms":327,"total_cost_usd":0}

Re-running the job, or pushing a new commit, will retry the review.

[kyle-sexton]

Pre-merge CI classification

• 25/25 checks green (hygiene, plugin-gate, changelog-parity-gate, skill-quality-gate, pr-issue-linkage, pr-title, portability-lint, silent-skip-gate, orphaned-fixture-gate, sync gates, zizmor, GitGuardian, security-review/changes all pass).
• claude-review / claude-security-review hit the known instant infra failure (ci: claude-review + claude-security-review workflows infra-fail instantly (0-1s, cost 0) on every attempt #1122, claude-code-action internal error, 0–1s, rerun-proof) — fail-open by workflow design with warning comments; not a review verdict.
• Codex review window observed post-green (7-min cooldown + comment/thread sweep): no findings, no review threads.

Merging per the drive-to-merged directive on record for this issue chain (#1138 → #1141).