Add state persistence for wassette runtime transfer between agents

[Copilot]

Wassette needs state persistence to enable agent handoffs, backups, and environment migrations. This adds JSON-based snapshot export/import with security-first design.

Implementation

Core module (state_persistence.rs)

• StateSnapshot with versioned JSON schema
• ComponentState captures metadata, policies, optional binaries (base64)
• Validation and file I/O operations

LifecycleManager methods

• export_state(options) → captures runtime state
• import_state(snapshot, options) → restores from snapshot
• Component filtering, metadata tagging, skip-existing mode

Security model

• Secrets excluded (never serialized)
• Policies included (auditable, not sensitive)
• Unix 0600 permissions on restored files
• Structure validation before import

API

// Export state (default: ~1KB/component, no binaries)
let snapshot = manager.export_state(SnapshotOptions {
    include_binaries: false,  // true for self-contained (~1-10MB/component)
    component_filter: Some(vec!["fetch-rs".into()]),  // or None for all
    metadata: Some(SnapshotMetadata { 
        description: Some("prod backup".into()),
        tags: Some(HashMap::from([("env", "prod")])),
        ..Default::default()
    }),
    ..Default::default()
}).await?;

snapshot.save_to_file("state.json").await?;

// Import state
let snapshot = StateSnapshot::load_from_file("state.json").await?;
let count = manager.import_state(&snapshot, RestoreOptions {
    skip_existing: true,
    ..Default::default()
}).await?;

Use cases

• Agent handoff: Transfer Copilot → Claude Code with preserved configuration
• Backup/restore: Regular snapshots for disaster recovery
• Environment promotion: Dev → staging → prod with consistent state
• Team collaboration: Share configs via git (small snapshots without binaries)
• CI/CD: Reproducible test environments from fixture snapshots

Related

Complements headless deployment (#307): manifest provisioning for initial setup, state snapshots for runtime transfer.

Files

• crates/wassette/src/state_persistence.rs - New module
• crates/wassette/src/lib.rs - Export/import methods
• crates/wassette/src/policy_internal.rs - PolicyInfo serialization
• docs/design/state-persistence.md - Architecture and security analysis
• docs/examples/state-persistence-examples.md - Usage patterns

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/Mossaka/wit-docs-inject/commits/HEAD
  • Triggering command: /home/REDACTED/.rustup/toolchains/1.90-x86_64-REDACTED-linux-gnu/bin/cargo install --git REDACTED (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Explore how to save the state of wassette for transfer between agents</issue_title>
<issue_description>Investigate methods to persist the state of wassette so that it can be transferred or shared between different agents. Consider use cases, possible data formats, and potential security or consistency considerations.

Related: #307</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Explore how to save the state of wassette for transfer between agents #466

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.