Sync Boatstack from Intelligence Flow Labs @ c288814c8913 - #78
Merged
operator-stack-publisher[bot] merged 1 commit intoJul 23, 2026
Merged
Conversation
operator-stack-publisher
Bot
deleted the
sync/intelligence-flow-c288814c8913
branch
July 23, 2026 15:21
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
Stop miscounting shipped features as open plans
Boatstack no longer treats already-shipped or locked features as unresolved plan candidates. Previously, in repositories that use worktree delivery mode with
workspace.cleanup_after = merge, shipping a feature removed the worktree that held its per-worktree deliverystate.json, while the committedplan.md/plan.lock.json/pr.mdsurvived. From a fresh build worktree,next-statusthen re-registered every historically shipped feature as an open plan and blocked withAMBIGUOUS.The plan-candidate check now relies on the durable committed artifacts: any feature carrying a
plan.lock.json(locked/built) orpr.md(shipped) is past planning and is excluded from open-plan candidates, regardless of whether its ephemeralstate.jsonstill exists. A feature with onlyplan.mdcorrectly remains the single open candidate. Delivery-state locality and cross-worktree push-denial are unchanged.Projection provenance
Generated from
operatorstack/intelligence-flow@c288814c89139fa36e7b914ce14d9917f12d32d0.Review provenance, tests, examples, and context-cost changes before merging.