[runtime] sync docs to v1.1.0 runtime cut#21
Merged
Conversation
Why: align runtime-layer docs with the v1.1.0 route, x402 default, and schema-validation behavior described for this cut. Contract impact: none
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.
Motivation
server.mjsfor thev1.1.0cut (route version, fabricated x402 defaults, and schema validation targets).v1.0.0and prevent stale guidance about schema resolution and x402 defaults.Description
README.mdto reference the live verb routes asPOST /<verb>/v1.1.0, state that schema validation targets thev1.1.0receipt schema tree underSCHEMA_HOST, and document that the runtime fabricatesx402.versionandx402.entrydefaults using the live API version (1.1.0) when callers omitx402.docs/CONFIGURATION.mdto changeAPI_VERSIONreferences to1.1.0, document the fabricatedx402defaults for omitted request metadata, and state thatSCHEMA_HOSTis used to constructv1.1.0receipt schema URLs during/verify?schema=1.docs/OPERATIONS.mdto describe the activePOST /<verb>/v1.1.0routes, the fabricatedx402defaults behavior, and that schema warmup/validation targets thev1.1.0schema path.SECURITY.mdsupported versions entry to1.1.xand added a narrowly scoped note about schema resolution targetingv1.1.0and the fabricatedx402defaults; no changes to signing/ENS claims were introduced.Testing
npm test; all tests passed (unit tests andtests/smoke.mjscompleted successfully).v1.0.0references in the modified doc files and validated the committed diff.Codex Task