This is a comment left during a code review.
Path: server/src/services/activity-log.ts
Line: 78

Comment:
**Plugin handler errors are silently discarded**

`emit()` returns a `Promise<PluginEventBusEmitResult>` where the `errors` array holds any failures from individual plugin handlers (they're already isolated per-plugin inside the bus). By using `void ... .catch(() => {})`, the result is thrown away entirely — so if a plugin handler throws, there's no log, no metric, and no way to diagnose the failure.

The `.catch(() => {})` is also effectively dead code because the bus never rejects (it catches all handler errors internally). Consider inspecting the result and logging failures:

```suggestion
    void _pluginEventBus.emit(event).then(({ errors }) => {
      for (const { pluginId, error } of errors) {
        console.error(`[plugin-event-bridge] handler error in plugin "${pluginId}":`, error);
      }
    });
```

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

---

This is a comment left during a code review.
Path: server/src/services/activity-log.ts
Line: 16-18

Comment:
**No guard against double-initialization**

`setPluginEventBus` can be called multiple times and silently replaces the current bus with no warning. In tests where `createApp()` is called per-suite or per-test, the module-level `_pluginEventBus` will be overwritten on each call, with no indication that an existing bus has been replaced.

A warn-or-throw guard would make misuse obvious:

```suggestion
export function setPluginEventBus(bus: PluginEventBus): void {
  if (_pluginEventBus !== null && _pluginEventBus !== bus) {
    console.warn("[activity-log] setPluginEventBus called more than once — replacing existing bus");
  }
  _pluginEventBus = bus;
}
```

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