Found tonight while fixing the carina host install.
EVIDENCE
.github/workflows/deploy.yml dist-zip builds and copies only: archied, archie-gateway, archie-state-store, archie-ui, archie-playbooks (the 'for cmd in ...' loop and the 'cp dist/...' line).
cmd/archie-messaging exists in the tree and builds cleanly at both v1.30.0 and current main.
The comment immediately above that loop asserts 'Every process in the documented deployment ships in the zip' -- false since the v1.30.0 messaging extraction, which is when Telegram/email/webhook moved OUT of archied and into archie-messaging.
Consequence on a real host: carina ran archied 1.30.0 with no archie-messaging binary or unit anywhere. archied logged 'stopping telegram gateway' at the extraction and never started one again; the Telegram bot was dead for two days with no error anywhere. The daemon itself looked healthy throughout (polling, curator passes, nats connected).
deploy_workflow_test.go does not pin the zip contents, which is why nothing caught it.
FIX
Add archie-messaging to both the build loop and the copy list in the dist-zip job.
Add a test asserting the packaged set matches the set of host-run commands, so a future extraction or addition cannot silently leave a process unpackaged. deploy_workflow_test.go is the natural home.
Check whether install/upgrade guidance needs to name the messaging service and its unit -- a host install that upgrades across v1.30.0 now needs it.
Mitigated on carina by hand: archie-messaging built from archied/v1.30.0 and installed with a user unit. The repo fix is what stops it recurring.
Close reason
Closed on GitHub; syncing bead state
Imported from beads archie-core-1c01 · GitHub #1041 · type bug · priority P1 · created 2026-09-21 · closed 2026-09-26
Found tonight while fixing the carina host install.
EVIDENCE
- .github/workflows/deploy.yml dist-zip builds and copies only: archied, archie-gateway, archie-state-store, archie-ui, archie-playbooks (the 'for cmd in ...' loop and the 'cp dist/...' line).
- cmd/archie-messaging exists in the tree and builds cleanly at both v1.30.0 and current main.
- The comment immediately above that loop asserts 'Every process in the documented deployment ships in the zip' -- false since the v1.30.0 messaging extraction, which is when Telegram/email/webhook moved OUT of archied and into archie-messaging.
- Consequence on a real host: carina ran archied 1.30.0 with no archie-messaging binary or unit anywhere. archied logged 'stopping telegram gateway' at the extraction and never started one again; the Telegram bot was dead for two days with no error anywhere. The daemon itself looked healthy throughout (polling, curator passes, nats connected).
- deploy_workflow_test.go does not pin the zip contents, which is why nothing caught it.
FIX
1. Add archie-messaging to both the build loop and the copy list in the dist-zip job.
2. Add a test asserting the packaged set matches the set of host-run commands, so a future extraction or addition cannot silently leave a process unpackaged. deploy_workflow_test.go is the natural home.
3. Check whether install/upgrade guidance needs to name the messaging service and its unit -- a host install that upgrades across v1.30.0 now needs it.
Mitigated on carina by hand: archie-messaging built from archied/v1.30.0 and installed with a user unit. The repo fix is what stops it recurring.
### Close reason
Closed on GitHub; syncing bead state
---
_Imported from beads `archie-core-1c01` · GitHub #1041 · type bug · priority P1 · created 2026-09-21 · closed 2026-09-26_
sam
added the highbug labels 2026-10-27 13:38:35 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found tonight while fixing the carina host install.
EVIDENCE
FIX
Mitigated on carina by hand: archie-messaging built from archied/v1.30.0 and installed with a user unit. The repo fix is what stops it recurring.
Close reason
Closed on GitHub; syncing bead state
Imported from beads
archie-core-1c01· GitHub #1041 · type bug · priority P1 · created 2026-09-21 · closed 2026-09-26