feat: v2 documentation with versioned navigation and updated SDKs

[VinciGit00]

Summary

• Versioned navigation: docs.json now uses navigation.versions with v2 as default and v1 as legacy, matching the structure from doc-private
• Updated SDK docs: Python and JavaScript SDK pages rewritten for v2 API based on scrapegraph-py#82 and scrapegraph-js#11 — new methods (extract, search, scrape, crawl.*, monitor.*, credits, history), FetchConfig/LlmConfig config objects, factory pattern for JS
• Updated mocking docs: Replaced built-in mock mode (removed in v2) with standard library testing patterns (unittest.mock, responses, Jest/Vitest, MSW)
• v1 legacy pages: 24 new pages under v1/ with deprecation banners pointing to v2 equivalents
• Design updates: New primary color (#AC6DFF), IBM Plex Sans font, updated backgrounds

Test plan

• Verify Mintlify builds successfully with versioned navigation
• Check v2 tab loads as default
• Check v1 tab shows legacy docs with deprecation warnings
• Verify all navigation links resolve correctly in both versions
• Review SDK code examples match the v2 PR APIs

🤖 Generated with Claude Code

[lurenss]

Rechecked only the v2 side of this PR against the current sgai-stack development branch plus scrapegraph-js#11 and scrapegraph-py#82. Ignoring intentional v1 legacy content, these are the remaining gaps in the v2 docs branch:

1. The v2 branch still does not provide a real canonical v2 API reference. The API Reference tab still points to old endpoint pages instead of /api/v2 reference pages, so there is no authoritative reference for the current stack routes (/scrape, /extract, /schema, /search, /history, /monitor, /crawl, /events, /credits, /validate).

2. services/scrape.mdx is still documenting the wrong canonical REST shape. It shows singular format and an old { id, format, content }-style response, while the current stack contract is formats[] and a results + metadata response. The SDKs keep compatibility shortcuts, but the page is not describing the actual v2 API contract.

3. services/extract.mdx is stale for v2. It still documents output_schema, fetch_config, llm_config, and old fetch flags like render_js, stealth, and wait_ms. The current stack contract is centered on schema, fetchConfig, and the shared v2 fetch config schema.

4. services/search.mdx is also stale for v2. It still says the default result count is 5 and documents output_schema / llm_config, while the current stack contract is numResults default 3 with format, mode, fetchConfig, prompt, schema, locationGeoCode, and timeRange.

5. services/crawl.mdx still documents legacy REST fields like depth, max_pages, and format as the main API shape. The current v2 contract is maxDepth, maxPages, maxLinksPerPage, allowExternal, and formats[].

6. services/monitor.mdx still presents the prompt-driven model as the main v2 API. The canonical current monitor create contract is formats[]-based. The SDKs support legacy-compatible monitor creation, but the docs page is not aligned to the actual stack contract.

7. sdks/javascript.mdx is still missing part of the current v2 JS SDK surface and has wrong examples for response shapes. The docs still use remainingCredits, totalCreditsUsed, endpoint, offset, and data.items, but the current stack/SDK responses are credits { remaining, used, plan, jobs } and history { data, pagination }. The page also does not document schema() or validate(), even though the JS v2 branch exposes both.

8. sdks/python.mdx has the same issue. It still documents search default 5, and it still uses remaining_credits, total_credits_used, endpoint, offset, and items-style history examples. It also lacks proper schema() / validate() coverage for the current Python v2 branch.

9. The MCP docs are internally inconsistent on the v2 branch. They claim full v2 coverage, but the documented tool list is still largely the old tool set rather than the actual v2-aligned surface.

10. transition-from-v1-to-v2.mdx still points readers to service pages / API reference pages for exact v2 payloads, but those pages are still mixed or stale as noted above.