fix(demo): use the managed analysis runtime - #19
Merged
Conversation
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 changed
Why
Braid owns an isolated analysis runtime. The demo incorrectly required an unrelated system Python installation to match it, so a valid installed package could fail before the product ran.
Direct product use
Installed
@tangle-network/braid@0.1.1was used against CLI Bridgemainat9658c4cwith Pi 0.83.0 andpi/tangle-router/glm-5.2. A typed slugify task completed in 54.5 seconds, rendered nine tool calls, wrote the implementation and tests, and independently passed 9/9 tests./activityshowed the retained run, AgentProfile, local execution, provider session, 17,966 input tokens, 2,247 output tokens, seven model calls, and complete history.Checks
pnpm checkpnpm typecheck