fix: use exact match for wait --component

Substring matching could resolve too early (e.g. waiting for App
matches AppLoader). Exact match is more appropriate for a gate
condition.

Author: piotrski

packages/agent-react-devtools/skills/react-devtools/references/commands.md

@@ -25,7 +25,7 @@ If profiling is active, shows `Profiling: active`.
 Block until at least one React app connects via WebSocket. Resolves immediately if already connected. Default timeout: 30s. Exits non-zero on timeout.
 
 ### `agent-react-devtools wait --component <name> [--timeout S]`
-Block until a component with the given display name appears in the tree. Uses case-insensitive substring matching (same as `find`). Useful after a reload to wait for a specific part of the UI to render. Default timeout: 30s. Exits non-zero on timeout.
+Block until a component with the given display name appears in the tree. Uses exact name matching. Useful after a reload to wait for a specific part of the UI to render. Default timeout: 30s. Exits non-zero on timeout.
 
 ## Component Inspection
 

packages/agent-react-devtools/src/daemon.ts

@@ -313,7 +313,7 @@ class Daemon {
       case 'connected':
         return this.bridge.getConnectedAppCount() > 0;
       case 'component':
-        return this.tree.findByName(cmd.name, false).length > 0;
+        return this.tree.findByName(cmd.name, true).length > 0;
       default:
         return false;
     }