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/ListSection.tsx

@@ -2,7 +2,7 @@ import { useCallback, useEffect, useRef, useState } from 'react';
 import { RefreshCw } from 'lucide-react';
 import { useClient } from 'hooks/useClient';
 import { readableError } from './errors';
-import { useConnectionChanged } from './channel';
+import { useNpmChanged } from './channel';
 
 /**
  * The four sections that are a list and nothing more — redirections, streams, 404 hosts, access lists.
@@ -44,7 +44,7 @@ export const ListSection = ({ path, emptyText, primary, secondary, isEnabled }:
 
   const [rows, setRows] = useState<Row[] | null>(null);
   const [error, setError] = useState<string | null>(null);
-  const [connectionSignal] = useConnectionChanged();
+  const [connectionSignal] = useNpmChanged();
 
   const load = useCallback(async () => {
     try {