fix: preserve operation outcomes during plug-in shutdown

Keep API logging callable after display cleanup by forwarding late messages to the console. Abort conflict-check admission and pending dispatch, and propagate cancellation to waiters.

Let started data operations follow their existing success and failure paths without delaying database close. Verify repeated shutdown, instance isolation, and unload/reload in unit, PouchDB, and real Obsidian tests.

src/serviceFeatures/conflictResolution/index.ts

@@ -52,7 +52,6 @@ export const useConflictResolutionFeature = createServiceFeature((host: Conflict
     const eventSubscriptions = new AbortController();
     const dispose = (): void => {
         checking.dispose();
-        operations.dispose();
         eventSubscriptions.abort();
     };
     services.context.events.onceEvent(EVENT_PLUGIN_UNLOADED, dispose, { signal: eventSubscriptions.signal });