docs(search): record routing policy and fallback tuning

TOOLS.md

@@ -45,6 +45,16 @@ Skills are shared. Your setup is yours. Keeping them apart means you can update
 - Tailscale IP:
   - `100.123.88.127`
 
+### Search routing
+
+- Default page-reading tool: native `web_fetch`
+- Default search path: `skills/local-meta-search/scripts/search.sh`
+- Routing policy:
+  - use **SearXNG first** for normal web lookups
+  - fall back to **Brave MCP** if SearXNG fails or returns weak/empty results
+  - use **Brave MCP directly** when Will explicitly asks for Brave / a second opinion
+- Backend labels should be called out in research answers when relevant
+
 ### Docker services
 
 - **searxng**

memory/2026-03-10.md

@@ -1,5 +1,13 @@
-# Session Notes — 2026-03-10
+# 2026-03-10
 
-- Will said the current assistant instance is running in a VM on his laptop for now.
-- Plan is to move the assistant to the main host later.
-- Will said he will be moving out of the current apartment on April 1st, 2026.
+## Search/fetch setup
+- Enabled native `web_fetch` in OpenClaw config.
+- Confirmed local SearXNG at `http://192.168.153.113:18803` is working.
+- Confirmed local Brave MCP endpoint at `http://192.168.153.113:18802/mcp` is reachable via `mcporter` as tool `brave_web_search`.
+- Added local skill `skills/brave-mcp-search` for direct Brave MCP-backed search.
+- Added local skill `skills/local-meta-search` to route search as:
+  - SearXNG first
+  - Brave MCP fallback on failure or weak/empty results
+- Search routing preference documented in `TOOLS.md`.
+
+Source: workspace changes + gateway config patch on 2026-03-10.

skills/local-meta-search/scripts/search.sh

@@ -34,7 +34,9 @@ run_brave() {
 
 searx_good=false
 if run_searx; then
-  if grep -qE '^[0-9]+\.' "$TMP1"; then
+  if grep -qE '^[0-9]+\.' "$TMP1" \
+     && ! grep -q 'Found 0 total results' "$TMP1" \
+     && ! grep -q 'No results found\.' "$TMP1"; then
     searx_good=true
   fi
 fi