This is a comment left during a code review.
Path: src/agents/tools/telegram-actions.ts
Line: 17

Comment:
**Import out of alphabetical order**

`editForumTopicTelegram` (starts with `e`) is inserted before `deleteMessageTelegram` (starts with `d`), breaking the alphabetical ordering of the other named imports in this block. It should come after `deleteMessageTelegram` and before the existing `editMessageTelegram`.

```suggestion
  deleteMessageTelegram,
  editForumTopicTelegram,
  editMessageTelegram,
```

How can I resolve this? If you propose a fix, please make it concise.

This is a comment left during a code review.
Path: extensions/telegram/src/send.ts
Line: 1566-1571

Comment:
**Misleading error when name is whitespace-only**

When `opts.name` is a whitespace-only string (e.g. `"   "`) and no `iconCustomEmojiId` is provided, `name` becomes `""` after trimming. The first guard (`!name && !iconCustomEmojiId`) fires with the message *"At least one of name or iconCustomEmojiId must be provided"* — even though the caller explicitly passed a `name`. The more accurate error ("Forum topic name cannot be empty") is unreachable in this path because `""` is falsy.

Swapping the two checks fixes the ordering:

```suggestion
  if (name != null && name.length === 0) {
    throw new Error("Forum topic name cannot be empty");
  }
  if (!name && !iconCustomEmojiId) {
    throw new Error("At least one of name or iconCustomEmojiId must be provided");
  }
```

With this ordering, a whitespace-only name surfaces the correct diagnostic immediately, and the "at least one of" guard still catches the case where neither field is provided at all.

How can I resolve this? If you propose a fix, please make it concise.

This is a comment left during a code review.
Path: extensions/telegram/src/send.ts
Line: 1563-1574

Comment:
**Silent data loss when `iconCustomEmojiId` is whitespace-only**

When `iconCustomEmojiId` is a whitespace-only string (e.g. `"   "`) it trims to `""`, which is falsy. If a valid `name` is also supplied, the code passes the "at least one" guard, proceeds normally, and only `name` ends up in `extra` — the caller's intended icon change is silently dropped.

The symmetric guard that already protects `name` (the `name != null && name.length === 0` block on line 1566) should be added for `iconCustomEmojiId` as well:

```suggestion
  const name = opts.name?.trim();
  const iconCustomEmojiId = opts.iconCustomEmojiId?.trim();

  if (name != null && name.length === 0) {
    throw new Error("Forum topic name cannot be empty");
  }
  if (iconCustomEmojiId != null && iconCustomEmojiId.length === 0) {
    throw new Error("Forum topic icon custom emoji ID cannot be empty");
  }
  if (!name && !iconCustomEmojiId) {
    throw new Error("At least one of name or iconCustomEmojiId must be provided");
  }
  if (name != null && name.length > 128) {
    throw new Error("Forum topic name must be 128 characters or fewer");
  }
```

How can I resolve this? If you propose a fix, please make it concise.

This is a comment left during a code review.
Path: extensions/telegram/src/send.test.ts
Line: 2072-2089

Comment:
**Missing tests for whitespace-only validation paths**

The two validation checks added to address previous review feedback — empty `name` after trim and empty `iconCustomEmojiId` after trim — are exercised by the implementation but have no corresponding test cases. The test suite currently covers:

- `opts = {}` (neither field provided) → "At least one…" ✓  
- `name: "x".repeat(129)` → "must be 128 characters…" ✓  

But it does not cover:
- `name: "   "` (whitespace-only) → should throw `"Forum topic name cannot be empty"`  
- `iconCustomEmojiId: "   "` (whitespace-only) → should throw `"Forum topic icon custom emoji ID cannot be empty"`  
- `name: "   "` + valid `iconCustomEmojiId` → should still throw `"Forum topic name cannot be empty"`, not `"At least one of…"`

These paths exist specifically because of the previously raised bugs, so adding tests ensures the fix is verifiable and won't regress.

```ts
it("throws when name is whitespace-only", async () => {
  const api = {} as unknown as Bot["api"];
  await expect(
    editForumTopicTelegram("-1001234567890", 42, { token: "tok", api, name: "   " }),
  ).rejects.toThrow("Forum topic name cannot be empty");
});

it("throws when iconCustomEmojiId is whitespace-only", async () => {
  const api = {} as unknown as Bot["api"];
  await expect(
    editForumTopicTelegram("-1001234567890", 42, {
      token: "tok",
      api,
      iconCustomEmojiId: "   ",
    }),
  ).rejects.toThrow("Forum topic icon custom emoji ID cannot be empty");
});
```

How can I resolve this? If you propose a fix, please make it concise.