Fix config-bundle gitsync FETCH_HEAD permission errors in director surfaces #1089
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
2 participants
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/ward!1089
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-1086"
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?
closes #1086
ward.workflow: pull-request-and-merge
The in-container review gate was intentionally skipped because the temporary ward default pending brokered QA.
WARD-OUTCOME: blocked 🛑
details
workflow: pull-request-and-merge; review summary: blocked by a pre-existing failing CI test review gate: intentionally skipped in-container because the temporary ward default pending brokered QA retrospective: the cache-path fix is in place and the new regression passes locally, but landing is blocked by `TestRunAgentAdvisorRefDispatchReturnsPromptlyViaBroker`, which fails on both this branch and `main` confidence: high surprise: the red check is unrelated to the config-bundle permission fix follow-ups: fix the broker stdio regression or its fixture, then re-run CIWARD-OUTCOME: blocked 🛑
details
workflow: pull-request-and-merge; review summary: blocked by a pre-existing failing CI test review gate: intentionally skipped in-container because the temporary ward default pending brokered QA retrospective: the cache handoff fix is in place and the config-bundle regression passes locally, but PR #1089 is still red on `TestRunAgentAdvisorRefDispatchReturnsPromptlyViaBroker` confidence: high surprise: the red check is unrelated to the config-bundle permission fix follow-ups: fix the broker stdio regression or its fixture, then re-run CI