CLI Companion Import

`ed companion import`

Restores a bundle written by ed companion export: episodes, observations, conversations, beliefs, claims, facts, core memory, the non-secret reasoner settings, and any media files sitting next to the bundle.

Usage:

ed companion import <path> [--json] [--endpoint <url>]

Name	Type / values	Default	What it does
`<path>`	file or directory	required	The `bundle.json`, or the export directory holding it.
`--json`	flag	off	Emit JSON on stdout.
`--endpoint`	URL	resolution order	Companion API base URL.

Examples:

ed companion import ~/backups/companion
ed companion import ~/backups/companion/bundle.json --json

--json reports inserted and skipped rows plus media restoration: {episodesInserted,episodesSkipped,observationsInserted,conversationsInserted, messagesInserted,beliefsInserted,claimsInserted,factsInserted, coreSectionsInserted,settingsInserted,mediaRestored,mediaFailed, pendingEpisodes}.

Importing merges rather than replaces: every record keeps the id it was exported with, records that already exist are skipped, and nothing is deleted, so running the same import twice changes nothing the second time. Settings are only filled in where the companion has none, so a configured reasoner is never clobbered by a restore. A media/ directory beside the bundle is restored file by file after the rows land. Episodes arrive unembedded and the companion starts indexing them in the background; the command reports how many are queued. A file that is not a companion export, or one written by a newer companion, is refused before anything is touched.

The backend also rejects malformed source hashes and source URIs that are absolute or escape the vault. Media filenames that do not match <64-character-sha256>-<basename> are ignored by the CLI. Each accepted media file is validated again by the backend before it is written. Individual media restore failures do not roll back imported rows and do not fail the command; their basenames are returned in mediaFailed and noted on stderr.

Import is not a replacement or a wipe. Back up the destination first if you need a rollback point for the merged state.