One changeset per thing a user of the library would notice

Five described work on the documentation and the repository - the interactive
examples, the recordings, the reference pages, the constructor pages, the parity
probe. None of them changes the jar, so none of them belongs in the release notes
of the jar. They are gone.

The rest are split. Two of them carried four or five changes each and ran to
forty lines; anybody reading the notes to find out whether their program still
works had to read a paragraph about the display band to find the one about
transparency. Each is now one change, three to nine lines, most of them opening
with what it does and following with what it used to do instead.

Author: mikebarkmin

.changeset/a-probe-that-runs-twice.md

@@ -4,13 +4,8 @@ type: patch
 
 Speech and thought bubbles hang off the sprite's hitbox.
 
-They were placed from the size of the costume, at nine tenths of its width and
-eleven tenths of its height. A costume is usually drawn into a canvas bigger than
-what is painted on it — a standing pose in a canvas tall enough to also hold a
-jumping one — so the bubble floated up and to the right of the sprite it belonged
-to, with its tail pointing at nothing. It now sits on the top right corner of the
-hitbox, which is the sprite as it looks.
-
-For the built-in slime, whose painted pixels fill 88 by 62 of a 128 by 128
-costume, that moves the bubble 14 pixels left and 72 pixels down, onto its
-shoulder.
+They were placed from the size of the costume, which is usually a canvas bigger
+than what is painted on it, so the bubble floated up and to the right of its
+sprite with its tail pointing at nothing. It now sits on the top right corner of
+the hitbox. For the built-in slime that moves it 14 pixels left and 72 down, onto
+its shoulder.

.changeset/bubble-anchor.md

@@ -0,0 +1,10 @@
+---
+type: minor
+---
+
+A built-in sprite name works everywhere a picture is named.
+
+`new Sprite("player", "slimeGreen")` threw `Could not load image: slimeGreen`:
+the constructor took a path where `addCostume()` took either. It now takes
+either, as do `Stage.setCursor`, `Window.useSplashLogo` and
+`Sprite.addCostumes`. A string with a file extension is still a path.

.changeset/builtin-names-everywhere.md

@@ -0,0 +1,8 @@
+---
+type: minor
+---
+
+`changePosition` takes two numbers as well as a vector.
+
+Moving by an amount worked only when the amount was already a `Vector2`, though
+`setPosition` has taken two numbers all along.

.changeset/builtin-names.md

@@ -0,0 +1,10 @@
+---
+type: patch
+---
+
+A `Color` says which colour it is.
+
+Printing one gave `org.openpatch.scratch.Color@35432107`, which is the first
+thing anyone tries when a tint looks wrong. It now reads
+`Color[r=255.0, g=128.0, b=0.0]`, and two colours with the same channels are
+equal.

.changeset/change-position-by-numbers.md

@@ -0,0 +1,8 @@
+---
+type: patch
+---
+
+`Stage.count` returns an `int`.
+
+It returned the `long` a `Stream` happened to hand back, so
+`int coins = myStage.count(Coin.class)` did not compile.

.changeset/change-position.md

@@ -0,0 +1,13 @@
+---
+type: minor
+---
+
+Transparency is the Scratch ghost effect.
+
+It ran from 0 to 255, where 0 was invisible and 255 the solid sprite you start
+with — upside down and on the wrong scale next to the `set [ghost v] effect to`
+shown beside it. It now runs 0 to 100, 0 solid and 100 invisible, and a value
+outside that is pinned rather than wrapped.
+
+`mySprite.setTransparency(50)` used to be nearly invisible; it is now half
+see-through.