Crate varar_runner 

varar-runner — the imperative shell shared by var test-runner adapters.

Oath discovery (the shared glob semantics), planning/running examples, failure rendering, and the filesystem varar.lock.json baseline store for drift. Contains no pipeline logic — it delegates to varar-core. Steps are supplied by the caller (Rust compiles step files in; there is no dynamic load_steps), as a Registry plus a context factory.

Re-exports

pub use baseline_store::FileBaselineStore;

pub use discovery::find_oaths;

pub use discovery::match_oath;

pub use render::render_failure;

pub use results::Results;

pub use results::result_file_path;

pub use results::write_oath_results;

pub use run::example_names;

pub use run::plan_oath;

pub use run::run_example;

Modules

baseline_store

The filesystem BaselineStore: the committed drift baseline lives at the project root as varar.lock.json. The core owns the format; this only reads and writes the raw text.

discovery

Oath discovery: the shared glob→regex semantics (matching the Python/Ruby runners byte-for-byte on **, *, ?), recursive file walk, include/exclude.

render

Pure human-readable rendering of a step failure, anchored to the .md. Port of varar_runner.render.render_failure; reuses the core diff payloads.

results

Persists run results for the language server (ADR 0014) — the shell half of the contract the core builds the payload for. Writes <root>/.varar/<oath_path>.json, which the (language-neutral) LSP reads to turn a failure into an editor diagnostic.

run

Planning and running examples, plus the adapter display-name rule.