fix(messaging): dedupe short-window getUpdates inbound replays

[ericcaiwx-star]

Summary

• Claim a stable inbound key (message_id → client_id → seq → body fingerprint) at the top of processOneMessage via OpenClaw createClaimableDedupe, then commit a disk tombstone under $OPENCLAW_STATE_DIR/openclaw-weixin/replay-dedupe/ so at-least-once getUpdates deliveries do not run the AI pipeline twice.
• Covers ~1s iLink replays and longer redeliveries (e.g. 30–50 min after a stuck long turn), including across process restart.
• Derive stable MessageSid from the same key when transport ids are present.
• Tests for key selection, claim/commit/TTL/release; CHANGELOG (EN/ZH).

Fixes #239
Related: openclaw/openclaw#116723

Scope / deploy assumption

• 24h replay-dedupe / tombstone window — same transport id / claim key. Not a content-dedupe window: a user intentionally re-sending the same text with a new message_id is processed.
• Disk-backed claim survives restart (single host / shared OPENCLAW_STATE_DIR). Multi-replica gateways without shared state still need a shared store or full channel ingress drain — out of scope here; this matches the transitional createClaimableDedupe pattern used by other channels (Discord / Mattermost / Nextcloud Talk / Feishu).

message_id on the wire

iLink GetUpdatesResp.msgs[] items are WeixinMessage; README documents message_id as the unique message id. Production debug already logs msgId / seq.

{
  "seq": 1234567890,
  "message_id": 9876543210,
  "from_user_id": "<redacted>",
  "to_user_id": "<redacted>",
  "create_time_ms": 1720000000000,
  "item_list": [{ "type": 1, "text_item": { "text": "<redacted>" } }],
  "context_token": "<redacted>"
}

Test plan

• npx vitest run src/messaging/inbound-dedupe.test.ts src/messaging/inbound.test.ts
• npx tsc --noEmit
• Maintainer: smoke personal WeChat — send one text, confirm single agent turn / single reply
• Long-turn / late redelivery: same message_id within 24h is dropped; intentional re-send (new id) still processes
• Restart gateway and confirm tombstone file under ~/.openclaw/openclaw-weixin/replay-dedupe/ still suppresses replay

[NewFuture]

Thanks for putting together a thorough replay-deduplication patch. The same at-least-once delivery gap exists in the current community release, and we would prefer an author-led port so the implementation context and authorship stay with you.

If you are interested, we would be glad to review a focused PR against:

https://github.com/NewFuture/openclaw-weixin

For the current codebase, please adapt the claim/commit flow to the ordinary and approval admission lanes, confirm compatibility with the supported OpenClaw persistent-dedupe API, and retain account-scoped storage. Regression coverage for restart persistence, cross-account isolation, claim release after failure/abort, media, and slash-command delivery would be especially helpful.

Contribution guide:
https://github.com/NewFuture/openclaw-weixin/blob/main/CONTRIBUTING.md

For transparency, NewFuture/openclaw-weixin is a community-maintained distribution, not the official Tencent/Weixin release.

[ericcaiwx-star]

Community port opened as invited: NewFuture/openclaw-weixin#41

Adapted for ordinary/approval admission lanes and OpenClaw 2026.7.1 createClaimableDedupe plugin-state API. This Tencent PR remains for upstream review.