docs: document EverOS 1.0.0 issue migration

[cyfyifanchen]

Summary

• Add EverOS 1.0.0 migration notes for legacy API routes, retired infrastructure, plugins, and benchmarks.
• Mark the OpenClaw card as an archived pre-1.0.0 reference instead of a current integration.
• Add a compatibility note to the legacy Claude Code plugin folder and include ruff cleanup for the deprecated-name checker.

Issue triage

This PR supports closing historical pre-1.0.0 issues that reference retired APIs such as /api/v1/memories, /api/v3/agentic/*, MongoDB/Elasticsearch/Milvus/Kafka, old OpenClaw plugin paths, and old benchmark pipelines. Remaining future-facing feature/research requests stay open.

Validation

• uv run pre-commit run --all-files
• make docs-check
• python3 scripts/check_deprecated_names.py

[cyfyifanchen]

Post-triage audit update:

I rechecked the issue closures with a stricter open-source standard: keep closed only if the report clearly targets retired pre-1.0.0 APIs/infrastructure or is directly answered by EverOS 1.0.0 docs/code.

Reopened because they are still valid 1.0.0 questions or need maintainer follow-up, even if they mention older terminology:

• 能不能提前给他灌输一些记忆，然后当客服用 #11 customer-service/pre-seeded memory use case
• 请问在 AI Coding 场景适用吗 #15 AI Coding use case
• [FEATURE] Retrieval pipeline in code doesn’t match the paper #65 paper-vs-code retrieval behavior
• Chat Agent + MemSys integration: recommended practices & official search tool schema? #193 chat-agent integration and official search/tool schema guidance

Added more specific post-triage verification comments to several closed issues where the original closure note was too generic, including provider support (#4, #6, #23, #29), search/profile/full-episode behavior (#46, #58, #78, #131, #158), timestamp behavior (#48), deletion lifecycle (#148 -> #14), and legacy OpenClaw/API docs (#191, #237).

Final state after correction: 33 issues closed as pre-1.0.0/answered, 18 issues remain open.