fix(docsync): name the store of a binding whose provider is switched off

Both shells keep a binding on screen after an admin switches its
provider off, and name its store through storeName(), which falls back
to a providerName on the link before the raw id. The server never sent
one, so such a binding was labelled with the provider id. publicLink
now carries providerName from document_providers.name whatever its
enabled flag, and every route and the MCP listing that return links go
through it.

The comments on docsync:changed in the realtime schema and the client's
event policy say that the event now also marks a binding created or
removed, and that the Files screen re-asks whether to offer the sync
button when it arrives.

server/src/nest/doc-sync/doc-sync-config.service.ts

@@ -113,6 +113,18 @@ export class DocSyncConfigService {
     return this.providerFields(providerId).filter((f) => f.secret === 1).map((f) => f.field_key);
   }
 
+  /**
+   * The display name whatever the enabled flag says. A binding outlives the
+   * admin switching its provider off, and the client only gets names for the
+   * providers that are still on, so without this it would show the raw id.
+   */
+  private providerName(providerId: string): string {
+    const row = this.db.connection
+      .prepare('SELECT name FROM document_providers WHERE id = ?')
+      .get(providerId) as { name: string } | undefined;
+    return row?.name ?? providerId;
+  }
+
   // ── Connections ────────────────────────────────────────────────────────────
 
   getConnection(id: number): ConnectionRow | undefined {
@@ -433,6 +445,7 @@ export class DocSyncConfigService {
       tripId: link.trip_id,
       connectionId: link.connection_id,
       providerId: link.provider_id,
+      providerName: this.providerName(link.provider_id),
       scopeKey: link.remote_scope_key,
       remoteRootId: link.remote_root_id,
       remoteRootPath: link.remote_root_path,