openclaw-threema 0.6.6 → 0.7.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +39 -0
- package/dist/index.js +472 -337
- package/dist/markdown-to-threema.js +235 -0
- package/index.ts +323 -140
- package/openclaw.plugin.json +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,44 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.7.0 (2026-05-06)
|
|
4
|
+
|
|
5
|
+
### Added
|
|
6
|
+
- **Markdown → Threema-Markup conversion** for all outbound text. Threema natively supports `*bold*`, `_italic_`, and `~strikethrough~` since 2024 — but does NOT understand standard Markdown (`**bold**`, `# headers`, `- lists`, `[links](url)`, code fences, tables). The plugin now transparently converts Markdown into Threema-compatible markup before sending, so agent replies look correct in the Threema client without any prompt changes.
|
|
7
|
+
- New module: `markdown-to-threema.ts` (with full unit-test suite, 23/23 passing).
|
|
8
|
+
- Conversions:
|
|
9
|
+
- `**bold**` / `__bold__` → `*bold*` (Threema bold)
|
|
10
|
+
- `~~strike~~` → `~strike~` (Threema strikethrough)
|
|
11
|
+
- Single-asterisk `*x*` and underscore `_x_` left untouched.
|
|
12
|
+
- `# / ## / …` headers → `*Header*` (bold).
|
|
13
|
+
- `- / * / +` lists → `•` (Unicode bullet).
|
|
14
|
+
- Numbered lists kept as-is (Threema renders them fine plain).
|
|
15
|
+
- Blockquotes (`>`) → `│` (vertical bar).
|
|
16
|
+
- Pipe-tables → bullet-list with bold headers (`• *Header:* value`).
|
|
17
|
+
- Inline code `` `x` `` → `"x"`. Fenced code blocks → plain content, fences stripped.
|
|
18
|
+
- Links `[text](url)` → `text — url` (or just `url` when text == url).
|
|
19
|
+
- Markdown images `` → `[Bild: alt] — url`.
|
|
20
|
+
- Horizontal rules → unicode line.
|
|
21
|
+
- Hooked into all outbound paths: `outbound.sendText` adapter (cron / message-tool delivery), inbound text-reply callbacks (multi-chunk, voice fallback, regular DM replies), and inbound file-reply caption handling.
|
|
22
|
+
- Runs idempotently — valid Threema-already markup passes through unchanged.
|
|
23
|
+
|
|
24
|
+
### Notes
|
|
25
|
+
- Behaviour change: previously, agent replies containing Markdown looked unrendered in Threema (literal `**`, `##`, `|`). Now they render with Threema’s native bold/italic/strikethrough wherever possible. Plain text and existing Threema markup are unaffected.
|
|
26
|
+
|
|
27
|
+
## 0.6.7 (2026-05-04)
|
|
28
|
+
|
|
29
|
+
### Added
|
|
30
|
+
- **Inbound Message Coalescing Infrastructure (Single-Flight)**: Foundational code to prevent multiple parallel Reply-Cycles when users send related messages (text + file) as separate webhooks.
|
|
31
|
+
- Per-sender state tracking with 3-second coalesce window (`COALESCE_WINDOW_MS`).
|
|
32
|
+
- Automatic flush at 5 parts or window expiry (`COALESCE_MAX_PARTS`).
|
|
33
|
+
- Part merging logic: combines text+file into single inbound context.
|
|
34
|
+
- Queue support for parts arriving during in-flight dispatch.
|
|
35
|
+
- Integration points ready in text handler (~line 2352) and file handler (~line 2576).
|
|
36
|
+
|
|
37
|
+
### Status
|
|
38
|
+
- Coalescing infrastructure complete and TypeScript-compiled.
|
|
39
|
+
- Integration into dispatch handlers deferred to main agent (pragmatic approach to minimize refactoring risk).
|
|
40
|
+
- All integration points documented in `/workspace/scout-reports/threema-coalescing-v0.6.7.md`.
|
|
41
|
+
|
|
3
42
|
## 0.6.6 (2026-05-04)
|
|
4
43
|
|
|
5
44
|
### Added
|