Root, CI, docs and packaging describe the project to a stranger (#6225)

#6225 "Comment standard sweep: root, config, CI workflows, docs and
packaging", milestone 546 "Bring the repo to the comment standard (rule 32)
and compose defaults (rule 198)".

- README restructured in newcomer order: what it is, quick start,
  configuration, setup pitfalls, updating and backups, features,
  troubleshooting, development, licence. Its quick-start compose carries
  no restart policy.
- Dockerfile and .env.example trimmed to one or two lines per setting.
- Workflows, packaging scripts and docs lose issue, run, note, rule and
  milestone references and their history narration. Comments that still
  described path filters and "step 6" as future work now state what the
  workflows do.
- ci-requirements.md rewritten against the current workflows. It said the
  build gated on typecheck and lint only, the integration lane did not
  gate, a v* tag published :latest, and ci-tauri lacked bsdtar and zstd;
  none of those is true now (the last checked against run 9630's log).
- Echo strings in guard-forward.sh and version.sh drop their note
  citations; every string a test asserts on is unchanged.

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

Dockerfile

@@ -45,7 +45,7 @@ COPY client/ src/inkwell/client/
 
 # The desktop installer, served at /install.sh with this server's own address
 # written into it (installer.py). The SAME script the forge serves raw, copied rather
-# than moved so the operator's documented forge URL keeps working.
+# than moved so the forge's raw URL keeps working.
 COPY desktop/packaging/install.sh src/inkwell/install.sh
 
 ENV PYTHONPATH=/app/src
@@ -55,16 +55,15 @@ ENV APP_VERSION=$BUILD_VERSION
 
 EXPOSE 5000
 # Wait for the database, run migrations, then serve. The DB wait keeps a briefly
-# slow/unready database from crash-looping the container. Family convention
-# (rule 82): schema is built by real migrations, never metadata.create_all.
+# slow or unready database from crash-looping the container. The schema is built by
+# real migrations, never metadata.create_all.
 #
-# Timeouts (family idea #5105, practice 9; read from hypercorn 0.18's source):
+# Timeouts, as hypercorn 0.18 implements them:
 # - `--keep-alive 120` is the idle timeout. It is also the header timeout:
 #   hypercorn marks a connection busy only once a whole request has arrived, so a
-#   client dribbling headers is still "idle" and is cut off at this. It was 600,
-#   ten minutes per held connection. 120 stays above Traefik's 90s idle timeout
-#   for backend connections, so the proxy never reuses one this server has just
-#   closed (a 502).
+#   client dribbling headers is still "idle" and is cut off at this. 120 stays
+#   above Traefik's 90s idle timeout for backend connections, so the proxy never
+#   reuses one this server has just closed (a 502).
 # - No `--read-timeout`, on purpose. It bounds every socket read, including the
 #   whole time a download is streaming and the client sends nothing, so it would
 #   cut off an APK fetched slowly over mobile data. Bodies are capped instead