docs(agave): add implementation reference profile - #30
Draft
linuskendall wants to merge 3 commits into
Draft
linuskendall wants to merge 3 commits into
linuskendall wants to merge 3 commits into
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.
AI description, click for details
Refs SVM-425
Closes SVM-426
Adds an Agave reference profile for all published methods and every standard-method or extension PR in the current review series. It pins the reviewed Agave and specs revisions, links published pages directly, uses stable PR links for pending pages, and maps each contract to its Agave handler and processor. The index now covers all 53 public HTTP registrations and all 18 WebSocket subscription lifecycle registrations at the pinned revision, including the 38 method pages in draft PRs #33 through #70.
The static review supports
Fullfor 14 published, 41 pending HTTP, and 16 pending WebSocket contracts, subject to the documented service flags for block and vote subscriptions. Agave lacks all five proposed extensions: three are partial extensions of existing methods and two introduce absent method names. The review also records that current Agave accepts an additiveminContextSlotfield ongetTransactionwhich the current specs do not document.Validation:
npm run validate,npm test,npx tsc --noEmit, andgit diff --check.🤖 Generated with AI