Sync Boatstack from Intelligence Flow Labs @ f671638f234f - #116
Merged
operator-stack-publisher[bot] merged 1 commit intoJul 26, 2026
Merged
Conversation
operator-stack-publisher
Bot
deleted the
sync/intelligence-flow-f671638f234f
branch
July 26, 2026 02:54
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
Concurrent first use hydrates the shared runtime exactly once
When several tool calls hit an empty shared-runtime slot at the same time, one guard hydrates
the slot and the others wait. A guard tests whether the slot is missing, then takes a
clone-wide lock to hydrate it. A slow guard could reach the lock only after the winner had
already finished and released it. Its test result was stale, so it took the lock and ran the
installer a second time.
The guard now re-tests the slot after it takes the lock and runs the installer only if the
slot is still missing or incomplete. So exactly one hydration happens under contention. This
also narrows the window where a peer is writing the helper while another guard starts it,
which complements the retry that already handles that case on Linux.
Projection provenance
Generated from
operatorstack/intelligence-flow@f671638f234faa96ea85336e9a76b164020df172.Review provenance, tests, and examples before merging.