v0.1.0

Read the tag annotation instead of trusting a flag that silently substitutes

--generate-notes was replaced with --notes-from-tag an hour ago to stop the
tag's own message being discarded. It did not work, and it failed in the worst
possible way: prism v0.116.0 was tagged with 2491 characters describing a WIRE
FORMAT CHANGE, and the release published 1189 characters of the last commit
message instead.

Not an error, not a warning -- something plausible. Anyone reading that release
to find out whether {} now goes out where [] used to would have found a note
about the formatting gate.

In a GitHub Actions checkout gh does not resolve the tag annotation, and says
nothing when it cannot. So the annotation is now read directly with
git tag -l --format='%(contents)', which is why these workflows check out at
fetch-depth 0, and passed as --notes-file. An empty result FAILS the step
rather than publishing an empty release.

Both affected releases have had their bodies restored from their tags:
prism-harness v0.3.0 and prism v0.116.0.

The general shape is one this ecosystem keeps meeting: a mechanism that reports
success while doing something else. The fix is the same every time -- read the
thing you actually want, and fail when it is not there.