[vishnuv688]

What & why

Closes #496. Part of #494. Stacked on #508.

Nothing stopped a change from making traces heavier, and planned work (#499 page resources, the dense filmstrip) grows them by design. Each smoke expectation file now carries a required traceBudget, and pnpm smoke:assert fails when the combined size of the zips an example's run wrote exceeds it, listing each zip largest first.

Type of change

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Polish (an improvement to an existing feature)
• Breaking change (existing behavior changes for users)
• Documentation
• Internal (build, CI, dependencies, tooling)

Packages touched

• shared (types and contracts)
• core (framework-agnostic capture/reporting)
• elements (published element/snapshot API — @wdio/elements)
• service (WebdriverIO adapter)
• nightwatch-devtools (Nightwatch adapter)
• selenium-devtools (Selenium adapter)
• selenium-devtools-py (Selenium Python adapter)
• backend (server)
• app (UI)
• script (page-injected runtime)
• trace (Trace mode)

Only conformance (the smoke checker and its expectation files), which the list does not include.

Capability matrix

• packages/conformance/src/features.ts updated, and tables regenerated with pnpm docs:capabilities, if this adds or changes user-facing behaviour

Not needed: CI only.

Notes for reviewers

Design notes

• The total is per example rather than per zip, because WDIO writes one zip per spec and the others write one.
• traceBudget carries maxBytes plus the measuredBytes baseline and where it was measured, so the headroom left is visible. It is required, so a new example cannot skip it.
• Every run now prints trace zips total N of a M-byte budget. Green runs upload no artifact (the upload step runs only on failure), so that log line is the only size record a passing job leaves.

Budgets (the measured total plus about 25%, rounded up to 10 KB)

This PR's first CI run (40948877371) measured every example with #508's dedupe in place, and the budgets are set from that:

Example	Measured	Budget
wdio-mocha (2 zips)	966,841	1,210,000
selenium-mocha	158,349	200,000
nightwatch-bdd	260,322	330,000
python-pytest	688,296	870,000

Against the earlier baseline (an older branch run's artifact, before #486), the dedupe cut Nightwatch by 31%, Python by 14% and WDIO by 9%; Selenium's example takes few per-action screenshots and barely moved. Run-to-run variation seen across artifacts is up to about 13%, inside the headroom.

Testing

pnpm test (3295 passed) and pnpm lint are green. New tests: under budget passes, over budget fails with the exact message, the check runs inside checkExample, the field is required, and invalid values are rejected.

Screenshots / recordings

Not applicable: no UI change.

🤖 Generated with Claude Code