the lists re-read when the agent changes something

an agent deleted two proxy hosts and both stayed on screen. the person had the
answer in the transcript and a stale list six inches above it — which is the
one thing a chat beside a list has to get right, and the reason it is beside
the list at all.

so the chat panel bumps the refresh channel when a turn ran tools, and every
section re-reads. gated on hadToolCalls: a turn that only talked changed
nothing, and re-reading after every sentence would put six requests behind
every reply.

the channel is renamed with it. it was proxy-manager:connection-changed, named
after its only publisher; it has two now and the second is the bigger one, so
it says what it MEANS — something at NPM changed, read it again.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Officer-Session: 656f5c85-e49a-4f1f-b9f3-042a04b4d043

web/NavPanel.tsx

@@ -2,7 +2,7 @@ import { useCallback, useEffect, useRef, useState } from 'react';
 import { useSearchParams } from 'react-router';
 import { useClient } from 'hooks/useClient';
 import { SECTIONS, DEFAULT_SECTION, isSectionKey, type SectionKey } from './sections';
-import { useConnectionChanged } from './channel';
+import { useNpmChanged } from './channel';
 
 /**
  * The left column: which part of Nginx Proxy Manager the detail panel is showing.
@@ -34,7 +34,7 @@ const useSectionCounts = () => {
   clientRef.current = client;
 
   const [counts, setCounts] = useState<Partial<Record<SectionKey, number>>>({});
-  const [connectionSignal] = useConnectionChanged();
+  const [connectionSignal] = useNpmChanged();
 
   const load = useCallback(async () => {
     const results = await Promise.all(