docs(changeset): say migrate meta prints the entry by default

Its default range runs to the chain terminus, protocol 18, so the
entry reaches authors through migrate meta now; only the upgrade guide
and spec-changes.json wait for the protocol major.

Claude-Session: https://claude.ai/code/session_01Sfe5YjBLwB9J3y8fvm2xq1
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.changeset/20592-ui-html-page-div-refused.md

@@ -17,8 +17,8 @@ the layout containers to reach for instead only when their layout is wanted, and
 says how to prove the rewrite done.
 
 What moves for a consumer of this package: `MIGRATIONS_BY_MAJOR` carries the
-entry, and `objectstack migrate meta` prints it for a range that reaches
-protocol 18. Nothing else does. The protocol-18 step is not cut yet, so
-`spec-changes.json` and the protocol upgrade guide, which project the steps up
-to the current protocol major, are unchanged, and no schema accepts or refuses
-anything it did not before.
+entry, and `objectstack migrate meta` prints it, because its default range
+already runs to protocol 18, the highest major with a step. Nothing else does.
+The protocol-18 step is not cut yet, so `spec-changes.json` and the protocol
+upgrade guide, which project the steps up to the current protocol major, are
+unchanged, and no schema accepts or refuses anything it did not before.