Discovery: opt-in joint parameter refinement (refine.rs, via lawsynth-opt
coordinate_minimize, guaranteed non-worsening trajectory MSE) and dependency/
causal hypothesis discovery (causal.rs, via lawsynth-causal Granger/independence/
time-order, framed as a hypothesis with its assumption set). CLI --refine/--causal.
Verification: wire tests/{conformance,end-to-end,cross-language} to execute against
the real compiled CLI — valid worlds round-trip, every bad-* asserted-rejected,
unbuilt native/TS legs honestly skipped. 26 pytest cases.
Rust workspace 342->352 tests; +26 system-verification cases. clippy/fmt clean.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Invalid expression rejection
This is an executable conformance case. Run it from this directory with:
python3 run.py
A checksum-valid bundle with an unknown binary expression tag must be rejected by the native decoder.
The fixture contract is in input.json; the observable acceptance, rejection, or explicitly unsupported outcome is in expected.json. The runner builds the archive and invokes the native LawSynth CLI for supported and invalid cases. It does not implement a shadow simulator.