#17620: fix(bluebubbles): skip typing indicators when Private API is disabled

## Problem When BlueBubbles Private API is unavailable (e.g. macOS Tahoe / macOS 26 with SIP enabled), the three typing indicator call sites in `monitor-processing.ts` fire unconditionally. Since the BlueBubbles typing endpoint requires Private API, every call fails and spams the error log with `typing restart failed` / `typing start failed` messages on every single inbound message. The send path (`send.ts`) already correctly gates on `privateApiEnabled` via `getCachedBlueBubblesPrivateApiStatus`, but the typing indicators were missed. ## Fix Wraps the three `sendBlueBubblesTyping` call sites in `monitor-processing.ts` with the existing `privateApiEnabled` check: 1. **`restartTypingSoon`** timer callback — typing restart between streaming blocks 2. **`onReplyStart`** — typing indicator at start of reply 3. **`finally` block** — typing stop after reply completes When `privateApiEnabled` is `false`, typing calls are simply skipped. No behavioral change when Private API is available. ## Testing - Tested on Mac mini running macOS Tahoe (26.0) with SIP enabled, BlueBubbles server reporting `private_api: false` - Confirmed typing error log spam is eliminated - Confirmed messages still send and receive correctly via AppleScript fallback - Confirmed no change in behavior when Private API is enabled (typing indicators still work normally) <!-- greptile_comment --> <h3>Greptile Summary</h3> Adds `privateApiEnabled` guard checks before three `sendBlueBubblesTyping` call sites to skip typing indicators when BlueBubbles Private API is unavailable, matching the existing pattern in `send.ts:line 347`. - All three call sites (typing restart timer, `onReplyStart`, and `finally` block) now check `privateApiEnabled` before attempting to send typing indicators - When Private API is disabled, typing calls are silently skipped instead of making API requests that would fail - Eliminates error log spam on systems running macOS Tahoe / macOS 26 with SIP enabled where Private API is unavailable - No functional change when Private API is available — typing indicators continue to work normally - Implementation is consistent with the defensive pattern used elsewhere in the codebase <h3>Confidence Score: 5/5</h3> - This PR is safe to merge with no risk - The changes are minimal, focused, and add defensive guards that only skip optional typing indicator calls when Private API is unavailable. The implementation correctly mirrors the existing pattern from `send.ts`, uses the same `getCachedBlueBubblesPrivateApiStatus` check already present in the codebase, and adds no new logic or side effects. All three guard placements are appropriate and the behavior change is purely to eliminate unnecessary API calls (and resulting error logs) when Private API is disabled, with zero functional impact when it's enabled. - No files require special attention _{Last reviewed commit: 1522505} <!-- greptile_other_comments_section --> _{(2/5) Greptile learns from your feedback when you react with thumbs up/down!} <!-- /greptile_comment -->