Release ipx 1.0.0, ipx-directory 1.0.0 and ipx-web 1.0.0, as Gitea releases

Each release is now a Gitea release as well as an image: scripts/release.sh takes the binary (or
the page's files) out of the deployed image, checks its version, and attaches it as a tarball with
the changelog section as the notes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

CLAUDE.md

@@ -298,7 +298,11 @@ a bug no release ever had, is not there at all; and "instead of" and "no longer"
 last release, not with last week. Issue numbers stay, all of them, on the line that survives. Then
 rename `[Unreleased]` to `## [X.Y.Z] - YYYY-MM-DD` and open a new empty `[Unreleased]` above it,
 set the service's version to `X.Y.Z` (dropping `-dev`), tag the commit with the service's tag, and
-update the compare links at the bottom of its changelog. Then, in the next commit, set its version
+update the compare links at the bottom of its changelog. Push the commit and the tag, build and
+deploy the service's image, then `sh scripts/release.sh ipx|directory|web` makes the Gitea
+release: that version's changelog section as its notes, and a tarball of what the image runs (the
+binary, or the page's files with the Caddyfile) attached, checked to be that version. Then, in the
+next commit, set its version
 to the next patch with `-dev` (after 0.9.0, `0.9.1-dev`), so a build between releases says so
 instead of claiming to be the last release. The release that follows can still be a minor or major
 one; `-dev` only says the work comes after `X.Y.Z`. A service never released is at `0.1.0-dev`,