docs(smartui): fix broken syntax in code snippets across SDK docs

[chaitanyas-maker]

What this fixes

I ran every fenced code block in the SmartUI doc set (1,317 blocks across 103 pages) through the real interpreters — python3 compile, node --check, ruby -c, json.loads — and fixed every block that could not parse. Five defect families came out, each reproduced live.

1. The .smartui.json config sample is invalid JSON (7 SDK pages)

enableJavaScript": true is missing its opening quote in the Cypress, Playwright, Puppeteer, Selenium-JS, Selenium-Ruby, TestCafe and WebdriverIO pages, and visual": true in the Espresso page.

Verified live against the CLI:

# documented config
[smartui] Error: Expected property name or '}' in JSON at position 7

# same config with the quote restored
✔ Screenshots captured successfully
✔ Finalized build

This one blocks onboarding outright — a user pasting the documented config cannot start.

2. Missing opening quote inside code (8 files, Java / JavaScript / Ruby)

smartuiSnapshot(driver, HomePage-Header"), By.id(content"), System.getenv(PROJECT_TOKEN"), new File(path/to/document.pdf"), page.navigate(https://example.com"), Map<String, Object">, and others.

3. Curly quotes in Cypress snippets (12 blocks)

cy.smartuiSnapshot(‘Screenshot Name’, options); fails with SyntaxError: Invalid or unexpected token.

4. JavaScript object literals inside Python blocks (Selenium and Playwright Python SDK)

# documented — SyntaxError, "class" is reserved in Python
options = { ignoreDOM: { class: ["Class-1"] } }

# fixed
options = { "ignoreDOM": { "class": ["Class-1"] } }

The other bare keys (id, xpath, cssSelector) parse but raise NameError at runtime. This also retags 23 fences that were marked ```rb or ```py while containing Python, so highlighting was wrong too.

5. Corrupted operators

async t ="> { should be async t => { (TestCafe), and gem 'lambdatest-selenium-driver', '~"> 1.0' should be '~> 1.0' (Ruby SDK).

Also fixed

• ffrom playwright.sync_api import ... typo in the Playwright Python quickstart
• Unclosed let config = { object in selenium-visual-regression.md
• Python using backticks where a string literal was intended in the Remote executor URL
• Two missing closing fences (smartui-appium-hooks.md, smartui-cli-env-variables.md) that left <TabItem> markup rendering inside code blocks
• A Java block tagged ```javascript
• Broken fence titles of the form title="... to ignore by" ID"

Likely root cause

36bc2ac3 "best practice section update for smartui docs" (10 Nov 2025, 42 files, 8,863 insertions) introduced families 1 and 2; f153c312 "fixes for tabs" introduced family 5. The signature — a dropped opening " combined with a spurious " inserted before > — looks like a bad HTML-entity decode in a bulk automated edit rather than hand-typing. These have been published for over eight months and are live on testmuCom today.

Verification

After this change, every Python, Ruby and JSON config block in the SmartUI doc set parses, and no file has an unbalanced code fence. The remaining JavaScript parse failures are deliberate partial fragments (bare 'LT:Options': { ... } objects and curl commands in js-tagged blocks), not defects.

Suggested follow-up

A CI step that syntax-checks fenced code blocks would stop this recurring. Happy to raise that separately if useful.