v0.4.0

Breaking: Schema directories passed to export --schemas now also need zenodo.json.
Copy the verified structural subset into your schema directory.
The new watcher uses the same five-file layout; see Zenodo coverage and limits.

Added

• Run an offline schema recovery example with an explicit synthetic approval and reproducible mapping hashes.
• Check Zenodo mapping paths against a verified structural subset; importer source changes produce review drafts. This does not validate complete deposits.
• Find corresponding fields in two formats and export seven SSSOM spokes with the
  crosswalk hub. The Go spoke relates a module path to the repository field.
• Preview broken schema paths, new fields and a behind mapping pin with the
  offline schema watcher. It prints deduplicated issue drafts.
• Mapping exports include each original crosswalk cell alongside the exported path, so readers can show corrections and empty cells.
  See the mapping export contract.

Changed

• The README now leads with checking and exporting. Finding codes, the dated findings report and contributor instructions have dedicated guides.

Fixed

• Missing Zenodo importer files produce review drafts instead of aborting unrelated schema and pin checks. See Zenodo coverage.
• The recovery example reports unreadable approvals and existing output directories as CLI errors without modifying existing files.
• Hub commands reject malformed original crosswalk cells, keeping mapping validation consistent with the export contract.
• SSSOM exports use distinct field and format URI prefixes so reference readers can load them.
  See the validation and compatibility guide.
• Schema conformance checks recognize array references and tuple item schemas.
• A CELL_NO_AUTHOR finding now says the author or contributor has no path, not no row, which was
  wrong when its curated row has a null path, as CFF's contributor row does.
• export refuses a crosswalk cell that already reads as a list, such as authors[], with a CELL_PATH finding, instead of
  writing authors[][] and its sub-terms into the export.
• A check of the working tree skips a directory whose name matches an input file, such as examples/x.json, as
  --ref already did, instead of exiting 2.