This is a comment left during a code review.
Path: extensions/bluebubbles/src/monitor.ts
Line: 266-273

Comment:
**Possible duplicate delivery for text-plus-attachment messages**

When a sender sends a message that has both text and an attachment, BlueBubbles fires `new-message` (text only, attachment not yet available) and then `updated-message` ~2–3 s later (same text, full attachment). The fix lets the `updated-message` through, which is the right call for attachment-only sends. However, for text+attachment, `normalizeWebhookMessage` will extract the same non-empty text from both events, producing a non-empty `rawBody` each time. `processMessage` has no deduplication by `messageId` on the inbound path, so the same text body would be dispatched to the session twice — first without the attachment placeholder and then with it.

This is the crucial code path:

```
new-message   → rawBody = "some text"        → enqueued → delivered
updated-message (2–3 s later, outside 500 ms debounce window)
              → rawBody = "some text"        → enqueued → delivered again
```

If BlueBubbles guarantees `updated-message` only fires for attachment-only sends (no accompanying text), this is fine. If it fires for text+attachment, users will see a duplicate line.

Consider checking the `messageId` against a short-lived seen-set before enqueueing (deduplication window of ~5 s would cover the `updated-message` delay), or restricting the pass-through to cases where `text` is empty so only attachment-only events are affected.

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/bluebubbles/src/monitor.ts
Line: 264-267

Comment:
**Misleading variable name and no-op alias**

`hasAttachments` is named like a boolean but is assigned an array, which makes `hasAttachments.length > 0` feel redundant on inspection. `payloadRecord` is also a pure alias of `payload` that adds no value. The full block can be simplified:

```suggestion
      const dataRecord = (payload as Record<string, unknown> & { data?: Record<string, unknown> }).data;
      const attachmentsFromData = Array.isArray(dataRecord?.attachments)
        ? (dataRecord.attachments as unknown[])
        : [];
      const attachmentsFromRoot = Array.isArray(payload.attachments)
        ? (payload.attachments as unknown[])
        : [];
      const hasAttachments = attachmentsFromData.length > 0 || attachmentsFromRoot.length > 0;
      const updatedMessageHasAttachments = eventType === "updated-message" && hasAttachments;
```

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/bluebubbles/src/monitor.ts
Line: 277-283

Comment:
**Stale log message**

The verbose log still says "without reaction" even though the filter now also passes events that have attachments. When an `updated-message` with no reaction and no attachment is dropped, the log is accurate for that case, but readers may be confused about why an attachment-carrying event was passed through while the drop-path still says "without reaction". Consider updating it:

```suggestion
            `webhook ignored ${eventType || "event"} without reaction or attachments`,
```

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