Description
## Context
pkg/wind was extracted from pkg/nim to separate messaging (Wind, Leaf, Connect) from the agent layer (Nim interface, Runner, 5A, Brain, Registry). Backwards-compatible type aliases exist in pkg/nim so existing services keep working.
## Goal
Migrate all services to import Wind, Leaf, and Connect from `pkg/wind` instead of `pkg/nim`. Once all services are migrated, remove the aliases from `pkg/nim/aliases.go`.
## Services to migrate
- [ ] nimsforestissue
- [ ] nimsforestecommerce
- [ ] hetznertreehouse
- [ ] nimsforeststripe
- [ ] landregistry
- [ ] nimsforestodoo
- [ ] nimsforestwebchat
- [ ] nimsforestwebviewer
- [ ] nimsforestgrove
- [ ] nimsforestproductize
- [ ] nimsforestorganize
- [ ] nimsforestledger
- [ ] agentclaudecode
- [ ] agenthuman
- [ ] nimschatwidget
- [ ] landconfigregistry
- [ ] nebula
- [ ] nimble
- [ ] napoleon
- [ ] nectar
- [ ] nudge
- [ ] nostradamus
- [ ] numbers
- [ ] nightwatch
## Per-service migration
1. Change imports from `github.com/nimsforest/nimsforest2/pkg/nim` to `github.com/nimsforest/nimsforest2/pkg/wind` for Wind/Leaf/Connect usage
2. Keep `pkg/nim` import only if the service uses Nim interface, Runner, 5A, Brain, or Registry
3. `go build ./...` must pass
4. Commit, push, deploy
## Final cleanup
Once all services are migrated, delete `pkg/nim/aliases.go` from nimsforest2.
Nebula's reasoning: This is a codebase-wide refactoring task to complete the pkg/nim → pkg/wind separation. Categorized as improvement since it's tech debt cleanup, not a new feature. Priority medium because the backwards-compatible aliases mean nothing is broken today, but completing the migration unblocks removing the aliases and keeps the architecture clean.