fix: resolve npm bin symlinks

[fqjony]

Summary

• resolve the npm global-bin symlink before starting the Node implementation
• release the fix as @udx/rabbit-repo 0.1.4

Validation

• make test
• npm pack --dry-run --json

[Copilot]

Pull request overview

This PR fixes execution when rabbit.ci is invoked through an npm-installed symlinked global bin entry by resolving the symlink chain to compute the correct script directory before launching the Node implementation. It also publishes the fix as @udx/rabbit-repo@0.1.4.

Changes:

• Resolve bin/rabbit.ci’s real location by following symlinks before computing SCRIPT_DIR.
• Extend tests/suite.sh to validate running the CLI via a symlinked “global bin” path.
• Bump package version to 0.1.4 (and lockfile version fields).

Reviewed changes

Copilot reviewed 2 out of 4 changed files in this pull request and generated no comments.

File	Description
bin/rabbit.ci	Adds symlink-resolution loop to ensure rabbit.ci.js is located correctly when invoked via npm global-bin symlinks.
tests/suite.sh	Adds coverage that runs the CLI through a symlink to emulate npm global-bin behavior.
package.json	Bumps package version to 0.1.4.
package-lock.json	Updates lockfile version fields to match 0.1.4.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.