Export coilyco config refs in ward containers #1287

Merged
coilyco-ops merged 3 commits from issue-1000 into main 2026-07-15 01:11:38 +00:00
Member

Coilyco engineer containers now export the resolved WARD_CONFIG_REF bundle for coilyco targets, so repo-local ward exec sees 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.

  • Exports the resolved config ref from coilyco launch plans.
  • Pins the behavior with a container env test.
  • Targeted 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

Coilyco engineer containers now export the resolved `WARD_CONFIG_REF` bundle for coilyco targets, so repo-local `ward exec` sees 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. - Exports the resolved config ref from coilyco launch plans. - Pins the behavior with a container env test. - Targeted `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
Export coilyco config refs in ward containers
Some checks failed
test / test (pull_request) Failing after 1m10s
92928f3b6e
Author
Member

WARDED_WORKFLOW: blocked 🛑

detailsworkflow: 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-wide ward exec test and pre-commit run --all-files were 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.

WARDED_WORKFLOW: blocked 🛑 <details><summary>details</summary>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 https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1287. Targeted `go test ./cmd/ward -run 'TestWardEnvCoilycoConfigRef|TestRunSetupWithUnsetRef|TestSmartDefaultsFromBundleSource|TestSelectConfigSourceReconstructsCoilycoTargetFromCheckout'` passed locally. The repo-wide `ward exec test` and `pre-commit run --all-files` were 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. </details>
Merge main into issue-1000
All checks were successful
test / test (pull_request) Successful in 2m16s
5d4e213ca1
Merge remote-tracking branch 'origin/main' into issue-1000
All checks were successful
test / test (pull_request) Successful in 55s
fb0b8cb903
Sign in to join this conversation.
No description provided.