docs: RELEASING.md initial-release runbook still assumes the current version is 0.1.0-alpha.1 (actual: 0.1.0-alpha.4)

[OmarAlJarrah]

Problem

The "Publishing the initial 0.1.0-alpha.1" runbook in RELEASING.md (lines 113, 117-118) states that .release-please-manifest.json currently records 0.1.0-alpha.1 (so the next automated release will be 0.1.0-alpha.2) and that gradle.properties reads version=0.1.0-alpha.1.

Both files are actually at 0.1.0-alpha.4:

• .release-please-manifest.json: {".": "0.1.0-alpha.4"}
• gradle.properties: version=0.1.0-alpha.4

alpha.1 through alpha.3 have already shipped, so the runbook's "the first automated release will be alpha.2" claim is also stale.

Impact

A maintainer following this runbook to bootstrap what they believe is the initial release would trigger a manual publish under the false premise that gradle.properties still reads alpha.1. In reality the workflow would publish (or attempt to re-publish) 0.1.0-alpha.4, risking a wrong or duplicate Maven Central deployment.

Suggested fix

Update the runbook to reflect the current manifest/gradle.properties version, or reframe it as a generic "bootstrapping a new alpha series" doc rather than one hardcoded to a specific already-passed version.