Rebuild public API reference into full infrastructure docs page#248
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/api.htmlwas a minimal index and needed to become a developer-facing API reference with the rebuilt site header, Docs dropdown, and footer.Description
public/api.htmlcontents with a full API Reference page that uses the same header/nav/docs dropdown and footer style as rebuilt docs pages./api/verify), request/response conventions, canonicalmetadata.prooffields, error/status model, security/trust boundaries, developer integration paths, and final CTAs.metadata.proof,json.sorted_keys.v1,SHA-256,Ed25519,vC4WbcNoq2znSCiQ, andruntime.commandlayer.eth.public/api.html, with no API behavior or schema modifications.Testing
npm installwhich completed successfully using the repository dependencies.npm testand all automated tests passed (26/26passing).npm run buildwhich failed because the repository does not define abuildscript, so no site build artifact was produced.Codex Task