Sync Boatstack from Intelligence Flow Labs @ 7cbafd41ee72 - #110
Merged
operator-stack-publisher[bot] merged 1 commit intoJul 25, 2026
Merged
Conversation
operator-stack-publisher
Bot
deleted the
sync/intelligence-flow-7cbafd41ee72
branch
July 25, 2026 16:03
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 now responds in Simplified Technical English
The README and the release notes already follow Simplified Technical English. Boatstack's
runtime did not. Its responses, its review findings, and its PR brief used no shared writing
standard.
The shared response contract now requires Simplified Technical English for every operation.
Boatstack writes short sentences. It uses the active voice and the present tense. It states
one idea per sentence, puts the condition first, and chooses the simple, common word. The
review-gate findings and the ship-gate PR brief follow the same rule.
The change is additive. It does not change the fixed outcome labels, the single next step,
the collapsed technical details, or the reply keys. So the responses stay easy to skim and
easy to translate, for both people and models.
You can publish a Boatstack version update from inside a session
The version-update publisher now runs inside a guarded session. Before this fix, the safety
hook denied
boatstack-helper publish-update-prevery time. It reported a directdelivery-state mutation. The publish then only worked from outside the session.
The cause was a false match. The publisher reads the update preview file. That file lives
under
.git/boatstack/. The tamper guard saw the path in the command and blocked the wholecommand, even though the path is a read argument to a trusted command.
The fix adds a narrow exemption for the sanctioned publisher, the same way
publish-prisalready trusted. The exemption covers only
boatstack-helper publish-update-pr. It isanchored end to end, so you cannot chain a second command after it. A direct write to any
.git/boatstack/path, such asrmof the delivery state, is still denied.The denial message is also clearer. If the guard blocks a real write, it names the command
that owns the state and points to
boatstack-helper diagnose-hookfor a false positive.Projection provenance
Generated from
operatorstack/intelligence-flow@7cbafd41ee72ad5b0e682a052ad3ebc6f21f5933.Review provenance, tests, and examples before merging.