docs(ats): show browser order contract and actual execution gates - #165
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
1 participant
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
Update the 0.4.0 source-candidate README to reflect merged Agent #164 and ATSv2 #444: the browser order wire and cross-language validators are present, while no browser order tool or trading-site adapter is registered. Distinguish ATS simulated paper from a paper account in Agent Browser and state the current runtime, paper and live gates.
Verification
npm run verify:production: 890 packed files, 4,844,612 / 5,000,000 unpacked bytes.node --test --test-isolation=none dist/test/ats_browser_order.test.js dist/test/ats_runtime_supervisor.test.js dist/test/ats_agent.test.js: 101 passed.python3 test/fixtures/ats_browser_order_verify.py: 189 vectors reproduced.npm run docs:check: six outputs verified.The npm package is already versioned 0.4.0 in source, while npm latest is 0.3.2. This documentation change does not publish, tag, or enable any execution path. The candidate packet still requires release qualification.