eco: smoke gate stages the working copy into the INSTALL Mods/ (mutates it even on a red gate) #463
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#463
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?
What
eco-native-smoke.ps1overlays<src>/Modsonto the install'sMods/before booting the throwaway world - inherited from the dissolved Go gate (stageModSourcein ward#582'seco_run.go), because EcoServer loads mods from the install tree, not the-storageworld dir.Consequence observed in the inbox#158 live-fire: a RED gate leaves the broken working copy sitting in the install's Mods/ (I removed
ZZWardBreakby hand between drills). The promote envelope's snapshot/rollback does not cover the gate path.Ask
Make the gate boot side-effect-free on the install: either stage into a temp copy of the install's Mods (junction/symlink tree or
-usermodsdir-style flag if EcoServer 0.13 supports one), or snapshot+restore around the gate the way promote does. Until then the gate's contract is "red gate may leave the tested files staged; promote or clean by hand."Related
coilysiren/inbox#158 (live-fire), docs/ops-eco.md, ward docs/eco-test.md.
Closed in the 2026-08-26 backlog burn-down (coilyco-bridge/agentic-os-kai#901).
Closing as stale.
eco-native-smoke.ps1is not present in this repository or in eco-ops any more, so the staging side effect it describes has no code behind it. Refile against whatever gate replaces it if the same mutation reappears.This was
priority/P3, the default tier that unsure and unscored issues land in, so it had never been positively judged worth keeping. The 2026-08-26 burn-down ranked the whole P3 pool and cut the bottom. Closed here means not on the list, not wrong or worthless.If this is live work, reopen it. The whole set is recoverable with
state:closed label:burndown-2026-08.