fix: preserve MCP project scope

[wbugitlab1]

Summary

• Preserve the optional MCP project argument in standalone memory_save, memory_recall, and memory_smart_search.
• Forward project from the full MCP server for memory_recall and memory_smart_search.
• Add read-tool schema entries and regenerate the MCP tools skill reference.
• Add regression coverage for standalone local fallback, standalone proxy forwarding, and full MCP tool-call forwarding.

Upstream issue reference: rohitg00#926.

Verification

• npm exec -- vitest run test/mcp-standalone.test.ts test/mcp-standalone-proxy.test.ts test/mcp-server-tools.test.ts failed red first with the expected missing project/schema forwarding failures.
• npx vitest run test/mcp-standalone.test.ts test/mcp-standalone-proxy.test.ts test/mcp-server-tools.test.ts passed: 46 tests.
• npm run build passed with existing tsdown deprecation/plugin timing warnings.
• npm run skills:check passed after npm run skills:gen.
• gitleaks protect --staged --redact passed.
• Targeted Semgrep on changed files passed with 0 findings.

Known Existing/Local Gate Issues

• Full npm test failed outside this MCP change: test/fs-watcher.test.ts retained 3 local watcher event-capture failures; test/retention.test.ts timed out in the full run but passed in isolated rerun.
• Full Semgrep reports pre-existing findings outside touched files.
• Full/history Gitleaks reports historical findings; no staged leaks were found for this patch.