Merge branch 'main' into refactor/abstraction-layer

Resolve merge conflicts by:
- Keeping version 0.2.2 from refactor branch (next release)
- Using fixed gh CLI release workflow from main (atomic release creation)
- Merging CHANGELOG histories: installer releases (0.1.x) and protocol work (2.x)

Conflicts resolved:
- .github/workflows/release.yml: Use gh CLI for atomic releases
- CHANGELOG.md: Merged both release histories chronologically
- pyproject.toml: Keep 0.2.2 for next refactor release

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

.github/workflows/release.yml

@@ -326,17 +326,13 @@ jobs:
           name: release-notes
 
       - name: Create GitHub Release
-        uses: softprops/action-gh-release@v1
-        with:
-          tag_name: ${{ needs.validate.outputs.tag }}
-          name: "BLE-Reticulum ${{ needs.validate.outputs.tag }}"
-          body_path: RELEASE_NOTES.md
-          draft: false
-          prerelease: false
-          files: |
-            release-artifacts/*
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          gh release create "${{ needs.validate.outputs.tag }}" \
+            release-artifacts/* \
+            --title "BLE-Reticulum ${{ needs.validate.outputs.tag }}" \
+            --notes-file RELEASE_NOTES.md
 
       - name: Release summary
         run: |