create-zkp2p-provider

name	create-zkp2p-provider
description	Create or update Peer (ZKP2P) provider capture templates for buyer TEE, identity, and payment flows. Use when capturing an authenticated platform request, mapping transaction metadata and public parameters, adding a provider action type, or testing a provider through PeerAuth and the developer portal.

Create a Peer provider

Turn an authenticated website request into a provider template that PeerAuth can capture safely and the attestation service can verify.

Protect the boundary

• Treat browser requests, responses, cookies, tokens, and customer data as sensitive. Never paste them into a public issue, skill, commit, or PR.
• Keep raw captures local and short-lived. Share only sanitized field shapes, selectors, and synthetic examples.
• Ask before controlling an authenticated browser or reading network traffic.
• Never persist secrets in paramNames, metadata rows, logs, fixtures, or screenshots.

Use the current TEE model

A provider template is a capture and metadata contract. It tells PeerAuth which request to observe or replay and which non-secret values to expose. PeerAuth encrypts the authenticated session material; the attestation service owns the verification policy and signed result.

Do not add retired Reclaim-only fields to a new template:

• proofEngine
• skipRequestHeaders
• secretHeaders
• responseMatches
• responseRedactions
• additionalProofs

The public provider service removes these keys. If a legacy consumer still needs one, stop and identify that exact consumer before changing the template.

Read runtime-contract.md before changing a provider that spans PeerAuth, mobile, or the attestation service.