Improve release and benchmark tooling

README.md

@@ -117,12 +117,15 @@ Update an installed client later:
 
 ```bash
 dosh update
+dosh update --check
+dosh --version
 ```
 
 `dosh update` first tries a release tarball named for the platform
 (`dosh-macos-aarch64.tar.gz`, `dosh-linux-x86_64.tar.gz`, etc.) from the latest
 Gitea/GitHub release. If that asset is not published yet, it falls back to the
-source build path.
+source build path. If the release also publishes `<artifact>.sha256`, the installer
+verifies the archive before installing it.
 
 Install the client on Windows PowerShell:
 
@@ -247,6 +250,15 @@ fast path after the first authentication has issued an attach ticket. See
 strongest claim is fast attach/reconnect plus native encrypted forwarding on
 Dosh-installed servers, not generic SSH compatibility.
 
+Generate a publishable Markdown benchmark report:
+
+```bash
+make bench-report
+```
+
+Set `DOSH_BENCH_SERVER`, `DOSH_BENCH_ITERS`, `DOSH_BENCH_ARGS`, and
+`DOSH_BENCH_REPORT` to target a real host and choose the output path.
+
 Run the explicit pre-launch soak and fuzz gates:
 
 ```bash
@@ -275,6 +287,7 @@ Build release tarballs for upload to Gitea/GitHub releases:
 
 ```bash
 make package-release
+GITEA_TOKEN=... scripts/upload-gitea-release.sh v0.1.0 target/dosh-release/dosh-*
 ```
 
 ## Performance Rules
@@ -311,7 +324,8 @@ Hot-path rules:
 
 - Replacing SSH as the first public-key trust mechanism.
 - Multi-user access control.
-- Windows support in v0.
+- Windows server/full parity in v0; the client installer supports prebuilt Windows
+  client artifacts when published.
 - Full mosh compatibility.
 - Perfect predictive local echo in the first MVP.