v1.1.0

Two ways this could answer confidently and wrongly, both closed.

A comparison across extraction profiles now refuses

Comparing the Code du travail between 2020 and 2026 reported 1,196 articles added
and 12 removed. Nothing of the sort happened. The 2020 version was read by
pdf-lu/1 and yielded 13 provisions anchored art_541-8; the 2026 version was
read by akn-lu/1 and yielded 1,197 anchored art_l_010-1. Pairing those by
anchor compares two parsers, not two states of the law, and reports the
disagreement as legislation.

diff now returns provision_level_comparable and, when the two sides came from
different profiles, the status profiles_differ with both profile names, instead
of a diff. The web view refuses in the same terms and links each version instead.

Only when both profiles are known and differ. A null profile means the version
carries no text, and two unknowns are not evidence of a mismatch.

A server with no corpus now says so

The index is roughly 947 MB and is not distributed in the repository or the
container image, so anyone building from source gets a working binary over an
empty shelf. Every tool used to answer such a caller with an empty list:
coverage returned [], search returned [], and nothing distinguished "this
law does not exist" from "no law was ever loaded here". A model reading that
concludes the corpus is empty and tells its user so.

Every tool call against a reader-less server now returns no_corpus_mounted,
naming the directory it searched, how to build an index, and the public hosted
endpoint that serves the same tools over the full corpus.

Also

• A required date argument that is missing or malformed returns
  from_date required (ISO date, YYYY-MM-DD) instead of the .NET internal
  Value cannot be null. (Parameter 's'), which named a parameter absent from the
  tool schema to a caller that is usually a model.
• Side-by-side comparison renders every row rather than only changed ones, so on a
  comparison made mostly of insertions the toggle no longer appears to do nothing.
• SQLitePCLRaw pinned forward to 3.0.5, closing GHSA-2m69-gcr7-jv3q (high
  severity), which arrived transitively via the newest Microsoft.Data.Sqlite.
• Sitemap lastmod uses observed_from rather than a law's commencement date,
  which could legitimately be years in the future.

157 tests, including golden snapshots of every rendered page and every tool
response, so any byte that moves has to be explained.