kevinveenbirkenbachandClaude Opus 5 9728d274d6 docs(swarm): the terminator does not start the backup pull in the lab ...

The routine flowchart marked a terminator-driven remote-2-local start on bkp-01, failing for lack of the ssh trust the drill installs later. Both halves are wrong: the lab deploys the app stack and the backup host with --skip-backup, so MODE_BACKUP is false, svc-bkp-remote-2-local never sets system_service_force_flush_final, and the unit never enters system_service_run_list.

The drill is the only caller that starts the pull. The unit journal of the failed run holds exactly one invocation, at 20:58:30 - one line after 01_ssh_trust.sh installed the key, and that first rsync moved 5.8 GB. A terminator-started pull would have run at ~20:55:4x, before the key existed.

The box also loses its trigger colouring, since nothing fires there.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-02 14:04:13 +02:00

..

act

fix(act): let the requested distro survive into the nested sweep

2026-07-30 15:08:51 +02:00

ci

feat(ci): index the rescue tree at every collection site

2026-08-01 02:13:29 +02:00

local

…

swarm

docs(swarm): the terminator does not start the backup pull in the lab

2026-08-02 14:04:13 +02:00

utils

fix(swarm): stop the data-root loop leak and the parse that capped it at 8

2026-08-02 00:07:35 +02:00

distros.sh

fix(test-e2e): report the abort instead of dying on it

2026-07-30 15:08:51 +02:00

roundtrip.sh

fix(roundtrip): gate on a drill marker, not a workflow step name

2026-08-01 02:13:17 +02:00