Repository navigation
fix(arm): resolve wake paths via wake-cmd (git-common/worktree-safe) - #8
Merged
Merged
Conversation
The /arm skill hardcoded .git/fleet/... inbox/wake paths. Those are wrong in a linked git worktree and under state_location=git-common (the real dir is git-common-dir/fleet -- the MAIN repo .git/fleet, not the worktree, not the local .fleet/state). A watcher armed from them is alive but orphaned: its heartbeat lands where the fleet never looks, so monitors reads UNMONITORED and DMs never proactively wake it. Fix the doc to source the exact inbox/mon paths from fleet.sh wake-cmd (never transcribe), derive the agents dir from mon, seed netdown=0 (no spurious first-tick ping), and add a Step-3 VERIFY forcing function (fleet.sh monitors must show MONITORED, else re-arm). Field-verified across several VS Code restarts on the trackboard fleet. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The /arm skill doc hardcoded .git/fleet/... inbox/wake paths. In a linked git worktree, and whenever state_location=git-common, the real state dir is git-common-dir/fleet (the MAIN repo .git/fleet) -- NOT the worktree .git/fleet and NOT the local .fleet/state. A Monitor armed from the hardcoded paths runs but is orphaned: its heartbeat lands where the fleet never looks, so fleet.sh monitors reads UNMONITORED and DMs never proactively wake the agent (they still deliver on the next turn).
Fix (doc-only)
Verification
Field-verified across several VS Code restarts on the trackboard fleet: agents that armed from hand-typed paths read UNMONITORED; re-arming from wake-cmd fixed it.
Doc-only markdown (.fleet/skills/arm/SKILL.md); no scripts touched, so shellcheck + smoke are unaffected.