Rebuild production proof page (stack-proof-demo) and update proof links#229
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
/verify.html.metadata.prooffields and the verified production signer/key details.Description
public/stack-proof-demo.htmlwith the requested light ENS/Stripe visual direction and required sections: hero, three-step proof outcome strip, architecture flow with explicit trust boundaries, canonical receipt example usingmetadata.proof, valid/invalid verification response cards, local run (terminal) block, and “what this proves / does not claim” copy.public/capabilities.htmlto point its hero "View Proof" CTA and footer proof links to/stack-proof-demo.html(no top-nav changes were made and the page remains distinct from/verify.html).json.sorted_keys.v1,SHA-256,Ed25519,vC4WbcNoq2znSCiQ, andruntime.commandlayer.eth, and removed/avoided stale or overclaiming language about signing/trust roots.Testing
npm installsuccessfully in the repository environment and dependencies are up-to-date.npm testand the test suite passed (26 tests, all passing).npm run buildand it failed because there is nobuildscript defined inpackage.json(this is informational and no build artifacts were required for the change).Codex Task