NEC-352: install-deployer.sh --check reports a month-stale deployer as verified #324

Merged
nectenda-agent merged 3 commits from worktree-nec-352-install-deployersh-check-reports-a-month into main 2026-10-28 11:46:39 +00:00
Collaborator

Task: NEC-352 — https://projectron.nerchure.com/tasks/373

install-deployer.sh --check and inventory.mjs compared only docker-compose.yml and the Caddyfile, so on 27 Oct both called eu1 and accounts verified while they ran the 26 September deployer. deploy/host-files.txt is now the one list of every file a host carries (deployer, units, backup script, Kuma bundle, compose, Caddyfile, deploy.env.example; snapshot.sh on ops). The installer copies exactly its rows (to .new, moved in once every copy lands; a failed copy is taken back), --check and the inventory compare exactly its rows with the identity host's units rewritten as installed, and the console's installer copies every source it names. Both installers build the Kuma bundle via lib/bundle-kuma.sh, so the console's copy matches the hosts'. A file the checker cannot read is reported absent-here, not dropped. A Caddyfile Caddy will not load now fails the install on the ops box too. New deploy/test/install-deployer.test.ts runs the real installer against a fake host; every new rule mutation-checked. Decision recorded: no self-reported deployer hash; automatic staleness signal filed as NEC-355. After merge, run deploy/install-deployer.sh once: every shard and identity host will show deployer and bundle drift until it runs.

Spec: docs/changes/NEC-352-install-deployer-check/spec.md

Changelog

NONE

Task: NEC-352 — https://projectron.nerchure.com/tasks/373 install-deployer.sh --check and inventory.mjs compared only docker-compose.yml and the Caddyfile, so on 27 Oct both called eu1 and accounts verified while they ran the 26 September deployer. deploy/host-files.txt is now the one list of every file a host carries (deployer, units, backup script, Kuma bundle, compose, Caddyfile, deploy.env.example; snapshot.sh on ops). The installer copies exactly its rows (to <dest>.new, moved in once every copy lands; a failed copy is taken back), --check and the inventory compare exactly its rows with the identity host's units rewritten as installed, and the console's installer copies every source it names. Both installers build the Kuma bundle via lib/bundle-kuma.sh, so the console's copy matches the hosts'. A file the checker cannot read is reported absent-here, not dropped. A Caddyfile Caddy will not load now fails the install on the ops box too. New deploy/test/install-deployer.test.ts runs the real installer against a fake host; every new rule mutation-checked. Decision recorded: no self-reported deployer hash; automatic staleness signal filed as NEC-355. After merge, run deploy/install-deployer.sh once: every shard and identity host will show deployer and bundle drift until it runs. Spec: `docs/changes/NEC-352-install-deployer-check/spec.md` ## Changelog NONE
Task: NEC-352
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EV8ztYrtXiWUQ61NPqoP7e
install-deployer.sh --check and inventory.mjs hashed docker-compose.yml and
the Caddyfile and nothing else, so on 27 October 2026 both called eu1 and
accounts healthy while they ran the 26 September deployer. deploy/lib/ is the
one set of files that reaches a host by no other path.

deploy/host-files.txt now lists every file the installer writes: source,
destination, mode, and whether a unit is rewritten for the host's app dir.
The installer copies exactly its rows (each to <dest>.new, moved into place
only once every copy has landed), --check and the inventory compare exactly
its rows, and the console's installer copies every source it names. Both
installers build the Kuma bundle through lib/bundle-kuma.sh, so the console's
copy is byte-identical to the hosts' and can be compared against. A file the
checker cannot read for itself is reported absent-here rather than dropped.

Task: NEC-352
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EV8ztYrtXiWUQ61NPqoP7e
Fail an install Caddy will not load, and take back a failed copy, as review found
All checks were successful
Release note / release-note (pull_request) Successful in 20s
CI / build (pull_request) Successful in 6m18s
CI / e2e (pull_request) Successful in 15m3s
CI / promote (pull_request) Has been skipped
07512a7130
Review of NEC-352 found that the shared install script ends on the timers, so
on the ops box, which has none, a Caddyfile that failed validation or reload
was reported installed; the old ops script had ended on that reload. The move
script now collects failures and exits non-zero. A copy that fails part way
now removes the .new files that had landed. The inventory CLI prints a file it
has no copy of as not checked, rather than marking the host, as the console
already did.

Task: NEC-352
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EV8ztYrtXiWUQ61NPqoP7e
cruelacid force-pushed worktree-nec-352-install-deployersh-check-reports-a-month from 07512a7130
All checks were successful
Release note / release-note (pull_request) Successful in 20s
CI / build (pull_request) Successful in 6m18s
CI / e2e (pull_request) Successful in 15m3s
CI / promote (pull_request) Has been skipped
to 2c047771ac
All checks were successful
Release note / release-note (pull_request) Successful in 18s
CI / build (pull_request) Successful in 6m7s
CI / e2e (pull_request) Successful in 14m58s
CI / promote (pull_request) Has been skipped
CI / build (push) Successful in 5m58s
CI / e2e (push) Successful in 14m45s
CI / promote (push) Successful in 33s
2026-10-28 11:30:37 +00:00
Compare
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Nectenda/nectenda!324
No description provided.