pika-cloud

The pika-agent-microvm crate contained the full microvm spawner HTTP client (MicrovmSpawnerClient), the higher-level MicrovmManagedVmProvider wrapper, parameter resolution logic (resolve_params, validate_resolved_params), the guest autostart bash script generator (microvm_autostart_script), OpenClaw gateway configuration builder, and an extensive test suite.

All of this is deleted because the platform no longer provisions agents via the microvm spawner. The Cargo.toml workspace members list removes both pika-agent-microvm and pika-agent-control-plane, replacing them with the new pika-cloud crate.

The vm-spawner crate was the HTTP server that managed microvm lifecycles (create, delete, recover, restore, backup-status). With the Incus-only hard cut, this entire binary is removed from the workspace. The Cargo.lock entry and workspace member listing are both cleaned up.

The pika-agent-control-plane crate is renamed to pika-cloud. This crate contains the shared type definitions used across the server, CLI, and CI tooling — including AgentProvisionRequest, AgentStartupPhase, IncusProvisionParams, and related enums/structs. The new name better reflects the crate's purpose as general cloud provisioning types rather than being tied to a specific microvm control plane.

The pika-cloud crate is organized into focused modules: lifecycle.rs (startup phases and status), mount.rs (mount point definitions), paths.rs (guest filesystem paths), policy.rs (policy types), and spec.rs (provision request and Incus parameter types). The anyhow dependency is dropped since the crate now only needs serde and serde_json.

The CLI's Cargo.toml swaps the dependency name and path. In cli/src/main.rs, the use statement is updated from pika_agent_control_plane to pika_cloud, importing the same types (AgentProvisionRequest, AgentStartupPhase, IncusProvisionParams).

The pika-server crate is updated to depend on pika-cloud instead of pika-agent-control-plane. All source files that previously imported from pika_agent_control_plane now import from pika_cloud. The managed OpenClaw guest module (managed_openclaw_guest.rs) similarly updates its imports for types like IncusProvisionParams, AgentStartupPhase, and AgentProvisionRequest.

This is the core architectural change in pikaci. Previously, executor.rs defined an Executor trait with incus and microvm modules implementing it. The microvm executor module is deleted entirely, and the Executor trait is removed.

The executor.rs module is reduced to a single re-export line: pub mod incus;. The Incus executor in executor/incus.rs is updated to add pika-cloud as a dependency and gains a provision_params field for IncusProvisionParams.

In model.rs, the ExecutorBackend enum is simplified — the Microvm variant and its associated MicrovmExecutorConfig are removed. The run.rs file no longer needs to match on executor backends or construct microvm executors.

The main.rs CLI removes the --microvm-spawner-url argument and all microvm-related configuration parsing, leaving only Incus-related options.

The pikahut crate's dependency list in Cargo.lock shows the swap from pika-agent-control-plane to pika-cloud. Test files that reference provisioning types or component configurations are updated to use the new crate name. The component.rs file and test support modules adjust their imports accordingly.

The rust/ workspace root crate (used for the core SDK and shared agent logic) adds pika-cloud as a dependency. The agent.rs module updates its imports to reference types from pika_cloud instead of the removed pika_agent_control_plane.

Two new Nix files define the Incus container images:

• managed-agent-image.nix — builds the image used for managed agent containers inside Incus, containing the necessary runtime dependencies.
• pikaci-image.nix — builds the image used by pikaci itself to run CI jobs in Incus containers.

The flake.nix is updated to wire these new image definitions into the Nix flake outputs, and flake.lock is updated with any new input pins.

The ci/forge-lanes.toml file defines which file paths trigger which CI lanes. Every lane that previously referenced crates/pika-agent-control-plane/** or crates/pika-agent-microvm/** is updated to reference crates/pika-cloud/** instead. The scripts/demo-agent-microvm.sh entry is removed from lane triggers since that script no longer exists.

Infrastructure Nix modules are updated to reflect the Incus-only world:

• microvm-host.nix is either removed or gutted of microvm-specific service definitions.
• pika-server.nix module removes references to the vm-spawner service and microvm provisioning.
• builder.nix removes microvm image build steps.
• The infra/justfile removes recipes like agent-microvm-tunnel that were used for SSH tunneling to the microvm spawner.
• infra/secrets/README.md is updated to remove references to microvm-specific secrets.

The CI Nix build system maintains a mirrored pika-core-workspace that lists workspace members for hermetic Nix builds. This mirror is updated to remove pika-agent-microvm and vm-spawner from the members list and add pika-cloud.

The linux-rust.nix expression is adjusted to reference the new crate paths. The just/checks.just file removes any microvm-specific check or lint targets.

Several new documentation files are added:

• incus-migration-plan.md — The overall plan for migrating from microvm to Incus, including phasing and rollback strategy.
• incus-dev-lane.md — How to use the Incus development lane for local testing.
• microvm-stuck-chat-runbook.md — Operational runbook for handling stuck microvm chats during the transition period.
• ci-selectors.md — Documents the CI selector mechanism for choosing test backends.
• integration-matrix.md — Defines the integration test matrix across backends.
• microvm-launcher-scope-lock.md, microvm-launcher-target.md, microvm-spawner-scope.md — Scope documentation freezing the microvm launcher and spawner to prevent further investment.
• agent-ci.md — Updated agent CI documentation reflecting the Incus-only backend.

A new incus-dogfood-check.sh script is added to scripts/. This script exercises the Incus provisioning path end-to-end, validating that container creation, agent startup, readiness checks, and cleanup all work correctly. It serves as a manual or CI-driven smoke test to build confidence before the production cutover.

Several tracking documents are added or updated:

• pika-cloud.md — Tracks remaining work items for the pika-cloud crate consolidation.
• microvm-v2.md — Documents the microvm v2 deprecation status and remaining cleanup.
• microvm-launcher-simplify.md — Tracks simplification of the (now frozen) microvm launcher.
• tests-living-plan.md — A living document for the test strategy as the backend migration progresses, ensuring test coverage is maintained through the transition.