fix(adapters): bump telegramify-markdown to 1.3.3 for blockquote escaping (#1340)

* fix(adapters): bump telegramify-markdown to 1.3.3 for blockquote escaping

telegramify-markdown 1.3.2 escapes the `>` blockquote marker (which
Telegram MarkdownV2 supports natively) and double-escapes any other
special character on the same line, so any blockquote ending in a
period (or containing `.`, `!`, `-`, etc.) is rejected by the Bot
API with "Character '.' is reserved and must be escaped". The bot
falls back to plain text and logs telegram.markdownv2_failed.

Upstream fixed both bugs in 1.3.3. Bumping the floor to ^1.3.3 and
adding a regression test on the canonical "> hi." case so the
behaviour can't silently regress if the dependency loosens later.

Fixes #1102

* test(adapters): broaden blockquote regression with multi-char and multi-line cases

Addresses review nit on #1340. 1.3.2's bug regressed both on multiple
special characters on one line and on multi-line blockquotes, so pinning
those shapes down adds real confidence against a future re-regression.

Expected outputs verified against telegramify-markdown 1.3.3:
- `> a.b-c!` escapes `.`, `-`, `!` exactly once, `>` marker unescaped.
- `> first.\n> second?` escapes `.` once, `?` passes through (not in
  Telegram MarkdownV2's reserved set), `>` marker unescaped on both lines.

* test(adapters): reframe blockquote regression comment around bug behavior

Address review on #1340: drop version-number framing in favor of
describing the bug behavior. Version numbers rot as the floor moves;
the bug behavior plus the issue link stays stable.

Author: truffle-dev

bun.lock

@@ -23,7 +23,7 @@
     "@slack/bolt": "^4.6.0",
     "discord.js": "^14.16.0",
     "grammy": "^1.36.0",
-    "telegramify-markdown": "^1.3.0"
+    "telegramify-markdown": "^1.3.3"
   },
   "peerDependencies": {
     "typescript": "^5.0.0"

packages/adapters/package.json

@@ -67,6 +67,24 @@ describe('telegram-markdown', () => {
       });
     });
 
+    describe('blockquotes', () => {
+      // Regression: telegramify-markdown escaped the `>` blockquote marker
+      // and double-escaped special characters on the same line, which
+      // Telegram rejected with "Character '.' is reserved and must be
+      // escaped". See coleam00/Archon#1102.
+      test('escapes special chars exactly once inside blockquotes', () => {
+        expect(convertToTelegramMarkdown('> hi.')).toBe('> hi\\.\n');
+      });
+
+      test('escapes multiple special chars exactly once on the same blockquote line', () => {
+        expect(convertToTelegramMarkdown('> a.b-c!')).toBe('> a\\.b\\-c\\!\n');
+      });
+
+      test('preserves the `>` marker on every line of a multi-line blockquote', () => {
+        expect(convertToTelegramMarkdown('> first.\n> second?')).toBe('> first\\.\n> second?\n');
+      });
+    });
+
     describe('edge cases', () => {
       test('handles empty string', () => {
         const result = convertToTelegramMarkdown('');