v0.2.2

kg-ingest now handles SIGTERM and SIGINT: it finishes the record in flight, closes the driver, and reports interrupted: true so a re-run continues from the ledger.

Previously a wrapped timeout killed the process mid-write. On the embedded Ladybug backend that could leave a partial write the database then refused to reopen — Storage exception: Checksum verification failed, the WAL file is corrupted — which took out every later read as well.

Found by an end-to-end run against a local model, not in review: extraction is slow enough that a cron timeout is a realistic trigger, and record-level resumability does not help once the database itself will not open.

A signal cannot save you from SIGKILL or a power cut. Take a snapshot with kg export before a long ingest into an embedded backend.