Create docs pages for Runtime, MCP, Schemas, and API; rebuild runtime page#237
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Motivation
Description
public/runtime.htmlinto a light/docs style runtime page documenting that the runtime is the production signer (signer_idruntime.commandlayer.eth, kidvC4WbcNoq2znSCiQ), the canonicalmetadata.prooffields (json.sorted_keys.v1,SHA-256,Ed25519), Trust Verification v1 endpoints, and trust-boundary guidance.public/mcp.html,public/schemas.html, andpublic/api.htmlimplementing the requested MCP-bridge positioning (MCP is a bridge, not the signer), schema hub content (canonical proof envelope + warning that schema-valid != verified), and API overview (runtime/MCP/verifier surfaces, example curls, and response states), while keeping nav/dropdown and footer links consistent with the existing docs pattern.Testing
npm installwhich completed successfully.npm testand all automated tests passed (26tests,0failures).npm run buildwhich failed because the repository has nobuildscript defined inpackage.json.Codex Task