Lead public copy with holdings-scoped positioning#89
Merged
Conversation
Refresh README, registry description, discovery strings, and exchange phrasing (examples, not a cap) ahead of org migration.
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.
Summary
server.json, and PyPI metadata to lead withportfolio/holdings-scoped context; allocation math stays opt-in.
bazaar.py(llms.txt, x402 manifest,server card, Bazaar) with ADR-012 exchange phrasing (examples, not a cap).
get_portfolio_statetool copy in bazaar and stdio MCP server.Test plan
pytest -q(375 passed)