程序员阿江(Relakkes) 2ca5228171 feat: make IM adapter behavior consistent ...

WeChat and DingTalk were using different pairing, attachment, and response
state paths, which made the new IM channels behave differently from Feishu
and Telegram. Align the shared pairing model, wire inbound media into the
existing attachment bridge, and map platform response capabilities to their
real APIs: WeChat block streaming plus typing, DingTalk AI Card streaming.

Constraint: WeChat iLink exposes typing and block streaming, but no editable message/card streaming API
Constraint: DingTalk streaming depends on the AI Card create/deliver/stream/finalize lifecycle
Rejected: Fake DingTalk typing with standalone markdown | it would add chat noise instead of platform state
Rejected: Auto-pair WeChat after QR login | it bypasses the shared IM pairing model
Confidence: high
Scope-risk: moderate
Directive: Keep WeChat streaming as block-send unless iLink adds editable messages; keep DingTalk streaming on AI Card APIs
Tested: bun run check:adapters; bun run check:server; cd desktop && bun run test src/stores/adapterStore.test.ts; cd desktop && bun run build; bunx tsc -p adapters/tsconfig.json --noEmit; git diff --check
Not-tested: Live WeChat and DingTalk platform smoke with real production credentials

2026-05-03 21:08:12 +08:00

..

__tests__

fix: batch resolve 5 issues from Feishu bug tracker

2026-04-12 13:36:14 +08:00

attachment-limits.ts

fix(adapters): drop HEIC mime, align Telegram error text, inline extractText

2026-04-11 21:09:00 +08:00

attachment-store.ts

fix(adapters): tsconfig-strict types for Dirent and Lark image upload

2026-04-11 21:14:28 +08:00

attachment-types.ts

feat: make IM adapter behavior consistent

2026-05-03 21:08:12 +08:00

image-block-watcher.ts

feat(adapters): add ImageBlockWatcher for streaming markdown image extraction

2026-04-11 21:08:30 +08:00