zeromind.installAsset

Pull an asset and its full transitive closure from another world into the working copy, materializing each piece as content you own. The root asset lands at a chosen destination (or a default under the source path), tree children go inside their parent's placement, and dependencies land in a per-source-world deps area so references stay intact. The pull refuses rather than land a broken, partially-resolved closure.

Installing is how a find is tried: once it is in, run it on the job, and change and finish it where it falls short. zm ls-tree @<guid>, zm grep <pattern> @<guid> and zm show @<guid>:<path> read a published asset's files in the shell, and zeromind.preview shows what an install would write.

version installs the asset as a branch, a tag or a commit id of the world it is published from holds it, in place of the version that world ships. A package pushed to a branch (zm checkout -b <branch> && zm push) installs into a fresh world from that branch before it is published, which is how to check that it installs whole. A ref that world does not resolve, or whose commit holds no version of the asset, refuses the install and names the ref.

Pulled content ships in your own commits and can be freely modified and diverged from the source; edits to it produce a world-local override version while preserving the link to the upstream original, and zm pr create <install root> sends them back to it so everyone who uses it gets them. Blob bytes are fetched lazily. After pulling, stage and commit to keep the imported content.