- Gateway/diagnostics: add startup phase spans, active work labels, stale terminal bridge markers, and default sync-I/O tracing in `pnpm gateway:watch` so slow Gateway turns are easier to attribute from logs and stability diagnostics.

- Plugins/loader: preserve real compiled plugin module evaluation errors on the native fast path instead of treating every thrown `.js` module as a source-transform fallback miss. Thanks @vincentkoc.

- QA/Mantis: add `pnpm openclaw qa mantis slack-desktop-smoke` to run Slack live QA inside a Crabbox VNC desktop, open Slack Web, and capture desktop screenshots beside the Slack QA artifacts.

- QA/Mantis: add an opt-in Discord thread attachment before/after scenario that creates a real thread, calls `message.thread-reply` with `filePath`, and captures baseline/candidate screenshot evidence.

- Discord: preserve `filePath` and `path` attachments when replying to a thread with the message tool.

- QA/Mantis: add visual desktop tasks with Crabbox MP4 recording, screenshot capture, and optional image-understanding assertions, and preserve video artifacts in Mantis before/after reports.

- QA/WhatsApp: add `pnpm openclaw qa whatsapp` for live DM canary and pairing-gate coverage using two pre-linked WhatsApp Web sessions from the QA credential pool.

- QA/Mantis: pass the runtime env through desktop-browser Crabbox and artifact-copy child commands, so embedded Mantis callers can provide Crabbox credentials without mutating the parent process. Thanks @vincentkoc.

and `mantis-report.md`. For the first Discord scenario, a successful verification

means baseline status is `fail` and candidate status is `pass`.

The second Discord before/after probe targets thread attachments:

```bash

pnpm openclaw qa mantis run \

--transport discord \

--scenario discord-thread-reply-filepath-attachment \

--baseline <bug-ref> \

--candidate <fix-ref> \

--output-dir .artifacts/qa-e2e/mantis/local-discord-thread-attachment

```

That scenario posts a parent message with the driver bot, creates a real Discord

thread, calls OpenClaw's `message.thread-reply` action with a repo-local

`filePath`, then polls the thread for the SUT reply and attachment filename. The

baseline screenshot shows the reply with no attachment; the candidate screenshot

shows the expected `mantis-thread-report.md` attachment.

The first VM/browser primitive is the desktop smoke:

```bash

The scenarios cover transport behavior that unit tests cannot prove end to end: mention gating, allow-bot policies, allowlists, top-level and threaded replies, DM routing, reaction handling, inbound edit suppression, restart replay dedupe, homeserver interruption recovery, approval metadata delivery, media handling, and Matrix E2EE bootstrap/recovery/verification flows. The E2EE CLI profile also drives `openclaw matrix encryption setup` and verification commands through the same disposable homeserver before checking gateway replies.

Discord also has Mantis-only opt-in scenarios for bug reproduction. Use

`--scenario discord-status-reactions-tool-only` for the explicit status reaction

timeline, or `--scenario discord-thread-reply-filepath-attachment` to create a

real Discord thread and verify that `message.thread-reply` preserves a

`filePath` attachment. These scenarios stay out of the default live Discord lane

because they are before/after repro probes rather than broad smoke coverage.

CI uses the same command surface in `.github/workflows/qa-live-transports-convex.yml`. Scheduled and default manual runs execute the fast Matrix profile with live frontier credentials, `--fast`, and `OPENCLAW_QA_MATRIX_NO_REPLY_WINDOW_MS=3000`. Manual `matrix_profile=all` fans out into the five profile shards so the exhaustive catalog can run in parallel while keeping one artifact directory per shard.

For transport-real Telegram, Discord, and Slack smoke lanes:

type Ctx = Pick<

ChannelMessageActionContext,

"action" | "params" | "cfg" | "accountId" | "requesterSenderId" | "mediaLocalRoots"

| "action"

| "params"

| "cfg"

| "accountId"

| "requesterSenderId"

| "mediaLocalRoots"

| "mediaReadFile"

>;

export async function tryHandleDiscordMessageActionGuildAdmin(params: {

const content = readStringParam(actionParams, "message", {

required: true,

});

const mediaUrl = readStringParam(actionParams, "media", { trim: false });

const mediaUrl =

readStringParam(actionParams, "media", { trim: false }) ??

readStringParam(actionParams, "path", { trim: false }) ??

readStringParam(actionParams, "filePath", { trim: false });

const replyTo = readStringParam(actionParams, "replyTo");

// `message.thread-reply` (tool) uses `threadId`, while the CLI historically used `to`/`channelId`.

replyTo: replyTo ?? undefined,

},

cfg,

{ mediaLocalRoots: ctx.mediaLocalRoots, mediaReadFile: ctx.mediaReadFile },

);

}

expect(handleDiscordActionMock).not.toHaveBeenCalled();

});

it("maps thread-reply filePath to Discord threadReply with media read context", async () => {

const mediaReadFile = vi.fn(async () => Buffer.from("report"));

await handleDiscordMessageAction({

action: "thread-reply",

params: {

threadId: "thread-123",

message: "thread update",

filePath: "/tmp/agent-root/report.md",

},

cfg: {

channels: { discord: { token: "tok", actions: { threads: true } } },

} as OpenClawConfig,

mediaLocalRoots: ["/tmp/agent-root"],

mediaReadFile,

});

expect(handleDiscordActionMock).toHaveBeenCalledWith(

expect.objectContaining({

action: "threadReply",

channelId: "thread-123",

content: "thread update",

mediaUrl: "/tmp/agent-root/report.md",

}),

expect.any(Object),

{

mediaLocalRoots: ["/tmp/agent-root"],

mediaReadFile,

},

);

});

it("forwards top-level components on sends", async () => {

const components = { blocks: [{ type: "text", text: "Pick one" }] };

expect(

__testing.findScenario(["discord-status-reactions-tool-only"]).map((scenario) => scenario.id),

).toEqual(["discord-status-reactions-tool-only"]);

expect(

__testing

.findScenario(["discord-thread-reply-filepath-attachment"])

.map((scenario) => scenario.id),

).toEqual(["discord-thread-reply-filepath-attachment"]);

});

it("collects the status reaction sequence across timeline snapshots", () => {

expect(html).toContain("Seen: 👀 → 🤔");

});

it("renders a human-readable thread attachment artifact", () => {

const html = __testing.renderDiscordThreadReplyAttachmentHtml({

attachmentFilenames: [],

expectedAttachmentFilename: "mantis-thread-report.md",

messageContent: "Mantis thread attachment reply",

scenarioTitle: "Discord thread reply preserves filePath attachment",

status: "fail",

threadName: "mantis-thread-filepath-1234",

});

expect(html).toContain("Attachment missing");

expect(html).toContain("No attachments on the SUT thread reply");

expect(html).toContain("mantis-thread-report.md");

});

it("waits for the Discord account to become connected, not just running", async () => {

vi.useFakeTimers();

try {