Bound parallel shards to one verifier pass (policy-rev 5, v3.1.1)

[ovhirup]

What

Fixes a conflict in the 3.1.0 policy block, found by the Codex review of #3 (P2 at SKILL.md:96).

The Harness rule sizes each delegation to what verifier and the reviewer can check in one pass, but the Graph rule still fanned every parallel shard into a single verifier pass. Each shard could fit one pass while the combined diff needed several.

One line changes in the block:

• Before: Before launching, state the shard count and why that many.
• After: Launch only as many shards as that pass and the reviewer can check; state the count and why.

The block stays 77 lines. No numeric cap. Leftover work runs as sequential gated batches, as the Harness rule already required.

Why not gate each shard separately: parallel shards share one working tree, so a verifier run on one shard would test a tree still holding the other shards' unfinished edits. One pass over the combined result also catches breaks between shards.

Also in this PR

• policy-rev 4 to 5, version 3.1.1, CI now asserts policy-rev: 5.
• Evals 1, 2 and 7 updated; README no longer pins a rev number.
• CHANGELOG 3.1.1 entry. The 3.1.0 entry is unchanged.
• Ports unchanged at rev 2: neither fans parallel work into one verification pass.

Verification

• All 8 validate.yml steps pass locally.
• Content checks (rev/version agreement, old line gone, new line present, block length, no rebound vocabulary in blocks) all match expected.
• Advisor reviewed the full diff: APPROVE.

Before merging

Read all reviews and comments, and wait for the Codex review on this head commit.

🤖 Generated with Claude Code