class Capsium::Package::Bundle

Bundled dependencies of an encapsulated (self-contained) package (ARCHITECTURE.md section 4a extension): dependency .cap files embedded under packages/ with a packages/index.json manifest mapping each dependency GUID to its file, version and SHA-256:

packages/
  index.json                # guid => {"file", "version", "sha256"}
  <name>-<version>.cap      # one per declared dependency

One-level bundling policy: only the dependencies DECLARED in the package’s own metadata.dependencies are bundled; to make a whole tree self-contained the parent must declare the transitive closure. At load time bundled dependencies resolve FIRST, before the store -> registry chain, and a package’s bundle is passed down to its dependencies so their re-declared dependencies resolve from it too (recursive-capable).

Security: bundled .cap files are covered by the parent package’s security.json checksums like every other file; the manifest SHA-256 is re-verified when a bundled dependency is resolved, and each bundled package’s own security.json is verified when it is loaded (the usual Capsium::Package activation checks).