[b-pm]

Summary

Fixes #61.

Headless beeper setup --email crashes because the released SDK exposes client.app.setup while the CLI still calls client.app.login. This updates the CLI to the @beeper/desktop-api 6.0.0 resource names and pins the SDK to commit fe1e736ccd101f687da03abfdaeb69ab57fa4bcf, instead of the moving next branch.

Changes

• Route email setup through client.app.setup.start/email/response/register.
• Route recovery-key commands through client.app.setup.recoveryKey and verification commands through client.app.setup.verifications.
• Update SDK types and active-verification lookup.
• Add regression tests against the installed SDK and a local HTTP server.
• Correct the crash-report link and align contact-search copy with the pinned SDK.
• Add a patch changeset.

The SAS double-prompt issue (#62) and the existing HTTP verification loop are unchanged.

Validation

This submits the unchanged commit 3e78a2f8c76071b0aa3f6bfe59963c4892455807 from b-pm/cli#1. Against current upstream main, it is one commit across 20 files.

Verified the fork CI run for this commit:

• Ubuntu / Bun 1.3.10: dependency installation, typecheck, build, README/API-copy/manifest checks, CLI smoke tests, and unit tests passed.
• Unit tests: 52 passed, 0 failed, including the new headless email setup tests.
• macOS / Bun 1.3.10: cancelled before any job steps ran. The workflow is therefore not fully green; macOS validation remains outstanding.

Opened as a draft pending upstream CI and review.

[zaosoula]

Reproduced on beeper-cli 0.6.4 (Homebrew, darwin-arm64) with a local Beeper Server (stable 4.3.284): beeper setup -t server --email … fails with undefined is not an object (evaluating 'client.app.login.start'). The Server answers on /v1/app/setup/{start,email,response,register}, which matches this PR. +1 for merging.