Expand QA-Lab with runtime parity scenarios

## What changed OpenClaw expanded its QA-Lab on 18 May 2026 with new runtime parity tiers. The update adds explicit checks for Codex versus Pi compatibility and broader tool fixture coverage. Token-efficiency artifacts now ship alongside each test run to surface per-scenario costs.

The changes arrived as part of the existing self-hosted package. No separate download is required for users already running the latest CLI build.

## Why it matters Vibe Builders gain a clearer way to compare agent behavior across model providers without leaving their own infrastructure. This reduces surprise token spend when switching between Codex and Pi for the same workflow.

The move pressures closed cloud agents that hide these runtime details behind managed dashboards. It also raises the bar for other open-source projects that still treat parity testing as an afterthought.

## How to use it Pull the latest OpenClaw release from GitHub and run the qa-lab command with the parity flag enabled. Results appear in the local reports directory as JSON plus a simple cost table.

Users on the free MIT build need only their existing VPS and an API key for the model under test. No paid tier or external service is required to view the new artifacts.

## Watch for Confirmation will come when community ClawHub skills start publishing their own parity scores. The bet breaks if token costs remain unpredictable despite the new reports. Expect a follow-up that adds scheduled parity runs across multiple providers next.