feat: index extra source roots beside the workspace, for the code you write against

The workspace index cannot answer questions about an installed framework or
SDK, and in plugin development that is where most of the reading goes: 64 of
80 tool calls in one real session went to the harness checkout under
/usr/local/lib/node_modules to look up the API being implemented.

A root is entered whatever it is called, and its dependencies are not: a
path ending in node_modules/... is the normal way to name a package tree,
while a node_modules below the root is somebody else's code. A result
carries the label that says which tree it came from and an absolute
sourcePath, the only form a follow-up read can resolve.

The tool description now also claims the move this replaces - searching
before reading files to find out what a module contains.

client/client.js

@@ -252,6 +252,16 @@ window.__ModuleLoader__.load({
         label: 'Scope marker files',
         hint: 'Comma separated filenames that make a directory its own scope. Empty uses the built-ins.',
       },
+      {
+        key: 'sourceRoots',
+        kind: 'list',
+        group: 'Focus',
+        label: 'Extra source roots',
+        hint:
+          'Comma separated trees to index beside the workspace, for code that is not in it. ' +
+          'A path, or name=path to choose the label results carry. Relative paths resolve against the ' +
+          'workspace; absolute ones are taken as given, e.g. /usr/local/lib/node_modules/@deepseek-ai',
+      },
 
       {
         key: 'expansionEnabled',