Task: SitePack Importerlink

Goallink

Import data from an unpacked SitePack package into the target system.

Inputlink

Path to the unpacked package (directory).

Requirementslink

• Read sitepack.manifest.json and sitepack.catalog.json.
• Determine profile(s) from manifest.profiles.
• Process artifacts from the catalog:
  • For known mediaType, perform import.
  • Unknown mediaType MUST be skipped and logged.
• Unknown entity.type MUST NOT crash; MAY import as opaque.
• Respect applyPolicy for config (e.g., never is not auto-applied).
• If a Transform Plan exists and is supported, MAY apply steps in order.
• Enforce path safety (no traversal, no absolute, no null bytes).
• If a sitepack.volumes.json descriptor is provided, validate it, verify each volume sha256/size, and assemble volumes into a temporary directory before importing.
• If a volume entry uses encryption.scheme = "age", the importer MUST use the referenced envelope header to locate the encrypted payload and decrypt before assembly (or fail with a clear error if unsupported).

Chunked assetslink

• Asset index entries may be single-blob (path) or chunked (chunks[]).
• For chunked assets, reconstruct the asset by concatenating chunks in ascending index order.
• Importers MUST validate each chunk sha256/size and the overall asset sha256/size.

Relationslink

• Importers SHOULD use a two-pass strategy:
  1. create entities (or placeholders) and build a mapping sitepackEntityId -> targetSystemId,
  2. resolve and apply relations using the mapping.
• If a Link cannot be resolved, it MUST be recorded as a warning and MUST NOT be fatal.

Outputlink

Create reports/import.json with at least this structure:

{
  "packageId": "...",
  "profiles": ["..."],
  "imported": {
    "entities": 0,
    "assets": 0,
    "config": 0,
    "recordsets": 0
  },
  "skipped": {
    "unknownMediaTypes": 0,
    "unknownEntityTypes": 0
  },
  "warnings": [],
  "errors": []
}