Expand description
Component plumbing shared by the per-agent export and import paths: purging dangling component refs, resolving a bundle’s components to their backing rows, and splicing history/instructions/memory into a manifest.
Structs§
- Resolved
Components 🔒 - A bundle’s components, resolved from the tables that are authoritative for them.
Constants§
- MEMORY_
NOT_ 🔒EXPORTED_ WARNING - Warning the agent-less
bundle.exportpushes when the bundle it is exporting is bound to an agent that actually has native memory.
Functions§
- bind_
imported_ 🔒components - Bind an imported bundle’s skills into the ref table.
- bound_
agent_ 🔒has_ native_ memory - Does any agent bound to
bundle_idhave mirrored native memory? - mcp_
servers_ 🔒not_ imported_ warning - The warning an import gives for the MCP servers an archive carries. A
bundle carries no MCP servers, so none is imported; they’re named so the
user can add them in Connectors
(
SPEC_BUNDLE_CONTENTS_MEMORY_NOT_MCP_2026_10_07.md§3.1).Nonewhen the archive has none. - purge_
bundle_ 🔒component_ refs - Drop a deleted bundle’s component refs.
- resolve_
bundle_ 🔒components - Resolve what a bundle actually contains, from
db_bundle_skills_ref. - set_
manifest_ 🔒component - Register
entriesundercomponents.<key>in the export’s manifest (bundle.json). - splice_
history_ 🔒component - Register the transcript files
bundle.export_for_agent_with_historyalready wrote into the archive undercomponents.history. - splice_
memory_ 🔒component - splice_
project_ 🔒instructions_ component - Splice native-memory files into an already-built bundle export’s
bundle.jsonmanifest and files list, addingcomponents.memory(ABF v0.2 §2.3). Kept OUTSIDEbundle_export.rsdeliberately — that module’sexport_bundle()is scoped to a bundle’s own components (instructions/skills/MCP/accounts) with no concept of “agent” or native memory at all; memory is agent-scoped, not bundle-scoped, so splicing it in here (the RPC-handler layer, which already resolves other agent-scoped data like skill rows) keeps that module’s documented scope intact rather than growing it a fifth, unrelated component category. A no-op whenmemory_filesis empty — matches the existing omit-empty-components convention used elsewhere in the manifest. Carry the agent’s project instructions into the export ascomponents.projectInstructions.