fix(docs): allow integration-specific language support
The docs checks on #3197 and #3199 failed because the OpenAI Toolset guide has TypeScript and Python examples but no Go SDK. The rule required all three Stagehand SDK languages on every page, with a one-off exception for Claude's toolset.
Allow pages under v4/integrations/ to use the SDK languages documented on that page. Keep all three languages required for core guides and references. Validate each tab group directly to preserve consistent language choices and reject duplicate tabs, while allowing repeated single-language groups.
Validation: all 45 docs unit tests pass, including seven language-policy cases; targeted lint, formatting, and whitespace checks pass. Local tests used the existing installed Vitest 4.1.9; CI uses the locked dependencies.
Summary by cubic
Fixes the docs language-policy test so integration guides no longer require SDK snippets they don't cover.
- Integration pages under
v4/integrations/now only require the SDK languages documented on that page, instead of all three. - Core guides and references still require TypeScript, Python, and Go.
- Language tabs are now validated per tab group, preserving consistent language choices within a page and rejecting duplicate tabs.