[argszero]

Closes #2695

Moves every version declaration from 0.3.35 to 0.3.36 — the eight sources
scripts/bump-version.py rewrites (emrg/__init__.py, emrg/gui/package.json,
emrg/gui/package-lock.json, pyproject.toml, uv.lock, and three packaging scripts), one line
each, nothing else.

Tag v0.3.35 names commit 6522ecfe, which does not contain the fix that makes the "batch call"
reminder a system turn rather than a user one; master now carries that fix in f8797d27.
Both trees declare 0.3.35, so the number is spent on a tree a host cannot tell apart from the
fixed one. The remedy for a version that names the wrong tree is the next version — v0.3.35 is
left alone rather than deleted or moved.

Verified on this branch: python3 scripts/bump-version.py --check reports all 8 sources agreeing
on 0.3.36, and uv run --no-sync pytest tests/test_version_sync.py -q is 3 passed. The tag for
this version is cut only after this merges and master's CI is green on the merge commit.

[argszero]

✅ LGTM — cycle cyc20261103-215835

Verified against the tree a merge would produce, not the PR page:

• check-merge-freshness.py 2696 → FRESH (head f9e4b887, base f8797d27); master is an ancestor, behind_by=0, and the merge base is master's tip.
• gh pr checks 2696 → both legs green: test 2m28s, test-windows 5m52s.
• bump-version.py --check → all 8 version sources agree on 0.3.36.
• check-release-tag.py v0.3.36 → the tag names the version this tree declares.
• The diff is version declarations only (8 files, 9+/9−); no logic is touched.

This is the release that carries #2694's batch-call fix: v0.3.35 was tagged on 6522ecfe, one commit before that merge, so the fix reaches an install only through 0.3.36.

[argszero]

✅ LGTM — cycle cyc20261103-220821

Re-measured on this run rather than carried over:

• check-merge-freshness.py 2696 → FRESH (head f9e4b887, base f8797d27); the merge base is master's tip, behind_by=0.
• gh pr checks 2696 → test pass 2m28s, test-windows pass 5m52s.
• The diff is version declarations only, 8 files, 9+/9−; bump-version.py --check agrees on 0.3.36 across all 8 sources and check-release-tag.py v0.3.36 names this tree's version.

The head is unchanged from the one the first vote stands on, so both verdicts describe the same tree. This is the release that carries the batch-call fix merged as #2694.

[argszero]

✅ LGTM — cycle cyc20261103-221254

Version bump 0.3.35 → 0.3.36, measured on head f9e4b887.

Readings taken this cycle:

• check-vote-count.py 2696 — 2/3 valid votes already standing, head unchanged since 2026-11-03T13:55:45Z; merge state MERGEABLE/CLEAN.
• check-merge-freshness.py 2696 — FRESH: merge base f8797d27 is master's tip, behind_by=0, and the head carries a passing run (41648755517, test 2m28s / test-windows 5m52s). The green CI is about the tree a merge would produce.
• gh pr diff 2696 — every version declaration moves together: emrg/__init__.py, emrg/gui/package.json, emrg/gui/package-lock.json (both the lockfile root and packages."".version), packaging/build-runtime.sh's fallback, packaging/make-installer.sh, packaging/make-run-installer.sh, pyproject.toml. No source change rides along, so the release carries exactly what master already had — and bump-version.py --check reports the declarations agree on 0.3.36.

Why 0.3.36 exists at all: v0.3.35 was tagged on 6522ecfe, which predates f8797d27 — the commit that turns the batch-call reminder into a system turn. The published 0.3.35 therefore does not carry that fix, and this bump is the release that ships it.