Say that this break falls between preview.1 and preview.2

preview.1 is published, and it has the conversion. Every other entry in the file
describes a change from 1.3.0 or 1.4.0, so the file's implicit frame is
release-to-release and a reader already on preview.1 would not learn from it that
this one lands on them. Checked: #848 is the only other commit to touch the file
since the preview.1 tag, and what it added is a 1.4.0 section, not a preview delta.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: Rafael-SOWNet

BREAKING-CHANGES.md

@@ -127,6 +127,11 @@ fine — only a concrete `List<Entity>` broke, which is why it survived to a 2.0
 This was not three separate defects. One conversion made *every* `params Entity[]` overload in
 the library uncallable with a list, including any added later.
 
+**This one moves between previews.** The conversion is present in `2.0.0-preview.1`, which is
+published, and gone from `2.0.0-preview.2`. It is so far the only entry here that changes
+between two previews rather than between releases: a reader coming from 1.3.0 or 1.4.0 can
+ignore the distinction, one already on preview.1 cannot.
+
 **What breaks.** Assigning a list where an `Entity` is expected:
 
 ```csharp