[mgratzer]

forge-batch was invoked 8 times against 263 forge-ship runs in six weeks of sessions, and --start once for real work, so this removes it: several Issues are now several forge-ship --guard sessions, started by a person or a coordinating session.

Notes

• Removes about 2,050 words of skill prose (21,789 to 19,742) and 377 lines from the lens, its tests and the contract check.
• Gone with it: Waves, touch sets, launch lines, FORGE_LAUNCHER, the start comments on Issues, and the merge-order test-merge. Nothing replaces them.
• Kept: forge-implement's open-work check (prerequisites, overlapping PRs) and the Serialized resources setting it reads. Only their batch wording changed.
• issue-operations.md still has List Issues by Scope, which no skill lists by any more; open-work's prerequisite rule points at its deps filter, so trimming it is a separate change.

Exercised

• Not exercised: the remaining skills change only in pointer lines (a Related Skills line in forge-ship, a list entry in setup-project's reference) and in two shared-module phrases that named batch ("the Plan or touch set names" is now "the Plan names"; the Serialized resources row lost its Wave case). No rule a remaining skill executes changed, so I did not spend a sandbox pair on it.
• scripts/check-skills.sh → no output, exit 0
• claude plugin test . → 14 pass, 0 fail (was 17; three tests covered batch)
• Try it: claude --plugin-dir ., then /forge map: the pipeline shows nine skills and no Waves pane