v0.1.5

Changed

• Picked up ktav 0.1.5 — the upstream Rust crate now exposes
  Error::Structured(ErrorKind) with byte-offset spans, retroactive
  #[non_exhaustive] on the error enums, and a public ktav::thin
  event-based parser. The JS binding's user-visible behaviour is
  unchanged: thrown Error values carry the same human-readable
  message (Display strings for the seven canonical categories are
  byte-identical to ktav 0.1.4 — verified by ktav's own pinning
  tests). Mapping ktav::ErrorKind to a structured JS error class
  hierarchy (KtavMissingSeparatorSpaceError, KtavDuplicateKeyError,
  etc.) is separate follow-up work tracked in the workspace's
  STRUCTURED_ERRORS.md.

Fixed

• CI/release workflows switched from npm ci to npm install.
  Strict npm ci validation rejects the lockfile when
  package.json declares per-platform optionalDependencies
  (@ktav-lang/js-<triple>) at a version that does not yet exist
  on the npm registry — which is exactly the state at release-time
  when these packages are about to be built and published by the
  workflow's own matrix jobs. npm install reconciles
  package.json with the lockfile and proceeds. Trade-off:
  marginally slower (re-resolves a few entries) but eliminates the
  chicken-and-egg deadlock that has blocked every release attempt
  since 0.1.3.

npm: ktav@0.1.5 (main) + @ktav-lang/js-<triple>@0.1.5 (eight platform packages).