Correct doc and help sentences that are false about the code (closes #233)

A blob is written whole to a temporary file and uploaded once finished,
not streamed to storage. The README, ARCHITECTURE.md and
config.example.yml now say a backup needs free temporary space for each
blob (twice that for an rclone destination that cannot stream uploads)
and for the metadata export's copies of the local index, in $TMPDIR, or
partly in /var/tmp when TMPDIR is unset. Also corrected: the snapshot ID
format, what restore reads and how incomplete snapshots are removed in
docs/DATAMODEL.md, what source_path holds, the index_path default, the
config search order in the snapshot create help, what snapshot remove
cleans up in the prune help, how the release installs Go, and the
script/release and script/fmt-check comments.

Model: opus-5-5

TODO.md

@@ -22,6 +22,22 @@ the tag exists and is exercised; what is left is merging `next` to
 
 # Completed Steps
 
+- 2026-10-07: Corrected documentation, help text and comments that were
+  false about the code
+  ([issue #233](https://git.eeqj.de/sneak/vaultik/issues/233)). A blob
+  is not streamed to storage. The README, `ARCHITECTURE.md` and
+  `config.example.yml` now say a backup needs free temporary space,
+  because each blob is written whole to a temporary file before it is
+  uploaded (up to about `blob_size_limit`; an rclone destination that
+  cannot stream uploads needs about twice that) and the metadata export
+  writes copies of the local index. Temporary files go to `$TMPDIR`
+  (default `/tmp`); with `TMPDIR` unset, SQLite writes one of those
+  copies to `/var/tmp`. Also corrected: the snapshot ID format, what restore
+  reads and how incomplete snapshots are removed in `docs/DATAMODEL.md`,
+  what `source_path` holds, the `index_path` and config file defaults,
+  what `snapshot remove` cleans up, how the release gets its Go
+  toolchain, and the `script/release` and `script/fmt-check` comments.
+
 - 2026-10-07: Cut the time the `internal/vaultik` and `internal/database`
   tests take ([issue #235](https://git.eeqj.de/sneak/vaultik/issues/235)).
   Most of the `internal/vaultik` time went to 24 tests that ran one at a