test(e2e): 升级任务先往发布版库里写 12 张表的种子行，升级后逐行比对并检查序列位置

docs/operations.md

@@ -21,7 +21,7 @@ release pins by digest, with its data on the host in `/var/lib/felis/postgres`.
 | OS family | Package manager | Architectures | Status |
 |---|---|---|---|
 | CentOS Stream 9 (firewalld active, SELinux enforcing) | dnf | aarch64 | **[VM-VERIFIED]** fresh install from release assets and its rerun, upgrade from v0.1.0 (moving the database off the host PostgreSQL 13 into felis-postgres), uninstall and reinstall |
-| Ubuntu 24.04 LTS | apt | x86_64 | **[CI]** fresh install and same-commit rerun from the pushed commit's release assets; the README's one-line install as a new host runs it (the newest release's own assets); upgrade from the newest release, installed from its assets by its own installer, onto them; the on-host build weekly |
+| Ubuntu 24.04 LTS | apt | x86_64 | **[CI]** fresh install and same-commit rerun from the pushed commit's release assets; the README's one-line install as a new host runs it (the newest release's own assets); upgrade from the newest release, installed from its assets by its own installer and seeded with rows in twelve tables, onto them, every seeded row read back unchanged; the on-host build weekly |
 | RHEL / Rocky / Alma 9, Fedora | dnf | x86_64, aarch64 | [CODE-ONLY] same code path as CentOS Stream |
 | Debian 12, other Ubuntu releases | apt | x86_64, aarch64 | [CODE-ONLY] |
 | openSUSE Leap / Tumbleweed | zypper | x86_64, aarch64 | [CODE-ONLY] |
@@ -570,7 +570,7 @@ instead, scale felis-postgres to 0, move the new major's directory out of
 `/var/lib/felis/postgres`, move `postgres-18.old` back as `/var/lib/felis/postgres/18`, and
 rerun the older release's installer.
 
-### The database's move into k3s [VM-VERIFIED]
+### The database's move into k3s [VM-VERIFIED] [CI]
 
 Releases before the move ran the database on a PostgreSQL the installer installed on the
 host. The first rerun of a release with felis-postgres moves it, once:
@@ -587,6 +587,11 @@ host. The first rerun of a release with felis-postgres moves it, once:
    holds other databases keeps running; its `felis` copy is then reachable over loopback
    only.
 
+The e2e upgrade job seeds the newest release's database with users, links, sessions, audit
+rows, backups, builds and the rest (`deploy/e2e_seed.sh`), upgrades, and checks that
+felis-postgres holds every seeded row with the same values after the pending migrations.
+While that release is v0.1.0, the upgrade is this move.
+
 From then on the host config points at felis-postgres (`127.0.0.1:15432`, and
 `deployment = "felis/felis-postgres"`, through which `felis db` runs `pg_dump`, `psql`
 and `pg_restore` inside the pod) and the pods at `felis-postgres.felis.svc:5432`.