1.0.18: Fix publish workflow by ignoring package-lock and tracking KodrDriv config

Summary

This release is focused on repository/publish hygiene rather than runtime behavior: it stabilizes publishing by ensuring package-lock.json is not tracked/committed and by committing the KodrDriv publish configuration that enforces that policy.

There are no functional/API changes to the library itself in this release.

Changes

Publishing / repo hygiene

• Stop tracking and committing package-lock.json.
  • package-lock.json is now gitignored.
  • CI already performs installs without a committed lockfile (and explicitly removes any existing lockfile before installing).
• Track KodrDriv publish configuration in the repo.
  • .kodrdriv/config.yaml is now committed (while other .kodrdriv/* files remain ignored).
  • KodrDriv is configured with publish.lockfilePolicy: ignore to avoid publish failures caused by a dirty lockfile during pre-publish steps.

Versioning

• Package version bumped to 1.0.18.

Impact

• Users: No runtime or API changes expected.
• Developers/maintainers:
  • Do not commit package-lock.json; local installs may generate it, but it should remain untracked.
  • Publishing should be more reliable because the workflow no longer fails due to lockfile changes that aren’t part of the release.

Breaking changes

• None detected in code or public API for this release. The main change is repository policy (lockfile is no longer committed).