0.9.49 was published by hand from the dev tree (its lockfile is fe74d80) and never pushed, so pear/main sat three commits behind what stortron runs. Pushing 0.9.49 as-is would make CI publish a second, different tree under the same version: the registry accepts that, and it is how pear-git-v3 split-brained in July. So this bumps the version and lets CI build it. The CI steps were dry-run on the exact commit first (pgv3's own loadCIConfig/runSteps, publish step excluded): install, the hosted-history check for all 7 siblings and vendoring all pass. pgh publish --dry-run: 63 version-splits and 1 code-differs, which is autobase@7.28.1 vs pear-git-v3. That is pgv3's two deliberate patches (apply-state.js warmup guard, index.js drain-loop BOUND); atproto-bridge's own copies are byte-identical to npm stock. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>