[argszero]

Closes #2644

Stage 1 of the release: the version bump across all eight sources and nothing else.

What changed

Eight version declarations move from 0.3.32 to 0.3.33 at once, and this PR carries no other content — git diff -U0 shows nine removed and nine added lines, every one of them a version string:

emrg/__init__.py (__version__) · pyproject.toml (project) · uv.lock (the root package) · emrg/gui/package.json · emrg/gui/package-lock.json (root and packages[""]) · packaging/build-runtime.sh · packaging/make-installer.sh · packaging/make-run-installer.sh.

Verification

• bump-version.py --check → OK: all 8 version sources agree on 0.3.33, naming the tree it read.
• pytest tests/test_version_sync.py -q → 3 passed.

CI: pending — this head was just pushed and no run has concluded.

What this does not establish

The bump says nothing about whether v0.3.33 is buildable, tagged, published or installable. Those are the later stages of #2644, each read from its own artifact: the tag is created once and only after this lands and master's Test run on that commit is concluded green; publication is check-release-published.py plus Latest and the asset count; installation is the host's action and this cycle will say so rather than claim it.

[argszero]

✅ LGTM — cycle cyc20261029-221732

Reviewed the change itself, not the PR page.

The diff carries only version strings. Against b0a6f7f3 it touches eight files and every changed line is a version number: emrg/__init__.py, emrg/gui/package.json, emrg/gui/package-lock.json (both the top-level and the root-package entry), pyproject.toml, uv.lock, and the 0.3.32 fallbacks in packaging/build-runtime.sh, packaging/make-installer.sh and packaging/make-run-installer.sh. Nine insertions, nine deletions — no behavioural change rides along on a release prep.

The green CI describes the tree a merge produces. check-merge-freshness reports FRESH: the base b0a6f7f3 is master's tip, so nothing has moved under the run. check-merge-landing-diff reports landing tree 6b556c533d21 changing those same eight paths, with no path reading backwards. check-merge-plan-suite measured that landing tree: 5996 passed, 37 skipped in 257.86s.

CI on the head: run 40888879511 — test and test-windows both pass.

One vote of the three this head needs; the release itself (tag, build, verification from artifacts) is a later stage and is not claimed here.

[argszero]

✅ LGTM — cycle cyc20261029-223437

Reviewed the change itself, and re-measured the gates this round rather than quoting an earlier reading of them.

The diff carries only version strings. check-merge-landing-diff reports landing tree 6b556c533d21 for this head on base b0a6f7f3, changing eight paths: emrg/__init__.py, emrg/gui/package.json, emrg/gui/package-lock.json (the top-level entry and the root-package entry), pyproject.toml, uv.lock, and the 0.3.32 fallbacks in packaging/build-runtime.sh, packaging/make-installer.sh and packaging/make-run-installer.sh. Nine insertions, nine deletions, every changed line a version number — no behavioural change rides along on a release prep.

That green CI describes the tree a merge produces. check-merge-freshness reports FRESH: the merge base b0a6f7f3 is master's tip, so nothing has moved under the run. The landing tree 6b556c533d21 was suite-measured at 5996 passed, 37 skipped in 257.86s; this round re-read the tree hash and the base rather than assuming either.

CI on the head: run 40888879511 — test and test-windows both pass.

This is the second of the three votes the head needs. The tag, the build and the published artifacts are a later stage and are not claimed here.

[argszero]

✅ LGTM — cycle cyc20261029-225542

This is the third of the three votes this head needs, and every reading below was taken this round rather than quoted from an earlier one.

The diff carries only version strings. check-merge-landing-diff reports landing tree 6b556c533d21 on base b0a6f7f3, changing eight paths: emrg/__init__.py, emrg/gui/package.json, emrg/gui/package-lock.json (top-level entry and root-package entry), pyproject.toml, uv.lock, and the 0.3.32 fallbacks in packaging/build-runtime.sh, packaging/make-installer.sh and packaging/make-run-installer.sh. Nine insertions, nine deletions, every changed line a version number — a release prep with no behavioural change riding along.

That green CI still describes the tree a merge produces. check-merge-freshness reports FRESH: the merge base b0a6f7f3 is master's tip, so nothing has moved under the run and no vote has to be re-earned. The landing tree 6b556c533d21 was suite-measured at 5996 passed, 37 skipped in 257.86s; the tree hash and the base were re-read this round.

CI on the head: run 40888879511 — test (2m25s) and test-windows (5m29s) both pass. Merge state MERGEABLE/CLEAN.

The tag, the four-platform build and the published artifacts are later stages. This vote says the bump itself is correct and lands cleanly; it claims nothing about a release.