Crate memstead_engine 

Full-flavor engine extension for Memstead.

This crate is the source-boundary home for code that the lean engine (memstead-base) must not carry. The boundary cut targets multi-mem lifecycle and the engine-only EngineError variants.

Today the crate hosts:

• The typed full-error envelope (FullEngineError) — wraps memstead_base::EngineError and carries the lifecycle-only variants (error::FullEngineError::MemPathNotAllowed, error::FullEngineError::MemReferencedByPolicy, error::FullEngineError::MemSchemaNotAllowed, error::FullEngineError::ConfigAlreadyExists).
• The mem-lifecycle orchestrators (mem_management::create_mem, mem_management::delete_mem) and their param/response types. They consume &mut memstead_base::Engine directly; full contributes lifecycle as free functions over the lean engine rather than via a wrapper struct or a policy-provider trait.

The matcher primitives (memstead_base::CreateRuleSet, memstead_base::DeleteRuleSet, memstead_base::MatcherSet) stay in lean — the lean engine’s cross_mem_link_allowed synthesises a CreateRuleSet on multi-folder workspaces, so they are a lean policy primitive used by both flavors.

Lifecycle functions currently return Result<_, memstead_base::EngineError> so the full-MCP server’s engine_err_unified mapper continues to consume them unchanged. A follow-up commit switches the return type to Result<_, FullEngineError> and drops the four lifecycle-only variants from memstead_base::EngineError.

Re-exports

pub use error::FullEngineError;

pub use error::RecoveryAction;

pub use health::ComposeHealthError;

pub use health::HealthArgs;

pub use health::HealthConfig;

pub use health::compose_health;

pub use overview::ALLOWED_OVERVIEW_INCLUDE_KEYS;

pub use overview::ComposeOverviewError;

pub use overview::DEFAULT_OVERVIEW_BUDGET;

pub use overview::OverviewArgs;

pub use overview::OverviewOutput;

pub use overview::Surface;

pub use overview::compose_overview;

Modules

error

Full-flavor engine error envelope.

health

Shared health composer used by the memstead_health MCP tool and any non-MCP caller (CLI, a future HTTP surface).

mem_management

Mem-lifecycle orchestrator — full home for the multi-mem create and delete pipelines. The matcher primitives (memstead_base::CreateRuleSet, memstead_base::DeleteRuleSet, memstead_base::MatcherSet) stay in lean because the lean engine’s cross_mem_link_allowed synthesises a memstead_base::CreateRuleSet on multi-folder workspaces. Only the lifecycle orchestrators — create_mem, delete_mem, their param/response types, the shared NOTE_MAX_LEN cap, and the validate_mem_path helper — live here.

overview

Shared overview composer used by both the memstead_overview MCP tool and the full CLI overview command.

workspace_config_edit

toml_edit-backed writer for .memstead/workspace.toml.