docs: sync country coverage with Grid Switch Corridor List

[pengying]

Summary

• Add China (CN) to the Coming Soon table.
• Row 88 of the Grid Switch Corridor List (US → China via Tazapay) has Public Roadmap = Yes and Status = Planned, which independently qualifies for Coming Soon even though China already has a separate Live corridor via Thunes (row 66). This matches the documented filter result from the last sync (Canada, China, Hong Kong, South Korea).
• No other changes: the Live table (63 countries, alphabetical), header counts ("63 countries"), and Regional Summary counts (Europe 32 / Middle East and Africa 16 / Asia-Pacific 10 / Americas 5 = 63) all already match the current spreadsheet exactly — origin/main had already absorbed the Ghana addition and more since PR docs: sync country coverage with Grid Switch Corridor List #532 was opened, so docs: sync country coverage with Grid Switch Corridor List #532 is now stale and does not cover this change.

Source of truth: Grid Switch Corridor List, tab "Grid Switch Corridor List".

Test plan

• Render mintlify/snippets/country-support.mdx locally and confirm the Coming Soon table lists Canada, China, Hong Kong, South Korea in alphabetical order.
• Confirm no other rows/counts changed (git diff touches only the one added line).

🤖 Generated with Claude Code

https://claude.ai/code/session_01P5Agg1zphAzLbrp3MeK2Y7

---

Generated by Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments

Project	Deployment	Actions	Updated
grid-cards-demo	Ignored		Sep 16, 2026 4:05pm UTC
grid-flow-builder	Ignored		Sep 16, 2026 4:05pm UTC
grid-wallet-demo	Ignored		Sep 16, 2026 4:05pm UTC

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
Grid	🟢 Ready	View Preview	Sep 16, 2026, 4:08 PM

[greptile-apps]

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking documentation clarification recommended for China's simultaneous live and planned coverage.

Findings

1.  China's availability is ambiguous ▶

Fix with agent prompt

### Issue 1
mintlify/snippets/country-support.mdx:134
China already appears in the available-country table with supported payment rails, but this new country-only row also labels it “Coming Soon.” The PR description explains that a separate corridor is planned; the documentation does not preserve that distinction, so readers cannot tell which China capability they need to wait for. Consider annotating the entry or adding a short note that an additional China corridor is planned while existing China support remains live.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Adds China (CN) to the Coming Soon country table.

• Preserves alphabetical order: Canada, China, Hong Kong, South Korea.
• Leaves existing available-country entries and coverage counts unchanged.
• A short clarification would distinguish the planned additional China corridor from China's existing live support.

_{Reviews (1) · Last reviewed commit: "docs: add China to Coming Soon country c..."}

[greptile-apps]

China's availability is ambiguous

China already appears in the available-country table with supported payment rails, but this new country-only row also labels it “Coming Soon.” The PR description explains that a separate corridor is planned; the documentation does not preserve that distinction, so readers cannot tell which China capability they need to wait for. Consider annotating the entry or adding a short note that an additional China corridor is planned while existing China support remains live.

Prompt To Fix With AI

This is a comment left during a code review.
Path: mintlify/snippets/country-support.mdx
Line: 134

Comment:
**China's availability is ambiguous**

China already appears in the available-country table with supported payment rails, but this new country-only row also labels it “Coming Soon.” The PR description explains that a separate corridor is planned; the documentation does not preserve that distinction, so readers cannot tell which China capability they need to wait for. Consider annotating the entry or adding a short note that an additional China corridor is planned while existing China support remains live.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[pengying]

Leaving China's dual listing as-is. It's intentional and directly sourced from the spreadsheet: row 66 (US→China via Thunes) is Live today, and row 88 (US→China via Tazapay) has Public Roadmap = Yes and Status = Planned — a separate corridor in development. Per the sync task's mapping rules, a Coming Soon row is determined per-corridor-row, not deduped against destinations that are already Live elsewhere, so China correctly appears in both tables. Not adding explanatory prose here since it's outside the scope of this sync and would require guessing at unannounced rollout details for the new corridor.

---

Generated by Claude Code