Provision external demo accounts and record non-secret configuration

Outcome

All human-owned accounts and eligibility needed for M0-F exist without placing credentials in GitHub or model context.

Scope

• Create or confirm Duffel test, Stripe, Google OAuth/OIDC, and Railway accounts/projects.
• Prepare candidate authorization-provider credentials if M0-F will compare a managed profile.
• Record only non-secret account identifiers, ownership, environment names, and completion evidence.

Acceptance

• Duffel test access is available to the product owner.
• Stripe test mode and a webhook endpoint plan are available.
• Google basic openid email profile configuration and cold-account eligibility are known.
• Railway project ownership and billing eligibility are confirmed.
• No secret value, token, OAuth code, or webhook secret appears in this issue or repository.

Dependencies

• None.

Review

Product-owner completion evidence; no model may handle or request the secret values.

Start with the issue's Scope and Acceptance sections, then coordinate with the product owner to confirm ownership and eligibility for Duffel, Stripe, Google OAuth/OIDC, and Railway. Record only non-secret identifiers, environment names, and completion evidence; done means every acceptance item is confirmed without secrets, tokens, OAuth codes, or webhook secrets appearing in GitHub or model context.