chore(build): replace npm with rnr task runner

- Remove Node.js dependencies (husky, commitlint)
- Remove package.json, package-lock.json, .husky/
- Add rnr task runner with platform binaries
- Add rnr.yaml with equivalent task definitions
- Update CLAUDE.md with rnr commands
- Update README.md contributing section
- Update .gitignore to allow .rnr/bin/ binaries

This eliminates the Node.js dependency for local development.
CI still uses Node.js for commit linting via the workflow.

Author: CalvinAllen

.gitignore

@@ -5,6 +5,9 @@ dist/
 *.so
 *.dylib
 
+# But allow rnr binaries (they should be committed)
+!.rnr/bin/*
+
 # Test binary, built with `go test -c`
 *.test
 

.husky/commit-msg

@@ -0,0 +1,7 @@
+version: 0.1.0
+platforms:
+- linux-amd64
+- macos-amd64
+- macos-arm64
+- windows-amd64
+- windows-arm64

.rnr/bin/rnr-linux-amd64

@@ -24,7 +24,7 @@ Guidance for Claude Code when working with the dtvem codebase.
 5. **Conventional commits** - Format: `type(scope): description`
 6. **GitHub Issues for TODOs** - Use `gh` CLI to manage issues, no local TODO files. Use conventional commit format for issue titles
 7. **Pull Requests** - Use the conventional commit format for PR titles as you do for commits
-8. **Run validation before commits** - Run `npm run check` (format, lint, test) before committing and pushing
+8. **Run validation before commits** - Run `./rnr check` (format, lint, test) before committing and pushing
 9. **Working an issue** - When working an issue, always create a new branch from an updated main branch
 10. **Branch Names** - Always use the conventional commit `type` from the issue title as the first prefix, and the `scope` as the second, then a very short description, example `feat/ci/integration-tests`
 11. **Check branch status before pushing** - ALWAYS verify the remote tracking branch still exists before pushing. If a PR was merged/deleted, create a new branch from main instead of trying to push to the old one.
@@ -35,7 +35,20 @@ Guidance for Claude Code when working with the dtvem codebase.
 
 ## Quick Reference
 
-### Build Commands
+### Task Runner (rnr)
+
+```bash
+./rnr --list           # List all available tasks
+./rnr check            # Format, lint, and test
+./rnr build            # Build both CLI and shim
+./rnr test             # Run tests
+./rnr format           # Format code
+./rnr lint             # Run linter
+./rnr clean            # Remove build artifacts
+./rnr deploy-local     # Build and deploy to local installation
+```
+
+### Build Commands (raw)
 
 ```bash
 # Build executables

.rnr/bin/rnr-macos-amd64

@@ -91,21 +91,17 @@ See [Getting Started](https://dtvem.io/docs/user-guide/getting-started) for more
 Contributions are welcome! See [CONTRIBUTING.md](CONTRIBUTING.md) for:
 
 - Setting up your development environment
-- npm scripts for building and testing
+- Task runner commands for building and testing
 - Commit conventions and PR guidelines
 - CI/CD workflows and release process
 - Adding new runtime providers
 
 ### Quick Setup
 
 ```bash
-# First, install dtvem (see Installation section above)
-# Then clone and set up the development environment:
 git clone https://github.com/CodingWithCalvin/dtvem.cli.git
-cd dtvem
-dtvem install      # Install Node.js for git hooks
-npm install        # Set up dev dependencies
-npm run check      # Run format, lint, and tests
+cd dtvem.cli
+./rnr check      # Run format, lint, and tests
 ```
 
 Looking for something to work on? Check out [good first issues](https://github.com/CodingWithCalvin/dtvem.cli/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22).