Retire stale Go-bin agent-compose copies that shadow Scoop #659
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/infrastructure#659
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
During agent-compose release verification,
Get-Command agent-compose -Allshowed a legacy%USERPROFILE%\go\bin\agent-compose.exebefore the current Scoop shim. The stale binary reporteddevand emitted pre-release role and evaluation content even though Scoop had correctly installed and hash-verified v0.68.0. Invoking the versioned Scoop executable directly proved the release asset was correct.This violates the release-pipeline contract because a host can appear upgraded while resolving an old local
go installcopy.Acceptance:
%USERPROFILE%\go\bin\agent-compose.exeandacompose.execopies.agent-composeandacomposecommands resolve to the Scoop-managed shims after convergence.agent-compose --versionand one current embedded-content check from the released binary.PATHentry.This is operational convergence work. The agent-compose v0.68.0 and v0.69.0 release assets and package metadata were healthy.