Fix Swift 6 file watcher teardown for releases

Move FileWatcher cleanup into the MainActor-isolated stop path so Swift 6 does not reject deinit access to non-Sendable Dispatch file system sources. Bump the app bundle version to 1.0.4 so the next release tag and packaged metadata stay aligned.

Constraint: The GitHub release workflow is tag-driven, so the bundle version should match the new patch release
Constraint: DispatchSourceFileSystemObject is not Sendable under Swift 6 checks in nonisolated deinit
Rejected: Add @preconcurrency to Dispatch imports | it would only downgrade a real Swift 6 isolation issue into a warning
Rejected: Leave version metadata at 1.0.3 | it would mismatch the new release tag users download
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Keep FileWatcher teardown on the main actor while it owns main-queue Dispatch sources
Tested: swift build --disable-sandbox; swift build -c release --disable-sandbox
Not-tested: Live GitHub Actions rerun of the macOS release workflow after tagging v1.0.4

Author: 陈一斌

SkillsManager/Info.plist

@@ -19,9 +19,9 @@
 	<key>CFBundlePackageType</key>
 	<string>APPL</string>
 	<key>CFBundleShortVersionString</key>
-	<string>1.0.3</string>
+	<string>1.0.4</string>
 	<key>CFBundleVersion</key>
-	<string>3</string>
+	<string>4</string>
 	<key>LSMinimumSystemVersion</key>
 	<string>$(MACOSX_DEPLOYMENT_TARGET)</string>
 	<key>NSHumanReadableCopyright</key>

SkillsManager/Services/FileWatcher.swift

@@ -46,8 +46,8 @@ final class FileWatcher: ObservableObject {
     }
 
     deinit {
-        for source in sources {
-            source.cancel()
+        MainActor.assumeIsolated {
+            stopAll()
         }
     }
 }