Add FuseGenerator binary package manifest for release zip distribution

Expose FuseGenerator as an SPM binary target backed by GitHub release assets.
Document how to update Package.swift URL/checksum for each new release.

Author: fmeunier

.gitignore

@@ -2,3 +2,4 @@ build
 project.xcworkspace
 xcuserdata
 .DS_Store
+.build

Package.swift

@@ -0,0 +1,19 @@
+// swift-tools-version:5.3
+import PackageDescription
+
+let package = Package(
+  name: "FuseGenerator",
+  products: [
+    .library(
+      name: "FuseGenerator",
+      targets: ["FuseGenerator"]
+    ),
+  ],
+  targets: [
+    .binaryTarget(
+      name: "FuseGenerator",
+      url: "https://github.com/fmeunier/FuseGenerator/releases/download/fuse-generator-1.5.0-rc3/FuseGenerator-1.5.0-rc3.qlgenerator.zip",
+      checksum: "8ebbd7609cfb5a5d41aeee14c62d94fdcf8a5b5416e7db41b42539ecda8dcd9e"
+    ),
+  ]
+)

README.md

@@ -71,6 +71,19 @@ After the workflow completes, verify on GitHub:
 - The zip asset is attached.
 - The SHA-256 value appears in release notes.
 
+### Update `Package.swift` for each release
+
+`Package.swift` declares a binary target that points at the published release zip and checksum.
+
+After publishing a new release tag:
+
+1. Copy the new asset URL from the release page.
+2. Copy the SHA-256 from release notes (or asset digest).
+3. Update `url` and `checksum` in `Package.swift`.
+4. Commit and push the `Package.swift` update.
+
+Current bootstrap state: `Package.swift` points at `fuse-generator-1.5.0-rc3` until a final non-RC tag is published.
+
 ### Testing the workflow safely
 
 Use a throwaway pre-release style tag first (still matches `fuse-generator-*`):