gloryfromca ce2713e9a5 fix(*): ship the cloud memory plugin with raven, not beside the release
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>
2026-10-20 21:54:35 +08:00
..

Raven operational scripts

Standalone CLIs and admin utilities. Not part of the Raven wheel — these scripts are invoked directly from a checkout and don't ship to end users.

Layout

scripts/
├── README.md                     This file.
├── boxlite_cli.py                Direct CLI for the boxlite microVM library.
└── check_mirasim_frames.py       Check a Mirasim host bundle for the frames the Mirasim adapter uses.

When to use

Script Purpose See
boxlite_cli.py Manage boxlite OCI images + VMs (pull / ls / create / start / stop / rm / shell). Independent of Raven — works even when no agent is running, can inspect VMs owned by another boxlite home. docs/sandbox/boxlite_cli.md
check_mirasim_frames.py After Mirasim updates, check that its host still names every frame and field raven/acp/mirasim/ speaks. Run it --against the bundle that last worked: a name renamed in one of the places that say it then shows as occurring fewer times, which presence alone cannot see. Reads the bundles as text and never runs them; exits 1 naming what is missing or fewer, 2 when a bundle cannot be read. the module docstring

scripts/boxlite_cli.py is complementary to the raven sandbox sub-command group (in raven/cli/sandbox_commands.py):

  • raven sandbox … — agent-runtime debug interface (Unix-socket connection to a SandboxDebugServer inside a running Raven process; only sees VMs owned by that process).
  • scripts/boxlite_cli.py … — direct boxlite library CLI (manages images, creates / cleans up VMs, can target any boxlite home dir).

Use raven sandbox when you want to inspect / shell into the VMs your live agent is currently using. Use scripts/boxlite_cli.py for everything else (image management, post-mortem cleanup, cross-process inspection, Raven-not-running scenarios).

Where fixture generators live

Test / benchmark data generators are NOT in scripts/ — they live alongside the benchmark or test that consumes them. Examples:

  • benchmarks/skill_evals/fixtures/build_mock_library.py — synthetic SQLite mass-library DB for test_skill_forge_e2e.py and skill_evals/run_eval.py.