the-provider-runtime-symmetry

To keep Claude and Codex provider runtimes in sync, run parity checks after editing shared provider code to validate that runtime options, environment construction, and executable lookups are mirrored across both adapters.

Provider runtime parity ensures that edits to shared provider code are reflected in both Claude and Codex adapters. You need it to prevent cross-provider drift and avoid production surprises when modifying shared runtime logic.

You validate environment construction and executable lookups by applying parity checks to edits in electron/providers and related env-building components. This ensures CLI env construction and tooling-status probes remain aligned across both runtimes.

You should run provider runtime parity checks after edits to any provider runtime, especially when changing runtime behavior or adding a new runtime option. Validate symmetry before merging to ensure both adapters remain aligned.

Syncing Claude and Codex provider runtimes affects edits in electron/providers and related env-building, IPC, and tooling-status components. It ensures runtime options and executable lookups are mirrored between both implementations.

Yes, provider runtime parity enforcement works with CLI env construction, executable lookup, IPC, and tooling-status probes. It validates that these environment-building components are mirrored across both Claude and Codex implementations.