Rebuild SDK page as developer entry for @commandlayer/agent-sdk@1.2.0#231
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
@commandlayer/agent-sdk@1.2.0that serves as the recommended entry point for integrating verifiable receipts.metadata.prooffields and recommended developer usage patterns (includingprivateKeyPem).Description
public/sdk-records.htmlas the SDK landing page and added the requested sections: Hero, Install (with version), Quickstart (usingprivateKeyPemandkeyId), Receipt shape, "What the SDK does" / "does not do", Runtime vs SDK, Trust Verification verbs, Verification states, CTAs, and footer updates.Home,Protocol,Capabilities,Verifier,SDK,Docs,Claim,GitHub) and kept the light ENS/Stripe visual direction consistent with existing pages.metadata.proofwithjson.sorted_keys.v1,SHA-256,Ed25519,kid = vC4WbcNoq2znSCiQ, andsigner_id = runtime.commandlayer.eth, and removed legacy fields likeprivateKey, top-levelproof, and lowercase algorithm labels.Testing
npm installsuccessfully without dependency errors.npm testand all automated tests passed (26tests passing).npm run buildwhich failed due to a missingbuildscript in the project (no change made to project scripts).Codex Task