fix(hub): stop keeping a copy of every group's file listing in the browser

`group_indexes` was an IndexedDB store holding a decrypted copy of each group's
index — every file's name, path, size, hash and uploader — written on every index
and on every delta, from three call sites.

It was the cross-group search of Phase 10b: `doSearch` read `getAllCachedIndexes`
and searched those records instead of dialling anything. On 2026-08-28 Search
began dialling the nodes, and that commit removed the reader and left the writers.
Since then the browser has gone on building a cleartext file listing that nothing
consulted, that no sign-out removed — the key database is a different one — and
that grew with every group ever opened. L7, at rest: kept code that nothing calls
does not sit still.

Drawing a group's files while its node is unreachable is the only thing such a
cache buys, and it is not wanted: a listing that cannot be opened is worse than an
honest absence. So there is nothing to read it with, and the writers go.

The store stays in the schema and is emptied instead. Dropping it needs a version
bump, a version bump is an upgrade another tab can block, and playlists share this
database — so the tidier change is the one with a failure mode. `purgeGroupIndexCache`
runs once per browser behind a flag, which clears what is already on people's
machines; a browser that refuses storage simply runs it again, which is harmless
because it is idempotent.

Three guards, each checked by reintroducing the fault: only `openDB` and the purge
may touch the store, the purge may only clear it, and the purge must actually be
called at start-up — a purge nobody calls is the same defect wearing the opposite
hat.

`test_sticky_header.py[firefox]` reports twelve setup errors in a full run here.
A Firefox instance is open on this machine, which is the trap CLAUDE.md describes;
the same twelve appear with these changes stashed, and the `[chrome]` half of the
same file, covering the same geometry, is clean.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

1 files changed, 2 insertions, 3 deletions

diff --git a/packages/meshbay-hub/tests/harness/search_fanout_harness.mjs b/packages/meshbay-hub/tests/harness/search_fanout_harness.mjs
index 74b4bb3..c05e23b 100644
--- a/packages/meshbay-hub/tests/harness/search_fanout_harness.mjs
+++ b/packages/meshbay-hub/tests/harness/search_fanout_harness.mjs
@@ -78,7 +78,6 @@ const shown = [];   // [{ at, groups }] — one entry per render the reader gets
 
 const session = { bundleKey: 'k' };
 const _loadBundleKey = async () => 'k';
-const cacheGroupIndex = () => {};
 
 // One group's index, answered on the clock rather than over a network.
 const fetchGroupIndex = (groupId) => new Promise((resolve, reject) => {
@@ -106,7 +105,7 @@ const lift = (signature) => {
 };
 
 const make = new Function(
-  'session', '_loadBundleKey', 'cacheGroupIndex', 'fetchGroupIndex', 'localStorage',
+  'session', '_loadBundleKey', 'fetchGroupIndex', 'localStorage',
   `const MAX_IN_FLIGHT = ${ceiling[1]};
    const DOWN_KEY = 'harness';
    ${lift('function lastKnownDown(')}
@@ -116,7 +115,7 @@ const make = new Function(
    return fetchAllIndexes;`,
 );
 const fetchAllIndexes = make(
-  session, _loadBundleKey, cacheGroupIndex, fetchGroupIndex, globalThis.localStorage);
+  session, _loadBundleKey, fetchGroupIndex, globalThis.localStorage);
 
 // ── The scenario ─────────────────────────────────────────────────────────────