fix(readme): drop stale + missing screenshot refs; test meta-tool activity store

- README referenced screenshots that are stale (client-detail, featureset-detail
  show the pre-redesign IA and the old "Default" FeatureSet) or never captured
  (workspaces, tool-optimization). Remove those image refs so the README isn''t
  broken or misleading; the feature text stays. Remaining images (servers,
  discover, discover-web, space-switcher) are current. The full set still needs a
  capture run on a machine with a display (see docs/screenshots/README.md).
- Add a unit test for metaToolActivityStore (ring-buffer trim, most-recent-first,
  clear) — guards the "activity vanished on tab change" fix.

Signed-off-by: Mohammod Al Amin Ashik <maa.ashik00@gmail.com>

Author: its-mash

README.md

@@ -111,20 +111,14 @@ Create isolated Spaces — each with their own servers, credentials, and permiss
 
 Your AI client tells McpMux which folder it's working in (its MCP *root*). McpMux uses that to **route each workspace to its own toolset** — open your backend repo and the AI sees your database and deploy tools; open a docs folder and it sees only search and filesystem. Map a folder once in the **Workspaces** tab (or let the AI do it — see below) and every future session from that exact path resolves automatically. Matching is per-folder and exact, so nothing leaks across projects.
 
-![Workspaces — route each folder to its own FeatureSet](docs/screenshots/workspaces.png)
-
 ### Control What Each Client Can Do
 
 Not every AI client should have the same power. Create Feature Sets — permission bundles that control exactly which tools, prompts, and resources a client can access. Build a "Read Only" set for cautious workflows, a "React Development" set with just GitHub and Filesystem, or a "Full Stack Dev" set with everything. Assign them per-client so each tool only goes where you want it.
 
-![Feature Sets — granular per-server tool selection](docs/screenshots/featureset-detail.png)
-
 ### See and Manage Every Connected Client
 
 Cursor, VS Code, Windsurf, Claude Code — see every AI client connected to your gateway in real time. Click any client to manage its workspace, grant or revoke feature sets, and see exactly which tools it can access. New clients authenticate via OAuth with a one-click approval flow.
 
-![Client Management — per-client permissions and effective features](docs/screenshots/client-detail.png)
-
 ### Let Your AI Curate Its Own Toolset
 
 Hand an assistant a hundred tools and it burns tokens and reaches for the wrong one. McpMux ships a built-in **Tool Optimization** capability so the AI can keep *itself* lean — straight from chat, no config files.
@@ -139,8 +133,6 @@ Reads are silent; anything that changes your setup pops a **one-click approval d
 
 > *"@mux build a minimal toolset for this Next.js repo and pin it to this folder."*
 
-![Tool Optimization — the AI composes and pins its own toolset, gated by your approval](docs/screenshots/tool-optimization.png)
-
 ---
 
 ## Security

tests/ts/stores/metaToolActivityStore.test.ts

@@ -0,0 +1,52 @@
+/**
+ * Guards the fix for "Recent meta-tool activity vanished on tab change":
+ * rows live in a global store (not component-local state), so this verifies
+ * the store's ring-buffer semantics directly.
+ */
+
+import { describe, it, expect, beforeEach } from 'vitest';
+import {
+  useMetaToolActivityStore,
+  MAX_META_TOOL_ROWS,
+} from '@/stores/metaToolActivityStore';
+import type { MetaToolAuditEvent } from '@/lib/api/metaTools';
+
+function ev(tool: string, i: number): MetaToolAuditEvent {
+  return {
+    client_id: `client-${i}`,
+    tool_name: tool,
+    decision: 'read',
+    summary: '',
+    timestamp: new Date(2026, 0, 1, 0, 0, i).toISOString(),
+  } as MetaToolAuditEvent;
+}
+
+describe('metaToolActivityStore', () => {
+  beforeEach(() => useMetaToolActivityStore.getState().clear());
+
+  it('keeps rows most-recent-first', () => {
+    const { push } = useMetaToolActivityStore.getState();
+    push(ev('first', 1));
+    push(ev('second', 2));
+    expect(useMetaToolActivityStore.getState().rows.map((r) => r.tool_name)).toEqual([
+      'second',
+      'first',
+    ]);
+  });
+
+  it('trims to the ring-buffer size, dropping the oldest', () => {
+    const { push } = useMetaToolActivityStore.getState();
+    for (let i = 0; i < MAX_META_TOOL_ROWS + 10; i++) push(ev('t', i));
+    const rows = useMetaToolActivityStore.getState().rows;
+    expect(rows.length).toBe(MAX_META_TOOL_ROWS);
+    // Newest kept, oldest evicted.
+    expect(rows[0].client_id).toBe(`client-${MAX_META_TOOL_ROWS + 9}`);
+    expect(rows.some((r) => r.client_id === 'client-0')).toBe(false);
+  });
+
+  it('clear empties the buffer', () => {
+    useMetaToolActivityStore.getState().push(ev('a', 1));
+    useMetaToolActivityStore.getState().clear();
+    expect(useMetaToolActivityStore.getState().rows).toEqual([]);
+  });
+});