Propagate selected fleet attribution into ward containers #1295

Closed
opened 2026-07-15 00:23:57 +00:00 by coilyco-ops · 0 comments
Member

warded containers currently let bootstrap fall back to the baked fleet defaults when WARD_GIT_NAME and WARD_GIT_EMAIL are absent. That keeps some engineer commits on example-bot even when the selected config bundle carries coilyco-ops attribution.\n\nFix the host launch plan to read the selected fleet attribution and emit WARD_GIT_NAME plus WARD_GIT_EMAIL into the container env. The in-container bootstrap already treats those env vars as authoritative.\n\nRelated: coilyco-flight-deck/agentic-os#432.

warded containers currently let bootstrap fall back to the baked fleet defaults when WARD_GIT_NAME and WARD_GIT_EMAIL are absent. That keeps some engineer commits on example-bot even when the selected config bundle carries coilyco-ops attribution.\n\nFix the host launch plan to read the selected fleet attribution and emit WARD_GIT_NAME plus WARD_GIT_EMAIL into the container env. The in-container bootstrap already treats those env vars as authoritative.\n\nRelated: coilyco-flight-deck/agentic-os#432.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/ward#1295
No description provided.