-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Open
Labels
needs-triageNew issue awaiting maintainer reviewNew issue awaiting maintainer review
Description
Bug Report
GSD version: 0.57.1 (@glittercowboy/gsd)
What happened
reassess-roadmap M016/S01 dispatched by auto-mode after slice completion. Agent writes S01-ASSESSMENT.md, auto-commit succeeds, working tree is clean — but the dispatcher's artifact check reports "Expected artifact not found" and re-dispatches. Loops 4 times before hitting the loop detector.
Evidence
- File exists on disk:
ls -laconfirms 1347 bytes at.gsd/milestones/M016/slices/S01/S01-ASSESSMENT.md git statusshows clean working treegit logshows 4 successivechore(M016/S01): auto-commit after reassess-roadmapcommits, each modifying the same file- No
gsd/*branch exists — commits land onmaster(the integration branch) STATE.mdalready advanced to S02 executing
Error message
Error: Loop detected: reassess-roadmap M016/S01 dispatched 4 times total.
Expected artifact not found.
Expected: .gsd/milestones/M016/slices/S01/S01-ASSESSMENT.md (roadmap reassessment)
Check branch state and .gsd/ artifacts.
Possible causes
- Artifact check may be looking on a different branch than the one the auto-commit lands on
- Check may run before the auto-commit flushes to disk
- Stale filesystem state between dispatch cycles
Reproduction
- Complete a slice in auto-mode (e.g. S01 of a multi-slice milestone)
- Auto-mode dispatches
reassess-roadmap M016/S01 - Agent writes
S01-ASSESSMENT.mdand it gets auto-committed - Dispatcher reports artifact not found and re-dispatches
- Loops until loop detector kills it
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
needs-triageNew issue awaiting maintainer reviewNew issue awaiting maintainer review