# Installer evidence: what `chlift install` builds, on real systemd hosts (2026-10-06)

> **Version names:** this evidence was recorded while the release was planned as v1.0.0 (it ships as v0.2.0)
> and the follow-up as 1.0.1 (now v0.2.1); chlift stays on 0.x. Checksum-pinned files keep the names they were recorded with.

The v1.0.0 fault soak ran on the soak harness's containers, not on what the installer builds
(`docs/evidence/single-soak/criteria.md`). These runs cover the installer itself. Each host is a container with
systemd as PID 1 (rootless Docker; `privileged` applies only inside the user namespace), reached over SSH like a
server. Every file is the raw output; home paths were replaced with `~`. Each folder has `SHA256SUMS`.

Binaries: **A** = the v1.0.0 candidate before the rpm re-run fix; **B** = A + the rpm re-run fix;
**C** = B + JSON columns in `--checksums`.

## one-server-e2e/: the README flow on ONE server (Ubuntu 24.04)
Postgres 16, ClickHouse with its embedded Keeper, and PeerDB (Docker) on one host; `e2e.yaml`, `plan.yaml`.
- `install.log` (B): ClickHouse 26.3.39.7, PeerDB stable-v0.37.10; 7 checks ok, including the PeerDB API and the
  staging bucket.
- `start.log`, `status.log` (B): `migrate start --apply-postgres`; snapshot 400000 / 200000 / 100000 rows, equal to Postgres.
- `cdc.sql`, `cdc.log`: one 20,000-row insert, 4,123 updates, 396 updates to 20 KB JSON values, 1,895 + 651 deletes.
- `check.log` (B): `migrate check --checksums` after the writes: counts equal, 0 of 64 buckets differ on 3 tables.
- `cutover.log` (B): final proof 0 differ; mirror stopped, slot and publication dropped.
- JSON in `--checksums`: `check-json-clean.log` (C): 7 columns incl. `properties`, 0 differ.
  One JSON value then emptied in ClickHouse: `check-old-emptied.log` (B, JSON not compared) still reports
  0 differ; `check-json-emptied.log` (C) reports 1 differing bucket and exits 1. `check-json-restored.log` (C):
  value restored, 0 differ.

## rocky9-systemd/: Rocky Linux 9, one server (ClickHouse + Keeper)
- `install.log` (A): 26.3.39.7-1 installed, the systemd unit enabled; 5 checks ok.
- `verify-after-reboot.log` (A): after a container restart, systemd started ClickHouse by itself; 5 checks ok.
- `install-rerun.log`, `rerun-old.log` (A): a re-run with nothing changed still reports "installed" and
  "restarted" (the rpm version check compared 26.3.39.7 with 26.3.39.7-1).
- `rerun-fixed.log` (B): the same re-run reports "running", nothing restarted. `rerun-fixed-bare.log` (B):
  `rhelsd-bare.yaml` pins with `clickhouse_build: 26.3.39.7` (no release suffix), also "running".

## ubuntu24-systemd/: Ubuntu 24.04, one server (ClickHouse + Keeper)
- `install.log` (B): 26.3.39.7 installed, the unit enabled; 5 checks ok.
- `verify-after-reboot.log` (B): after a container restart, 5 checks ok.
- `install-rerun.log` (B): "running", nothing restarted.

Not covered here: replicated layouts through the installer on systemd hosts, and RHEL itself (Rocky Linux stands in).
