[runtime] add remaining trust-verification v1 receipt endpoints#73
Merged
GsCommand merged 1 commit intoMay 20, 2026
Merged
Conversation
Why: complete runtime-backed canonical receipt coverage for all Trust Verification v1 verbs with existing signing flow. Contract impact: none
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
signendpoint so clients can obtain signed canonical receipts for all trust-verification actions.makeReceiptflow to ensure canonicalmetadata.proofand consistent verification behavior without accepting request-provided private keys.Description
POST /trust-verification/<verb>/v1.0.0routes for verbs:sign,attest,authorize,approve,reject,permit,grant,authenticate, andendorsevia a shared loop inserver.mjs.{ payload }and returns400witherror: "missing_payload"when missing, using the existingextractSignPayloadhelper.executionobject withentry: <canonical>/trust-verification/<verb>,verb,version: "1.0.0", andclass: "trust-verification", then emits a signed receipt via the existingmakeReceiptflow (no request-side private key handling added). The emitted response is wrapped withwrapReceiptResponsesoreceipt.metadata.proofis present.runtime/tests/runtime-signing.test.mjsto exercise each verb for: proof presence, verb/class/version fields, proof algs (Ed25519/SHA-256), successful/verifyverification, tamper detection, and missing-payload rejection.server.mjs,runtime/tests/runtime-signing.test.mjs.Testing
npm install,npm run check,npm test, andnpm run ci.metadata.proof, thatexecution/receipt fields reflectverb,class: "trust-verification", andversion: "1.0.0", thatproof.signature.alg === "Ed25519"andproof.hash.alg === "SHA-256", that/verifyaccepts the produced receipt, and that tampering invalidates the receipt signature.Codex Task