chore: sync t3code-bin to 0.0.34

Matches what is already published to edge: 0.0.34 was built on the server
before the bump reached git, so the checkout read as out of date and queued a
rebuild of the older 0.0.33-2 that promotion then refused. Produced by
bin/sync-upstream, the same path the scheduled workflow uses.

pkgbuilds/t3code-bin/PKGBUILD

@@ -7,8 +7,8 @@
 # from the release feed the app updates itself from.
 
 pkgname=t3code-bin
-pkgver=0.0.33
-pkgrel=2
+pkgver=0.0.34
+pkgrel=1
 pkgdesc="Open-source control plane for coding agents"
 arch=('x86_64')
 url="https://t3.codes"
@@ -60,7 +60,7 @@ source_x86_64=("${_appimage}::https://github.com/pingdotgg/t3code/releases/downl
 noextract=("${_appimage}")
 sha256sums=('cb905ff341372ef2ef6e402cf485959f8bd1df8f0efebee4cda1afdd5e6abc0a'
             '935d8f2af0c703f9c39517ee57cc4930b19d02d533be930b63f0e82f93614b43')
-sha256sums_x86_64=('415c8648f43c3d22d572f27f2c50fdc8c310ea7fcde9537b903e1e2f1c8775a1')
+sha256sums_x86_64=('6077e207cc1e7e65858f73313534abe1da357227f40225854e1abac34dedba04')
 
 prepare() {
   chmod +x "${srcdir}/${_appimage}"