feat(recall): qualify typed supplements and prepare MCP 1.0.5

[escott-]

Summary

• Prepare MCP 1.0.5 with primary-authorized typed document/event/node recall supplements across manual recall, session grounding and proactive context.
• Submit only source identities for fresh authorization; never admit discovery text as evidence or reuse stale formatted supplemental caches.
• Replace stale core-cache projections when fresh source authority revokes, deletes or changes their relevance; filter both text and structured JSON to selected evidence.
• Preserve doc/node identity and follow-up routes, reject query/scope/provenance spoofing, and separate source score families.
• Bump evidence policy to v3 while keeping sticky v2 cohort assignment; qualification/canary thresholds unchanged.

Verification

• MCP mcp-tools suite at version 1.0.5: 1,443 passed.
• Qualification evaluator: 18 passed.
• npm launcher: 6 passed.
• Public boundary/version contract check passed.
• Full workspace/all-target clippy -- -D warnings passed; diff checks clean.
• Local HTTP integration proves repeated same-client requests reauthorize changed and then revoked evidence.

Deployment dependency / gates

Requires companion API PR #560 (migration 404 and POST /session/recall/evidence) to be deployed before public/private runtime adoption. Missing endpoint fails closed as unavailable, not successful empty evidence.

This is release preparation, not a published release. After protected main review and green public CI, use an annotated v1.0.5 tag and the normal public-release approval. Verify immutable GitHub/R2/npm/registry artifacts, then private pin PR/canary. No held-out qualification or live non-shadow promotion is claimed. New v3 policy needs a fresh qualification receipt; existing >=48h / >=1,000 eligible-operation canary gates remain intact.