fix: restore warded directors and refresh dev-base pins #815
No reviewers
Labels
No labels
burndown-2026-06
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/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agentic-os!815
Loading…
Reference in a new issue
No description provided.
Delete branch "aos/codex/20260730t122017z-14414-def8dd85"
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?
Fixes #811 and #813.
The explicit director launch path had regressed to a native shadow. That bypassed Ward, so no broker socket existed and AOSguard fell through to SSM, where the sealed surface had no usable AWS credential source. This restores the established warded director path while preserving native shadow launches for non-director roles.
The patch also refreshes the nine stale shared tool pins at the top of docker/dev-base/Dockerfile.
Validation:
Follow-up #814 tracks the existing mcporter Node 24 engine warning without coupling a runtime-major change to this patch.