1.0.6: Publish workflow and repo hygiene updates (lockfile + KodrDriv config)

Summary

This release is a maintenance/update release focused on making publishing more reliable and keeping the repo clean, primarily by formalizing lockfile handling and tracking only the necessary KodrDriv publish configuration.

Changes

Publishing / release process

• Added KodrDriv publish configuration via .kodrdriv/config.yaml to enforce a consistent rule during publish:
  • publish.lockfilePolicy: ignore (publishing should not require a committed package-lock.json).
• Updated .gitignore to:
  • Ignore KodrDriv working files (.kodrdriv*, .kodrdriv/*) while explicitly keeping !.kodrdriv/config.yaml tracked.
  • Ignore package-lock.json.

Why it matters: KodrDriv publish workflows can fail prechecks if the working tree becomes dirty due to lockfile rewrites. These changes make publishes less brittle by aligning repo tracking with the publish policy.

Package metadata / tooling

• Updated package.json (small maintenance changes):
  • Version set to 1.0.6
  • Minor dependency/tooling and script refinements (no functional runtime changes indicated by the diff scope).

Impact

For library consumers

• No user-facing API changes are indicated in this release; it is primarily build/publish hygiene.

For contributors / maintainers

• package-lock.json is now intentionally not tracked and is gitignored.
  • Local installs may still generate a lockfile; it should not be committed.
  • CI/publish will rely on npm install behavior without a committed lockfile, so dependency resolution may vary over time within semver ranges.

Breaking changes

• No breaking changes detected in the changes from main to HEAD.
• Note: while not an API break, the repository policy change (not committing package-lock.json) may require workflow adjustments for contributors who previously relied on a committed lockfile for reproducible installs.