Sync Boatstack from Intelligence Flow Labs @ c550ef95f440 - #150
Merged
operator-stack-publisher[bot] merged 1 commit intoJul 28, 2026
Merged
Conversation
operator-stack-publisher
Bot
deleted the
sync/intelligence-flow-c550ef95f440
branch
July 28, 2026 17:11
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
The merged-goal pursuit now has explicit limits, and stops when it hits one
With
delivery.terminal: merged, the flow pursues your pull request only inside a clear contract: at most three recorded post-publish fix cycles, no reviewer asking for changes, and a branch that merges cleanly. When any of those ends — the budget is spent, changes are requested, the base conflicts — the pursuit pauses: the step comes back to you, nothing further is prescribed, and the pause is remembered so it still holds tomorrow in a fresh session, even offline.Recording the next correction is the explicit reset that starts a fresh cycle. The status reason always tells you why the pursuit paused. With the default
publishedgoal, none of this bookkeeping is evaluated or written.Projection provenance
Generated from
operatorstack/intelligence-flow@c550ef95f440e8b463ae0d436953e10ad91e1ab6.Review provenance, tests, and examples before merging.