[enricopiovesan]

Monday SEO Q&As grounded in last week's weekly demo findings, plus MCP drift fixes.

New Q&As (hub + llms.txt):

• /questions/why-does-traverse-mcp-fail-with-catalog-load-failed.html — crates.io traverse-mcp 0.15.0 can't start outside a checkout (traverse#1720, open); workarounds; no traverse-mcp-v* release yet (#1701 on main, #1721).
• /questions/why-does-traverse-mcp-fail-with-registry-metadata-cache-invalid.html — prepare-cache accepts a trimmed synced-state the Mode A server rejects (traverse#1721, open); digest-only Mode A.
• /questions/does-the-same-wasm-give-byte-identical-output-on-every-host.html — policy_hash split from sorted-key re-serialization in traverse-mcp (traverse#1722, open); sorted-key input is byte-identical on all three hosts.

Drift fixes:

• how-do-i-connect-cursor-to-traverse: said Cursor "exchanges JSON-RPC" and can list tools; traverse-mcp speaks its own line-delimited command protocol (matches mcp-setup protocol note and stdio_server.rs on main).
• docs/troubleshooting fix: use SVG logo (PNG is gitignored) #7: manual test showed an invented JSON-RPC tools/list reply; now uses {"command":"describe_server"} with -- stdio, config args ["stdio"].
• docs/guides/mcp-setup: version badge v0.10.1 -> v0.15.0; checkout prerequisite notes #1720.
• OS-behavior Q&A: added input-bytes caveat (#1722). Agent MCP Q&A: related links.

No release claims; everything unreleased is marked open.