Registration hard-blocked for new users: node v0.5.0 requires iCaptcha proof but released gl v0.3.8 predates icaptcha-client

[ddfp777]

What happened?

Fresh install, new user, following https://gitlawb.com/start exactly.

Repro:

1. Install gl v0.3.8 (latest release) on Linux (WSL2 Ubuntu)
2. gl identity new → OK
3. gl register → 403: "iCaptcha proof required (missing proof header). Solve a challenge at https://icaptcha.gitlawb.com for level >= 3 and resend with the x-icaptcha-proof header."

Cause: node v0.5.0 gates register/repo-create behind iCaptcha, but v0.3.8 (current latest release) contains no icaptcha-client — verified via strings on the release binary: no x-icaptcha-proof handling. The transparent solve-and-retry flow exists on main (crates/icaptcha-client, crates/gl/src/http.rs) but hasn't shipped.

Impact: every new identity is blocked from registering with the public node. Likely affects everyone starting via the Hy3 builder bounty today.

Fix: cut a release from main. Workaround in the meantime: build gl + git-remote-gitlawb from source.

DID that hit this: did:key:z6MksApMMMq14ycCqrviT7o3byEymutQNBEM6BMRgwTnLEo1

Expected behavior

Following https://gitlawb.com/start on a fresh install: gl register should register the new identity with the public node (solving the iCaptcha challenge automatically, as the icaptcha-client code on main does).

Steps to reproduce

1. Install gl v0.3.8 (latest release) on Linux (WSL2 Ubuntu, x86_64)
2. gl identity new → OK
3. gl register → 403 icaptcha_proof_required

Affected crate

gitlawb-node

Version or commit

gl 0.3.8 (latest release binary from Gitlawb/releases, gitlawb-v0.3.8-x86_64-unknown-linux-musl.tar.gz)

Environment

No response

Relevant logs