Repository navigation
docs: verify local example with public runtime 0.4.0a1 - #15
Merged
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.
The documented local agent-loop example was rerun from a fresh public Python runtime installation and the locked Node source build. Health, command stdout, file bytes and owned server-process termination passed. Refresh the runtime pin to 0.4.0a1 and preserve earlier evidence.
Fixes #14. The initial stale-workspace path report was corrected after checking current main; no runtime code change is needed.
Validation: npm ci/build, real node examples/agent-loop.mjs, typecheck, 24 Node tests and git diff --check passed. This is local HTTP/process acceptance, not cloud or model acceptance.