fix: remove husky

[DaxServer]

Summary by CodeRabbit

• Chores
  • Removed Husky and its related configuration, including the pre-commit linting hook and associated environment variable from the release workflow.
  • Updated dependencies to remove Husky from development dependencies.

[coderabbitai]

## Walkthrough

This change removes Husky from the project by deleting its dependency from package.json, eliminating the pre-commit hook file, and updating the release workflow to stop disabling Husky explicitly. As a result, automated linting on commit is no longer enforced, and Husky is no longer part of the development setup.

## Changes

| File(s)                       | Change Summary                                            |
|------------------------------|-----------------------------------------------------------|
| .github/workflows/release.yml | Removed the `HUSKY=0` environment variable from release job. |
| .husky/pre-commit             | Deleted the pre-commit hook that ran `bun lint`.          |
| package.json                 | Removed "husky" from devDependencies and deleted the prepare script invoking husky. |

## Possibly related PRs

- geocoding-ai/mcp#4: Adds Husky and a pre-commit lint hook, which is the opposite of this PR's removal of Husky and its hooks.
- geocoding-ai/mcp#5: Modifies the release workflow by explicitly disabling Husky, contrasting with this PR's removal of that environment variable.

## Poem

> Goodbye to Husky, our linting friend,  
> No more hooks before commits send.  
> The code is free, the leash is gone,  
> Developers cheer and hop along.  
> With every push and every merge,  
> The bunny leaps—no linting urge! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 477fccc and dabb09f.

📒 Files selected for processing (1)

• package.json (0 hunks)

💤 Files with no reviewable changes (1)

• package.json

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.