emrg: v0.3.35 names a tree without the batch-call fix, so the next release is 0.3.36 #2695

What is wrong

Tag v0.3.35 names commit 6522ecfe, and master has moved past it to f8797d27 — the
merge of the fix that makes the "batch call" reminder a system turn instead of a user
turn. Both the tagged tree and today's master declare the same version, 0.3.35, while
their contents differ: the tagged tree carries the old user role, master carries the
system one. One version number therefore names two different programs, and a host reading
0.3.35 cannot tell which of them they have.

The Build Release run 41646786107 that the tag triggered was still building when this was
written, with no release published yet (gh release view v0.3.35 answers release not found). Whether it publishes or fails, the same conclusion holds: the version number has to
move, because 0.3.35 is already spent on a tree that does not contain the fix.

The symptom the fix addresses is visible on any host running an older build: after a round
that dispatches exactly one tool call, the daemon appends a reminder whose text is
batch call, and it appends it as a user turn. A user turn is the host's voice — a client
renders it as the host's own bubble, a transcript attributes it to the host, and a compaction
summarises it as something the host said — so the reminder appears in the conversation as a
message the host never typed.

What the release must satisfy

1. Every version declaration in the tree agrees on 0.3.36 — the eight sources
   scripts/bump-version.py rewrites, proved by tests/test_version_sync.py.
2. The release commit is cut on a master that contains the fix (f8797d27 or later), so the
   published artifact actually carries it.
3. Tag v0.3.36 is created only after that master state is reached, and it names a tree whose
   version is 0.3.36 (scripts/check-release-tag.py v0.3.36).
4. The published release is non-draft, non-prerelease, and carries the full 11-asset set for all
   four platforms, including the macOS package and both .zsync files, confirmed by
   scripts/check-release-published.py v0.3.36.
5. v0.3.35 is left alone. It is not deleted, moved or re-created, and no published version is
   rolled back — the remedy for a version that names the wrong tree is the next version, not a
   rewrite of the last one.