Sync Boatstack from Intelligence Flow Labs @ 146f50c0f330 - #156
Merged
operator-stack-publisher[bot] merged 1 commit intoJul 30, 2026
Merged
Conversation
operator-stack-publisher
Bot
deleted the
sync/intelligence-flow-146f50c0f330
branch
July 30, 2026 11:18
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
Plan-approved visual scenarios now ship with require semantics
When the approved plan declares
pr_visual_evidencerelevancerelevantwith scenarios, the configuredsuggestpolicy escalates to require semantics for that feature: publication blocks until current PASS evidence exists, even when no capture capability is registered yet. A plan that promises pixels can no longer ship with aNOT_VERIFIEDgap. The escapes stay explicit:offglobally, or a per-featurenot_relevantdecision with a reason for genuinely nonvisual changes. Because Boatstack now captures registered scenarios automatically during ship, provisioned repositories will not notice the escalation. One-time effect after upgrading: an existingsuggestpreview for a feature with declared scenarios reports a changed context fingerprint — regenerate the preview withpr-contextbefore publishing.Projection provenance
Generated from
operatorstack/intelligence-flow@146f50c0f3309e592ed45374b8cddb3d8ed64d85.Review provenance, tests, and examples before merging.