docs: repoint stale nexus-contract ref + adapter→in-crate aggregate-runner (#66)#131
Merged
Merged
Conversation
…unner (#66) - #59 refs were stale (no such issue on the public repo); the nexus integration contract lives on the private bombay-nexus#4 board. - Reframe the 'nexus adapter' bullet: per #66 there is no separate adapter crate — the aggregate-runner is an in-crate module behind the 'aggregate' feature, with nexus + nexus-store as feature-gated deps.
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.
Docs-only CLAUDE.md fixes from the #66 design thread.
#59refs → the nexus integration contract; that issue number does not exist on this public repo. The contract lives on the privatebombay-nexus#4board (marked private inline).aggregatefeature, withnexus+nexus-storeas feature-gated deps.No code change; 2 lines in CLAUDE.md.
Refs #66.