Agent working orders: one issue keeps one branch and one PR

[erikdarlingdata]

Why

An issue that is too big for one agent was getting several branches and several PRs. That splits the history, the PR summary and the CHANGELOG entry across pieces of one issue. The rule is now one issue, one branch, one PR, even when several agents build it.

What changes

Docs only. One file, .claude/skills/lane-orders/SKILL.md:

• The opening paragraph says a big issue still gets one branch and one PR.
• "Worktree and branch" gets a bullet for shared issue branches. The dispatching session creates the branch from origin/dev and names it. Each agent works on its own part branch, then fetches, merges the issue branch, reruns its targeted tests and pushes to the issue branch. A rejected push means fetch, merge and push again. No force-push.
• The PR section says to open the PR only if none exists for the issue branch. Otherwise, add your part to its body under ## <your part>. One agent writes the top summary and the single CHANGELOG entry. Agents that fix findings push to the PR's own branch.
• The PR body rule now runs the plain-English checker once, fixes the real hits in one pass and publishes. It replaces the 2026-09-25 rule against running it.
• The dispatch checklist says to create the issue branch before sending out several agents, and to name it in every task. A separate PR is only for a part that must ship first. A PR built in waves gets one check per wave on that wave's commits, plus one final check on the whole PR.

Test plan

• git diff --stat shows one file changed.
• Each new sentence is present in the file (searched for one phrase from each edit).
• No code, build or tests apply to this change.