Telegram Web proof: the Telegram Bot API gives stable live message evidence, but

Telegram Web login state is not required for normal Mantis automation.

`Mantis Telegram Desktop Proof` is the agentic native Telegram Desktop

before/after wrapper. A maintainer can trigger it from a PR comment with

`@Mantis telegram desktop proof`, from the Actions UI with freeform

instructions, or through the generic `Mantis Scenario` dispatcher. The workflow

hands the PR, baseline ref, candidate ref, and maintainer instructions to Codex.

The agent reads the PR, decides what Telegram-visible behavior proves the

change, runs the real-user Crabbox Telegram Desktop proof lane for baseline and

candidate, iterates until the native GIFs are useful, writes paired

`motionPreview` artifacts into `mantis-evidence.json`, uploads the bundle, and

posts a 2-column PR evidence table when a PR number is available.

For human-in-the-loop Telegram desktop setup, use the scenario builder:

```bash

@Mantis telegram scenarios=telegram-status-command,telegram-mentioned-message-reply

```

`Mantis Telegram Desktop Proof` is the agentic native Telegram Desktop

before/after wrapper for PR visual proof. Start it from the Actions UI with

freeform `instructions`, through `Mantis Scenario` (`scenario_id:

telegram-desktop-proof`), or from a PR comment:

```text

@Mantis telegram desktop proof

```

The Mantis agent reads the PR, decides what Telegram-visible behavior proves the

change, runs the real-user Crabbox Telegram Desktop proof lane on baseline and

candidate refs, iterates until the native GIFs are useful, writes a paired

`motionPreview` manifest, and posts the same 2-column GIF table through the

Mantis GitHub App when `pr_number` is set.

- `pnpm openclaw qa mantis telegram-desktop-builder`

- Leases or reuses a Crabbox Linux desktop, installs native Telegram Desktop, configures OpenClaw with a leased Telegram SUT bot token, starts the gateway, and records screenshot/MP4 evidence from the visible VNC desktop.

- Defaults to `--credential-source convex` so workflows only need the Convex broker secret. Use `--credential-source env` with the same `OPENCLAW_QA_TELEGRAM_*` variables as `pnpm openclaw qa telegram`.