Test mode

There is no separate staging company. Test mode lives inside the production platform with hard isolation:

• Keys: sk_test_… keys can only address the application’s test tenant. A live resource id in a test request returns 404 not_found.
• Sources: seeded from the Simulated connector (provider: "simulated"): a deterministic inbox and drive with promotional mail, old attachments, duplicates, a 2021 W2.pdf, large videos, and trial/renewal/overage emails from realistic vendor senders.
• Plans and executions: simulated: true on every resource. Executions run the full lifecycle (fetch → vault → verify → commit → source action → reclaim) against the simulated provider and issue real signed receipts.
• Usage: events are recorded with simulated: true and never rated for money; GET /v1/usage reports test usage separately.
• Webhooks: only mode: test webhooks receive test events, marked with the CloudEvents extension sweepsimulated: true.

Scenarios

POST /v1/developer/applications/{id}/test-mode/seed accepts a scenario:

Scenario	What you get
storage_pressure (default)	~2,000 objects, ~40 GB nominal, a Gmail at 91% and a Drive at 78% with a growth trend
trials_and_meters	inboxes with trial-ending, renewal, price-increase, overage and credit-exhaustion emails
creator_revenue	payout, adjustment and statement emails plus a Stripe-shaped payout feed
clean	connected sources with nothing to reclaim (tests the “everything is healthy” path)

Seeding is idempotent per seed string; reseeding with the same seed reproduces identical ids.