Sync Boatstack from Intelligence Flow Labs @ c9e110ae06ef - #79
Merged
operator-stack-publisher[bot] merged 1 commit intoJul 23, 2026
Merged
Conversation
operator-stack-publisher
Bot
deleted the
sync/intelligence-flow-c9e110ae06ef
branch
July 23, 2026 16:56
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
Resolve managed-PR build lock across both feature layouts
Boatstack managed PR preparation no longer blocks the ship gate for features whose plan lock was written in the older feature-root layout. Previously
managedPRSourceslooked for the task graph only at<feature>/compiled/tasks.json; a feature activated withtasks.jsonat the feature root (nocompiled/directory) failed the build-lock check withtask_graphmismatch and reported "managed PR requires a current build lock" even after build, test, and review had passed.The task graph is now resolved across both layouts through a single shared resolver that also backs evidence resolution, preferring each artifact's canonical location and falling back to the alternate. Features activated in either layout prepare their managed PR identically; no migration is required.
Projection provenance
Generated from
operatorstack/intelligence-flow@c9e110ae06ef139d8ae336262558bc8bf21a1e2a.Review provenance, tests, examples, and context-cost changes before merging.