spec: 010 Task 11.2 — the trailing newline on the last 14 files

[iancooper]

Spec 010, Phase 11, Task 11.2 (P2-1). Whitespace only. 14 published pages gain one byte each; nothing a reader can see changes and no URL moves.

Deferred from spec 011 so the banner diff contained nothing but banners, and landed here for the same reason in reverse: a whitespace-only sweep is safe once no content PR is in flight.

14, not the 17 the task recorded

Re-derived twice — once when the phase opened, and again at the head this cut from, because the phase's own five PRs had edited 17 pages in between. Both returned 14: those edits were to link targets and headings, and none of them is a file's last line.

(Re-measuring at the ref you are cutting from is Phase 8's lesson — a figure right when written and wrong when used. Here it held, which is the cheap outcome of a cheap check.)

The diff is provably nothing but newlines

• Each file grew by exactly one byte, asserted as after == before + b"\n" before the next file was touched.
• git diff -U0 re-adds all 14 removed lines verbatim — 14 removed, 14 added, compared as lists and equal.

A whitespace sweep is the one change nobody reads closely, which is the argument for asserting it rather than reviewing it.

No line count in the spec moves

A page's length is len(text.splitlines()), which a trailing newline does not change — asserted per file during the sweep. Under wc -l all 14 would have gained a line, which is exactly the instrument design §16 finding 1 ruled against.

Gates

linkcheck 144 files, clean; pagelint 0 errors / 791 warnings / 143 pages; --check-shape 0; --check-redirects 0 at 77 entries.

🤖 Generated with Claude Code