The release builds everos-cloud-memory's wheel and attaches it, but no installer and no upgrade named it, so the only way in was `uv tool install --with`, which the next `raven upgrade` undoes: uv replaces the tool's requirement set with what the command names, and the upgrade names the release's plugin list alone. A user who picked the cloud backend was told to install a plugin that had no install path. The live-service gate that kept it out is met: the six key-gated tests in tests/integration/test_everos_cloud_real_cloud.py ran against api.evermind.ai on 2026-10-09. So the distribution joins the list a complete install is made of -- release.yml, publish_beta.py for the beta channel, both installers' local-clone lists, and the Docker image's three plugin defaults. Installed is not selected: memory.backend still decides, doctor and the gateway build only the backend it names, and the one visible change is that `raven onboard` asks which memory backend to use rather than taking the only one installed. The rung that drops the product engines kept only everos-memory. That rung exists so long-term memory outlives a native build a platform refuses, so on such a machine every upgrade uninstalled the cloud backend from under a host configured to use it. install.sh, install.ps1 and the upgrade helper now keep both memory distributions, and the contract test reads which those are off the backend/distribution pairing rather than naming one by hand. Co-authored-by: Claude (claude-opus-5) <noreply@anthropic.com>
Raven Documentation
This directory holds design notes, dated records, and developer references that are too detailed for the main README.
For first-time users, start at the root README.md. Domain terms live in
CONTEXT.md, routed from CONTEXT-MAP.md. Several files below are dated
records kept for their history rather than descriptions of the current tree;
each such file carries a banner saying so.
Index
showcase.md/showcase.zh-CN.md- more showcases, linked from each root README: real runs, each shown as its task graph and what the run produced.technical-report/- the Raven technical report: abstract, citation, and a link to the PDF, which lives on a GitHub Release rather than in git.documentation-references.md- public reference sources and implementation evidence behind the protocol, orchestration, permissions, and extension guides.dev.md- local development notes.browser-and-desktop.md- the model'sbrowser_*tools over the shared Chromium, and desktop control through a desktop MCP server; enabling, permissions, what was verified.TRACING_STANDARD_API.md- the tracing span contract between raven and raven-tracing.research-report-quality.md- how a deep-research report is graded against a competitor's, and whatscripts/research_report_audit.pysettles mechanically.sandbox/- BoxLite sandbox usage and debugging notes.specs/- dated design records (YYYY-MM-DD-*.md) plus the self-evolution SOP and playbook specs; each describes the tree as of its date.plans/- historical implementation plans; an archive, deliberately not held to today's layout.examples/- benchmark and runtime configuration examples.Proactivity-Plan.md/Proactivity-Implementation.md- proactive-behavior design intent and as-built notes.Proactivity-Cost-Analysis.md- dated cost snapshot (2026-04).memory-plugin-architecture.md- design record for the memory-plugin architecture; the bundled-in-tree layout it proposes was superseded byplugins-dist/.everos-memory-e2e-test-plan.md- dated end-to-end memory validation plan.skill-hub-integration-design.md- design record; shipped asraven/skill_hub/.