Cut v0.3.39: master has moved two commits past the published release #2724

What is observed

The most recent published release is v0.3.38. Since the commit that release carries, master has advanced two commits:

• the bookmark's per-cycle narration is counted as a rotation structure fault
• the ios-app template answers a platform-capability question from the platform, CI and the host

Neither is in any published build. An installation that upgrades today receives none of them, and the version it reports is the same one that already lacks them — so a host comparing two installations cannot tell which one carries the newer work.

What is expected instead

A release that carries master's current contents, with every version declaration naming the same number.

What the fix must satisfy

• Every declaration moves together — the eight sources this repository keeps — and a reading proves they agree, rather than one declaration being taken as the truth for the rest.
• The version a tag names is the version the tagged tree declares.
• The full test suite passes on the tree that would be released, not only on some earlier tree.
• No tag is cut until the bump is on master and CI has concluded green on that exact merge commit: a published tag cannot be withdrawn, and a tag fires the release build.

Scope

The bump itself is this issue's whole subject. Building and publishing the release is the next stage, gated on the bump landing.