monitor-stack: route unexpected failures through the troubleshooter (#214) - #226
Merged
Merged
Conversation
build-and-test: Python test resultsStatus: ✅ Passed Test log |
jodavis-claude
changed the title
jodavis
approved these changes
Aug 31, 2026
jodavis
marked this pull request as ready for review
August 31, 2026 20:52
jodavis-claude
force-pushed
the
dev/claude/Issue-214
branch
from
August 31, 2026 21:03
e06dcb1 to
37f3025
Compare
…leshooter monitor-stack's hard-stop points just reported failure in detail and stopped, forcing whatever spawned it (or the user, in the now-common direct-invocation case from #215) to absorb the raw diagnosis. Every failure that indicates a genuine pipeline bug rather than a usage/precondition issue — a missing feature branch or bottom-of-stack PR, a stack_checkout.py/stack_pr_poll.py/ stack_rebase_continue.py script error, a stack_complete cleanup failure, or a fix-pr/ resolve-rebase-conflict spawn reporting anything other than successful — now dispatches dev-team:troubleshooter with the epic's own context file instead, mirroring the same pattern workflow-orchestrate and concurrent-orchestrate already use for their own pipeline anomalies. This keeps the actual debugging investigation, and any bug it files, out of the calling session's context, and bounds each occurrence to one troubleshooter-applied retry before falling back to a plain hard stop. Step 1's worktree-freshness guard (a documented upstream Claude Code bug, not this plugin's own) and step 2b's own epic-derivation failure (a usage issue) are left as direct hard stops, since neither is something workflow-troubleshoot's fix strategies apply to. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SXkXzYacgX31sUpJ3CqSX4 (cherry picked from commit c9343e42557dbac08a848e880b7c4fa215220c94)
jodavis-claude
force-pushed
the
dev/claude/Issue-214
branch
from
August 31, 2026 21:13
37f3025 to
3be16da
Compare
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
3 participants
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.
Summary
monitor-stack's hard-stop points just reported failure in detail and stopped, forcing whatever spawned it (or the user, in watch-stack should not isolate itself #215's now-common direct-invocation case) to absorb the raw diagnosis, instead of following the same troubleshooter patternworkflow-orchestrate/concurrent-orchestratealready use for their own pipeline anomalies.stack_checkout.py/stack_pr_poll.py/stack_rebase_continue.pyscript error, astack_completecleanup failure, or afix-pr/resolve-rebase-conflictspawn reporting anything other thansuccessful— now dispatchesdev-team:troubleshooterwith the epic's own context file, bounded to one retry per occurrence before falling back to a plain hard stop.workflow-troubleshoot's fix strategies apply to.git rebase --abort+ hard-stop behavior is unchanged.python3 -m pytest plugins/dev-team/skills/workflow-orchestrate/scripts— 297 passed (no Python changed by this PR; prose-only change tomonitor-stack/SKILL.md).Closes #214