Whether this twin's answers match a captured real vendor response.
MCP create_payment_intent Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/stripe/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP retrieve_payment_intent Not checked
this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/stripe/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP list_payment_intents Not checked
this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/stripe/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP confirm_payment_intent Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/stripe/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP update_payment_intent Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/stripe/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP cancel_payment_intent Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/stripe/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP simulate_crypto_deposit Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/stripe/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP retrieve_charge Not checked
this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/stripe/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP list_charges Not checked
this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/stripe/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP retrieve_balance Not checked
this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/stripe/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP list_balance_transactions Not checked
this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/stripe/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP retrieve_event Not checked
this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/stripe/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP list_events Not checked
this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/stripe/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP create_refund Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/stripe/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP retrieve_refund Not checked
this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/stripe/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP list_refunds Not checked
this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/stripe/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP create_customer Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/stripe/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP retrieve_customer Not checked
this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/stripe/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP update_customer Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/stripe/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP delete_customer Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/stripe/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP list_customers Not checked
this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/stripe/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP list_customer_payment_methods Not checked
this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/stripe/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP create_payment_method Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/stripe/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP retrieve_payment_method Not checked
this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/stripe/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP attach_payment_method Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/stripe/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
MCP detach_payment_method Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/stripe/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
POST /v1/payment_intents Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
GET /v1/payment_intents/:id Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
GET /v1/payment_intents Not checked
nothing has ever compared this surface against real Stripe. It IS one of the 6 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.
Run FIDELITY_STRIPE_KEY=… bun run tools/fidelity-watch/capture-stripe-upstream-golden.ts.
POST /v1/payment_intents/:id/confirm Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
POST /v1/payment_intents/:id Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
POST /v1/payment_intents/:id/cancel Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
POST /v1/test_helpers/payment_intents/:id/simulate_crypto_deposit Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
GET /v1/charges/:id Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
GET /v1/charges Not checked
nothing has ever compared this surface against real Stripe. It IS one of the 6 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.
Run FIDELITY_STRIPE_KEY=… bun run tools/fidelity-watch/capture-stripe-upstream-golden.ts.
GET /v1/balance Not checked
nothing has ever compared this surface against real Stripe. It IS one of the 6 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.
Run FIDELITY_STRIPE_KEY=… bun run tools/fidelity-watch/capture-stripe-upstream-golden.ts.
GET /v1/balance_transactions Not checked
nothing has ever compared this surface against real Stripe. It IS one of the 6 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.
Run FIDELITY_STRIPE_KEY=… bun run tools/fidelity-watch/capture-stripe-upstream-golden.ts.
GET /v1/events/:id Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
GET /v1/events Not checked
nothing has ever compared this surface against real Stripe. It IS one of the 6 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.
Run FIDELITY_STRIPE_KEY=… bun run tools/fidelity-watch/capture-stripe-upstream-golden.ts.
POST /v1/refunds Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
GET /v1/refunds/:id Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
GET /v1/refunds Not checked
nothing has ever compared this surface against real Stripe. It IS one of the 6 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.
Run FIDELITY_STRIPE_KEY=… bun run tools/fidelity-watch/capture-stripe-upstream-golden.ts.
POST /v1/customers Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
GET /v1/customers/:id Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
GET /v1/customers Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
POST /v1/customers/:id Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
DELETE /v1/customers/:id Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
GET /v1/customers/:id/payment_methods Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
POST /v1/payment_methods Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
GET /v1/payment_methods/:id Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
POST /v1/payment_methods/:id/attach Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.
POST /v1/payment_methods/:id/detach Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/stripe/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.
Run tsx tools/fidelity-watch/capture-stripe-m1.ts and commit every fixture it writes. It says nothing about parity with real Stripe, which only the L1 upstream lane can answer.