v0.1.12

Turn on noUnusedLocals/noUnusedParameters

Release 0.1.12

Two ranges that only touch overlap when both bounds are closed

The boundary case used inclusiveStart || inclusiveEnd, so [a,b) and [b,c)
were reported as overlapping. They share exactly one instant — the second
range's start, which is also the first range's end — and it belongs to both
only when both bounds are closed. With the end open it is in the second alone,
and there is no instant in both.

An && is what that means. A range pair that genuinely shares a span is
unaffected.

Print the test run, not just its JSON

The workflow ran vitest with --reporter=json alone, so a failing job wrote
its report to a file and nothing to the log: an exit code, and not one word
about which test failed. Twice today that meant finding a failure by deduction
instead of reading it.

The default reporter runs alongside; the JSON one still feeds the smoke gate.

Format the Rust crates, and gate it so they stay formatted

Twelve of the thirteen crates had drifted — 949 differences in all, atlas
alone 345, and build.rs files that had never been through the formatter.
None of their workflows checked, so nothing ever said so; the drift only
surfaced when it took a publish job down.

cargo fmt applied throughout, and a cargo fmt --check step added to each
workflow so this cannot happen again. Formatting only: the Rust tests pass
unchanged in every crate.

One spot in atlas needed a real edit rather than the formatter: cargo fmt
rewrote a return Err(format!(…)) arm back to the inline form on every run
while --check kept asking for the block form, so the file could never
converge. The message is bound to a name, which fits the line budget and
settles it.

---

Changes since v0.1.11.