Module import_for_agent 

bundle.import_for_agent: apply an ABF to an existing agent definition, serialised per agent by bundle_import_for_agent_lock.

Structs

BundleImportForAgentResponse 🔒

Response for bundle.import_for_agent.

ImportForAgentReq 🔒

Functions

bundle_import_for_agent_impl 🔒

bundle.import_for_agent — ABF v0.2 §2.3. The only import path that processes a components.memory key; the generic bundle.import explicitly skips it (see parse_bundle_import_with_budget’s own components.memory guard). Unlike bundle.import/bundle.import.commit, this is a single-step import — no preview phase — since a memory-bearing import has its own unconditional safety net instead: the target agent must have ZERO existing db_agent_native_memory rows, or the whole import is rejected before any write happens. Simpler than skip/rename/replace conflict resolution, and sufficient for v0.2 (see the spec’s revision note for why merge semantics are an explicit follow-up, not designed here). Extracted from the RPC closure into a directly-callable, directly-testable function, matching bundle_import_preview_impl’s pattern.

register_bundle_import_for_agent 🔒

resolved_memory_paths 🔒

Every memory/* path listed under components.memory in a parsed import’s manifest (bundle.json, or armory.json before ABF v0.3) — mirrors how components.instructions/ components.skills are read elsewhere in this file, kept local to bundle.import_for_agent since no other handler needs it.