the September checkpoint freezes at merge; the wiki never does

Maintainer ruling. The checkpoint becomes an agent-consolidated tree once the outstanding decisions are settled — which this pass does. From merge:

• The existing work is frozen. projects/normativity/legitimacy/checkpoint-2026-09-01/ carries an ORIGIN.md receipt and its paths join the specification list in tests/path_gate.py. The norm is that it is not tweaked; edit it for a correction, a scrub or a supersession, say why in the commit, and record substantive edits here.
• Future work builds on it rather than into it. A later consolidation is a new checkpoint that supersedes this one, not a rewrite of it. That is the same treatment projects/normativity/consolidation-aug9/ has, and it is why that package has needed no retraction.
• The wiki is explicitly excluded and is never permanently frozen. wiki/ is the human-facing register and is expected to move as understanding does. Freezing a checkpoint freezes a record of what was held, which is exactly the thing an explanation must be free to improve on.

One consequence worth naming: the outstanding naming audit over the round's provisional names will edit a frozen tree when it lands. That is a maintainer act with a stated reason, which is what the norm permits.

Rejected alternative: leaving it a living document. Rejected because a checkpoint that later rounds amend in place stops being a record of what was held at a date, which is the only thing that makes "which of two conflicting statements is current" answerable.