multi-server client with an explicit protocol-era boundary
client registry
server/discover probe -> modern result or recognized modern error -> stay modern
unrecognized error or timeout -> isolated legacy initialize fallback
cache era per peer; every modern request still repeats version + capabilities + clientInfo
modern peer: files
server/discover -> 2026-07-28
tools: read, search
lists: sorted + cache hints
calls: fresh params._meta
legacy peer: archive
discover -> unrecognized -32601
then initialize + initialized
tools: restore, search
legacy wire stays legacy
modern peer: notes
server/discover -> 2026-07-28
tools: create, search
lists: sorted + cache hints
calls: fresh params._meta
deterministic merged namespace and route table
create | read | restore | search | files/search | notes/search
canonical name -> peer + local name; silent overwrite is forbidden
A peer record is client bookkeeping, not server-side protocol session state.