Kit runs mount archie-agent from the directory archied runs from (internal/app/archied/kit_launcher.go). install.sh installs only release.json required_topology.units, which omits archie-agent, so a fresh install has no agent binary and an install.sh upgrade leaves a stale one. Done when install.sh (release and --from-source) installs archie-agent next to archied.
Close reason
archie-agent now ships in the release beside archied: release.json gains required_topology.binaries ([archie-agent], no service), deploy.yml builds and copies units+binaries into the zip with the agentworker stamp, install.sh installs both for a release and builds both from source, and releaseupdate stages/switches/restores the binaries with the units while units still drive restart and MigrationPlan. cmd/archie-agent gained -version (reports agentworker.Version) so the release is verified like every unit. Verified: readManifest+apps() carry archie-agent, MigrationPlan names no agent service, and the releaseupdate suite passes.
Imported from beads archie-core-4v502 · GitHub #1671 · type bug · priority P2 · created 2026-10-13 · closed 2026-10-26
Kit runs mount archie-agent from the directory archied runs from (internal/app/archied/kit_launcher.go). install.sh installs only release.json required_topology.units, which omits archie-agent, so a fresh install has no agent binary and an install.sh upgrade leaves a stale one. Done when install.sh (release and --from-source) installs archie-agent next to archied.
### Close reason
archie-agent now ships in the release beside archied: release.json gains required_topology.binaries ([archie-agent], no service), deploy.yml builds and copies units+binaries into the zip with the agentworker stamp, install.sh installs both for a release and builds both from source, and releaseupdate stages/switches/restores the binaries with the units while units still drive restart and MigrationPlan. cmd/archie-agent gained -version (reports agentworker.Version) so the release is verified like every unit. Verified: readManifest+apps() carry archie-agent, MigrationPlan names no agent service, and the releaseupdate suite passes.
---
_Imported from beads `archie-core-4v502` · GitHub #1671 · type bug · priority P2 · created 2026-10-13 · closed 2026-10-26_
sam
added the mediumbug labels 2026-10-27 13:38:54 +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.
Kit runs mount archie-agent from the directory archied runs from (internal/app/archied/kit_launcher.go). install.sh installs only release.json required_topology.units, which omits archie-agent, so a fresh install has no agent binary and an install.sh upgrade leaves a stale one. Done when install.sh (release and --from-source) installs archie-agent next to archied.
Close reason
archie-agent now ships in the release beside archied: release.json gains required_topology.binaries ([archie-agent], no service), deploy.yml builds and copies units+binaries into the zip with the agentworker stamp, install.sh installs both for a release and builds both from source, and releaseupdate stages/switches/restores the binaries with the units while units still drive restart and MigrationPlan. cmd/archie-agent gained -version (reports agentworker.Version) so the release is verified like every unit. Verified: readManifest+apps() carry archie-agent, MigrationPlan names no agent service, and the releaseupdate suite passes.
Imported from beads
archie-core-4v502· GitHub #1671 · type bug · priority P2 · created 2026-10-13 · closed 2026-10-26