Sync Boatstack from Intelligence Flow Labs @ 7f71d4816931 - #135
Merged
operator-stack-publisher[bot] merged 1 commit intoJul 27, 2026
Merged
Conversation
operator-stack-publisher
Bot
deleted the
sync/intelligence-flow-7f71d4816931
branch
July 27, 2026 15:04
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 next-step response is now rendered by the helper, not re-derived from prose
Asking Boatstack "what's next" always had a deterministic answer, but the user-facing response — the outcome line and the single next action — was described in the skill instructions as prose, and every agent re-derived it from a written state table on every turn. That table was one more place the guidance could drift from the machine.
next-status --format responsenow renders the canonical response contract directly: the branded banner, one plain-language outcome line, and exactly one "### Next step" block carrying the exact runnable command whenever one is prescribable — the identical command lineflow nextprints, produced by the same prescription layer, never a copy. The skill instructions now point at the renderer instead of restating the table, and a conformance suite pins the parity, the single-next-step shape, and the rule that machine stage names never leak into status prose.This is the first slice of compiling the instruction layer down into the helper: where a rule can be rendered deterministically, the prose now defers to the rendering.
Projection provenance
Generated from
operatorstack/intelligence-flow@7f71d4816931f34405b6c9a6bccca0eb4e29021f.Review provenance, tests, and examples before merging.