fix(packaging): put the release recipes on v3's build

Neither packaging/arch/PKGBUILD nor the Homebrew formula had been run
since Phase 1, and both were still calling v2's CLI: `wails3 build`
takes -tags, -obfuscated and -garbleargs and nothing else, so
`-clean -trimpath -ldflags` fails at the flag parser. Both also
installed from build/bin/, which is v2's output path — v3 writes to
bin/, and build/ is tracked build assets now.

Three more things the tree needs that neither recipe had. The tasks
invoke `wails3` by bare name, so scripts/toolbin has to be on PATH or
the build dies at its first sub-task. `wails3 build` has no -ldflags at
all, and build:native computes BUILD_FLAGS in its own vars: so a CLI
variable cannot override it — LDFLAGS_EXTRA is appended inside the
production -ldflags string instead, on linux and darwin alike, empty by
default so make build-dev/build-prod are unchanged. And bundling is a
separate step from building: `task build` produces a bare binary on
both platforms, so the formula's macOS path runs `task package`.

The build assets were the scaffold's, not this app's. Info.plist named
CFBundleExecutable `yjref` and com.example.yjref, nfpm packaged
./bin/yjref, the .desktop template said "A yjref application" — an .app
built from that plist would not have launched. They generate from
build/config.yml, whose info block had never been filled from
wails.json either; `wails3 task common:update:build-assets` is the fix.
nfpm's homepage and license are not derived from it and are set by
hand, which is noted in place, and the refresh regenerates build/ios
and build/android, which this repo does not carry.

arch-package.yml's pacman list moves to webkitgtk-6.0/gtk4 to match the
PKGBUILD's depends(): makepkg installs nothing itself, so a mismatch
fails at link time rather than at check time.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UDCbcCZQepnpSQYJ6SxxZm

build/config.yml

@@ -4,14 +4,19 @@
 version: '3'
 
 # This information is used to generate the build assets.
+# The version here is the one baked into the platform *metadata* assets
+# (Info.plist, the .desktop file, nfpm). It is not what the app reports:
+# main.version is stamped at link time from the packaging recipes, which
+# derive it from the git tag. Keep it in step with packaging/arch/PKGBUILD's
+# pkgver and the Homebrew formula's version when cutting a release.
 info:
   companyName: "yellowjacket" # The name of the company
   productName: "yellowjacket" # The name of the application
   productIdentifier: "app.yellowjacket" # The unique product identifier
-  description: "A cross-platform desktop music player" # The application description
+  description: "Cross-platform desktop music player — local library, MusicBrainz explore & auto-tag" # The application description
   copyright: "(c) 2026, yellowjacket" # Copyright text
   comments: "yj@yellowjacket.app" # Comments
-  version: "0.0.1" # The application version
+  version: "1.3.0" # The application version
   # cfBundleIconName: "appicon" # The macOS icon name in Assets.car icon bundles (optional)
   #                               # Should match the name of your .icon file without the extension
   #                               # If not set and Assets.car exists, defaults to "appicon"