chore(ward): delete the shadowed legacy .coily/coily.yaml #9
No reviewers
Labels
No labels
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/scoop-bucket!9
Loading…
Reference in a new issue
No description provided.
Delete branch "aos/claude/mg96-legacy"
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?
Part of the coilysiren/inbox#365 teardown. Stale-migration debris.
This repo carried both
.ward/ward.yamland.coily/coily.yamlat the root. Ward'srepocfg.gochecks.ward/ward.yamlfirst (cmd/ward/repocfg.go:25-26), so the legacy file was permanently shadowed and unreachable. The catalog-graph builder in agentic-os-kai reads only.ward/ward.yamlas well (CONFIG_RELPATHS), so nothing consumed it.Its contents were stale on top of being unreachable:
descriptionthan the live filedependsOn: [otel-a2a-relay-cli], the o2r channel archived in the June 2026 surface reduction per agentic-os AGENTS.mdagent.workflow, which the live file declares asmerge-remote-mainThe live
.ward/ward.yamlfully supersedes it, so this is a pure deletion.Note this does not generalize to every
.coily/coily.yaml. eco-mods carries two in subdirectories (unity/,unity-embedded/) with no sibling.ward/, so ward's cwd walk-up does reach those. They stay.