[dh] docs: add troubleshooting sections to harness docs#125
Merged
Conversation
Add a Troubleshooting section to each harness doc covering worktree-not-found issues caused by missing or incorrect worktree_dir configuration. Conductor doc gets extra guidance for repos with multiple Conductor projects pointing at the same repo. The Coast Runtime block (skills_prompt.txt and SKILLS_FOR_HOST_AGENTS.md) now directs agents to the relevant harness troubleshooting section when they hit configuration issues.
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.
Add a Troubleshooting section to each harness doc covering worktree-not-found issues caused by missing or incorrect worktree_dir configuration. Conductor doc gets extra guidance for repos with multiple Conductor projects pointing at the same repo. The Coast Runtime block (skills_prompt.txt and SKILLS_FOR_HOST_AGENTS.md) now directs agents to the relevant harness troubleshooting section when they hit configuration issues.