Public Docs and Support Pages Refresh: What Changed

# Public Docs and Support Pages Refresh\n\nThis refresh focuses on one goal: make the site more useful before a visitor signs in. Public pages are not just SEO inventory. They are often the first place users decide whether the product is clear, trustworthy, and supportable.\n\n## What changed\n\nThe Docs page now has a clearer quickstart, more endpoint coverage, stronger operational guidance, and better error semantics. Help and Contact now behave like support pages instead of thin blog-style placeholders. Policy pages have also been expanded into structured documents with better sectioning and clearer follow-up paths.\n\n## Why it matters\n\nWhen visitors cannot understand where to start, what the API does, or how support works, trust drops before conversion. Better public content reduces support friction and makes onboarding more credible for both operators and developers.\n\n## What teams should keep doing\n\nOperators should keep service guidance aligned with live supply conditions. Product and engineering should continue replacing placeholders with source-of-truth content anywhere that affects billing expectations, refund logic, or onboarding steps.\n\nThis refresh does not finish the work, but it raises the baseline from page existence to actual usefulness.