Rebuild schemas reference page with protocol-ready documentation#249
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
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
public/schemas.htmlfrom a minimal/unstable stub into a senior-developer protocol schema reference page with correct nav/footer and infrastructure-level guidance.Description
public/schemas.htmlwith a full protocol-ready reference page that matches the site header/nav/dropdown/footer style used by other rebuilt docs pages.metadata.proof.canonicalization = "json.sorted_keys.v1",metadata.proof.hash.alg = "SHA-256",metadata.proof.signature.alg = "Ed25519",metadata.proof.signature.kid = "vC4WbcNoq2znSCiQ",metadata.proof.signer_id = "runtime.commandlayer.eth"), Trust Verification v1 family and live verbs, expected file/path model table, schema validation vs cryptographic verification, capability expansion model, developer usage flow, and compact request/receipt snippets.Testing
npm installsuccessfully.npm testand all automated tests passed (26tests passed,0failed).npm run buildbut the repository does not define abuildscript, so no build step was executed.Codex Task