revert(shell): drop the acompose director carve-out #1039
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!1039
Loading…
Reference in a new issue
No description provided.
Delete branch "aos/claude/fx48"
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?
acompose director <harness>routed toaos --warded --composed --guardedwhile every other role went to the native shadow. Kai asked for the carve-out gone, so acompose now treats director like any other role.This knowingly reverts the shell half of #815 and reopens #811. The root cause is still live:
WARD_BROKER_SOCKappears nowhere on the native path.aos-cli/native_shadow.gohas no broker wiring.So a native director cannot dispatch engineers, and aosguard falls through to SSM for Forgejo credential resolution. A warded launch stays available by hand (
aos --agent <harness> --role director --warded --composed --guarded) for sessions that need dispatch.Scope
shell/common.sh- director branch deleted.tests/test_shell_agent_launch.py- the warded-director test now asserts the native-shadow path, and the sibling test loses its now-meaninglessnon_directorname.docs/native-agent-workspaces.md- the claim that director uses warded AOS was false after this change.Untouched, and still special-casing director: the
director/engineer/qafixed Ward lanes and argument rules inaos-cli/composition.go, and thedirector/opskubeconfig mount inaos-cli/kubeconfig.go.Validation
ward exec test- 522 passedpre-commit run --all-files- all hooks passed