Settle the open points of the Ubuntu and nixpkgs image (closes #38)

ca-certificates, nix-bin and runit come from a dated Ubuntu snapshot no
older than the pinned Ubuntu image. The Dockerfile names the SHA-256 hash
of each snapshot InRelease file apt uses, and the build checks them before
apt-get install, so every package is checked against hashed files. That
install uses the Go image's CA certificate file. ca-certificates is
installed by name. The image writes build-users-group = to
/etc/nix/nix.conf so root can build without a daemon. nixpkgs comes from
its release file on releases.nixos.org, checked by SHA-256, and takes about
500 MiB of disk. runsvinit is archived upstream and is built at a fixed
commit with a go.mod written for the build. The example run scripts put
their code in a main function.

Model: opus-5-5

SPEC.md

@@ -1156,12 +1156,12 @@ The image holds:
 - Ubuntu 26.04 LTS, the newest long-term support release of Ubuntu, pinned by
   digest. The image moves to the next LTS release when that ships.
 - Three packages from Ubuntu, `ca-certificates`, `nix-bin` and `runit`,
-  installed from a dated snapshot of Ubuntu's archive (see "Packages from
+  installed from a dated snapshot of Ubuntu's archive and checked by hash (see
-  Ubuntu" below). The Ubuntu image has no CA certificates, and they come with
+  "Packages from Ubuntu" below). The Ubuntu image has no CA certificates, and
-  `nix-bin` only because a library it uses recommends them, so `ca-certificates`
+  they come with `nix-bin` only because a library it uses recommends them, so
-  is installed by name. Without it Nix cannot download packages, and
+  `ca-certificates` is installed by name. Without it Nix cannot download
-  `smallwebwaf`, unable to reach GeoJS, would count every visitor as coming from
+  packages, and `smallwebwaf`, unable to reach GeoJS, would count every visitor
-  an unknown country.
+  as coming from an unknown country.
 - Nix, the package manager, from Ubuntu's own `nix-bin` package, and nixpkgs,
   the collection of packages Nix installs from, fixed at one commit (see
   "Packages from nixpkgs" below). Root uses Nix directly, and no Nix daemon runs
@@ -1173,11 +1173,11 @@ The image holds:
   nor nixpkgs packages `runsvinit`, so the image builds it from its source
   (`github.com/peterbourgon/runsvinit`) at a fixed commit hash. Its repository
   is archived and has not changed since 2015, and its last tag is `v2.0.0`. It
-  has no `go.mod`, which Go needs to build it, so the build writes one; since
+  has no `go.mod`, and `go build` of its directory needs one, so the build
-  `runsvinit` uses only Go's standard library, that file names nothing else.
+  writes one; since `runsvinit` uses only Go's standard library, that file names
-  `runsvinit` starts runit's `runsvdir`, which starts a `runsv` for each
+  nothing else. `runsvinit` starts runit's `runsvdir`, which starts a `runsv`
-  directory under `/etc/service`; each `runsv` runs the `run` script in its
+  for each directory under `/etc/service`; each `runsv` runs the `run` script in
-  directory, and runs it again whenever it exits. Ubuntu's runit looks for
+  its directory, and runs it again whenever it exits. Ubuntu's runit looks for
   services in `/etc/service` too, so when `docker stop` has `runsvinit` stop
   each service with runit's `sv`, `sv` finds it.
 - The `smallwebwaf` binary, and a user of its own, `smallwebwaf` (uid and gid
@@ -1249,12 +1249,21 @@ Packages from Ubuntu: the image installs `ca-certificates`, `nix-bin` and
 given moment, rather than from the archive itself, whose packages change with
 every update. The image's Dockerfile names that moment, in apt's
 `--snapshot 20261001T000000Z` form, on both `apt-get update` and
-`apt-get install`, so the same Dockerfile always installs the same files, which
+`apt-get install`. That moment is never earlier than the date of the pinned
-apt checks against the archive's signature as usual. The snapshot service is
+Ubuntu image, since packages from an older snapshot can need older versions of
+packages the Ubuntu image already holds, and it moves forward whenever that
+image's digest does. `apt-get update` keeps the snapshot's `InRelease` files,
+which apt checks against the archive's signature, in `/var/lib/apt/lists/`; each
+lists the SHA-256 hash of the package lists it covers, and each package list the
+hash of every package in it. The Dockerfile also names the SHA-256 hash of each
+`InRelease` file apt uses, and the build checks them after `apt-get update` and
+before `apt-get install`, so every package apt installs is checked, through
+those files, against hashes the Dockerfile names. The snapshot service is
 reached over HTTPS, and the Ubuntu image has no CA certificates of its own, so
 this one install uses those of the Go image that `smallwebwaf` is built in,
 which is pinned by digest too: apt's `Acquire::https::CaInfo` option names that
-file.
+image's CA certificate file, `/etc/ssl/certs/ca-certificates.crt`, copied into
+the build.
 
 Packages from nixpkgs: nixpkgs is fixed at one commit of its newest release
 branch, `nixos-26.05` today. For each commit of the branch that has passed its
@@ -1267,12 +1276,13 @@ before unpacking it. nixpkgs is set up for root under the name `nixpkgs`, so the
 app's Dockerfile installs a package with `nix-env -iA nixpkgs.<name>`, and
 whatever it installs is on the `PATH` of every service. Because nixpkgs stays at
 that commit, an app built on the same `smallwebwaf` image gets the same packages
-each time it is built. Unpacked, nixpkgs adds about 200 MiB to the image, and
+each time it is built. Unpacked, nixpkgs takes about 500 MiB of disk, more on
-each package an app installs from it adds its own size, with everything it
+some filesystems such as ZFS, and each package an app installs from it adds its
-depends on. A newer commit of the branch, with its security fixes, comes with a
+own size, with everything it depends on. A newer commit of the branch, with its
-newer `smallwebwaf` image, as do Ubuntu's own fixes; an app takes them by
+security fixes, comes with a newer `smallwebwaf` image, as do Ubuntu's own
-changing the digest in its `FROM` line. When nixpkgs makes its next release,
+fixes; an app takes them by changing the digest in its `FROM` line. When nixpkgs
-every six months, the image moves to that release's branch.
+makes its next release, every six months, the image moves to that release's
+branch.
 
 The two processes: