Export coilyco config refs in ward containers #1287
No reviewers
Labels
No labels
burndown-2026-06
pressure-test
sunday-sprint
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
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/ward!1287
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-1000"
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?
Coilyco engineer containers now export the resolved
WARD_CONFIG_REFbundle for coilyco targets, so repo-localward execsees the launch-selected config source instead of the baked neutral default. This stays scoped to coilyco launches and keeps neutral/external ward users on the baked defaults.go test ./cmd/ward -run ...passed locally. The full repo gate is still blocked here by container temp space.closes #1000
ward.workflow: pull-request-and-merge
WARDED_WORKFLOW: blocked 🛑
details
workflow: pull-request-and-merge; review summary: review gate intentionally skipped because temporary ward default pending brokered QA.Status: branch pushed and PR open at #1287. Targeted
go test ./cmd/ward -run 'TestWardEnvCoilycoConfigRef|TestRunSetupWithUnsetRef|TestSmartDefaultsFromBundleSource|TestSelectConfigSourceReconstructsCoilycoTargetFromCheckout'passed locally. The repo-wideward exec testandpre-commit run --all-fileswere blocked here by container temp-space limits, and no Forgejo Actions run surfaced for issue-1000 yet.Felt: the code change was a tight env-export fix, but verification got pinned by the container filesystem ceiling.
Confidence: medium. Surprise: the PR opened cleanly, but CI never surfaced a branch run in the task feed.
Follow-ups: clear the temp-space blocker, rerun the full ward gate, and then merge once Forgejo shows the branch green.