Problem
Program behavior depends not only on input but also on packages, routes, backends, and optimizations; conventional fuzzing misses that dimension.
Compiler testing · configuration plans
Program behavior depends not only on input but also on packages, routes, backends, and optimizations; conventional fuzzing misses that dimension.
Program behavior depends not only on input but also on packages, routes, backends, and optimizations; conventional fuzzing misses that dimension.
Flaky executions, infrastructure failures, and preserving the exact mismatch category.
A language-neutral core, typed observations, seven oracle families, fresh-process replay, exact fingerprints, and deterministic program/plan reducers.
Reproducible artifacts and explicit separation of confirmed, unstable, inconclusive, and infrastructure outcomes.
Fresh-process confirmation, exact fingerprints, typed outcomes, and deterministic reduction.
Outcome model, oracle core, replay, fingerprinting, and reducers.