- `{ groupId: string, sutToken: string, testerUserId: string, testerUsername: string, telegramApiId: string, telegramApiHash: string, tdlibDatabaseEncryptionKey: string, tdlibArchiveBase64: string, tdlibArchiveSha256: string, desktopTdataArchiveBase64: string, desktopTdataArchiveSha256: string }`

- `groupId`, `testerUserId`, and `telegramApiId` must be numeric strings.

- `tdlibArchiveSha256` and `desktopTdataArchiveSha256` must be SHA-256 hex strings.

- `kind: "telegram-user"` represents one Telegram burner account. Treat the lease as account-wide: the TDLib CLI driver and Telegram Desktop visual witness restore from the same payload, and only one job should hold the lease at a time.

Telegram real-user lease restore:

```bash

tmp=$(mktemp -d /tmp/openclaw-telegram-user.XXXXXX)

node --import tsx scripts/e2e/telegram-user-credential.ts lease-restore \

--user-driver-dir "$tmp/user-driver" \

--desktop-workdir "$tmp/desktop" \

--lease-file "$tmp/lease.json"

TELEGRAM_USER_DRIVER_STATE_DIR="$tmp/user-driver" \

uv run ~/.codex/skills/custom/telegram-e2e-bot-to-bot/scripts/user-driver.py status --json

node --import tsx scripts/e2e/telegram-user-credential.ts release --lease-file "$tmp/lease.json"

```

Use the restored Desktop profile with `Telegram -workdir "$tmp/desktop"` when a visual recording is needed. In local operator environments, `scripts/e2e/telegram-user-credential.ts` reads `~/.codex/skills/custom/telegram-e2e-bot-to-bot/convex.local.env` by default if process env vars are absent.

Agent-driven Crabbox session:

```bash

pnpm qa:telegram-user:crabbox -- start \

--tdlib-url http://artifacts.openclaw.ai/tdlib-v1.8.0-linux-x64.tgz \

--output-dir .artifacts/qa-e2e/telegram-user-crabbox/pr-review

pnpm qa:telegram-user:crabbox -- send \

--session .artifacts/qa-e2e/telegram-user-crabbox/pr-review/session.json \

--text /status

pnpm qa:telegram-user:crabbox -- finish \

--session .artifacts/qa-e2e/telegram-user-crabbox/pr-review/session.json

```

`start` leases the `telegram-user` credential, restores the same account into

TDLib and Telegram Desktop on a Crabbox Linux desktop, starts a local mock SUT

gateway from the current checkout, opens the visible Telegram chat, starts

desktop recording, and writes a private `session.json`. While the session is

alive, an agent can keep testing until satisfied:

- `send --session <file> --text <message>` sends through the real TDLib user and waits for the SUT reply.

- `run --session <file> -- <remote command>` runs an arbitrary command on the Crabbox and saves its output, for example `bash -lc 'source /tmp/openclaw-telegram-user-crabbox/env.sh && python3 /tmp/openclaw-telegram-user-crabbox/user-driver.py transcript --limit 20 --json'`.

- `screenshot --session <file>` captures the current visible desktop.

- `status --session <file>` prints the lease and WebVNC command.

- `finish --session <file>` stops the recorder, captures screenshot/video/motion-trim artifacts, releases the Convex credential, stops local SUT processes, and stops the Crabbox lease unless `--keep-box` is passed.

- `publish --session <file> --pr <number>` publishes a GIF-only PR comment by default. Pass `--full-artifacts` only when logs or JSON artifacts are intentionally needed.

For deterministic visual repros, pass `--mock-response-file <path>` to `start`

or to the one-command `probe` shorthand. The runner defaults to a standard

Crabbox class, 24fps recording, 24fps motion GIF previews, and 1920px GIF

width. Override with `--class`, `--record-fps`, `--preview-fps`, and

`--preview-width` only when the proof needs different capture settings.

One-command Crabbox proof:

```bash

pnpm qa:telegram-user:crabbox -- --text /status

```

The default `probe` command is shorthand for one start/send/finish cycle. Use

it for a quick `/status` smoke. Use the session commands for PR review,

bug-reproduction work, or any case where the agent needs minutes of arbitrary

experimentation before deciding the proof is complete. Use `--id <cbx_...>` to

reuse a warm desktop lease, `--keep-box` to keep VNC open after finish,

`--desktop-chat-title <name>` to pick the visible chat, and `--tdlib-url <tgz>`

when using a prebaked Linux `libtdjson.so` archive instead of building TDLib on

a fresh box. The runner verifies `--tdlib-url` with `--tdlib-sha256 <hex>` or,

by default, a sibling `<url>.sha256` file.

- `kind: "telegram-user"` is reserved for the Mantis Telegram Desktop proof workflow. Generic QA Lab lanes must not acquire it.

Broker-validated multi-channel payloads: