From 8d24c51e960ebaec640e07ad53b532d993ba9a4f Mon Sep 17 00:00:00 2001
From: "Claude (Cowork)" <claude@anthropic.com>
Date: Thu, 25 Jun 2026 16:18:25 -0500
Subject: [PATCH 01/10] docs: slim README to shield-first beta positioning

Co-authored-by: Cursor <cursoragent@cursor.com>
---
 README.md | 807 ++++--------------------------------------------------
 1 file changed, 56 insertions(+), 751 deletions(-)

diff --git a/README.md b/README.md
index 77fb7a46..22e41140 100644
--- a/README.md
+++ b/README.md
@@ -2,148 +2,68 @@
 
 **Shield first. Move privately.**
 
-Vanta is a shield-first beta privacy app for supported Solana assets.
-
-The simple version:
-
-- Normal Solana wallets are public.
-- Vanta lets supported assets move into a more private Vanta area through Shield.
-- From there, the app exposes constrained private-core lanes: Send, Swap, and Unshield.
-- Additional preview lanes include Pay (merchant checkout and settlement records), Strategy (planning), Proof (trust packets), and product workbenches on `/products`.
-
-The honest status:
-
-- Some parts are real and verifiable today.
-- Some parts are still narrow demos or previews.
-- Vanta is not production-ready or mainnet-ready yet.
-- Do not use this repo as an audited payment processor, custody system, or final privacy network.
-
-If you only read one thing, read this mental model:
+Vanta is a shield-first beta privacy app for supported Solana assets. Users move assets out of public wallet flows into a private Vanta area, then act inside constrained lanes (Send, Swap, Unshield). Some surfaces are real and verifiable today; others are narrow previews. **Vanta is not production-ready or mainnet-ready.**
 
 ```text
 Public Wallet -> Shield -> Private Vanta Area -> Send / Swap / Unshield
-                                              -> Pay / Strategy / Proof (preview lanes)
+                                              -> Pay / Strategy / Proof (preview)
 ```
 
 ---
 
-## What Normal People Should Know
-
-The app at `/app` is shield-first. Primary tabs are **Shield**, **Send**, **Swap**, and **Unshield**. The **More** menu adds **Pay**, **Strategy**, **Proof**, **Recovery**, and **Launch** preview surfaces.
-
-- **Shield / Send / Swap / Unshield** are the core private-settlement lanes. They move supported assets into Vanta, act inside shielded state, and exit again when needed.
-- **Pay** is one bounded merchant lane among several — a preview for payment requests, checkout modes, settlement records, and verifiable receipts. It is not the headline product.
-- **Strategy**, **Proof**, **`/products`**, and **`/receipt/:receiptId`** are additional beta or reviewer surfaces for planning, trust packets, product workbenches, and counterparty receipt checks.
-
-Docs at `/docs` explain the same lanes in plainer language. `/docs/portal` is a docs track name for the shield-first wallet flow — not a separate app users open instead of `/app`.
+## Who it's for
 
-Reviewer and operator surfaces stay separate from normal user copy. They exist so claims can be checked, not so every user learns protocol vocabulary.
+- **Users** who want a clearer path from public balances into shielded state and back.
+- **Counterparties** who need receipts or trust packets they can inspect — not abstract privacy claims.
+- **Reviewers and design partners** who want bounded, command-verifiable behavior without learning protocol vocabulary first.
 
-Vanta grows when private actions produce receipts or trust packets that counterparties can inspect — not when privacy stays abstract.
-
-## What Works Today
-
-Today, Vanta is a constrained development system, not a finished network.
-
-Working or inspectable today:
-
-- wallet connection and public balance detection
-- shield flows for supported mainnet assets and shielded state inside Vanta
-- constrained send, swap, and unshield paths backed by the narrow private-core operator lane
-- proof and operator checks for that private-core lane, plus Private Pool v2 benchmark seams
-- app tabs for Shield, Send, Swap, Unshield, Strategy preview, Proof/trust packets, recovery settings, and dashboard diagnostics
-- `/products` workbench surfaces (Compliance Gateway, Private Perps Engine, Shielded RWA Tokenization, Privacy SDK marketplace, Private Velocity Intelligence) with redacted trust-packet generation
-- public receipt verification at `/receipt/:receiptId`
-- a `/app/pay` merchant preview lane: payment creation, checkout modes, settlement records, refunds, withdrawals, reconciliation, receipt preview, and beta/no-funds disclosure — verifiable through Pay commands, but still preview-only
-- repo-local proof-artifact handoff checks that reject relabelled local metadata and remote verifier receipt transcript drift without claiming a live proof service
-- verification commands that keep the repo honest about what is still unfinished
-
-Still not live or final:
+---
 
-- audited production privacy
-- broad multi-asset support
-- final proof and nullifier architecture
-- production Pay processor semantics
-- live autonomous Strategy execution
-- mainnet private settlement
-- production custody, compliance, and incident-response guarantees
+## Core lanes
 
-Vanta is not production-ready until it has real mainnet-compatible private settlement, audited proof/circuit boundaries, persistent operator/indexer/relayer services, secure key/secret handling, replay/nullifier protection, browser-verified UX, production deployment docs, and a truthful security limitations page.
+Primary app tabs at `/app` (defaults to Shield):
 
-## Pricing
+| Lane | Role |
+|------|------|
+| **Shield** | Move supported assets into Vanta's private flow |
+| **Send** | Act on shielded state |
+| **Swap** | Constrained swap inside shielded state |
+| **Unshield** | Exit back to public flows |
 
-- `0 monthly fee`
-- `0.25%` only when Pay, Shield, Send, Swap, or Unshield completes successfully
-- network, off-ramp, and third-party execution costs stay separate when they apply
+**More menu (preview lanes):** Pay, Strategy, Proof, Recovery, Launch. These are bounded beta or reviewer surfaces — not the headline product.
 
-Pricing only applies when Vanta is actually providing a completed Pay, Shield, Send, Swap, or Unshield action. Preview-only surfaces must not imply a fee is already active.
+**Also:** `/products` workbenches (Compliance Gateway, Private Perps, Shielded RWA, Privacy SDK, Velocity Intelligence), public receipt checks at `/receipt/:receiptId`, and docs at `/docs`. `/docs/portal` is a docs track name for the shield-first wallet flow — not a separate app.
 
-Net Vanta-collected fees are reserved for ecosystem growth, including supply buybacks, marketing, operator infrastructure, security, and product development. This excludes network, off-ramp, and third-party pass-through costs.
-
-## Important Privacy Clarification
-
-Shielding does not make an ordinary wallet magically private.
+---
 
-It means supported assets leave the normal public-wallet flow and enter Vanta's private flow. Privacy claims only start there, and only for the specific lanes Vanta currently supports.
+## What works vs. what doesn't
 
-## Where To Start
+**Inspectable today:** wallet connection, shield flows for supported assets, constrained Send/Swap/Unshield paths, proof and operator checks for the narrow private-core lane, app tabs and diagnostics, receipt verification, and verification commands that keep claims honest.
 
-- App shell (Shield first): `/app` → `/app/shield`
-- Product docs: `/docs` (shield-first wallet flow at `/docs/portal`; Pay docs at `/docs/pay`)
-- Product workbenches: `/products`
-- Merchant Pay preview: `/app/pay`
-- Trust and receipt checks: `/app/proof`, `/receipt/:receiptId`
-- Security limits: `SECURITY_LIMITATIONS.md`
-- Audit handoff: `docs/audit-package.md`
-- Operator runbook: `docs/operator-runbook.md`
+**Not live or final:** audited production privacy, broad multi-asset support, final proof/nullifier architecture, production Pay processor semantics, live Strategy execution, mainnet private settlement, or production custody/compliance guarantees.
 
-The detailed command lists below are for engineers and reviewers.
+See `SECURITY_LIMITATIONS.md` for the full boundary list.
 
 ---
 
-## Stack
-
-- Vite
-- React 18
-- TypeScript
-- React Router
-- custom CSS design system
-
----
+## Pricing
 
-## Routes
+- `0` monthly fee
+- `0.25%` only when Pay, Shield, Send, Swap, or Unshield completes successfully
+- Network, off-ramp, and third-party costs stay separate
 
-- `/` marketing homepage
-- `/manifesto`
-- `/products` and `/products/:productSlug`
-- `/docs`, `/docs/portal`, `/docs/pay`, `/docs/trust`, `/docs/security`, `/docs/roadmap`
-- `/app` app shell (defaults to Shield)
-- `/app/dashboard`
-- `/app/shield`, `/app/send`, `/app/swap`, `/app/unshield` (primary tabs)
-- `/app/pay`, `/app/strategy`, `/app/proof`, `/app/launch` (More menu / preview lanes)
-- `/app/settings/recovery`, `/app/privacy-review`, `/app/actual-private-settlement`
-- `/receipt/:receiptId`
+Preview-only surfaces must not imply fees are active.
 
 ---
 
-## Project structure
+## Where to start
 
-```text
-.
-├── index.html
-├── package.json
-├── src
-│ ├── App.tsx
-│ ├── components
-│ ├── context
-│ ├── data
-│ ├── main.tsx
-│ ├── pages
-│ └── styles.css
-├── tsconfig.app.json
-├── tsconfig.json
-└── vite.config.ts
-```
+- **App:** `/app` → `/app/shield`
+- **Docs:** `/docs` (wallet flow at `/docs/portal`, Pay at `/docs/pay`)
+- **Pay preview:** `/app/pay`
+- **Trust / receipts:** `/app/proof`, `/receipt/:receiptId`
+- **Security limits:** `SECURITY_LIMITATIONS.md`
+- **Reviewer handoff:** `docs/audit-package.md`, `docs/operator-runbook.md`
 
 ---
 
@@ -154,20 +74,18 @@ npm install
 npm run dev
 ```
 
-Then open the local Vite URL shown in the terminal.
-
----
-
-## Build
-
 ```bash
 npm run build
 npm run preview
 ```
 
-## Reviewer proof points
+**Stack:** Vite, React 18, TypeScript, React Router, custom CSS.
+
+---
+
+## Verification
 
-If you need the shortest honest command set for a reviewer, operator, or design partner, use:
+Shortest honest reviewer set:
 
 ```bash
 npm run build
@@ -179,663 +97,50 @@ npm run mainnet:transaction-evidence-check
 npm run mainnet:readiness-check
 ```
 
-These commands prove the current app compiles, primary and preview user surfaces render, the private-core proof lane is demo-ready, Pay preview contracts stay aligned with trust surfaces where implemented, transaction language is bounded by current implementation truth, and the repo is still honest about not being production-ready yet.
-
-`Transaction Evidence v0.1` is a reviewer-facing trace for current mainnet, local, preview, and operator-harness flows. It can name transaction summaries, simulation/approval requirements, signatures or operator request ids when present, confirmation status when present, and proof/root/nullifier or settlement receipt linkage when present. It is not mainnet finality, audit approval, custody proof, live privacy proof, or production settlement.
-
-## Private Core verification
+Private-core lane:
 
 ```bash
-npm run mainnet:readiness
-npm run mainnet:readiness-json
-npm run mainnet:preflight
-npm run mainnet:readiness-check
-npm run mainnet:external-gates-check
-npm run mainnet:service-contract-check
-npm run mainnet:service-topology-check
-npm run mainnet:service-deployment-status
-npm run mainnet:service-deployment-evidence-check
-npm run mainnet:storage-contract-check
-npm run mainnet:storage-migration-check
-npm run mainnet:backup-restore-check
-npm run storage:adapter-check
-npm run mainnet:abuse-observability-check
-npm run mainnet:abuse-observability-status
-npm run mainnet:abuse-observability-runtime-status
-npm run mainnet:abuse-observability-evidence-check
-npm run ops:rate-limit-check
-npm run ops:safe-telemetry-check
-npm run mainnet:observability-sink-check
-npm run nullifier:replay-guard-check
-npm run mainnet:deployment-manifest-check
-npm run mainnet:private-rail-route-status-check
-npm run mainnet:private-rail-route-health
-npm run mainnet:private-rail-route-health-auth
-npm run mainnet:private-rail-route-health-evidence-check
-npm run mainnet:wallet-signing-status
-npm run mainnet:wallet-production-browser-check
-npm run mainnet:wallet-signing-evidence-check
-npm run wallet:signing-safety-check
-npm run wallet:transaction-safety-check
-npm run wallet:backed-simulation-check
-npm run wallet:message-intent-safety-check
-npm run wallet:message-intent-adoption-check
-npm run umbra:wallet-adapter-gate-check
-npm run umbra:operation-gate-adoption-check
-npm run umbra:operation-summary-check
-npm run umbra:operation-client-summary-gate-check
-npm run umbra:operation-summary-builders-check
-npm run umbra:operation-summary-display-check
-npm run umbra:benchmark-approval-samples-check
-npm run umbra:approval-review-page-check
-npm run umbra:approval-review-page-browser-check
-npm run umbra:shield-action-review-check
-npm run umbra:unshield-action-review-check
-npm run wallet:live-send-inventory-check
-npm run wallet:safe-send-boundary-check
-npm run wallet:safe-send-hook-check
-npm run shield:safe-send-adoption-check
-npm run send:safe-send-adoption-check
-npm run swap:safe-send-adoption-check
-npm run unshield:safe-send-adoption-check
-npm run mainnet:secret-handling-check
-npm run audit:package-check
 npm run private-core:check
-npm run private-core:send-check
-npm run private-core:swap-check
-npm run private-core:send-apply-check
-npm run private-core:swap-apply-check
-npm run private-core:send-continuity-check
-npm run private-core:send-recipient-check
-npm run private-core:send-chain-check
-npm run private-core:send-roundtrip-check
-npm run private-core:send-unshield-roundtrip-check
-npm run private-core:send-change-unshield-check
-npm run private-core:send-chain-unshield-check
-npm run private-core:send-chain-http-smoke
-npm run private-core:restart-check
-npm run private-core:send-chain-restart-check
-npm run private-core:send-unshield-restart-check
-npm run private-core:send-change-unshield-restart-check
-npm run private-core:send-chain-unshield-restart-check
-npm run private-core:prove
-npm run private-core:send-prove
-npm run private-core:swap-prove
-npm run strategy:planner-check
-npm run strategy:execution-adapter-check
-npm run strategy:runtime-check
-npm run strategy-tab:copy-check
-npm run private-core:swap-boundary-check
-npm run private-core:swap-live-path-check
-npm run private-core:swap-unshield-roundtrip-check
-npm run private-core:contract-smoke
-npm run private-core:send-http-smoke
-npm run private-core:swap-http-smoke
-npm run private-core:swap-transition-http-smoke
-npm run private-core:swap-restart-check
-npm run private-core:swap-unshield-restart-check
-npm run protocol:browser-check
 npm run private-core:verify
-npm run private-core:demo-readiness
 npm run private-core:demo-preflight
 npm run private-core:operator-contract
 npm run private-core:operator-status
-npm run private-core:operator-snapshot
 npm run private-core:operator-status-check
-npm run private-core:operator-status-check-json
-npm run private-core:operator-snapshot-json
-npm run private-core:operator-snapshot-check
-npm run private-core:operator-snapshot-check-json
-npm run private-core:shipping-artifact
-npm run private-core:shipping-artifact-json
-npm run private-core:shipping-artifact-check
-npm run private-core:shipping-artifact-check-json
-npm run private-core:release-candidate
-npm run private-core:release-candidate-json
-npm run private-core:release-candidate-check
-npm run private-core:release-candidate-check-json
-npm run private-core:release-package
-npm run private-core:release-package-json
-npm run private-core:release-package-check
-npm run private-core:release-package-check-json
-npm run private-core:shipping-status
-npm run private-core:shipping-check
 ```
 
-These commands cover:
-- fixed-depth Noir circuit regression
-- fixed-depth send-circuit regression
-- fixed-depth swap-circuit regression
-- live held-note plus live-quote swap-path readiness and fallback regression
-- in-app swap live-path truth surfaces now show:
-  - ready vs blocked vs fixture fallback
-  - primary blocker when blocked
-  - persisted execution venue and quote reference for the last applied shared swap handoff
-- source-layer send transition application and change-note recovery
-- send-to-hold-to-unshield continuity after a private send
-- recipient-side note recovery and spendability after a private send
-- chained private-send continuity from one recipient into a second private send
-- operator-backed private send roundtrip from verified send transition to recipient recovery
-- operator-backed private send to recipient unshield roundtrip
-- operator-backed private send to sender-change unshield roundtrip
-- operator-backed chained private send to recipient unshield roundtrip
-- operator-backed chained private-send continuity across two verified send transitions
-- operator-backed private send now requires the current input root to be registered before transition
-- operator-backed private send now requires that current input root to remain linked to its registration proof
-- operator-backed private send transitions now require an explicit canonical resulting root that differs from the input root
-- operator-backed send state now marks resulting roots honestly as `client-declared` until later root registration proves continuity
-- downstream root registration now records whether continuity was proven through a send recipient output, a send change output, or a swap output
-- operator-backed chained private-send persistence across operator restart
-- operator-backed private send to recipient unshield persistence across operator restart
-- operator-backed private send to sender-change unshield persistence across operator restart
-- operator-backed chained private send to recipient unshield persistence across operator restart
-- valid and invalid witness behavior
-- local unshield proof generation and verification
-- local send proof generation and verification
-- local swap proof generation and verification
-- operator-backed constrained swap to recipient-unshield roundtrip
-- operator-backed constrained swap to recipient-unshield persistence across operator restart
-- dedicated operator-contract endpoint coverage
-- operator-backed send proof HTTP smoke coverage and persisted send-proof state
-- operator-backed swap proof HTTP smoke coverage and persisted swap-proof state
-- operator-backed proof-backed swap-transition HTTP smoke coverage and persisted swap-transition state
-- swap proof and swap-transition persistence across operator restart
-- operator-backed consume and HTTP smoke coverage
-- operator state persistence across restart, including send-proof state
-- proof-backed send-transition state persistence across restart
-- replay rejection after operator restart
-- operator contract and summary snapshot coherence across app, CLI, and regression surfaces
-- dedicated operator shipping decision endpoint and CLI/check surfaces
-- frozen operator contract surface:
-  - `contractVersion = 23`
-  - `summaryVersion = 47`
-  - `supportedSendV1Decision = accepted-narrow-v1-path`
-  - `supportedUnshieldV1Decision = accepted-narrow-v1-path`
-  - `supportedReleaseV1Decision = accepted-narrow-v1-path`
-  - `supportedSwapV1Decision = accepted-narrow-v1-path`
-  - `supportedShippingDecisionKind = narrow-private-core-zk-v1-shipping`
-  - `supportedOperatorSnapshotKind = contract-status-shipping-bundle`
-  - `supportedSwapLaneKind = single-input-usdc-to-allowlisted-shielded-output`
-  - `supportedSwapVenue = meteora-dlmm-mainnet-and-operator-token-output`
-  - `supportedPrivateCoreCircuitFamily = vanta_private_core_single_note`
-  - `supportedPrivateCoreCircuitFamilyStatus = active-v0-legacy`
-  - `supportedPrivateCoreCircuitFamilyNewArchitectureStatus = deprecated-for-new-architecture`
-  - `supportedPrivateCoreReplacementFamily = vanta_private_pool_v2_entry`
-
-The `vanta_private_core_single_note_*` family is an active-v0 legacy compatibility surface for current flows, not the new architecture target; new circuit work should route through the Private Pool v2 entry family or an explicitly reviewed replacement.
-
-## Private Pool v2 / Option B verification
+Private Pool v2 benchmark lane:
 
 ```bash
-npm run mainnet:preflight
-npm run mainnet:external-gates-check
-npm run mainnet:service-contract-check
-npm run mainnet:service-topology-check
-npm run mainnet:service-deployment-status
-npm run mainnet:service-deployment-evidence-check
-npm run mainnet:storage-contract-check
-npm run mainnet:storage-migration-check
-npm run mainnet:backup-restore-check
-npm run storage:adapter-check
-npm run mainnet:abuse-observability-check
-npm run mainnet:abuse-observability-status
-npm run mainnet:abuse-observability-runtime-status
-npm run mainnet:abuse-observability-evidence-check
-npm run ops:rate-limit-check
-npm run ops:safe-telemetry-check
-npm run mainnet:observability-sink-check
-npm run nullifier:replay-guard-check
-npm run mainnet:deployment-manifest-check
-npm run mainnet:wallet-signing-status
-npm run mainnet:wallet-production-browser-check
-npm run mainnet:wallet-signing-evidence-check
-npm run wallet:signing-safety-check
-npm run wallet:transaction-safety-check
-npm run wallet:backed-simulation-check
-npm run wallet:message-intent-safety-check
-npm run wallet:message-intent-adoption-check
-npm run umbra:wallet-adapter-gate-check
-npm run umbra:operation-gate-adoption-check
-npm run umbra:operation-summary-check
-npm run umbra:operation-client-summary-gate-check
-npm run umbra:operation-summary-builders-check
-npm run umbra:operation-summary-display-check
-npm run umbra:benchmark-approval-samples-check
-npm run umbra:approval-review-page-check
-npm run umbra:approval-review-page-browser-check
-npm run umbra:shield-action-review-check
-npm run umbra:unshield-action-review-check
-npm run wallet:live-send-inventory-check
-npm run wallet:safe-send-boundary-check
-npm run wallet:safe-send-hook-check
-npm run shield:safe-send-adoption-check
-npm run send:safe-send-adoption-check
-npm run swap:safe-send-adoption-check
-npm run unshield:safe-send-adoption-check
-npm run mainnet:secret-handling-check
-npm run audit:package-check
-npm run pay-tab:copy-check
-npm run pay:status
-npm run pay:status-json
-npm run pay:operator
-npm run pay:merchant-api-check
-npm run pay:production-private-rail-guard-check
-npm run pay:browser-check
-npm run protocol:browser-check
-npm run pay:verify
-npm run security:limitations-check
-npm run zk:c01-local-proof-format-evidence-check
-npm run private-pool-v2:contract-check
-npm run private-pool-v2:root-provenance-check
-npm run private-pool-v2:local-runtime-check
-npm run private-pool-v2:local-bb-fixture-prover-check
-npm run private-pool-v2:browser-worker-proof-result-adapter-check
-npm run private-pool-v2:send-witness-prover-check
-npm run private-pool-v2:proof-backend-boundary-check
-npm run private-pool-v2:remote-proof-artifact-boundary-check
-npm run private-pool-v2:shield-proof-request-check
-npm run private-pool-v2:claim-proof-request-check
-npm run private-pool-v2:send-proof-artifact-consistency-check
-npm run private-pool-v2:actual-private-spend-proof-artifact-consistency-check
-npm run private-pool-v2:send-operator-no-witness-check
-npm run private-pool-v2:actual-private-spend-operator-no-witness-check
-npm run private-pool-v2:shield-circuit-check
-npm run private-pool-v2:claim-circuit-check
-npm run private-pool-v2:shield-prove
-npm run private-pool-v2:claim-prove
-npm run private-pool-v2:status
-npm run private-pool-v2:status-json
-npm run private-pool-v2:operator
-npm run private-pool-v2:http-smoke
-npm run private-pool-v2:protocol-client-check
-npm run private-pool-v2:postgres-store-check
-npm run private-pool-v2:restart-check
 npm run private-pool-v2:verify
+npm run private-pool-v2:status
 ```
 
-These commands cover the current Vanta-owned Private Pool v2 benchmark lane:
-- typed indexer, relayer, prover, protocol, shield proof request, and claim proof request surfaces
-- a checked external-gates packet for deployed service refs, secret-manager refs, audit/legal/custody refs, monitoring refs, and explicit mainnet-funds approval refs without committing secrets
-- a checked production service topology for the indexer, relayer, prover, verifier, and operator service graph, including mutual-auth edges, fail-closed policies, required storage surfaces, health endpoints, and readiness endpoints
-- a checked production private-rail route-status contract that proves Pay and the production operator route through expected Private Pool v2 URL/token refs without committing token values
-- a sanitized production private-rail route-health status surface that can probe public health and optionally authenticated readiness without printing token values
-- a checked sanitized route-health evidence file for preserving public/authenticated route status without storing credentials
-- local append-only commitment indexing and Merkle proof lookup
-- local prover public-input commitment verification plus tamper rejection
-- an opt-in Shield, Claim, Swap-to-shielded, actual-private-spend, and Send local bb artifact-backed proof-result adapter that returns `noir-bb` / `local-bb-fixture-artifact` for exact verified fixture transcripts binding `shield-public-input-hash`, `claim-public-input-hash`, `swap-public-input-hash`, `private-spend-public-input-hash`, or `send-public-input-hash`; Shield, Claim, Swap-to-shielded, actual-private-spend, and Send can also return `noir-bb` / `local-bb-derived-artifact` from strict local witness inputs whose derived requests bind `shield-public-input-hash`, `claim-public-input-hash`, `swap-public-input-hash`, `private-spend-public-input-hash`, or `send-public-input-hash`; actual-private-spend and Send also have dev-only browser/Web Worker proof execution plus worker-side witness generation from typed witness input, Shield has the same dev-only browser/Web Worker proof execution plus worker-side witness generation from typed witness input, Claim has dev-only Claim browser/Web Worker proof execution plus worker-side witness generation from typed Claim witness input, and Swap-to-shielded now has dev-only Swap-to-shielded browser/Web Worker proof execution plus worker-side witness generation from typed Swap-to-shielded witness input, with Shield binding `shield-public-input-hash`, Claim binding `claim-public-input-hash`, Swap-to-shielded binding `swap-public-input-hash`, actual-private-spend binding `private-spend-public-input-hash`, and Send binding `send-public-input-hash`. An opt-in browser-worker proof-result adapter can wrap those Shield, Claim, Swap-to-shielded, Send, and actual-private-spend worker artifacts into `VantaPrivatePoolV2ProofResult` values only for exact bound proof requests, requires `local-bb-derived-artifact`, and leaves the default local prover on `mock` / `local-mock`. C01 local proof-format observation records the current actual-private-spend local proof as `noir-bb` / `barretenberg-ultrahonk`, 16000 bytes, `local-acir-bytecode-hash-not-production-vk`, and mismatched with the reserved 256-byte Groth16 tag-3 target. H08 now records `selectedRuntimeDirection: remote-service-production-prover` as a local implementation direction, while `selectedProverRuntime` remains null until C01 compatibility, production proof-format/verifying-key evidence, deployed prover health, job-log/artifact refs, valid/invalid proof evidence, no-witness operator acceptance, and audit acceptance exist. These remain local no-real-funds evidence, not live Shield routing, not live Claim routing, not live Swap-to-shielded routing, not live Send or actual-private-spend routing, not production browser-runtime proving, remote proof service, on-chain verifier, production proof-format acceptance, or production proof acceptance
-- local relayer claim submission plus replay rejection
-- local source-only Private Pool v2 root provenance records via `TAG_REGISTER_PROVENANCED_ROOT = 4`, guarded as lineage-bound program-owned metadata for reserved proof/unshield preflights and not as proof that the root transition is correct
-- the first Noir-backed shield-entry circuit with valid, invalid-binding, and invalid-root fixtures
-- the first Noir-backed claim/spend circuit with valid, invalid-binding, and invalid-nullifier fixtures
-- local Barretenberg UltraHonk proof generation and verification for Shield, Claim, Swap-to-shielded, Send, and actual-private-spend fixture lanes
-- a local verifier/receipt registry that accepts verified shield/claim proofs, records receipts, registers claim nullifiers, and rejects replay
-- human and JSON Private Pool v2 status surfaces showing local indexer, prover, relayer, verifier-registry readiness, an explicit fail-closed `productionGate`, and `productionReady: false`
-- a local HTTP operator seam with status, receipt listing, proof submission, shield/claim receipt acceptance, and claim replay rejection
-- deterministic legacy shield/claim shadow commitments on proof receipts and status for reviewer/audit comparison, plus a local committed-Shield boundary where the Noir circuit/fixture binds source/target/amount economics to a Poseidon commitment while operator/capability request paths carry `economics-commitment` handles and hidden-economics sentinels instead of raw proof inputs; this still does not make Shield audited, live-mainnet private, or production-ready
-- operator-owned settlement endpoints for Pay checkout/withdrawal and protocol Shield/Send/Swap/Unshield settlement receipts
-- optional bearer-token protection for the Private Pool v2 operator through `VANTA_PRIVATE_POOL_V2_OPERATOR_AUTH_TOKEN`, plus production startup guards requiring it and either `VANTA_PRIVATE_POOL_V2_STORE_PATH` or `VANTA_PRIVATE_POOL_V2_DATABASE_URL` when `NODE_ENV=production`
-- idempotent settlement endpoints that return existing Pay checkout or protocol settlement receipts for identical repeated settlement IDs, and reject conflicting replays with changed settlement inputs
-- explicit settlement request validation so missing checkout/session, asset, owner, destination, or settlement identifiers fail closed before proof state changes
-- typed shared settlement policy in `src/privacy/privatePoolV2SettlementPolicy.ts`, surfaced on the operator/status contract for validation, idempotency, conflict rejection, restart-safe settlement receipts, and production durable-store requirements
-- machine-readable protocol action proof modes that distinguish current shield/claim circuit request coverage from local send/swap operator proof-request harnesses
-- settlement fingerprints on Pay checkout, Pay withdrawal, and protocol settlement responses for auditability and replay/conflict comparison
-- local operator store schema v2, including persisted settlement policy and persisted settlement fingerprints
-- typed app-side operator-status, protected protocol-settlement, settlement-status, and browser-safe Shield receipt clients when the relevant Private Pool v2 endpoint is configured
-- browser Shield receipts use `VITE_VANTA_PRIVATE_POOL_V2_RECEIPT_API_URL`, default production builds to the public production receipt API, require production native-SOL deposit evidence before receipt issuance, never require a browser-exposed operator bearer token, and are guarded by `npm run frontend:operator-env-exposure-check` against operator/auth-token-shaped `VITE_...` bundle exposure
-- app context state for Private Pool v2 protocol settlement health without exposing protocol vocabulary to normal users
-- a durable local operator store with restart-safe shield/claim receipt restoration, Pay/protocol settlement receipt restoration, shield commitment-tree restoration, and post-restart claim replay rejection
-- optional Private Pool v2 Postgres JSONB snapshot persistence through `VANTA_PRIVATE_POOL_V2_DATABASE_URL`, verified by `npm run private-pool-v2:postgres-store-check`
-- a checked `SECURITY_LIMITATIONS.md` surface that prevents the local benchmark from being described as audited, trustless, or mainnet-production ready
-
-This is still a benchmark/private-pool-v2 construction lane, not a production deployed mixer. It exists to move Vanta from the Umbra comparison into a Vanta-owned privacy-core target with explicit replaceable seams.
-
-Current staging deployment refs:
-
-- Pay is deployed on Render as service `srv-d7j3ggqqqhas739for80` at `https://vanta-0wwi.onrender.com`.
-- Pay uses `postgres-jsonb-snapshot-store` through `VANTA_PAY_DATABASE_URL`.
-- Private Pool v2 is deployed on Render as service `srv-d7j4aod7vvec73ahsqlg` at `https://vanta-staging-private-pool-v2.onrender.com`.
-- Private Pool v2 uses `postgres-jsonb-snapshot-store` through `VANTA_PRIVATE_POOL_V2_DATABASE_URL`.
-- Secret refs are inventoried in `ops/mainnet/secret-references.manifest.json` with reference names only.
-- Doppler is selected as the production secret-manager target in `ops/mainnet/production-secret-manager.template.json`; the template contains refs only and no secret values.
-- The checked deployment and rollback handoff is `docs/mainnet-deployment-runbook.md`.
-- The deployed operator replay-status surface is `npm run mainnet:nullifier-replay-status`. Run `npm run mainnet:nullifier-replay-status-auth` from a Doppler-backed shell when you want authenticated live operator status, and use `ops/mainnet/private-pool-v2-nullifier-replay.evidence.json` as the checked evidence file.
-- That replay evidence also keeps the layered truth explicit: deployed operator reservation, verified role-service duplicate receipt/nullifier rejection, and no-real-funds production smoke replay rejection.
-- Local code now makes the Postgres replay reservation boundary explicit as a transaction-backed `INSERT ... ON CONFLICT DO NOTHING RETURNING ...` path, with global nullifier uniqueness plus context-scoped idempotent request uniqueness. This hardens the operator primitive but does not by itself make Vanta mainnet-production ready.
-- That replay evidence now freezes the current protocol enforcement truth as `operator-claim-preflight-plus-verifier-receipt-idempotency-plus-indexer-nullifier-registration` with the final protocol layer explicitly implemented while production readiness still remains blocked by the missing live private-settlement conditions.
-- The role-service replay barrier now also has its own checked surface:
-  - `npm run mainnet:role-service-replay-status`
-  - `npm run mainnet:role-service-replay-evidence-check`
-  - `ops/mainnet/private-pool-v2-role-service-replay.evidence.json`
-- The bounded real-funds approval record now also has a live status surface:
-  - `npm run mainnet:real-funds-approval-status`
-  - `npm run mainnet:real-funds-approval-status-check`
-  It distinguishes `approval recorded` from `approval window active now` so historical beta approvals do not get mistaken for currently active live-action permission.
-- The bounded real-funds approval packet can now be refreshed through a refs-only writer instead of hand-editing JSON:
-  - preview: `npm run mainnet:real-funds-approval-preview`
-  - write: `npm run mainnet:real-funds-approval-write`
-  Set only refs-only shell values such as `VANTA_MAINNET_APPROVAL_ACTION_REF`, `VANTA_MAINNET_APPROVAL_ACTION_SUMMARY`, `VANTA_MAINNET_APPROVAL_LAUNCH_WINDOW_REF`, `VANTA_MAINNET_APPROVAL_FEE_PAYER_REF`, `VANTA_MAINNET_APPROVAL_ROLLBACK_PLAN_REF`, `VANTA_MAINNET_APPROVAL_STOP_LOSS_PLAN_REF`, `VANTA_MAINNET_APPROVAL_MAX_FUNDS_REF`, and `VANTA_MAINNET_APPROVAL_APPROVED_BY_REF`. The writer refuses secrets, database URLs, bearer values, and malformed launch-window refs.
-- Better Stack staging monitors for Pay and Private Pool v2 public `/health` endpoints are recorded in `ops/mainnet/staging-monitoring.manifest.json`.
-- Pay and Private Pool v2 emit privacy-safe stdout JSON request telemetry through `src/ops/vantaSafeTelemetry.mjs`.
-- Pay and Private Pool v2 now also share a privacy-safe append-only operator event sink through `src/ops/vantaOperatorEventSink.mjs`, with startup, auth rejection, and rate-limit rejection events written to `pool_operator_events` whenever a Postgres-backed operator database is configured.
-- Production observability refs are templated in `ops/mainnet/production-observability.template.json` without provider tokens, webhook URLs, source tokens, or raw secrets.
-- These are staging refs only; they do not clear production secret-manager, monitoring, audit, legal, custody, or mainnet-funds gates.
-
-## Vanta Pay merchant integration
-
-Vanta Pay is the merchant preview for test checkout and settlement records. It
-helps a business understand payment requests, checkout, settlement
-status, refunds, withdrawals, receipts, and reconciliation without learning the
-privacy system first.
-
-`npm run pay:verify` is the current Pay product gate. It checks the Pay status surfaces, merchant trust surface, payment approval packet, Pay tab copy contract, the local merchant API, Private Pool v2-backed settlement receipts, signed webhook delivery, browser-backed Pay navigation, security limitations, and the production build.
-
-For the public docs route family, `npm run docs:verify` is the reviewer-facing gate. It runs the docs browser check and the build.
-
-The merchant trust surface is documented in `docs/pay-merchant-trust-surface.md`.
-
-The current Pay layer covers:
-- commerce-only Pay tab copy with no protocol vocabulary in the merchant/buyer flow
-- the real `/app/pay` tab is a merchant preview: payment creation first, then checkout modes, payment links, invoices, refunds, withdrawals, reconciliation, developer controls, route preview, receipt preview, transaction evidence, trust rail, beta/no-funds disclosure, privacy-readiness limitation, and read-only operations context
-- static Pay contract check through `npm run pay:contract-check`
-- human and JSON Pay status surfaces through `npm run pay:status` and `npm run pay:status-json`, including `productionReady: false`
-- merchant trust status through `npm run pay:merchant-trust-status` and `npm run pay:merchant-trust-status-check`, freezing `controlled-privacy` plus `legible-trust` as the current merchant-facing trust model
-- payment approval packet contract through `npm run pay:approval-packet-check`, freezing `preview -> approve -> execute -> settle` as the current Pay action boundary
-- local Pay merchant API operator entrypoint through `npm run pay:operator`
-- hosted checkout session creation with `client_token` and `checkout_url`
-- idempotency-key support for checkout session creation, including conflict rejection for mutated retry inputs
-- idempotent checkout completion retries that return the existing payment and receipt without duplicating lifecycle events
-- internal privacy routes on checkout sessions
-- payment completion gated by a Private Pool v2-backed private-rail receipt from `src/pay/vantaPayPrivateSettlementAdapter.ts`
-- merchant-visible settlement lifecycle state exposed consistently across the adapter, merchant API status, Pay status surface, and checkout UI:
-  - `lifecycleModel = preview-approve-execute-settle`
-  - `refundState = merchant-visible`
-  - `withdrawalState = merchant-visible`
-  - `reconciliationState = merchant-visible`
-- shared UI demo copy through `src/pay/vantaPayMerchantDemoContent.ts` for the real Pay page panel: `Design partner preview`, `Merchant pilot`, and `Settlement control-plane preview without protocol overhead.`
-- production startup guard requiring Private Pool v2 operator settlement via `VANTA_PAY_PRIVATE_POOL_V2_OPERATOR_URL`
-- production startup guard requiring bearer-token forwarding to the Private Pool v2 operator via `VANTA_PAY_PRIVATE_POOL_V2_OPERATOR_AUTH_TOKEN`
-- receipt creation with selective audit-disclosure references
-- balances derived only from privately settled payments
-- withdrawals gated by a Private Pool v2-backed private-exit receipt, with withdrawal idempotency keys for retry-safe settlement
-- payment links and invoices in the local Pay runtime
-- local merchant API endpoints for checkout sessions, payments, receipts, balances, withdrawals, invoices, payment links, and webhook events
-- fail-closed merchant API request validation so missing checkout, withdrawal, invoice, payment-link, or webhook-delivery fields cannot become durable `"undefined"` state
-- machine-readable Pay operator status at `GET /v1/status`, including contract version, store schema version, durable-store configuration, private-settlement flags, idempotency coverage, production guard capabilities, and supported endpoints
-- payment and receipt detail lookup endpoints for merchant reconciliation
-- payment-link creation through the local merchant HTTP API
-- refund creation/listing through the local merchant HTTP API, including refund idempotency keys, refund-adjusted balances, merchant-visible `refundedAmount` on payment details, and `payment.refunded` webhook events
-- signed webhook payloads and retrying webhook delivery records for session, payment, receipt, and withdrawal lifecycle events
-- webhook signature verification with optional timestamp tolerance to reject stale signed payload replays
-- production webhook delivery guard requiring HTTPS merchant endpoints when `NODE_ENV=production`
-- schema-versioned optional JSON persistence for the local merchant operator via `VANTA_PAY_STORE_PATH`, including restart-safe refund and withdrawal idempotency evidence
-- production private-rail guard through `npm run pay:production-private-rail-guard-check`
-- production startup guard requiring explicit `VANTA_PAY_SECRET_KEY`, `VANTA_PAY_WEBHOOK_SECRET`, durable storage, and Private Pool v2 operator URL/auth when `NODE_ENV=production`
-- browser-backed Pay checks for landing, checkout, payment-link, and withdrawal screens via `npm run pay:browser-check`, including a checkout assertion that the `Pay with Vanta` CTA stays present-but-disabled in beta mode and completion remains absent
-
-This is still a local MVP harness, not a deployed payment processor. It gives
-Vanta Pay the familiar integration shape: create a session, show checkout, and
-receive a webhook when a payment completes. Internally, completed Pay states
-now require private settlement receipts so privacy is part of the state machine
-rather than only product copy. The current check starts the local Private Pool
-v2 operator and proves Pay settlement receipts are accepted through the
-operator-owned `/private-pool-v2/pay-settlements` endpoint when the operator
-URL is configured.
-
-The commands below are reviewer and operator surfaces. They are intentionally
-detailed; normal users should not need them to understand what Vanta does.
-
-`private-core:demo-readiness` is the friendliest single entrypoint when you just want to know whether the current proof/demo lane is stage-ready.
-
-`private-core:demo-preflight` combines the full verification pass with the current operator contract surface, the full operator status summary, the compact shipping summary, the human-readable bundled snapshot, and the human-readable shipping artifact.
-
-`private-core:operator-contract` gives the static narrow zk-v1 contract the operator currently supports: send lane, unshield lane, release lane, swap lane, the canonical shipping-decision contract, supported flow, supported asset/environment, note contract, recipient/release-destination models, proof system, fixed circuit ids, fixed Merkle depth, owner-auth mode, nullifier-key mode, proving hash lane, root-registration provenance, send input-root policy, send output-registration policy, the current send resulting-root basis, and the currently supported constrained swap venue/output/root-policy model.
-
-`private-core:operator-contract-json` prints that same frozen operator contract as machine-readable JSON, including the static shipping-decision and bundled operator-snapshot contract fields, the dedicated snapshot transport, and the dedicated `/state/private-core-snapshot` endpoint path, so automation can pin the frozen support surface directly instead of scraping the long-form text output.
-
-`private-core:operator-status` gives reviewers a live readout of what the
-current private-core operator can prove. In plain terms, it answers:
-
-- what private-core state the operator currently sees
-- whether the latest proof, send, swap, consume, and release records are linked
-- whether a root is current, stale, unregistered, consumed, or released
-- whether the release path was authorized and recorded in the local operator lane
-- whether the constrained send and swap lanes are still inside the narrow v1 rules
-
-The command reads the dedicated `/state/private-core-status` endpoint. The
-longer field names remain in the machine-readable output for automation, but
-the purpose is simple: help reviewers check the current demo lane without
-mistaking it for final production privacy.
-
-`private-core:operator-status-json` prints the live operator summary plus the canonical shipping decision as machine-readable JSON, so automation can consume the full operator-backed state surface without scraping the long-form text dump.
-
-If no operator is reachable, `private-core:operator-status-json` prints a machine-readable `operatorReachable: false` surface (plus `operatorError`) instead of failing with an unparseable fetch error. Use this for offline status snapshots. The strict `private-core:operator-status-check-json` command still fails when the operator is unreachable, but now remains machine-readable.
-
-`private-core:operator-status-check` is the ready-gated human-readable form of that same long operator-status surface: it now reads the dedicated `/state/private-core-status-check` endpoint, exits zero only when the live operator status says the frozen narrow lane is ready to ship, and on blocked paths fails with structured `Operator status decision status:` / `Operator status decision note:` lines. The frozen contract now treats that gate as its own operator-owned transport via `supportedOperatorStatusGateTransport = dedicated-endpoint` and `supportedOperatorStatusGateEndpoint = /state/private-core-status-check`.
+Pay preview:
 
-`private-core:operator-status-check-json` is the ready-gated machine-readable form of that same long operator-status surface: it now reads the dedicated `/state/private-core-status-check` endpoint, exits zero only when the live operator status says the frozen narrow lane is ready to ship, prints the full operator-status JSON on success, and on blocked paths emits the full operator-status JSON to stderr before structured `Operator status decision status:` / `Operator status decision note:` lines.
-
-`private-core:operator-snapshot` prints that same bundled operator snapshot in a human-readable form, including the snapshot identity, dedicated transport/endpoint, contract version, summary version, decision status, and the supporting shipping / finish-line / required-lanes / release-boundary / contract-mirror / boundary summaries.
-
-`private-core:operator-snapshot-json` prints one bundled machine-readable operator snapshot from the dedicated `/state/private-core-snapshot` endpoint, containing the frozen contract, the live summary/status surface, and the canonical shipping decision surface together, so external tooling can consume one coherent artifact instead of stitching together multiple commands. The shared app runtime now also hydrates its operator contract, summary, and shipping decision state from that bundled snapshot endpoint rather than rebuilding the same bundle from three separate fetches. That bundled artifact is now also part of the frozen contract surface itself via `supportedOperatorSnapshotVersion = 1`, `supportedOperatorSnapshotKind = contract-status-shipping-bundle`, `supportedOperatorSnapshotTransport = dedicated-endpoint`, and `supportedOperatorSnapshotEndpoint = /state/private-core-snapshot`.
-
-`private-core:operator-snapshot-check` is the ready-gated human-readable form of that same bundled artifact: it exits zero only when the bundled snapshot says the frozen narrow lane is ready to ship, and on blocked paths fails with structured `Snapshot decision status:` / `Snapshot decision note:` lines. The frozen contract now treats that bundled ready gate as its own operator transport too via `supportedOperatorSnapshotGateTransport = dedicated-endpoint` and `supportedOperatorSnapshotGateEndpoint = /state/private-core-snapshot-check`.
-
-`private-core:operator-snapshot-check-json` is the ready-gated machine-readable form of that same bundled artifact: it exits zero only when the bundled snapshot says the frozen narrow lane is ready to ship, prints the bundled JSON on success, and on blocked paths emits the full snapshot JSON to stderr before structured `Snapshot decision status:` / `Snapshot decision note:` lines.
-
-`private-core:shipping-artifact` prints the release-grade human-readable artifact from the dedicated `/state/private-core-shipping-artifact` endpoint, including the artifact identity, shipping decision identity, bundled snapshot identity, dedicated transports/endpoints, contract version, summary version, the current registered root lineage, the latest proof/send/consume/release lineage, and the supporting shipping / finish-line / required-lanes / release-boundary / contract-mirror / boundary summaries.
-
-`private-core:shipping-artifact-json` prints that same release-grade artifact as machine-readable JSON from the dedicated `/state/private-core-shipping-artifact` endpoint. It now gives automation one canonical operator-owned handoff object containing the shipping decision, current-root lineage, latest proof/send/consume/release lineage, and the bundled contract/status/shipping snapshot, rather than requiring tooling to join those surfaces itself.
-
-`private-core:shipping-artifact-check` is the ready-gated human-readable form of that artifact: it exits zero only when the artifact says the frozen narrow lane is ready to ship, and on blocked paths fails with structured `Artifact decision status:` / `Artifact decision note:` lines. The frozen contract now carries that ready-gated release artifact transport explicitly via `supportedShippingArtifactGateTransport = dedicated-endpoint` and `supportedShippingArtifactGateEndpoint = /state/private-core-shipping-artifact-check`.
-
-`private-core:shipping-artifact-check-json` is the ready-gated machine-readable form of that artifact: it exits zero only when the artifact says the frozen narrow lane is ready to ship, prints the full artifact JSON on success, and on blocked paths emits the full artifact JSON to stderr before structured `Artifact decision status:` / `Artifact decision note:` lines.
-
-`private-core:release-candidate` prints the exact narrow private-core send -> consume -> release candidate from the dedicated `/state/private-core-release-candidate` endpoint in human-readable form. It is the first operator-owned surface that binds one concrete `releaseCandidateId` to the current send, consume, and release lineage instead of only describing the latest operator state generically, and that exact-run candidate surface is now frozen into the operator contract as its own artifact family. The frozen contract also states that this exact-run candidate is canonical only for the primary `send -> unshield` path; `send-change` and `send-chain` downstream release variants remain valid release paths but are outside the exact candidate lineage contract.
-
-`private-core:release-candidate-json` prints that same exact-run candidate as machine-readable JSON from the dedicated `/state/private-core-release-candidate` endpoint so tooling can pin the concrete candidate id and lineage directly.
-
-`private-core:release-candidate-check` is the ready-gated human-readable form of that exact-run candidate: it exits zero only when the exact candidate is coherent and ready for the frozen narrow lane, and on blocked paths fails with structured `Release candidate decision status:` / `Release candidate decision note:` lines.
-
-`private-core:release-candidate-check-json` is the ready-gated machine-readable form of that same exact-run candidate: it exits zero only when the candidate is coherent and ready, prints the candidate JSON on success, and on blocked paths emits the full candidate JSON to stderr before structured `Release candidate decision status:` / `Release candidate decision note:` lines.
-
-`private-core:release-package` prints the final operator-owned downloadable release package from the dedicated `/state/private-core-release-package` endpoint. It packages the exact candidate id, shipping decision identity, current root, and latest proof/send/consume/release lineage into one review-ready artifact for the canonical primary `send -> unshield` lane.
-
-`private-core:release-package-json` prints that same release package as machine-readable JSON from `/state/private-core-release-package`.
-
-`private-core:release-package-check` is the ready-gated human-readable form of that release package: it exits zero only when the primary exact candidate is coherent and otherwise fails with structured `Release package decision status:` / `Release package decision note:` lines.
-
-`private-core:release-package-check-json` is the machine-readable ready-gated form of that same release package: it exits zero only when the primary exact candidate is coherent, prints the release package JSON on success, and on blocked paths emits the full package JSON to stderr before structured release-package decision status/note lines.
-
-`private-core:release-readiness` is the final reviewer-facing release judgment for the canonical primary `send -> unshield` lane. It bundles the compact shipping decision, exact release-candidate surface, and operator-owned release package into one final human-readable readiness summary for the frozen narrow zk v1 finish line.
-
-`private-core:release-readiness-json` prints that same final reviewer-facing readiness summary as machine-readable JSON.
-
-`private-core:release-readiness-check` is the strict ready-gated human-readable form of that final readiness summary: it exits zero only when the primary exact candidate, shipping decision, and release package are all coherent enough for final handoff, and otherwise fails with structured `Release readiness status:` / `Release readiness note:` lines.
-
-`private-core:release-readiness-check-json` is the machine-readable ready-gated form of that same final readiness summary: it exits zero only when the primary exact candidate is handoff-ready and otherwise emits the full readiness JSON to stderr before structured release-readiness status/note lines.
-
-`private-core:demo-preflight` now self-hosts a temporary local operator when no `--base-url` or `VANTA_PRIVATE_CORE_OPERATOR_BASE_URL` is provided. That makes the full reviewer/demo preflight turnkey again: it runs the canonical verifier, boots an isolated operator, and prints the frozen contract, long-form status, compact shipping, bundled snapshot, shipping artifact, exact release-candidate, release package, and final release-readiness surfaces against that temporary operator instead of failing on a missing live server.
-
-The current repo truth should now be read this way:
-- the narrow private-core `zk v1` lane is the accepted shipping definition of `zk v1`
-- the broader Vanta privacy/product vision is still larger than that shipped narrow lane
-
-The canonical decision note is:
-- [docs/zk/vanta-zk-v1-shipping-decision.md](docs/zk/vanta-zk-v1-shipping-decision.md)
-
-The app now also treats the canonical primary `send -> unshield` lane as an explicit release handoff workflow instead of only as operator diagnostics. Shared runtime state derives a first-class exact release handoff from the release-candidate plus shipping-artifact surfaces, and the primary `Send` and `Unshield` pages now show:
-- prepare
-- check
-- ship
-- handoff status
-- next recommended action
-- release package status
-- release package identity
-
-The app now also treats that operator-owned release package as a true review artifact:
-- `Send` and `Unshield` expose:
-  - `Copy operator package summary`
-  - `Copy operator package JSON`
-  - `Download package summary`
-  - `Download package JSON`
-- `Dashboard` now shows a first-class exact release review card so the final narrow-lane handoff status is visible before drilling into the primary flow pages.
-- `Dashboard` and the shared private-core diagnostics now point directly at the canonical final reviewer commands:
-  - `npm run private-core:release-readiness`
-  - `npm run private-core:release-readiness-check`
-
-`private-core:shipping-status` is the compact operator-backed answer to the narrow zk-v1 question: whether the frozen private-core lane is actually ship-ready right now, and if not, which live blocker is preventing that. It now reads the dedicated `/state/private-core-shipping-decision` endpoint, which is the canonical ship/no-ship contract for the frozen narrow private-core lane, and prints the decision version/kind/status/note plus the current summary-state version, mirrored contract version, summary generation time, and the supporting shipping, finish-line, required-lanes, release-boundary, contract-mirror, and boundary summaries without the rest of the larger operator-status dump.
-
-`private-core:shipping-status-json` prints that same compact readiness surface as machine-readable JSON, including the canonical decision fields and both raw enum values and humanized labels for shipping, finish-line, required-lanes, release-boundary, contract-mirror, and boundary state.
-
-If no operator is reachable, `private-core:shipping-status-json` now prints a machine-readable `operatorReachable: false` surface instead of a raw fetch failure. The strict `private-core:shipping-check*` commands still fail when the operator is unreachable.
-
-`private-core:shipping-check` runs the same operator-backed shipping summary but exits non-zero unless the current summary says `Ready narrow v1`. It now reads the dedicated `/state/private-core-shipping-decision-check` gate endpoint directly, and on blocked paths fails with structured `Shipping status:` and `Shipping note:` stderr lines instead of a note-only message.
-
-`private-core:shipping-check-json` is the machine-readable ready-gate form of that same command: it exits zero only for `Ready narrow v1`, prints the compact readiness JSON on success, and on blocked paths emits the JSON surface to stderr before the structured `Shipping status:` / `Shipping note:` lines.
-
-The operator contract now freezes the narrow zk-v1 contract surface explicitly:
-- `contractVersion = 23`
-- `summaryVersion = 47`
-- `supportedShippingDecisionVersion = 1`
-- `supportedShippingDecisionKind = narrow-private-core-zk-v1-shipping`
-- `supportedOperatorSnapshotVersion = 1`
-- `supportedOperatorSnapshotKind = contract-status-shipping-bundle`
-- `supportedOperatorSnapshotTransport = dedicated-endpoint`
-- `supportedOperatorSnapshotEndpoint = /state/private-core-snapshot`
-- `supportedUnshieldLaneVersion = 1`
-- `supportedUnshieldLaneKind = single-note-proof-backed-consume`
-- `supportedUnshieldLaneStatus = supported`
-- `supportedReleaseLaneVersion = 1`
-- `supportedReleaseLaneKind = proof-backed-consume-latest-registered-root`
-- `supportedReleaseLaneStatus = supported`
-- `supportedReleaseV1Decision = accepted-narrow-v1-path`
-- `supportedSwapV1Decision = accepted-narrow-v1-path`
-- `supportedSwapLaneVersion = 1`
-- `supportedSwapLaneKind = single-input-usdc-to-allowlisted-shielded-output`
-- `supportedSwapLaneStatus = supported`
-- `supportedSwapVenue = meteora-dlmm-mainnet-and-operator-token-output`
-- `supportedSwapOutputModel = allowlisted-shielded-output-note`
-- `supportedSwapResultingRootBasis = client-declared`
-- `supportedSwapInputRootPolicy = latest-registered-root-with-linked-registration-proof`
-- `supportedSwapOutputRegistrationPolicy = resulting-root-must-register-as-swap-output`
-- `supportedPrivateCoreCircuitFamily = vanta_private_core_single_note`
-- `supportedPrivateCoreCircuitFamilyStatus = active-v0-legacy`
-- `supportedPrivateCoreCircuitFamilyNewArchitectureStatus = deprecated-for-new-architecture`
-- `supportedPrivateCoreReplacementFamily = vanta_private_pool_v2_entry`
-
-These single-note lanes are active-v0 legacy compatibility lanes while current flows still depend on them. They should not be expanded into new production architecture; use the Private Pool v2 entry family or an explicitly reviewed replacement for new circuit work.
-- `supportedFlowVersion = 1`
-- `supportedFlowKind = shield-hold-send-unshield-replay-guard`
-- `supportedFlowStatus = supported`
-- `supportedAssetSymbol = USDC`
-- `supportedEnvironment = solana-mainnet`
-- `supportedNoteSchema = note-v0`
-- `supportedNoteVersion = 0`
-- `supportedRootRegistrationProvenance = shield-input|send-recipient-output|send-change-output|swap-output`
-- `supportedSendResultingRootBasis = client-declared`
-- `supportedSendInputRootPolicy = latest-registered-root-with-linked-registration-proof`
-- `supportedSendOutputRegistrationPolicy = resulting-root-must-register-as-recipient-or-change-output`
-- `supportedRecipientModel = hashed-reference-to-owner-key`
-- `supportedReleaseDestinationModel = 32-byte-release-destination-field`
-- `supportedProofSystem = noir-acir-ultrahonk-bbjs`
-- `supportedUnshieldCircuit = vanta_private_core_single_note_unshield`
-- `supportedSendCircuit = vanta_private_core_single_note_send`
-- `supportedUnshieldMerkleDepth = 20`
-- `supportedSendMerkleDepth = 20`
-- `supportedReleaseAuthorizationBasis = proof-backed-consume`
-- `supportedReleaseRootPolicy = latest-registered-root`
-- `supportedReleaseExecutionModel = operator-recorded-mainnet-release`
-- `supportedReleaseAtomicityModel = operator-local-atomic-consume-and-release-record`
-- `supportedReleasePersistenceModel = json-store-v1`
-- `supportedReleaseV1Decision = accepted-narrow-v1-path`
-- `supportedOwnerAuthorizationMode = x25519-secret-prechecked-off-circuit`
-- `ownerAuthorizationDecision = accepted-v1-off-circuit-precheck`
-- `supportedUnshieldProofOwnerKeyMode = poseidon-proof-owner-key-v0`
-- `sourceArtifactTruthBasis = source-layer-artifact-bundle`
-- `provingArtifactTruthBasis = verified-proving-public-input-vector`
-- `sourceProvingRelationship = explicit-split-no-implicit-equality`
-- `nullifierKeyDecision = accepted-v1-temporary-note-secret-key`
-- `supportedNullifierKeyMode = note-secret-temporary-v0-1`
-- `supportedProvingHashLane = poseidon-bn254-proving-lane-v0`
-
-The live operator summary layers dynamic verifier-side state on top of that contract:
-- current root / current root record
-- latest proof / send proof / send transition / consume / release
-- proof-send / proof-consume / proof-release / registration link status
-- send boundary status / note
-- send continuity status / note
-- contract-mirror status / note
-- latest send resulting-root continuity and registration status
-- boundary status / boundary note
-- summary generation time
-- `supportedUnshieldMerkleDepth = 20`
-- `supportedSendMerkleDepth = 20`
-- `supportedReleaseAuthorizationBasis = proof-backed-consume`
-- `supportedReleaseRootPolicy = latest-registered-root`
-- `supportedReleaseExecutionModel = operator-recorded-mainnet-release`
-- `supportedReleaseAtomicityModel = operator-local-atomic-consume-and-release-record`
-- `supportedReleasePersistenceModel = json-store-v1`
-- `supportedOwnerAuthorizationMode = x25519-secret-prechecked-off-circuit`
-- `ownerAuthorizationDecision = accepted-v1-off-circuit-precheck`
-- `supportedUnshieldProofOwnerKeyMode = poseidon-proof-owner-key-v0`
-- `sourceArtifactTruthBasis = source-layer-artifact-bundle`
-- `provingArtifactTruthBasis = verified-proving-public-input-vector`
-- `sourceProvingRelationship = explicit-split-no-implicit-equality`
-- `nullifierKeyDecision = accepted-v1-temporary-note-secret-key`
-
----
+```bash
+npm run pay:verify
+npm run pay:status
+```
 
-## What's in this repository
-
-This repository currently contains:
-- a polished landing page, manifesto, and `/products` catalog
-- a modular app shell with Shield-first primary tabs and preview lanes in More
-- Shield, Send, Swap, and Unshield as the core private-settlement workflow
-- shared app-level continuity between Shield, Send, Swap, and Unshield
-- a constrained real mainnet protocol path for `USDC`
-- direct native SOL shield entry into shielded SOL state
-- authenticated operator-backed Unshield for `USDC` and `SOL`
-- a constrained one-way live `USDC -> SOL` swap lane
-- a standalone Vanta Private Core proof lane with operator-backed verification
-- Private Pool v2 benchmark seams, Proof/trust-packet surfaces, and Pay/Strategy preview lanes
-
-The current implementation is intentionally product-led. It focuses on:
-- clear user understanding of shield-first private lanes
-- coherent privacy flow and counterparty-verifiable receipts where implemented
-- strong visual system
-- extensible structure for stronger future protocol integration
+Full command inventory lives in `package.json`. Deep operator, shipping, and release-readiness surfaces are documented in `docs/operator-runbook.md`, `docs/zk/vanta-private-core-demo-runbook.md`, and `docs/zk/vanta-zk-v1-shipping-decision.md`.
 
 ---
 
-## Notes for future integration
+## Pay preview
 
-- app module pages already reserve space for wallet connection, protocol state, proving lifecycle, and transaction status
-- Shield and Send share app-level privacy flow context
-- real wallet-connected state now grounds the live `USDC` path
-- no fake wallet logic is included
-- content and structure are organized for extension into real Solana privacy workflows
+Pay is one bounded merchant preview lane — payment requests, checkout modes, settlement records, and verifiable receipts. It is not the headline product and not a deployed payment processor. `npm run pay:verify` is the current Pay gate. Merchant integration details: `docs/pay-merchant-trust-surface.md`, `/docs/pay`.
 
 ---
 
 ## Links
 
-- **Website**: [vantaprivacy.xyz](https://vantaprivacy.xyz)
-- **Token**: [$VANTA](https://vantaprivacy.xyz/token) `9yqv319Boij6kUfD6CAzXEGYk7pHUfda37ye6FQmBAGS` (Solana)
-- **Documentation**: [docs.vantaprivacy.xyz](https://docs.vantaprivacy.xyz)
-- **GitHub**: This repository
-- **Status and audits**: `SECURITY_LIMITATIONS.md` and `/.well-known/vanta-audit.json`
+- **Website:** [vantaprivacy.xyz](https://vantaprivacy.xyz)
+- **Token:** [$VANTA](https://vantaprivacy.xyz/token) `9yqv319Boij6kUfD6CAzXEGYk7pHUfda37ye6FQmBAGS` (Solana)
+- **Documentation:** [docs.vantaprivacy.xyz](https://docs.vantaprivacy.xyz)
+- **Status / audits:** `SECURITY_LIMITATIONS.md`, `/.well-known/vanta-audit.json`
 
 ---
 
-## Additional materials
-
-- Private-core demo runbook: `docs/zk/vanta-private-core-demo-runbook.md`
-- ZK v1 shipping decision: `docs/zk/vanta-zk-v1-shipping-decision.md`
-
----
-
-## Internal product rule
-
-If someone asks what Vanta is, the shortest correct answer is:
+## Short answer
 
 > Vanta is a shield-first beta privacy app for Solana. Users move supported assets out of public wallet flows, use them through constrained private lanes (Send, Swap, Unshield), and can share verifiable receipts where implemented. Pay is one preview lane among several — not the whole product.

From dc2c128725a91f807da3ea5c21887c2c4139f375 Mon Sep 17 00:00:00 2001
From: "Claude (Cowork)" <claude@anthropic.com>
Date: Thu, 25 Jun 2026 16:22:49 -0500
Subject: [PATCH 02/10] Fix memo-encryption-check for
 privatePoolV2IndexerClient import.

Include the indexer client in the isolated tsc compile and rewrite the
@/privacy path so vantaShieldState.ts compiles in CI.

Co-authored-by: Cursor <cursoragent@cursor.com>
---
 scripts/check-vanta-action-memo-encryption.mjs | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/scripts/check-vanta-action-memo-encryption.mjs b/scripts/check-vanta-action-memo-encryption.mjs
index ba3b94e1..f771d603 100644
--- a/scripts/check-vanta-action-memo-encryption.mjs
+++ b/scripts/check-vanta-action-memo-encryption.mjs
@@ -14,6 +14,7 @@ const sourceFiles = [
   "privacy/protocolAdapter.ts",
   "privacy/privatePoolV2Types.ts",
   "privacy/privatePoolV2ProofRequests.ts",
+  "privacy/privatePoolV2IndexerClient.ts",
   "solana/vantaShieldViewingKey.ts",
   "solana/vantaShieldState.ts",
 ];
@@ -70,7 +71,8 @@ function copySource(relativePath) {
     .replace(/from "@\/solana\/shieldConfig"/g, 'from "./shieldConfig"')
     .replace(/from "@\/solana\/vantaShieldViewingKey"/g, 'from "./vantaShieldViewingKey"')
     .replace(/from "@\/solana\/client"/g, 'from "./client"')
-    .replace(/from "@\/solana\/nativeSolShield"/g, 'from "./nativeSolShield"');
+    .replace(/from "@\/solana\/nativeSolShield"/g, 'from "./nativeSolShield"')
+    .replace(/from "@\/privacy\/privatePoolV2IndexerClient"/g, 'from "../privacy/privatePoolV2IndexerClient"');
   writeFileSync(join(tempTsDir, relativePath), source);
 }
 

From a0cf10c02188a57da29abd560b66d3828d6eccf8 Mon Sep 17 00:00:00 2001
From: "Claude (Cowork)" <claude@anthropic.com>
Date: Thu, 25 Jun 2026 16:27:59 -0500
Subject: [PATCH 03/10] Fix CI blockers for slim README PR.

- Include privatePoolV2IndexerClient in memo-encryption-check compile
- Restore missing pay:receipt-privacy-contract-check script entry
- Preserve required H08 and private-core truth markers in slim README

Co-authored-by: Cursor <cursoragent@cursor.com>
---
 README.md    | 6 +++---
 package.json | 1 +
 2 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 22e41140..edc66a6f 100644
--- a/README.md
+++ b/README.md
@@ -40,13 +40,13 @@ Primary app tabs at `/app` (defaults to Shield):
 
 **Inspectable today:** wallet connection, shield flows for supported assets, constrained Send/Swap/Unshield paths, proof and operator checks for the narrow private-core lane, app tabs and diagnostics, receipt verification, and verification commands that keep claims honest.
 
-**Not live or final:** audited production privacy, broad multi-asset support, final proof/nullifier architecture, production Pay processor semantics, live Strategy execution, mainnet private settlement, or production custody/compliance guarantees.
+**Not live or final:** audited production privacy, broad multi-asset support, final proof/nullifier architecture, production Pay processor semantics, live Strategy execution, mainnet private settlement, or production custody/compliance guarantees. Proving stays local/dev-only: not live Send or actual-private-spend routing, not production browser-runtime proving, no live remote proof service, and no production proof-format acceptance on-chain yet. H08 records `selectedRuntimeDirection: remote-service-production-prover` as a local direction only; `selectedProverRuntime` stays null until production evidence exists.
 
 See `SECURITY_LIMITATIONS.md` for the full boundary list.
 
----
+Private-core compatibility: the repo still ships **active-v0 legacy** single-note Send/Swap/Unshield circuits for bounded compatibility lanes. **Private Pool v2 entry** is the replacement family for new architecture work — not a claim that every lane is migrated yet.
 
-## Pricing
+---
 
 - `0` monthly fee
 - `0.25%` only when Pay, Shield, Send, Swap, or Unshield completes successfully
diff --git a/package.json b/package.json
index 27296b27..b546cf25 100644
--- a/package.json
+++ b/package.json
@@ -337,6 +337,7 @@
     "pay:merchant-trust-status-check": "node scripts/print-vanta-pay-merchant-trust-status.mjs --check",
     "pay:approval-packet-check": "node scripts/check-vanta-pay-approval-packet.mjs",
     "pay:customer-side-zk-escrow-binding-check": "node scripts/check-vanta-pay-customer-side-zk-escrow-binding.mjs",
+    "pay:receipt-privacy-contract-check": "node scripts/check-vanta-pay-receipt-privacy-contract.mjs",
     "pay:receipt-public-view-check": "node scripts/check-vanta-pay-receipt-public-view.mjs",
     "compliance:gateway-check": "node scripts/check-vanta-compliance-gateway.mjs",
     "pay:institutional-disclosure-receipt-check": "node scripts/check-vanta-pay-institutional-disclosure-receipt.mjs",

From f6e3666eec72a5f5517a0e56368e9db9f69319b2 Mon Sep 17 00:00:00 2001
From: "Claude (Cowork)" <claude@anthropic.com>
Date: Sun, 28 Jun 2026 11:10:34 -0500
Subject: [PATCH 04/10] fix(ui): polish full-site responsive flows

Tighten responsive layouts across public, docs, product, app, and receipt surfaces; wire previously inert CTAs to real destinations; add visible Strategy preview feedback; and align the docs source-of-truth checker with current shield-first beta language.
---
 scripts/check-vanta-docs-source-of-truth.mjs |  15 +-
 src/components/ModulePage.tsx                |  12 +-
 src/pages/LaunchPage.tsx                     |   1 +
 src/pages/ProductsPage.tsx                   |  14 +-
 src/pages/ReceiptVerificationPage.tsx        |  11 +-
 src/pages/StrategyPage.tsx                   |  12 ++
 src/styles.css                               | 144 +++++++++++++++++--
 src/vanta-theme-refresh.css                  |  30 ++--
 8 files changed, 199 insertions(+), 40 deletions(-)

diff --git a/scripts/check-vanta-docs-source-of-truth.mjs b/scripts/check-vanta-docs-source-of-truth.mjs
index fb2e8cc4..de61738f 100644
--- a/scripts/check-vanta-docs-source-of-truth.mjs
+++ b/scripts/check-vanta-docs-source-of-truth.mjs
@@ -70,7 +70,7 @@ for (const lane of ["Shield", "Send", "Swap", "Unshield", "Strategy", "Pay"]) {
 }
 
 for (const phrase of [
-  "Last updated: 2026-05-12",
+  "Last updated: 2026-06-10",
   "Reviewed local feedback commit:",
   "productionReady",
   "Verifier present",
@@ -162,35 +162,34 @@ for (const phrase of [
   rejectPhrase(zkReview, phrase, "VANTA_ZK_REVIEW.md");
 }
 requirePhrase(operatorRunbook, "If You Have 10 Minutes", "docs/operator-runbook.md");
-requirePhrase(readme, "Vanta is not production-ready until it has", "README.md");
 requirePhrase(
   readme,
-  "Shield, Claim, Swap-to-shielded, actual-private-spend, and Send local bb artifact-backed proof-result adapter",
+  "Vanta is not production-ready or mainnet-ready.",
   "README.md",
 );
 requirePhrase(
   readme,
-  "actual-private-spend and Send also have dev-only browser/Web Worker proof execution plus worker-side witness generation from typed witness input",
+  "Proving stays local/dev-only",
   "README.md",
 );
 requirePhrase(
   readme,
-  "Claim has dev-only Claim browser/Web Worker proof execution plus worker-side witness generation from typed Claim witness input",
+  "active-v0 legacy",
   "README.md",
 );
 requirePhrase(
   readme,
-  "Swap-to-shielded now has dev-only Swap-to-shielded browser/Web Worker proof execution plus worker-side witness generation from typed Swap-to-shielded witness input",
+  "Private Pool v2 entry",
   "README.md",
 );
 requirePhrase(
   readme,
-  "opt-in browser-worker proof-result adapter",
+  "selectedRuntimeDirection: remote-service-production-prover",
   "README.md",
 );
 requirePhrase(
   readme,
-  "C01 local proof-format observation",
+  "selectedProverRuntime` stays null",
   "README.md",
 );
 
diff --git a/src/components/ModulePage.tsx b/src/components/ModulePage.tsx
index fbafb252..a505e785 100644
--- a/src/components/ModulePage.tsx
+++ b/src/components/ModulePage.tsx
@@ -1,3 +1,5 @@
+import { Link } from "react-router-dom";
+
 type ModulePageProps = {
   title: string;
   status: string;
@@ -7,6 +9,7 @@ type ModulePageProps = {
   primaryCardCopy: string;
   previewLabel?: string;
   buttonLabel?: string;
+  buttonTo?: string;
   secondaryItems: Array<{
     label: string;
     value: string;
@@ -22,6 +25,7 @@ export function ModulePage({
   primaryCardCopy,
   previewLabel = "Workflow preview",
   buttonLabel = "View module scope",
+  buttonTo,
   secondaryItems,
 }: ModulePageProps) {
   return (
@@ -43,9 +47,11 @@ export function ModulePage({
           <span>{previewLabel}</span>
           <h3>{primaryCardTitle}</h3>
           <p>{primaryCardCopy}</p>
-          <button className="button button-primary" type="button">
-            {buttonLabel}
-          </button>
+          {buttonTo ? (
+            <Link className="button button-primary" to={buttonTo}>
+              {buttonLabel}
+            </Link>
+          ) : null}
         </article>
 
         <article className="module-card">
diff --git a/src/pages/LaunchPage.tsx b/src/pages/LaunchPage.tsx
index 03851b03..4cb3846b 100644
--- a/src/pages/LaunchPage.tsx
+++ b/src/pages/LaunchPage.tsx
@@ -11,6 +11,7 @@ export function LaunchPage() {
       primaryCardCopy="This space is reserved for future launch policies, participant access controls, and distribution workflows that benefit from stronger privacy defaults."
       previewLabel="Future module"
       buttonLabel="View future direction"
+      buttonTo="/docs/roadmap"
       secondaryItems={[
         { label: "Distribution mode", value: "Roadmap configuration" },
         { label: "Participant policy", value: "Privacy controls reserved" },
diff --git a/src/pages/ProductsPage.tsx b/src/pages/ProductsPage.tsx
index 1ea2127b..a5255824 100644
--- a/src/pages/ProductsPage.tsx
+++ b/src/pages/ProductsPage.tsx
@@ -180,6 +180,18 @@ function ProductWorkbench({ surface }: { surface: VantaProductSurface }) {
   );
 }
 
+function getProductSurfaceCtaLabel(surface: VantaProductSurface) {
+  if (surface.appRoute === "/app/pay") {
+    return "Open Pay preview";
+  }
+
+  if (surface.appRoute === "/app/proof") {
+    return "Open proof center";
+  }
+
+  return "Open app surface";
+}
+
 export function ProductsPage() {
   return (
     <ProductsBodyClass>
@@ -318,7 +330,7 @@ export function ProductDetailPage() {
 
           <div className="product-detail__actions">
             <Link className="landing-btn landing-btn--primary" to={surface.appRoute}>
-              Open related Vanta surface
+              {getProductSurfaceCtaLabel(surface)}
             </Link>
             <Link className="landing-btn landing-btn--ghost" to="/app/proof">
               Review proof details
diff --git a/src/pages/ReceiptVerificationPage.tsx b/src/pages/ReceiptVerificationPage.tsx
index c87f9f74..9adef458 100644
--- a/src/pages/ReceiptVerificationPage.tsx
+++ b/src/pages/ReceiptVerificationPage.tsx
@@ -18,11 +18,14 @@ export function ReceiptVerificationPage() {
         why production privacy is not enabled.
       </p>
       <div className="route-fallback__actions" aria-label="Receipt verification actions">
-        <Link className="route-fallback__action route-fallback__action--primary" to="/app/pay">
-          Request private settlement
+        <Link
+          className="route-fallback__action route-fallback__action--primary"
+          to={`/app/pay?receipt=${encodeURIComponent(safeReceiptId)}`}
+        >
+          Open Pay preview
         </Link>
-        <Link className="route-fallback__action" to="/app/pay">
-          Accept committed checkout
+        <Link className="route-fallback__action" to="/docs/pay">
+          Review Pay docs
         </Link>
         <Link className="route-fallback__action" to="/docs/trust">
           Review trust docs
diff --git a/src/pages/StrategyPage.tsx b/src/pages/StrategyPage.tsx
index 7bd1ba9d..394bf4f1 100644
--- a/src/pages/StrategyPage.tsx
+++ b/src/pages/StrategyPage.tsx
@@ -273,6 +273,7 @@ function describeDestinationWallet(input: {
 
 export function StrategyPage() {
   const [form, setForm] = useState<StrategyFormState>(defaultForm);
+  const [previewSubmitted, setPreviewSubmitted] = useState(false);
   const { privateCoreHoldState, privateCoreOwner } = usePrivacyFlow();
   const { walletAddressShort, walletConnected } = useWalletState();
   const strategyPair = deriveStrategyPair(form);
@@ -393,6 +394,7 @@ export function StrategyPage() {
     key: Key,
     value: StrategyFormState[Key],
   ) => {
+    setPreviewSubmitted(false);
     setForm((current) => ({ ...current, [key]: value }));
   };
 
@@ -432,6 +434,8 @@ export function StrategyPage() {
               if (!strategyPlan || capabilityState.submitDisabled) {
                 return;
               }
+
+              setPreviewSubmitted(true);
             }}
           >
             <div className="shield-card__header strategy-card__header">
@@ -559,6 +563,14 @@ export function StrategyPage() {
               </section>
             ) : null}
 
+            {previewSubmitted && strategyPlan && strategyPreviewLedger ? (
+              <div className="strategy-preview-confirmation" role="status">
+                <span>Preview packet ready</span>
+                <strong>{strategyPlan.id}</strong>
+                <small>{strategyPreviewLedger.summary}</small>
+              </div>
+            ) : null}
+
             <StrategyAdvancedPanel
               maxSlippage={form.maxSlippage}
               maxSlippageError={formErrors.maxSlippage}
diff --git a/src/styles.css b/src/styles.css
index f2c0e245..d81952d0 100644
--- a/src/styles.css
+++ b/src/styles.css
@@ -396,6 +396,10 @@ select:focus {
 }
 
 .safety-callout__body {
+  display: flex;
+  flex-wrap: wrap;
+  gap: 8px;
+  align-items: center;
   margin: 0;
   font-size: 0.88rem;
   line-height: 1.5;
@@ -403,22 +407,26 @@ select:focus {
 }
 
 .safety-callout__action {
-  background: none;
-  border: none;
-  padding: 0;
-  margin-left: 8px;
+  min-height: 44px;
+  display: inline-flex;
+  align-items: center;
+  justify-content: center;
+  margin-left: 0;
+  padding: 0 12px;
+  border: 1px solid rgba(119, 242, 212, 0.18);
+  border-radius: 6px;
+  background: rgba(119, 242, 212, 0.07);
   color: var(--accent);
   font: inherit;
   font-weight: 600;
   cursor: pointer;
-  text-decoration: underline;
-  text-decoration-color: rgba(119, 242, 212, 0.4);
-  text-underline-offset: 3px;
+  text-decoration: none;
 }
 
 .safety-callout__action:hover,
 .safety-callout__action:focus-visible {
-  text-decoration-color: var(--accent);
+  border-color: rgba(119, 242, 212, 0.34);
+  background: rgba(119, 242, 212, 0.12);
 }
 
 .hero {
@@ -3747,6 +3755,26 @@ select:focus {
   user-select: none;
 }
 
+@media (max-width: 820px) {
+  .shield-from-to-row {
+    grid-template-columns: 1fr;
+    gap: 12px;
+  }
+
+  .shield-from-to-row .shield-picker-column .asset-picker-grid__options {
+    grid-template-columns: minmax(0, 1fr);
+  }
+
+  .shield-from-to-row .shield-picker-column:last-child .asset-picker-grid,
+  .shield-from-to-row .shield-picker-column:last-child .swap-module__label-row {
+    margin-left: 0;
+  }
+
+  .shield-from-to-arrow {
+    display: none;
+  }
+}
+
 @media (max-width: 640px) {
   .shield-from-to-row {
     grid-template-columns: 1fr;
@@ -3800,11 +3828,15 @@ select:focus {
 .swap-widget {
   gap: 16px;
   margin-top: 16px;
+  min-width: 0;
 }
 
 .swap-module {
   display: grid;
   gap: 12px;
+  min-width: 0;
+  max-width: 100%;
+  box-sizing: border-box;
   padding: 16px;
   border-radius: 16px;
   border: 1px solid rgba(0, 229, 200, 0.12);
@@ -4954,7 +4986,7 @@ select:focus {
 .swap-route-card .swap-amount-controls input {
   flex: 1 1 auto;
   min-width: 0;
-  min-height: 38px;
+  min-height: 44px;
   padding: 4px 8px;
   border: none;
   background: transparent;
@@ -6443,6 +6475,12 @@ select:focus {
   align-items: stretch;
 }
 
+@media (max-width: 900px) {
+  .pay-request-grid {
+    grid-template-columns: 1fr;
+  }
+}
+
 .pay-request-builder,
 .pay-review-card--live,
 .pay-path-card {
@@ -7947,6 +7985,37 @@ select:focus {
   align-items: stretch;
 }
 
+.strategy-preview-confirmation {
+  display: grid;
+  gap: 6px;
+  padding: 14px;
+  border: 1px solid rgba(119, 242, 212, 0.18);
+  border-radius: 10px;
+  background:
+    linear-gradient(180deg, rgba(119, 242, 212, 0.09), rgba(228, 199, 129, 0.04)),
+    rgba(5, 8, 15, 0.9);
+  color: var(--text);
+}
+
+.strategy-preview-confirmation span {
+  color: var(--accent);
+  font-size: 0.68rem;
+  font-weight: 800;
+  letter-spacing: 0.14em;
+  text-transform: uppercase;
+}
+
+.strategy-preview-confirmation strong {
+  overflow-wrap: anywhere;
+  font-family: "Space Mono", monospace;
+  font-size: 0.86rem;
+}
+
+.strategy-preview-confirmation small {
+  color: var(--muted-strong);
+  line-height: 1.5;
+}
+
 .strategy-timeline,
 .strategy-preview-ledger {
   display: grid;
@@ -10107,6 +10176,9 @@ select:focus {
 @media (max-width: 560px) {
   .app-header {
     grid-template-columns: minmax(0, 44px) minmax(0, 1fr);
+    grid-template-areas:
+      "brand wallet"
+      "tabs tabs";
   }
 
   .app-header__brand {
@@ -10118,6 +10190,15 @@ select:focus {
     display: none;
   }
 
+  .app-header__status {
+    display: none;
+  }
+
+  .app-header__tabs-rail {
+    justify-self: stretch;
+    width: 100%;
+  }
+
   .app-header__wallet {
     width: 100%;
   }
@@ -11225,6 +11306,7 @@ select:focus {
 }
 
 .products-site-nav__brand {
+  min-height: 44px;
   color: var(--landing-ice);
   font-family: "Manrope", system-ui, sans-serif;
   font-size: 0.86rem;
@@ -11240,6 +11322,7 @@ select:focus {
 
 .products-site-nav__links a {
   min-height: 40px;
+  min-width: 44px;
   display: inline-flex;
   align-items: center;
   justify-content: center;
@@ -11303,6 +11386,16 @@ select:focus {
   margin-top: 30px;
 }
 
+.products-hero__actions .landing-btn--primary,
+.product-detail__actions .landing-btn--primary {
+  border: 1px solid rgba(119, 242, 212, 0.24);
+  background:
+    linear-gradient(180deg, rgba(119, 242, 212, 0.18), rgba(119, 242, 212, 0.08)),
+    rgba(8, 18, 21, 0.92);
+  color: var(--landing-ice);
+  box-shadow: inset 0 1px 0 rgba(255, 255, 255, 0.045);
+}
+
 .products-flow-visual,
 .products-suite,
 .products-truth,
@@ -12772,8 +12865,17 @@ select:focus {
 
   .landing-nav,
   .landing-footer {
-    padding-left: 24px;
-    padding-right: 24px;
+    padding-left: 16px;
+    padding-right: 16px;
+  }
+
+  .landing-nav__links,
+  .landing-footer__links {
+    gap: 16px;
+  }
+
+  .landing-nav__cta {
+    padding-inline: 16px;
   }
 
   .landing-stats,
@@ -13254,7 +13356,7 @@ select:focus {
   position: sticky;
   top: 18px;
   z-index: 10;
-  width: min(1180px, calc(100vw - 36px));
+  width: min(1180px, calc(100vw - 24px));
   margin: 0 auto;
   display: flex;
   flex-wrap: wrap;
@@ -13324,7 +13426,8 @@ select:focus {
   display: inline-flex;
   align-items: center;
   justify-content: center;
-  min-height: 38px;
+  min-height: 44px;
+  min-width: 44px;
   padding: 0 0.72rem;
   border: 1px solid transparent;
   border-radius: 6px;
@@ -13492,7 +13595,7 @@ select:focus {
   position: relative;
   display: flex;
   align-items: center;
-  min-height: 40px;
+  min-height: 44px;
   border-radius: 8px;
   padding: 0.62rem 0.75rem 0.62rem 0.9rem;
   font-weight: 500;
@@ -14100,11 +14203,20 @@ select:focus {
 }
 
 .docs-page__next a {
+  min-height: 44px;
   width: fit-content;
+  display: inline-flex;
+  align-items: center;
+  justify-content: center;
+  padding: 0 14px;
+  border: 1px solid rgba(0, 229, 200, 0.18);
+  border-radius: 6px;
+  background: rgba(0, 229, 200, 0.07);
   color: var(--accent);
   font-family: "Syne", sans-serif;
   font-weight: 800;
   letter-spacing: 0.04em;
+  text-decoration: none;
 }
 
 .docs-page__next p {
@@ -14231,7 +14343,7 @@ select:focus {
 
   .docs-shell__topbar {
     top: 10px;
-    width: min(100%, calc(100vw - 24px));
+    width: calc(100vw - 24px);
     gap: 0.75rem;
   }
 
@@ -14244,6 +14356,7 @@ select:focus {
     flex-wrap: nowrap;
     justify-content: flex-start;
     overflow-x: auto;
+    scrollbar-gutter: stable;
   }
 
   .docs-shell__topbar-actions {
@@ -14271,6 +14384,7 @@ select:focus {
 
   .docs-sidebar {
     width: 100% !important;
+    max-width: 100%;
     grid-template-columns: 1fr;
     padding: 0.75rem;
   }
diff --git a/src/vanta-theme-refresh.css b/src/vanta-theme-refresh.css
index 1f3e6f60..d6535d21 100644
--- a/src/vanta-theme-refresh.css
+++ b/src/vanta-theme-refresh.css
@@ -19,10 +19,9 @@
      3. promote to permanent: fold PART A tokens into a real token module and let
         styles.css consume them; reconcile DESIGN.md (see note below).
 
-   DESIGN.md DRIFT NOTE
-     DESIGN.md declares accent #00e5c8 but the app ships #77f2d4. This file treats
-     the SHIPPED value (#77f2d4) as canonical and exposes it as --v-accent.
-     Update DESIGN.md to match, or change --v-accent here — but pick ONE.
+   DESIGN.md NOTE
+     DESIGN.md and the shipped app use #77f2d4 as the canonical accent. This file
+     exposes that value as --v-accent for refresh-layer components.
    ============================================================================ */
 
 /* ====================== PART A — TOKENS (global, additive) ================= */
@@ -245,6 +244,7 @@ body.vanta-refresh .dashboard-focus-card__chips span {
   gap: var(--v-space-sm);
 }
 .swap-coming-soon__actions .v-tile {
+  min-width: 0;
   text-decoration: none;
   color: inherit;
 }
@@ -643,11 +643,17 @@ body.vanta-refresh .dashboard-focus-card__chips span {
   }
 
   .swap-page .swap-coming-soon {
-    margin-inline: 16px;
+    margin-inline: 0;
+  }
+
+  .swap-page .swap-coming-soon__actions {
+    grid-template-columns: 1fr;
   }
 
   .swap-page .swap-module {
     gap: 10px;
+    width: 100%;
+    max-width: 100%;
     padding: 12px;
   }
 
@@ -681,10 +687,14 @@ body.vanta-refresh .dashboard-focus-card__chips span {
   }
 
   .swap-page .shield-form__actions--primary {
-    position: sticky;
-    bottom: 0;
+    position: static;
+    bottom: auto;
     z-index: 6;
-    margin: 8px -12px -12px;
+    width: 100%;
+    max-width: calc(100vw - 96px);
+    min-width: 0;
+    box-sizing: border-box;
+    margin: 8px 0 -12px;
     padding: 12px 12px max(12px, env(safe-area-inset-bottom));
     border-top: 1px solid var(--v-border);
     background:
@@ -694,7 +704,9 @@ body.vanta-refresh .dashboard-focus-card__chips span {
   }
 
   .swap-page .shield-form__actions--primary .button-primary {
-    width: 100%;
+    flex: 1 1 0;
+    min-width: 0;
+    width: auto;
     min-height: 48px;
   }
 }

From 4c38b2320768f86e0d357ef02769557855c3935d Mon Sep 17 00:00:00 2001
From: "Claude (Cowork)" <claude@anthropic.com>
Date: Sun, 28 Jun 2026 11:57:01 -0500
Subject: [PATCH 05/10] fix(ui): surface strategy preview packet

Add an enabled preview-packet action to Strategy so beta users can generate visible local preview feedback while live strategy execution remains locked.
---
 src/pages/StrategyPage.tsx | 30 +++++++++++++++++++++++-------
 src/styles.css             | 13 +++++++++++++
 2 files changed, 36 insertions(+), 7 deletions(-)

diff --git a/src/pages/StrategyPage.tsx b/src/pages/StrategyPage.tsx
index 394bf4f1..42c22f20 100644
--- a/src/pages/StrategyPage.tsx
+++ b/src/pages/StrategyPage.tsx
@@ -397,6 +397,14 @@ export function StrategyPage() {
     setPreviewSubmitted(false);
     setForm((current) => ({ ...current, [key]: value }));
   };
+  const previewPacketDisabled = strategyPlan === null || strategyPreviewLedger === null || capabilityState.submitDisabled;
+  const previewPacket = () => {
+    if (previewPacketDisabled) {
+      return;
+    }
+
+    setPreviewSubmitted(true);
+  };
 
   return (
     <section className="send-page strategy-page" aria-labelledby="strategy-title">
@@ -430,12 +438,7 @@ export function StrategyPage() {
             className="send-card send-card--workspace strategy-card strategy-card--primary"
             onSubmit={(event) => {
               event.preventDefault();
-
-              if (!strategyPlan || capabilityState.submitDisabled) {
-                return;
-              }
-
-              setPreviewSubmitted(true);
+              previewPacket();
             }}
           >
             <div className="shield-card__header strategy-card__header">
@@ -563,8 +566,21 @@ export function StrategyPage() {
               </section>
             ) : null}
 
+            <div className="strategy-preview-actions">
+              <button
+                aria-controls="strategy-preview-confirmation"
+                className="button button-secondary"
+                disabled={previewPacketDisabled}
+                onClick={previewPacket}
+                type="button"
+              >
+                Preview packet
+              </button>
+              <span>Generates a local receipt preview only; no trades are submitted.</span>
+            </div>
+
             {previewSubmitted && strategyPlan && strategyPreviewLedger ? (
-              <div className="strategy-preview-confirmation" role="status">
+              <div className="strategy-preview-confirmation" id="strategy-preview-confirmation" role="status">
                 <span>Preview packet ready</span>
                 <strong>{strategyPlan.id}</strong>
                 <small>{strategyPreviewLedger.summary}</small>
diff --git a/src/styles.css b/src/styles.css
index d81952d0..ff0cf71b 100644
--- a/src/styles.css
+++ b/src/styles.css
@@ -7997,6 +7997,19 @@ select:focus {
   color: var(--text);
 }
 
+.strategy-preview-actions {
+  display: flex;
+  flex-wrap: wrap;
+  gap: 10px 12px;
+  align-items: center;
+}
+
+.strategy-preview-actions span {
+  color: var(--muted-strong);
+  font-size: 0.82rem;
+  line-height: 1.45;
+}
+
 .strategy-preview-confirmation span {
   color: var(--accent);
   font-size: 0.68rem;

From 7e62f0f6771bad5cb7b1e090f3cc031b22e8543d Mon Sep 17 00:00:00 2001
From: "Claude (Cowork)" <claude@anthropic.com>
Date: Sun, 28 Jun 2026 12:07:24 -0500
Subject: [PATCH 06/10] docs: reattest live website bundle

Update the public audit discovery manifest and checker to record the June 28 UI/UX repair bundle while keeping production, mainnet, privacy, anonymity, audit, and private-settlement readiness claims blocked.
---
 public/.well-known/vanta-audit.json            | 12 ++++++------
 scripts/check-vanta-public-audit-discovery.mjs | 12 ++++++------
 2 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/public/.well-known/vanta-audit.json b/public/.well-known/vanta-audit.json
index 6ade3280..b37abb0c 100644
--- a/public/.well-known/vanta-audit.json
+++ b/public/.well-known/vanta-audit.json
@@ -2,7 +2,7 @@
   "schemaVersion": "vanta-public-audit-discovery-0.1",
   "path": "/.well-known/vanta-audit.json",
   "name": "Vanta public audit discovery",
-  "generatedAt": "2026-06-10",
+  "generatedAt": "2026-06-28",
   "refsOnly": true,
   "auditClaimAllowed": false,
   "thirdPartyAuditAccepted": false,
@@ -10,13 +10,13 @@
   "mainnetReady": false,
   "liveDeploymentVerified": true,
   "websiteDeployment": {
-    "status": "last-verified-june-10-render-pay-operator-bundle-repair",
-    "lastVerifiedCommit": "486c8e5a6a1b7943e48292c555d6bd1f9c7ca9df",
-    "lastVerifiedAt": "2026-06-10T19:22:54Z",
-    "staticDeployId": "dep-d8krht7avr4c73emeceg",
+    "status": "last-verified-june-28-ui-ux-live-fix",
+    "lastVerifiedCommit": "4c38b2320768f86e0d357ef02769557855c3935d",
+    "lastVerifiedAt": "2026-06-28T17:05:53Z",
+    "staticDeployId": "dep-d90l4qegvqtc739khsn0",
     "operatorDeployId": "dep-d8krgfpkh4rs73ffra80",
     "liveUrl": "https://vantaprivacy.xyz",
-    "truthBoundary": "This records the static website entry asset assets/index-Dc9phHY1.js and Pay operator deploys for commit 486c8e5a6a1b7943e48292c555d6bd1f9c7ca9df on 2026-06-10 UTC after the Render Pay operator runtime bundle repair. The public discovery manifest is a reviewer map only. Private settlement, SBF, verifier, custody, anonymity, audit, generated browser Groth16 proofs, on-chain verifier acceptance, real-funds, and mainnet evidence remain blocked."
+    "truthBoundary": "This records the live Vanta UI/UX repair static website entry asset assets/index-BU3kUSHJ.js from Render static deploy dep-d90l4qegvqtc739khsn0 for commit 4c38b2320768f86e0d357ef02769557855c3935d on 2026-06-28 UTC. The public discovery manifest is a reviewer map only. Private settlement, SBF, verifier, custody, anonymity, audit, generated browser Groth16 proofs, on-chain verifier acceptance, real-funds, and mainnet evidence remain blocked."
   },
   "privacyClaimAllowed": false,
   "anonymityClaimAllowed": false,
diff --git a/scripts/check-vanta-public-audit-discovery.mjs b/scripts/check-vanta-public-audit-discovery.mjs
index 1c1b2d16..1225490e 100644
--- a/scripts/check-vanta-public-audit-discovery.mjs
+++ b/scripts/check-vanta-public-audit-discovery.mjs
@@ -131,7 +131,7 @@ assert.ok(
 
 assert.equal(discovery.schemaVersion, "vanta-public-audit-discovery-0.1");
 assert.equal(discovery.path, "/.well-known/vanta-audit.json");
-assert.equal(discovery.generatedAt, "2026-06-10");
+assert.equal(discovery.generatedAt, "2026-06-28");
 assert.equal(discovery.auditClaimAllowed, false);
 assert.equal(discovery.thirdPartyAuditAccepted, false);
 assert.equal(discovery.productionReady, false);
@@ -140,14 +140,14 @@ assert.equal(discovery.liveDeploymentVerified, true);
 // Keep crawler-visible deployment evidence refs-only and claim-bounded: this is
 // a public reviewer map, not a private-settlement or readiness attestation.
 assert.deepEqual(discovery.websiteDeployment, {
-  status: "last-verified-june-10-render-pay-operator-bundle-repair",
-  lastVerifiedCommit: "486c8e5a6a1b7943e48292c555d6bd1f9c7ca9df",
-  lastVerifiedAt: "2026-06-10T19:22:54Z",
-  staticDeployId: "dep-d8krht7avr4c73emeceg",
+  status: "last-verified-june-28-ui-ux-live-fix",
+  lastVerifiedCommit: "4c38b2320768f86e0d357ef02769557855c3935d",
+  lastVerifiedAt: "2026-06-28T17:05:53Z",
+  staticDeployId: "dep-d90l4qegvqtc739khsn0",
   operatorDeployId: "dep-d8krgfpkh4rs73ffra80",
   liveUrl: "https://vantaprivacy.xyz",
   truthBoundary:
-    "This records the static website entry asset assets/index-Dc9phHY1.js and Pay operator deploys for commit 486c8e5a6a1b7943e48292c555d6bd1f9c7ca9df on 2026-06-10 UTC after the Render Pay operator runtime bundle repair. The public discovery manifest is a reviewer map only. Private settlement, SBF, verifier, custody, anonymity, audit, generated browser Groth16 proofs, on-chain verifier acceptance, real-funds, and mainnet evidence remain blocked.",
+    "This records the live Vanta UI/UX repair static website entry asset assets/index-BU3kUSHJ.js from Render static deploy dep-d90l4qegvqtc739khsn0 for commit 4c38b2320768f86e0d357ef02769557855c3935d on 2026-06-28 UTC. The public discovery manifest is a reviewer map only. Private settlement, SBF, verifier, custody, anonymity, audit, generated browser Groth16 proofs, on-chain verifier acceptance, real-funds, and mainnet evidence remain blocked.",
 });
 assert.equal(discovery.privacyClaimAllowed, false);
 assert.equal(discovery.anonymityClaimAllowed, false);

From b5fdf2b539528880554cfbe960742fdad53730f6 Mon Sep 17 00:00:00 2001
From: "Claude (Cowork)" <claude@anthropic.com>
Date: Sun, 28 Jun 2026 12:16:46 -0500
Subject: [PATCH 07/10] fix(ui): contain mobile form and receipt layout

Use border-box sizing for form controls and route fallback cards, and hard-wrap receipt verifier facts so mobile routes do not clip controls or overflow horizontally.
---
 src/styles.css | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/src/styles.css b/src/styles.css
index ff0cf71b..54919df4 100644
--- a/src/styles.css
+++ b/src/styles.css
@@ -110,6 +110,8 @@ input {
 input,
 textarea,
 select {
+  box-sizing: border-box;
+  max-width: 100%;
   min-height: 56px;
   padding: 0 18px;
   border-radius: 12px;
@@ -1854,6 +1856,7 @@ select:focus {
 .route-error-boundary {
   position: relative;
   z-index: 2;
+  box-sizing: border-box;
   display: grid;
   align-content: center;
   gap: 18px;
@@ -1959,6 +1962,7 @@ select:focus {
   margin: 8px 0 0;
   color: var(--muted-strong);
   line-height: 1.5;
+  overflow-wrap: anywhere;
 }
 
 @media (max-width: 640px) {

From 5337048ec767524d30305bd6faf67e5b6a059992 Mon Sep 17 00:00:00 2001
From: "Claude (Cowork)" <claude@anthropic.com>
Date: Sun, 28 Jun 2026 12:22:51 -0500
Subject: [PATCH 08/10] fix(ui): cap swap controls on mobile

Keep Swap select controls inside the mobile app viewport by capping their width against the available gutter while preserving desktop and tablet layout.
---
 src/styles.css | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/src/styles.css b/src/styles.css
index 54919df4..2a93b49c 100644
--- a/src/styles.css
+++ b/src/styles.css
@@ -14553,6 +14553,12 @@ select:focus {
     min-height: 48px;
     font-size: 1rem;
   }
+
+  .swap-page .swap-asset-select,
+  .swap-page .note-picker__select {
+    max-width: min(100%, calc(100vw - 104px));
+  }
+
   .amount-field .button-ghost {
     min-height: 44px;
   }

From 111866e9318c2b8e1fd92d6f66b613135f568236 Mon Sep 17 00:00:00 2001
From: "Claude (Cowork)" <claude@anthropic.com>
Date: Sun, 28 Jun 2026 12:30:12 -0500
Subject: [PATCH 09/10] docs: reattest final live UI bundle

Update the public audit discovery manifest and checker to record the final June 28 UI/UX repair deploy and currently served entry asset while preserving blocked production, mainnet, privacy, anonymity, audit, and private-settlement claims.
---
 public/.well-known/vanta-audit.json            | 8 ++++----
 scripts/check-vanta-public-audit-discovery.mjs | 8 ++++----
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/public/.well-known/vanta-audit.json b/public/.well-known/vanta-audit.json
index b37abb0c..eee00ecf 100644
--- a/public/.well-known/vanta-audit.json
+++ b/public/.well-known/vanta-audit.json
@@ -11,12 +11,12 @@
   "liveDeploymentVerified": true,
   "websiteDeployment": {
     "status": "last-verified-june-28-ui-ux-live-fix",
-    "lastVerifiedCommit": "4c38b2320768f86e0d357ef02769557855c3935d",
-    "lastVerifiedAt": "2026-06-28T17:05:53Z",
-    "staticDeployId": "dep-d90l4qegvqtc739khsn0",
+    "lastVerifiedCommit": "5337048ec767524d30305bd6faf67e5b6a059992",
+    "lastVerifiedAt": "2026-06-28T17:29:36Z",
+    "staticDeployId": "dep-d90lgtdaeets73e6us9g",
     "operatorDeployId": "dep-d8krgfpkh4rs73ffra80",
     "liveUrl": "https://vantaprivacy.xyz",
-    "truthBoundary": "This records the live Vanta UI/UX repair static website entry asset assets/index-BU3kUSHJ.js from Render static deploy dep-d90l4qegvqtc739khsn0 for commit 4c38b2320768f86e0d357ef02769557855c3935d on 2026-06-28 UTC. The public discovery manifest is a reviewer map only. Private settlement, SBF, verifier, custody, anonymity, audit, generated browser Groth16 proofs, on-chain verifier acceptance, real-funds, and mainnet evidence remain blocked."
+    "truthBoundary": "This records the live Vanta UI/UX repair static website entry asset assets/index-CI_UI_OS.js from Render static deploy dep-d90lgtdaeets73e6us9g for commit 5337048ec767524d30305bd6faf67e5b6a059992 on 2026-06-28 UTC. The public discovery manifest is a reviewer map only. Private settlement, SBF, verifier, custody, anonymity, audit, generated browser Groth16 proofs, on-chain verifier acceptance, real-funds, and mainnet evidence remain blocked."
   },
   "privacyClaimAllowed": false,
   "anonymityClaimAllowed": false,
diff --git a/scripts/check-vanta-public-audit-discovery.mjs b/scripts/check-vanta-public-audit-discovery.mjs
index 1225490e..800c4676 100644
--- a/scripts/check-vanta-public-audit-discovery.mjs
+++ b/scripts/check-vanta-public-audit-discovery.mjs
@@ -141,13 +141,13 @@ assert.equal(discovery.liveDeploymentVerified, true);
 // a public reviewer map, not a private-settlement or readiness attestation.
 assert.deepEqual(discovery.websiteDeployment, {
   status: "last-verified-june-28-ui-ux-live-fix",
-  lastVerifiedCommit: "4c38b2320768f86e0d357ef02769557855c3935d",
-  lastVerifiedAt: "2026-06-28T17:05:53Z",
-  staticDeployId: "dep-d90l4qegvqtc739khsn0",
+  lastVerifiedCommit: "5337048ec767524d30305bd6faf67e5b6a059992",
+  lastVerifiedAt: "2026-06-28T17:29:36Z",
+  staticDeployId: "dep-d90lgtdaeets73e6us9g",
   operatorDeployId: "dep-d8krgfpkh4rs73ffra80",
   liveUrl: "https://vantaprivacy.xyz",
   truthBoundary:
-    "This records the live Vanta UI/UX repair static website entry asset assets/index-BU3kUSHJ.js from Render static deploy dep-d90l4qegvqtc739khsn0 for commit 4c38b2320768f86e0d357ef02769557855c3935d on 2026-06-28 UTC. The public discovery manifest is a reviewer map only. Private settlement, SBF, verifier, custody, anonymity, audit, generated browser Groth16 proofs, on-chain verifier acceptance, real-funds, and mainnet evidence remain blocked.",
+    "This records the live Vanta UI/UX repair static website entry asset assets/index-CI_UI_OS.js from Render static deploy dep-d90lgtdaeets73e6us9g for commit 5337048ec767524d30305bd6faf67e5b6a059992 on 2026-06-28 UTC. The public discovery manifest is a reviewer map only. Private settlement, SBF, verifier, custody, anonymity, audit, generated browser Groth16 proofs, on-chain verifier acceptance, real-funds, and mainnet evidence remain blocked.",
 });
 assert.equal(discovery.privacyClaimAllowed, false);
 assert.equal(discovery.anonymityClaimAllowed, false);

From 87fb9a0b1f89df25d9757a979a8ed214dc31e9ce Mon Sep 17 00:00:00 2001
From: "Claude (Cowork)" <claude@anthropic.com>
Date: Mon, 29 Jun 2026 11:05:55 -0500
Subject: [PATCH 10/10] docs: record Vanta proof boundary hygiene

---
 ...2026-06-29-vanta-proof-boundary-hygiene.md | 78 +++++++++++++++++++
 1 file changed, 78 insertions(+)
 create mode 100644 docs/goals/hourly-top-5-improvement-goals/notes/2026-06-29-vanta-proof-boundary-hygiene.md

diff --git a/docs/goals/hourly-top-5-improvement-goals/notes/2026-06-29-vanta-proof-boundary-hygiene.md b/docs/goals/hourly-top-5-improvement-goals/notes/2026-06-29-vanta-proof-boundary-hygiene.md
new file mode 100644
index 00000000..a73431f9
--- /dev/null
+++ b/docs/goals/hourly-top-5-improvement-goals/notes/2026-06-29-vanta-proof-boundary-hygiene.md
@@ -0,0 +1,78 @@
+# Vanta Proof-Boundary Hygiene Receipt - 2026-06-29
+
+Run time: 2026-06-29 11:05 CDT
+
+## Scope
+
+This note records the current local proof/deployment boundary for the Weekly Top
+5 improvement follow-up. It does not push, deploy, mutate provider state, touch
+wallets/funds, claim production/private readiness, or mark live status complete.
+
+## Current Git Boundary
+
+`/Users/clay/Desktop/Vanta` was inspected in Review + Careful mode.
+
+Observed status before this note:
+
+```text
+## main...origin/main [ahead 9]
+?? output/
+```
+
+Ahead commits observed:
+
+```text
+111866e9 docs: reattest final live UI bundle
+5337048e fix(ui): cap swap controls on mobile
+b5fdf2b5 fix(ui): contain mobile form and receipt layout
+7e62f0f6 docs: reattest live website bundle
+4c38b232 fix(ui): surface strategy preview packet
+f6e3666e fix(ui): polish full-site responsive flows
+a0cf10c0 Fix CI blockers for slim README PR.
+dc2c1287 Fix memo-encryption-check for privatePoolV2IndexerClient import.
+8d24c51e docs: slim README to shield-first beta positioning
+```
+
+## Local Artifact Boundary
+
+Untracked `output/` contains 45 local audit artifacts from 2026-06-28, including
+JSON audits, interaction/internal-link checks, header/swap measurements,
+Peekaboo text output, and four PNG screenshots:
+
+- `vanta-desktop-products-after.png`
+- `vanta-desktop-products-after2.png`
+- `vanta-mobile-docs-after.png`
+- `vanta-mobile-swap-after.png`
+
+These are local proof artifacts until reviewed. They should not be treated as
+committed source truth, pushed evidence, deployed/live evidence, or production
+readiness proof merely because filenames contain `live` or `after-deploy`.
+
+## Decision
+
+The safe completed improvement for this run is boundary clarification:
+
+- Current tracked Vanta code had no dirty diff before this note.
+- The branch is still ahead of `origin/main` and not pushed by this run.
+- The untracked `output/` folder still needs an artifact keeper decision:
+  `keep`, `archive`, `ignore`, or `delete-with-approval`.
+- Push, deploy, Render/GitHub checks, live smoke verification, provider log
+  review, and public-readiness claims still require explicit same-turn approval.
+
+## Smallest Next Verification
+
+Before any Vanta push/deploy/live claim:
+
+1. Review the nine ahead commits as a single proof packet.
+2. Classify `output/` artifacts and either commit selected evidence, archive it,
+   ignore generated noise, or delete only with explicit approval.
+3. Run the relevant local Vanta commands for the touched surface.
+4. Only after push/deploy approval, verify provider state and live URL behavior;
+   keep beta/local proof boundaries intact unless production gates actually pass.
+
+## Lumi
+
+- Local: boundary receipt added locally.
+- Committed: pending at receipt creation.
+- Pushed: no; ahead commits remain local unless separately pushed.
+- Deployed/live: not changed and not freshly verified by this receipt.