Sync Boatstack from Intelligence Flow Labs @ f42f1a845ecc - #155
Merged
operator-stack-publisher[bot] merged 1 commit intoJul 30, 2026
Merged
Conversation
operator-stack-publisher
Bot
deleted the
sync/intelligence-flow-f42f1a845ecc
branch
July 30, 2026 10:40
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
Boatstack captures visual evidence itself during ship
When a plan declares relevant visual scenarios and the repository registers a capture command (
project.commands.visual),pr-context,check-pr, andpublish-prnow run the capture harness automatically whenever evidence is missing or stale. The agent no longer has to be told to take or attach screenshots — its remaining step is the privacy review of the captured PNGs. A harness failure records a bounded gap inpr_visual_evidence_capture_detailand keeps today'ssuggestbehavior; underrequire, the publication block is now a calm denial that names the full recovery ladder (capture-evidence,capability-register,provision-capability,record-pr-visual-evidence, or anot_relevantplan decision). A capture command that modifies the working tree is refused with the exact violating paths. Repositories without a registered command keep the prior prescribed path exactly.Projection provenance
Generated from
operatorstack/intelligence-flow@f42f1a845ecc6e5905d6e38dca863749cc19f0c0.Review provenance, tests, and examples before merging.