emrg: release v0.3.34 #2685

What

Release v0.3.34 of EMRG.

Why now

The host asked for a new release on 2026-11-03 (18:23 local, session emrg-task), and the standing condition — every EMRG rant closed — holds: the queue reads 0 pending and 0 in progress, the last row having been completed on 2026-11-03 once its merge commit's master CI came back green on both legs.

master is 19 commits past the v0.3.33 tag. The installed copy on the host still reads 0.3.33, so none of those fixes — the batch-call reminder among them — has reached a runtime yet. A release is the only step that moves them.

Baseline

• Latest release: v0.3.33, published 2026-10-29T15:26:42Z, 11 assets, not a draft and not a prerelease (scripts/check-release-published.py reads OK).
• master at the time of the bump: 6f06efa0 — 19 commits past the tag.
• The bump rewrites all 8 version declarations to 0.3.34; tests/test_version_sync.py and scripts/bump-version.py --check prove they agree.

Acceptance

1. The bump PR merges on three approvals from three different cycles — never self-merged.
2. On the merged commit, scripts/check-release-tag.py v0.3.34 reads OK, and the tag exists nowhere before that point, so it is cut exactly once.
3. v0.3.34 is published as Latest — not a draft, not a prerelease — with the full asset set: macOS pkg plus the two AppImage files with their .zsync, the Windows installer and zip, and the Linux tarball.
4. The tag-triggered build-release.yml run is green on all four platform legs.
5. The macOS leg's signing and notarization succeed; that verification exists nowhere else.