Summary

• Problem: two review-thread regressions were still live after the broader runtime cleanup: Discord username/handle sends no longer had the plugin directory resolver wired into the messaging target resolver, and generated gateway transcript files could be reused after a stale session row rotated to a new session id.
• Why it matters: username-targeted Discord DMs should keep resolving through the directory/cache path, and /new/session reset should not append a fresh session into the previous generated transcript file.
• What changed: Discord now exposes a lazy messaging.targetResolver.resolveTarget bridge to resolveDiscordTarget, and gateway session merge drops stale sessionFile when sessionId changes so the generated transcript path can rotate.
• What did NOT change: no Discord send transport behavior, permission model, explicit user:/channel: parsing, or custom transcript path migration policy changed beyond the stale-session reset case.

Change Type (select all)

• Bug fix
• Feature
• Refactor required for the fix
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Related: review follow-up for runtime regressions
• This PR fixes a bug or regression

Real behavior proof (required for external PRs)

• Behavior or issue addressed: Discord username target resolution and generated gateway transcript rotation on session reset.
• Real environment tested: local macOS checkout for focused regression tests; remote Crabbox/Blacksmith changed gate passed on tbx_01kr4z72c5zfhb9c43pm106zav.
• Exact steps or command run after this patch: pnpm test:serial src/agents/bash-tools.exec-host-node.test.ts src/agents/pi-embedded-subscribe.handlers.tools.test.ts src/infra/outbound/sanitize-text.test.ts src/infra/outbound/deliver.test.ts extensions/telegram/src/bot.helpers.test.ts extensions/telegram/src/bot.create-telegram-bot.test.ts extensions/whatsapp/src/inbound/send-api.test.ts extensions/discord/src/audit.test.ts extensions/discord/src/channel.test.ts src/gateway/server-methods/agent.test.ts
• Evidence after fix: 7 Vitest shards passed in 39.57s; 10 files, 372 tests.
• Observed result after fix: focused reviewed surfaces pass, including new Discord target resolver and gateway transcript reset coverage.
• What was not tested: live Discord send and live gateway session reset against a running external gateway; remote pnpm check:changed did not execute because the Blacksmith Testbox job stayed queued.
• Before evidence: reviewer reported the runtime regressions against the previous patch.

Root Cause (if applicable)

• Root cause: the generic outbound resolver integration did not expose the Discord directory resolver, and stale session merge logic preserved a generated transcript path even when the session id changed.
• Missing detection / guardrail: no regression test asserted username resolution through discordPlugin.messaging.targetResolver, and no gateway test covered stale stored session rows with generated transcript paths rotating to a new session id.
• Contributing context (if known): other reviewed items were already fixed on current origin/main; this PR locks the remaining two live gaps.

Regression Test Plan (if applicable)

• Coverage level that should have caught this:
  • Unit test
  • Seam / integration test
  • End-to-end test
  • Existing coverage already sufficient
• Target test or file: extensions/discord/src/channel.test.ts, src/gateway/server-methods/agent.test.ts.
• Scenario the test should lock in: Discord username input resolves through the directory-backed target resolver; stale generated transcript paths are dropped when an existing session entry rotates ids.
• Why this is the smallest reliable guardrail: both regressions were contract wiring bugs at local seams, so targeted tests catch them without requiring a live channel or external gateway.
• Existing test that already covers this (if any): existing channel/gateway suites covered adjacent behavior but not these exact regressions.
• If no new test is added, why not: N/A.

User-visible / Behavior Changes

• Discord username/handle outbound targets resolve again through the Discord directory path.
• Generated gateway transcript paths rotate on session reset instead of reusing the old session file.

Diagram (if applicable)

N/A

Security Impact (required)

• New permissions/capabilities? (Yes/No) No
• Secrets/tokens handling changed? (Yes/No) No
• New/changed network calls? (Yes/No) No
• Command/tool execution surface changed? (Yes/No) No
• Data access scope changed? (Yes/No) No
• If any Yes, explain risk + mitigation: N/A

Repro + Verification

Environment

• OS: macOS local checkout; Blacksmith Testbox attempted for remote changed gate.
• Runtime/container: Node/pnpm workspace.
• Model/provider: N/A.
• Integration/channel (if any): Discord, Gateway sessions.
• Relevant config (redacted): synthetic tests only.

Steps

1. Run the focused reviewed-surface regression suite listed above.
2. Run pnpm changed:lanes --json.
3. Attempt remote Crabbox/Blacksmith pnpm check:changed.

Expected

• Targeted regression tests pass.
• Changed lanes select core, core tests, extensions, and extension tests.
• Remote changed gate executes when Testbox capacity is available.

Actual

• Targeted regression tests passed.
• pnpm changed:lanes --json selected core, coreTests, extensions, and extensionTests.
• Crabbox/Blacksmith lease tbx_01kr4z72c5zfhb9c43pm106zav passed pnpm check:changed in 3m12s command time, exit 0. Actions run: https://github.com/openclaw/openclaw/actions/runs/25584797503.

Evidence

• Failing test/log before + passing after
• Trace/log snippets
• Screenshot/recording
• Perf numbers (if relevant)

Human Verification (required)

• Verified scenarios: focused reviewed-surface test bundle, git diff --check, changed-lane selection, Crabbox/Blacksmith pnpm check:changed pass.
• Edge cases checked: Discord directory result returns source: "directory"; gateway stale transcript path clears only when stored sessionId differs from the active session id.
• What you did not verify: live Discord DM send and live gateway transcript creation; remote pnpm check:changed passed on Crabbox/Blacksmith.

Review Conversations

• I replied to or resolved every bot review conversation I addressed in this PR.
• I left unresolved only the conversations that still need reviewer or maintainer judgment.

Compatibility / Migration

• Backward compatible? (Yes/No) Yes
• Config/env changes? (Yes/No) No
• Migration needed? (Yes/No) No
• If yes, exact upgrade steps: N/A

Risks and Mitigations

• Risk: Discord target resolver mapping could accidentally misclassify non-user target forms.
  • Mitigation: keep explicit kind mapping narrow and delegate normalization/directory lookup to the existing Discord resolver.
• Risk: generated transcript rotation could clear a stale path in edge cases that previously reused it.
  • Mitigation: only clear when the stored entry's sessionId differs from the new active sessionId; same-session paths are preserved.