ci: every push to master is a release, the metainfo's newest

A push to master published the build as the rolling `beta` branch and
refreshed a `latest` prerelease; a tag cut the stable release. Now every
push to master is the release: CI takes the version from the
metainfo's newest <release>, publishes `stable`, tags the pushed commit
and creates the release with that entry's notes. A version that is
released already fails the job before anything is built or published,
and so does a lookup that cannot tell, so a push to master adds a new
<release>. Publishing is master's alone: a manual run on another branch
builds and tests and cuts nothing. Tags are no longer a trigger, and the
rolling `beta` and `latest` steps are gone. The README and AGENTS say
so, and the first release's entry, 1.0.0, takes the date of its push
and names what it ships.

packaging/flatpak/net.catcrafts.CrafterReview.metainfo.xml

@@ -27,10 +27,18 @@
   </provides>
   <content_rating type="oars-1.1"/>
   <releases>
-    <release version="1.0.0" date="2026-10-31">
+    <release version="1.0.0" date="2026-11-02">
       <description>
-        <p>First release: the pre-push review gates in C++26, shipped as a Flatpak.</p>
-        <p>Every lens is off until the repository's config turns it on. The commit-truth lens, repo-facts, reads the commit messages and the documentation of the range as Gate 4.</p>
+        <p>New</p>
+        <ul>
+          <li>Pre-push review gates for a commit range: Claude processes review the approach, the running application, a bug proof, security and the commit messages, and a range is send-ready only when every gate passes on its exact frozen hash.</li>
+          <li><code>crafter-review init</code> sets a repository up: its config and the <code>/prepush</code> skill.</li>
+          <li>Modes in the repository's config (<code>modes.&lt;name&gt;</code>): the kind of artifact, the lenses it runs and their effort. Every lens is off until a mode lists it.</li>
+          <li>Seats from a dotenv file - <code>--env-file</code>, <code>$SEATS_ENV_FILE</code>, the working directory's <code>.env</code> or the machine's own <code>~/.config/crafter-review/env</code> - over the environment's, on one seat board for every driver on a machine.</li>
+          <li>A repository's own section appended to a lens's charter (<code>lenses.&lt;name&gt;.section</code>).</li>
+          <li>Pre-send review of a kernel patch series or a mailing-list reply (<code>--mode series</code>, <code>--mode reply</code>).</li>
+          <li>Shipped as a Flatpak with its own git, Node and ripgrep.</li>
+        </ul>
       </description>
     </release>
   </releases>