ryo-executor 0.1.0

[experimental] Mutation execution engine for RYO - parallel execution, conflict detection, workspace management
Documentation
//! Placeholder V2 implementations for MutationSpecs without corresponding Mutations
//!
//! These specs exist in blueprint DSL but have no ryo-mutations implementation:
//! - AddSpec: Add Spec type alias
//! - MoveItem: Move item between modules
//! - PluginTransform: Execute WASM plugin
//!
//! # Quality Policy (from ast_reg_apply.rs)
//!
//! ## DON'T:
//! - Create hacky workarounds just to make tests pass
//! - Use temporary allocations or intermediate representations (defeats V2 purpose)
//! - Copy V1 patterns that don't fit the registry-based model
//!
//! ## When V2 Cannot Handle a Mutation Cleanly:
//! 1. Do NOT hack the implementation or tests to force it to work
//! 2. Do evaluate if ASTMutationContext needs new methods
//! 3. Do consider if ASTRegistry/SymbolRegistry need enhancements
//! 4. Do document the design gap and propose a proper solution
//!
//! # Design Decision
//!
//! These are not implemented as ASTRegApply because:
//! - AddSpec: Could be implemented via AddTypeAlias composition
//! - MoveItem: Could be implemented via RemoveItem + AddItem composition
//! - PluginTransform: Requires WASM runtime, out of scope for V2 core
//!
//! Consider implementing as Blueprint-level compositions rather than
//! individual mutations.

// No ASTRegApply implementations here - these are handled directly in blueprint_executor.rs