v0.1.3 — Expanded test coverage, dependency refresh, and workspace guidance

Highlights

Stronger test coverage and import validation

This release focuses on making @eldrforge/commands-git easier to change safely by adding comprehensive Vitest coverage:

• Added isolated unit tests for the primary commands:

  • clean
  • commit
  • precommit
  • review

  These tests fully mock external dependencies to keep behavior deterministic.

• Added module import/export validation:

  • New imports.test.ts and a broader smoke.test.ts ensure src/index exports remain stable and modules load correctly (helps catch packaging/export regressions early).

• Added extended tests for performance helpers:

  • PerformanceTimer
  • package.json discovery/scanning helpers
  • dependency collection
  • file dependency detection helpers

Impact: No runtime behavior changes, but significantly improved confidence when refactoring or updating dependencies.

Dependency updates

Updated internal @eldrforge dependencies to newer patch versions:

• @eldrforge/core: ^0.1.1 → ^0.1.2
• @eldrforge/git-tools: ^0.1.17 → ^0.1.18
• @eldrforge/github-tools: ^0.1.19 → ^0.1.20
• @eldrforge/ai-service: ^0.1.18 → ^0.1.19
• @eldrforge/shared: ^0.1.7 → ^0.1.8

package-lock.json was updated accordingly.

Impact: Consumers should see minimal change (patch-level bumps), but you should still run a fresh install (npm install) when upgrading.

Developer notes

Cursor rule: avoid local dependencies

Added a Cursor rule at .cursor/rules/no-local-dependencies.md that documents a team constraint:

• Do not use local file:// dependencies between projects.
• Prefer published packages with versioned dependencies.

This is documentation/guidance (not runtime enforcement), intended to prevent accidental “works on my machine” dependency graphs.

Breaking changes

• No breaking API changes detected.
• No production source changes in this range; changes are tests, dependency versions, and editor tooling guidance.