Updates

docs/harness-integration.md

@@ -43,16 +43,16 @@ it with `# completed`. Computer-use tools are custom harness tools backed by
 
 ## Adding a tool
 
-1. Put the implementation in the appropriate skill module. Public web search
-   and page fetch already live in
-   `vendor/agent-harness/agent/web-search.js` (`web_search`, `google_search`,
-   `fetch_page`, `web_fetch`, `wiki_search`, `hn_search`, `code_search`), which
-   calls the Playwright sidecar in `browser-use/`. Extra clicks use the custom
-   `browser` gateway from `skills/browser-tools.js`. Webcam stills use
-   `skills/webcam-tools.js` after Settings → Camera → Allow now.
+1. Put the implementation in the appropriate skill module. Public web access is
+   only the custom `browser` gateway from `skills/browser-tools.js`, which
+   calls the Playwright sidecar in `browser-use/`. Do not register
+   `web_search` or `web_fetch`. Webcam stills use `skills/webcam-tools.js`
+   after Settings → Camera → Allow now.
 2. Export a JSON-schema tool with a stable name, description, timeout, and
    permission level.
-3. Route QVAC work through the master facade.
+3. Route QVAC work through the master facade. Opt-in Groq is only for
+   thinking about a `browser` result. Other tool turns stay on local QVAC.
+   Skills still do not call Groq.
 4. Add a focused fixture test with a fake master or backend.
 5. Update [API](api.md), the capability matrix, and the roadmap if the tool is
    user-visible.