swarm_memory 2.1.5 → 2.1.6

data/lib/swarm_sdk/plugin.rb

@@ -1,309 +0,0 @@
-# frozen_string_literal: true
-
-module SwarmSDK
-  # Base class for SwarmSDK plugins
-  #
-  # Plugins provide tools, storage, configuration parsing, and lifecycle hooks.
-  # Plugins are self-registering - they call SwarmSDK::PluginRegistry.register
-  # when the gem is loaded.
-  #
-  # ## Adding Custom Attributes to Agents
-  #
-  # Plugins can add custom attributes to Agent::Definition that are preserved
-  # when agents are cloned (e.g., in Workflow). To do this:
-  #
-  # 1. Add attr_reader to Agent::Definition for your attribute
-  # 2. Parse the attribute in Agent::Definition#initialize
-  # 3. Implement serialize_config to preserve it during serialization
-  #
-  # @example Plugin with custom agent attributes
-  #   # 1. Extend Agent::Definition (in your plugin gem)
-  #   module SwarmSDK
-  #     module Agent
-  #       class Definition
-  #         attr_reader :my_custom_config
-  #
-  #         alias_method :original_initialize, :initialize
-  #         def initialize(name, config = {})
-  #           @my_custom_config = config[:my_custom_config]
-  #           original_initialize(name, config)
-  #         end
-  #       end
-  #     end
-  #   end
-  #
-  #   # 2. Implement plugin with serialize_config
-  #   class MyPlugin < SwarmSDK::Plugin
-  #     def name
-  #       :my_plugin
-  #     end
-  #
-  #     def tools
-  #       [:MyTool, :OtherTool]
-  #     end
-  #
-  #     def create_tool(tool_name, context)
-  #       # Create and return tool instance
-  #     end
-  #
-  #     # Preserve custom config when agents are cloned
-  #     def serialize_config(agent_definition:)
-  #       return {} unless agent_definition.my_custom_config
-  #
-  #       { my_custom_config: agent_definition.my_custom_config }
-  #     end
-  #   end
-  #
-  #   SwarmSDK::PluginRegistry.register(MyPlugin.new)
-  #
-  # Now agents can use your custom config:
-  #
-  #   agent :researcher do
-  #     my_custom_config { option: "value" }
-  #   end
-  #
-  # And it will be preserved when Workflow clones the agent!
-  #
-  # @example Real-world: SwarmMemory plugin
-  #   # SwarmMemory adds 'memory' attribute to agents
-  #   class SDKPlugin < SwarmSDK::Plugin
-  #     def serialize_config(agent_definition:)
-  #       return {} unless agent_definition.memory
-  #       { memory: agent_definition.memory }
-  #     end
-  #   end
-  #
-  class Plugin
-    # Plugin name (must be unique)
-    #
-    # @return [Symbol] Plugin identifier
-    def name
-      raise NotImplementedError, "#{self.class} must implement #name"
-    end
-
-    # List of tools provided by this plugin
-    #
-    # @return [Array<Symbol>] Tool names (e.g., [:MemoryWrite, :MemoryRead])
-    def tools
-      []
-    end
-
-    # Create a tool instance
-    #
-    # @param tool_name [Symbol] Tool name (e.g., :MemoryWrite)
-    # @param context [Hash] Creation context
-    #   - :agent_name [Symbol] Agent identifier
-    #   - :storage [Object] Plugin storage instance (if created)
-    #   - :agent_definition [Agent::Definition] Full agent definition
-    #   - :chat [Agent::Chat] Chat instance (for tools that need it)
-    #   - :tool_configurator [Swarm::ToolConfigurator] For tools that register other tools
-    # @return [RubyLLM::Tool] Tool instance
-    def create_tool(tool_name, context)
-      raise NotImplementedError, "#{self.class} must implement #create_tool"
-    end
-
-    # Create plugin storage for an agent (optional)
-    #
-    # Called during agent initialization. Return nil if plugin doesn't need storage.
-    #
-    # @param agent_name [Symbol] Agent identifier
-    # @param config [Object] Plugin configuration from agent definition
-    # @return [Object, nil] Storage instance or nil
-    def create_storage(agent_name:, config:)
-      nil
-    end
-
-    # Parse plugin configuration from agent definition
-    #
-    # @param raw_config [Object] Raw config (DSL object or Hash from YAML)
-    # @return [Object] Parsed configuration
-    def parse_config(raw_config)
-      raw_config
-    end
-
-    # Contribute to agent system prompt (optional)
-    #
-    # @param agent_definition [Agent::Definition] Agent definition
-    # @param storage [Object, nil] Plugin storage instance (if created)
-    # @return [String, nil] Prompt contribution or nil
-    def system_prompt_contribution(agent_definition:, storage:)
-      nil
-    end
-
-    # Tools that should be marked immutable (optional)
-    #
-    # Immutable tools cannot be removed by other tools (e.g., LoadSkill).
-    #
-    # @return [Array<Symbol>] Tool names
-    def immutable_tools
-      []
-    end
-
-    # Agent storage enabled for this agent? (optional)
-    #
-    # @param agent_definition [Agent::Definition] Agent definition
-    # @return [Boolean] True if storage should be created
-    def storage_enabled?(agent_definition)
-      false
-    end
-
-    # Lifecycle: Called when agent is initialized
-    #
-    # @param agent_name [Symbol] Agent identifier
-    # @param agent [Agent::Chat] Chat instance
-    # @param context [Hash] Initialization context
-    #   - :storage [Object, nil] Plugin storage
-    #   - :agent_definition [Agent::Definition] Definition
-    #   - :tool_configurator [Swarm::ToolConfigurator] Configurator
-    def on_agent_initialized(agent_name:, agent:, context:)
-      # Override if needed
-    end
-
-    # Lifecycle: Called when swarm starts
-    #
-    # @param swarm [Swarm] Swarm instance
-    def on_swarm_started(swarm:)
-      # Override if needed
-    end
-
-    # Lifecycle: Called when swarm stops
-    #
-    # @param swarm [Swarm] Swarm instance
-    def on_swarm_stopped(swarm:)
-      # Override if needed
-    end
-
-    # Lifecycle: Called on every user message
-    #
-    # Plugins can return system reminders to inject based on the user's prompt.
-    # This enables features like semantic skill discovery, context injection, etc.
-    #
-    # @param agent_name [Symbol] Agent identifier
-    # @param prompt [String] The user's message
-    # @param is_first_message [Boolean] True if this is the first message in the conversation
-    # @return [Array<String>] System reminders to inject (empty array if none)
-    #
-    # @example Semantic skill discovery
-    #   def on_user_message(agent_name:, prompt:, is_first_message:)
-    #     skills = semantic_search(prompt, threshold: 0.65)
-    #     return [] if skills.empty?
-    #
-    #     [build_skill_reminder(skills)]
-    #   end
-    def on_user_message(agent_name:, prompt:, is_first_message:)
-      []
-    end
-
-    # Contribute to agent serialization (optional)
-    #
-    # Called when Agent::Definition.to_h is invoked (e.g., for cloning agents
-    # in Workflow). Plugins can return config keys that should be
-    # included in the serialized hash to preserve their state.
-    #
-    # This allows plugins to maintain their configuration when agents are
-    # cloned or serialized, without SwarmSDK needing to know about plugin-specific fields.
-    #
-    # @param agent_definition [Agent::Definition] Agent definition
-    # @return [Hash] Config keys to include in to_h (e.g., { memory: config })
-    #
-    # @example Memory plugin serialization
-    #   def serialize_config(agent_definition:)
-    #     return {} unless agent_definition.memory
-    #
-    #     { memory: agent_definition.memory }
-    #   end
-    def serialize_config(agent_definition:)
-      {}
-    end
-
-    # Snapshot plugin-specific state for an agent
-    #
-    # Called during state snapshot creation (e.g., session persistence).
-    # Return any state your plugin needs to persist for this agent.
-    # The returned hash will be JSON serialized.
-    #
-    # @param agent_name [Symbol] Agent identifier
-    # @return [Hash] Plugin-specific state (empty hash if nothing to snapshot)
-    #
-    # @example Memory read tracking
-    #   def snapshot_agent_state(agent_name)
-    #     entries = StorageReadTracker.get_read_entries(agent_name)
-    #     return {} if entries.empty?
-    #
-    #     { read_entries: entries }
-    #   end
-    def snapshot_agent_state(agent_name)
-      {}
-    end
-
-    # Restore plugin-specific state for an agent
-    #
-    # Called during state restoration. Restore any persisted state.
-    # This method is idempotent - calling it multiple times with
-    # the same state should produce the same result.
-    #
-    # @param agent_name [Symbol] Agent identifier
-    # @param state [Hash] Previously snapshotted state (with symbol keys)
-    # @return [void]
-    #
-    # @example Memory read tracking
-    #   def restore_agent_state(agent_name, state)
-    #     entries = state[:read_entries] || state["read_entries"]
-    #     return unless entries
-    #
-    #     StorageReadTracker.restore_read_entries(agent_name, entries)
-    #   end
-    def restore_agent_state(agent_name, state)
-      # Override if needed
-    end
-
-    # Get digest for a tool result (e.g., file hash, memory entry hash)
-    #
-    # Called during tool result metadata collection. Returns a digest
-    # that can be used to detect if the resource has changed since
-    # it was last read. This enables change detection hooks.
-    #
-    # @param agent_name [Symbol] Agent identifier
-    # @param tool_name [String] Name of the tool (e.g., "MemoryRead")
-    # @param path [String] Path or identifier of the resource
-    # @return [String, nil] Digest string or nil if not tracked by this plugin
-    #
-    # @example Memory read tracking
-    #   def get_tool_result_digest(agent_name:, tool_name:, path:)
-    #     return unless tool_name == "MemoryRead"
-    #
-    #     StorageReadTracker.get_read_entries(agent_name)[path]
-    #   end
-    def get_tool_result_digest(agent_name:, tool_name:, path:)
-      nil
-    end
-
-    # Translate YAML configuration into DSL calls
-    #
-    # Called during YAML-to-DSL translation. Plugins can translate their
-    # specific YAML configuration keys into DSL method calls on the builder.
-    # This allows SDK to remain plugin-agnostic while plugins can add
-    # YAML configuration support.
-    #
-    # @param builder [Agent::Builder] Builder instance (self in DSL context)
-    # @param agent_config [Hash] Full agent config from YAML
-    # @return [void]
-    #
-    # @example Memory plugin YAML translation
-    #   def translate_yaml_config(builder, agent_config)
-    #     memory_config = agent_config[:memory]
-    #     return unless memory_config
-    #
-    #     builder.instance_eval do
-    #       memory do
-    #         directory(memory_config[:directory])
-    #         adapter(memory_config[:adapter]) if memory_config[:adapter]
-    #         mode(memory_config[:mode]) if memory_config[:mode]
-    #       end
-    #     end
-    #   end
-    def translate_yaml_config(builder, agent_config)
-      # Override if plugin needs YAML configuration support
-    end
-  end
-end

data/lib/swarm_sdk/plugin_registry.rb

@@ -1,101 +0,0 @@
-# frozen_string_literal: true
-
-module SwarmSDK
-  # Plugin registry for managing SwarmSDK extensions
-  #
-  # Plugins register themselves when loaded, providing tools, storage,
-  # and lifecycle hooks without SwarmSDK needing to know about them.
-  module PluginRegistry
-    @plugins = {}
-    @tool_map = {}
-
-    class << self
-      # Register a plugin
-      #
-      # @param plugin [Plugin] Plugin instance
-      # @raise [ArgumentError] If plugin with same name already registered
-      def register(plugin)
-        raise ArgumentError, "Plugin must inherit from SwarmSDK::Plugin" unless plugin.is_a?(Plugin)
-
-        name = plugin.name
-        raise ArgumentError, "Plugin name required" unless name
-        raise ArgumentError, "Plugin #{name} already registered" if @plugins.key?(name)
-
-        @plugins[name] = plugin
-
-        # Build tool → plugin mapping
-        plugin.tools.each do |tool_name|
-          if @tool_map.key?(tool_name)
-            raise ArgumentError, "Tool #{tool_name} already registered by #{@tool_map[tool_name].name}"
-          end
-
-          @tool_map[tool_name] = plugin
-        end
-      end
-
-      # Get plugin by name
-      #
-      # @param name [Symbol] Plugin name
-      # @return [Plugin, nil] Plugin instance or nil
-      def get(name)
-        @plugins[name]
-      end
-
-      # Get all registered plugins
-      #
-      # @return [Array<Plugin>] All plugins
-      def all
-        @plugins.values
-      end
-
-      # Check if plugin is registered
-      #
-      # @param name [Symbol] Plugin name
-      # @return [Boolean] True if registered
-      def registered?(name)
-        @plugins.key?(name)
-      end
-
-      # Get plugin that provides a tool
-      #
-      # @param tool_name [Symbol] Tool name
-      # @return [Plugin, nil] Plugin that provides tool or nil
-      def plugin_for_tool(tool_name)
-        @tool_map[tool_name]
-      end
-
-      # Check if tool is provided by a plugin
-      #
-      # @param tool_name [Symbol] Tool name
-      # @return [Boolean] True if tool is plugin-provided
-      def plugin_tool?(tool_name)
-        @tool_map.key?(tool_name)
-      end
-
-      # Get all tools provided by plugins
-      #
-      # @return [Hash<Symbol, Plugin>] Tool name → Plugin mapping
-      def tools
-        @tool_map.dup
-      end
-
-      # Clear all plugins (for testing)
-      #
-      # @return [void]
-      def clear
-        @plugins.clear
-        @tool_map.clear
-      end
-
-      # Emit lifecycle event to all plugins
-      #
-      # @param event [Symbol] Event name
-      # @param args [Hash] Event arguments
-      def emit_event(event, **args)
-        @plugins.each_value do |plugin|
-          plugin.public_send(event, **args) if plugin.respond_to?(event)
-        end
-      end
-    end
-  end
-end

data/lib/swarm_sdk/proc_helpers.rb

@@ -1,53 +0,0 @@
-# frozen_string_literal: true
-
-module SwarmSDK
-  # Helper methods for working with Procs and Lambdas
-  #
-  # Provides functionality to convert regular Proc objects into Lambdas to enable
-  # safe use of return statements in DSL blocks (like input/output transformers).
-  module ProcHelpers
-    class << self
-      # Convert a Proc to a Lambda
-      #
-      # The fundamental difference between a Proc and a Lambda is in how they handle
-      # return statements. In a Proc, return exits the enclosing method (or program),
-      # while in a Lambda, return only exits the lambda itself.
-      #
-      # This method converts a Proc to a Lambda by:
-      # 1. Converting the proc to an unbound method via define_method
-      # 2. Wrapping it in a lambda that binds and calls the method
-      # 3. In the method, return exits the method (not the original scope)
-      #
-      # This allows users to write natural control flow with return statements:
-      #
-      # @example
-      #   my_proc = proc { |x| return x * 2 if x > 0; 0 }
-      #   my_lambda = ProcHelpers.to_lambda(my_proc)
-      #   my_lambda.call(5)  # => 10 (return works safely!)
-      #
-      # @param proc [Proc] The proc to convert
-      # @return [Proc] A lambda with the same behavior but safe return semantics
-      def to_lambda(proc)
-        return proc if proc.lambda?
-
-        # Save local reference to proc so we can use it in module_exec/lambda scopes
-        source_proc = proc
-
-        # Convert proc to unbound method
-        # define_method with a block converts the block to a method, where return
-        # exits the method (not the original scope)
-        unbound_method = Module.new.module_exec do
-          instance_method(define_method(:_proc_call, &source_proc))
-        end
-
-        # Return lambda which binds our unbound method to correct receiver and calls it
-        lambda do |*args, **kwargs, &block|
-          # Bind method to the original proc's receiver (the context where it was defined)
-          # This preserves access to instance variables, local variables via closure, etc.
-          receiver = source_proc.binding.eval("self")
-          unbound_method.bind(receiver).call(*args, **kwargs, &block)
-        end
-      end
-    end
-  end
-end

data/lib/swarm_sdk/prompts/base_system_prompt.md.erb

@@ -1,117 +0,0 @@
-You are an AI agent designed to help users with their tasks. Use the instructions below and the tools available to you to assist the user.
-
-IMPORTANT: Assist with defensive security tasks only. Refuse to create, modify, or improve code that may be used maliciously. Allow security analysis, detection rules, vulnerability explanations, defensive tools, and security documentation.
-IMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are appropriate for the task at hand. You may use URLs provided by the user in their messages or local files.
-
-# Tone and style
-
-You should be concise, direct, and to the point.
-You MUST answer concisely with fewer than 4 lines (not including tool use or code generation), unless user asks for detail.
-IMPORTANT: You should minimize output tokens as much as possible while maintaining helpfulness, quality, and accuracy. Only address the specific query or task at hand, avoiding tangential information unless absolutely critical for completing the request. If you can answer in 1-3 sentences or a short paragraph, please do.
-IMPORTANT: You should NOT answer with unnecessary preamble or postamble (such as explaining your actions or summarizing what you did), unless the user asks you to.
-Do not add additional explanation or summary unless requested by the user. After working on a task, just stop, rather than providing an explanation of what you did.
-Answer the user's question directly, without elaboration, explanation, or details. Brief answers are best. Avoid introductions, conclusions, and explanations. You MUST avoid text before/after your response, such as "The answer is <answer>.", "Here is the content..." or "Based on the information provided, the answer is..." or "Here is what I will do next...". Here are some examples to demonstrate appropriate verbosity:
-<example>
-user: 2 + 2
-assistant: 4
-</example>
-
-<example>
-user: what is 2+2?
-assistant: 4
-</example>
-
-<example>
-user: is 11 a prime number?
-assistant: Yes
-</example>
-
-<example>
-user: what command should I run to list files in the current directory?
-assistant: ls
-</example>
-
-<example>
-user: How many golf balls fit inside a jetta?
-assistant: 150000
-</example>
-
-<example>
-user: what files are in the directory src/?
-assistant: [reads directory and sees foo.c, bar.c, baz.c]
-user: which file contains the implementation of foo?
-assistant: src/foo.c
-</example>
-When you run a non-trivial bash command, you should explain what the command does and why you are running it, to make sure the user understands what you are doing (this is especially important when you are running a command that will make changes to the user's system).
-Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like Bash or comments as means to communicate with the user during the session.
-If you cannot or will not help the user with something, please do not say why or what it could lead to, since this comes across as preachy and annoying. Please offer helpful alternatives if possible, and otherwise keep your response to 1-2 sentences.
-Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.
-IMPORTANT: Keep your responses short and focused.
-
-# Proactiveness
-
-You are allowed to be proactive, but only when the user asks you to do something. You should strive to strike a balance between:
-
-- Doing the right thing when asked, including taking actions and follow-up actions
-- Not surprising the user with actions you take without asking
-For example, if the user asks you how to approach something, you should do your best to answer their question first, and not immediately jump into taking actions.
-
-# Professional objectivity
-
-Prioritize technical accuracy and truthfulness over validating the user's beliefs. Focus on facts and problem-solving, providing direct, objective technical info without any unnecessary superlatives, praise, or emotional validation. It is best for the user if you honestly applies the same rigorous standards to all ideas and disagrees when necessary, even if it may not be what the user wants to hear. Objective guidance and respectful correction are more valuable than false agreement. Whenever there is uncertainty, it's best to investigate to find the truth first rather than instinctively confirming the user's beliefs.
-
-# Following conventions
-
-When making changes to files, first understand the file's conventions. Mimic existing style, use existing libraries and utilities, and follow existing patterns.
-
-- NEVER assume that a given library is available, even if it is well known. Whenever you reference a library or framework, first check that this project already uses the given library. For example, you might look at neighboring files, or check configuration files like package.json, requirements.txt, Cargo.toml, Gemfile, and so on depending on the context.
-- When you create something new, first look at existing examples to see how they're written; then consider naming conventions and other patterns.
-- When you edit something, first look at the surrounding context (especially imports/requires) to understand the choice of frameworks and libraries. Then consider how to make the given change in a way that is most consistent with existing patterns.
-- Always follow security best practices. Never introduce code that exposes or logs secrets and keys. Never commit secrets or keys to repositories.
-
-# Doing tasks
-
-The user will primarily request you perform tasks. This includes solving problems, adding new functionality, refactoring, explaining content, and more. For these tasks the following steps are recommended:
-
-- Use the available search tools to understand the context and the user's query. You are encouraged to use the search tools extensively both in parallel and sequentially.
-- Implement the solution using all tools available to you
-- Verify the solution if possible with tests. NEVER assume specific test framework or test script. Check the project documentation or search to determine the testing approach.
-- When you have completed a task, if there are linting or validation commands available to you, run them to ensure your work is correct. NEVER assume what these commands are - check the project documentation first.
-NEVER commit changes unless the user explicitly asks you to. It is VERY IMPORTANT to only commit when explicitly asked, otherwise the user will feel that you are being too proactive.
-
-# Tool usage policy
-
-- When doing file search, prefer to use the Grep and Glob tools efficiently to reduce resource usage.
-- You should proactively use specialized tools when the task at hand matches their purpose.
-- You can call multiple tools in a single response. If you intend to call multiple tools and there are no dependencies between them, make all independent tool calls in parallel. Maximize use of parallel tool calls where possible to increase efficiency. However, if some tool calls depend on previous calls to inform dependent values, do NOT call these tools in parallel and instead call them sequentially. For instance, if one operation must complete before another starts, run these operations sequentially instead. Never use placeholders or guess missing parameters in tool calls.
-- If the user specifies that they want you to run tools "in parallel", you MUST send a single message with multiple tool use content blocks. For example, if you need to delegate a task to multiple agents in parallel, send a single message with multiple DelegateTask tool calls.
-- Use specialized tools instead of bash commands when possible, as this provides a better user experience. For file operations, use dedicated tools: Read for reading files instead of cat/head/tail, Edit/MultiEdit for editing instead of sed/awk, and Write for creating files instead of cat with heredoc or echo redirection. Reserve bash tools exclusively for actual system commands and terminal operations that require shell execution. NEVER use bash echo or other command-line tools to communicate thoughts, explanations, or instructions to the user. Output all communication directly in your response text instead.
-
-You MUST answer concisely with fewer than 4 lines of text (not including tool use or code generation), unless user asks for detail.
-
-
-# Today's date
-
-<today-date>
-#{date}
-#</today-date>
-
-# Environment information
-
-Here is useful information about the environment you are running in:
-<env>
-Working directory: <%= cwd %>
-Platform: <%= platform %>
-OS Version: <%= os_version %>
-</env>
-
-IMPORTANT: Assist with defensive security tasks only. Refuse to create, modify, or improve code that may be used maliciously. Allow security analysis, detection rules, vulnerability explanations, defensive tools, and security documentation.
-
-# Code References
-
-When referencing specific functions or pieces of code include the pattern `file_path:line_number` to allow the user to easily navigate to the source location.
-
-<example>
-user: Where are errors handled?
-assistant: Errors are handled in the `processRequest` function in src/services/handler.ts:245.
-</example>

data/lib/swarm_sdk/restore_result.rb

@@ -1,65 +0,0 @@
-# frozen_string_literal: true
-
-module SwarmSDK
-  # Result object returned from snapshot restore operations
-  #
-  # Provides information about the restore process, including any warnings
-  # about agents or delegations that couldn't be restored due to configuration
-  # mismatches.
-  #
-  # @example Successful restore
-  #   result = swarm.restore(snapshot_data)
-  #   if result.success?
-  #     puts "All agents restored successfully"
-  #   end
-  #
-  # @example Partial restore with warnings
-  #   result = swarm.restore(snapshot_data)
-  #   if result.partial_restore?
-  #     puts result.summary
-  #     result.warnings.each do |warning|
-  #       puts "  - #{warning[:message]}"
-  #     end
-  #   end
-  class RestoreResult
-    attr_reader :warnings, :skipped_agents, :skipped_delegations
-
-    # Initialize restore result
-    #
-    # @param warnings [Array<Hash>] Warning messages with details
-    # @param skipped_agents [Array<Symbol>] Names of agents that couldn't be restored
-    # @param skipped_delegations [Array<String>] Names of delegation instances that couldn't be restored
-    def initialize(warnings:, skipped_agents:, skipped_delegations:)
-      @warnings = warnings
-      @skipped_agents = skipped_agents
-      @skipped_delegations = skipped_delegations
-    end
-
-    # Check if restore was completely successful
-    #
-    # @return [Boolean] true if all agents restored without warnings
-    def success?
-      warnings.empty?
-    end
-
-    # Check if restore was partial (some agents skipped)
-    #
-    # @return [Boolean] true if some agents were skipped
-    def partial_restore?
-      !warnings.empty?
-    end
-
-    # Get human-readable summary of restore result
-    #
-    # @return [String] Summary message
-    def summary
-      if success?
-        "Snapshot restored successfully. All agents restored."
-      else
-        "Snapshot restored with warnings. " \
-          "#{skipped_agents.size} agents skipped, " \
-          "#{skipped_delegations.size} delegation instances skipped."
-      end
-    end
-  end
-end