@@ -252,7 +252,7 @@ Telegram Web login state is not required for normal Mantis automation.
|
252 | 252 | |
253 | 253 | `Mantis Telegram Desktop Proof` is the agentic native Telegram Desktop |
254 | 254 | before/after wrapper. A maintainer can trigger it from a PR comment with |
255 | | -`@Mantis telegram desktop proof`, from the Actions UI with freeform |
| 255 | +`@openclaw-mantis telegram desktop proof`, from the Actions UI with freeform |
256 | 256 | instructions, or through the generic `Mantis Scenario` dispatcher. The workflow |
257 | 257 | hands the PR, baseline ref, candidate ref, and maintainer instructions to Codex. |
258 | 258 | The agent reads the PR, decides what Telegram-visible behavior proves the |
@@ -351,7 +351,7 @@ region, and public URL values directly. The reusable publisher requires:
|
351 | 351 | You can also trigger the status-reactions run directly from a PR comment: |
352 | 352 | |
353 | 353 | ```text |
354 | | -@Mantis discord status reactions |
| 354 | +@openclaw-mantis discord status reactions |
355 | 355 | ``` |
356 | 356 | |
357 | 357 | The comment trigger is intentionally narrow. It only runs on pull request |
@@ -361,15 +361,15 @@ and the current PR head SHA as the candidate. Maintainers can override either
|
361 | 361 | ref: |
362 | 362 | |
363 | 363 | ```text |
364 | | -@Mantis discord status reactions baseline=origin/main candidate=HEAD |
| 364 | +@openclaw-mantis discord status reactions baseline=origin/main candidate=HEAD |
365 | 365 | ``` |
366 | 366 | |
367 | 367 | Telegram live QA can also be triggered from a PR comment: |
368 | 368 | |
369 | 369 | ```text |
370 | | -@Mantis telegram |
371 | | -@Mantis telegram scenario=telegram-status-command |
372 | | -@Mantis telegram scenarios=telegram-status-command,telegram-mentioned-message-reply |
| 370 | +@openclaw-mantis telegram |
| 371 | +@openclaw-mantis telegram scenario=telegram-status-command |
| 372 | +@openclaw-mantis telegram scenarios=telegram-status-command,telegram-mentioned-message-reply |
373 | 373 | ``` |
374 | 374 | |
375 | 375 | By default it uses the current PR head SHA as the candidate and runs |
|
