the package-install matrix in #78 checks that the systemd unit file is present, but never that the service actually starts and serves. the unit's ExecStart path changed recently (/usr/local/bin to /usr/bin in #78), exactly the kind of thing a presence-only check misses.
propose: an integration test in a systemd-capable container that installs the unit, systemctl start kerno, and asserts the service reaches active and /healthz responds, then systemctl stop is clean. this validates the bare-metal path end to end, not just file placement.
depends on the harness (#143), overlaps the install checks in #78 but covers runtime, not just install. label area/ops.
the package-install matrix in #78 checks that the systemd unit file is present, but never that the service actually starts and serves. the unit's
ExecStartpath changed recently (/usr/local/bin to /usr/bin in #78), exactly the kind of thing a presence-only check misses.propose: an integration test in a systemd-capable container that installs the unit,
systemctl start kerno, and asserts the service reaches active and/healthzresponds, thensystemctl stopis clean. this validates the bare-metal path end to end, not just file placement.depends on the harness (#143), overlaps the install checks in #78 but covers runtime, not just install. label area/ops.