Sync Boatstack from Intelligence Flow Labs @ 64b1891a9ecc - #122
Merged
operator-stack-publisher[bot] merged 1 commit intoJul 26, 2026
Merged
Conversation
operator-stack-publisher
Bot
deleted the
sync/intelligence-flow-64b1891a9ecc
branch
July 26, 2026 17:28
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.
What this sync releases
A managed delivery activates inside its cut worktree, not on the base branch
In worktree mode, Boatstack cuts a fresh worktree for each feature and expects the build to
happen there. It suggested this but never enforced it: if you drove the flow from the
repository root — the main worktree, still on the base branch — after the worktree had been
cut, activation ran there anyway. That stranded the compiled task graph and plan lock on the
base branch and created a second, competing delivery record, split off from the one in the cut
worktree.
Activation now refuses to run in that situation. When workspace management is on in worktree
mode and a feature's workspace has already been cut, activating from the main worktree on the
base branch is blocked with a clear message: change into the cut worktree and run it there.
The guard is precise — it does nothing during the normal flow (which cuts the worktree first,
then activates inside it), when workspace management is off or in branch mode, or before a
workspace exists — so only the base-branch mistake is stopped. Delivery state stays
worktree-local as before; this simply keeps activation out of the wrong worktree.
Projection provenance
Generated from
operatorstack/intelligence-flow@64b1891a9eccda6ede3df1b5350462d8179ef112.Review provenance, tests, and examples before merging.