fix: running uat and writing-plans at the same time, uat not block anything (#45) - #47
Merged
Conversation
The feature route called uat.RunFeature() inline between the committed spec and runPlanThenExecute(), so a whole extra Claude session sat between SPEC_READY and the plan session starting. "Non-blocking" only ever meant "a UAT failure does not fail the pipeline" — it still blocked on wall time. The checklist is a side errand on a spec that is already committed and nothing downstream reads it, so it now starts on its own goroutine (UAT.StartFeature) and the plan session runs concurrently with it. The returned wait func is deferred, so the pipeline joins the session on every exit path: it must not outlive the worktree and context that handleIssue tears down on return. Claude.nextSeq now takes a mutex — two sessions share one *Claude, and they must not race on the log sequence counter or be handed the same number. Judgement calls made headlessly: - Bug route left sequential: its UAT step is the last thing in the pipeline, so there is nothing to overlap it with. Only the feature route (the one the issue names) changes. - The two order-coupled feature tests now key on prompt content instead of call ordinals, since call order is no longer deterministic. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
17 tasks
# Conflicts: # pipeline_feature_test.go
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
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.
Closes #45
Automated by loope (bug flow). Spec and plan, if any, are committed in this branch under docs/.