docs: document Stripe account sandbox distinction

[mjaskolski]

Documents the non-obvious distinction between a main account’s classic Test mode and the additional sandbox created by new-account onboarding, including safe account-ID verification and stable settings routes.

---

Summary by cubic

Add documentation that clarifies the difference between a main Stripe account’s Test mode and the onboarding-created sandbox, so teams don’t create resources in the wrong account. Includes a quick verification flow using the URL account ID and /v1/account, plus stable dashboard routes for API keys and settings.

^{Written for commit cd746e9. Summary will update on new commits.}

[cubic-dev-ai]

1 issue found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="agent-workspace/domain-skills/stripe/account-sandboxes.md">

<violation number="1" location="agent-workspace/domain-skills/stripe/account-sandboxes.md:16">
P3: Step 3's `/v1/account` path is ambiguous about how to retrieve it — the document doesn't specify whether the agent should navigate to it in the Stripe dashboard (`https://dashboard.stripe.com/v1/account`) or make an HTTP request to the REST API (`https://api.stripe.com/v1/account` with an `Authorization` header). In a browser-automation harness context, these are distinct operations with different syntax, and the agent has no way to infer which is intended. Specify the full URL and retrieval method so the verification step is actionable.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

P3: Step 3's /v1/account path is ambiguous about how to retrieve it — the document doesn't specify whether the agent should navigate to it in the Stripe dashboard (https://dashboard.stripe.com/v1/account) or make an HTTP request to the REST API (https://api.stripe.com/v1/account with an Authorization header). In a browser-automation harness context, these are distinct operations with different syntax, and the agent has no way to infer which is intended. Specify the full URL and retrieval method so the verification step is actionable.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At agent-workspace/domain-skills/stripe/account-sandboxes.md, line 16:

<comment>Step 3's `/v1/account` path is ambiguous about how to retrieve it — the document doesn't specify whether the agent should navigate to it in the Stripe dashboard (`https://dashboard.stripe.com/v1/account`) or make an HTTP request to the REST API (`https://api.stripe.com/v1/account` with an `Authorization` header). In a browser-automation harness context, these are distinct operations with different syntax, and the agent has no way to infer which is intended. Specify the full URL and retrieval method so the verification step is actionable.</comment>

<file context>
@@ -0,0 +1,28 @@
+1. Read the account ID from the URL.
+2. Open `/{main_account_id}/test/apikeys`.
+3. Verify the API key by retrieving `/v1/account` and comparing its `id` with
+   the intended main account ID.
+
+Useful stable routes:
</file context>