# Equivalent assertion fixtures
Each case preserves its source recall matchers and desired findings. `assertionModules` entries identify original synthetic providers by literal load specifier. Ruby supports a limited configured assertion-factory proof; these cases also require provider, alias, mutation and comparison behavior beyond that subset. Each case's oracle remains authoritative: equivalent handlers require findings, conflicting handlers forbid them, and uncertain providers must not gain assertion trust. Undeclared providers intentionally have identical source; spelling alone never grants trust. A passing subset does not close the remaining completion gaps.
Each isolated run uses the shared `equivalent-assertions` root to resolve providers, `--definitions` to select handlers, and `--config` to select configuration. The checker never executes Ruby. Mappings record translated dimensions and narrow syntax/API exclusions.
Namespace factory objects are original callable proxies that capture method(:expect) and delegate call to that explicitly exported Method. Their modifier and nested-builder members express the JavaScript callable-with-properties dimension through Ruby objects. The exported expect(actual) has no added overload. A configured file identity does not grant trust to arbitrary helper return values.