docs: polish client cookbook validation

Use standard authentication terminology and propagate direct test failures through the process exit code.

Tests: Docker lint and documentation unit suite (6 passed)

Author: ihor-sokoliuk

__tests__/unit/documentation.test.ts

@@ -193,5 +193,7 @@ export async function runTests(): Promise<TestResult> {
 }
 
 if (process.argv[1] !== undefined && fileURLToPath(import.meta.url) === process.argv[1]) {
-  runTests();
+  runTests().then((testResults) => {
+    process.exit(testResults.failed > 0 ? 1 : 0);
+  }).catch(console.error);
 }

docs/client-configurations.md

@@ -31,7 +31,7 @@ that the client can never support it.
 | Cline | Yes | Yes | Yes |
 | OpenCode | Yes | Yes | Yes |
 
-Claude Desktop remote connectors accept authless or OAuth servers, but a
+Claude Desktop remote connectors accept unauthenticated or OAuth servers, but a
 network-exposed `mcp-searxng` server uses its own static bearer-token hardening.
 Cursor's current remote MCP documentation likewise specifies OAuth. Because
 `mcp-searxng` does not implement MCP OAuth, this cookbook keeps both clients on