Every Location booted on the server emits catalog, agent, command, skill,
reference, integration, websearch and MCP events, including Locations this
client never opened. Each event eagerly re-fetched that location's catalog,
producing request waves across hundreds of directories.
Events still invalidate so the next explicit read is fresh, but only catalogs
a consumer already read are re-fetched, mirroring the existing config.updated
guard. credential.* events apply the same rule per stored location key.
Websearch providers have no explicit reader; the TUI's integration dialog
relies on events to fill them, so that refresh is gated on the location having
been opened (syncInfo) instead of on a prior read.