zeromind.reviewUpdate

What updating one unit changes, before you apply it. Writes nothing.

The answer is the update, not the asset: from (the version this world holds) and to (the version the origin holds now), then commits, the commits of the origin world in between, newest first, each { id, message, author, date }, then the files.

• An installed asset (its root path, as zeromind.updates lists it): the commits that change the install, back to the one that moved it from the version you hold. files lists each file the update adds, changes or removes with its unified text diff (diff is nil for a binary file). local_edit says whether this world edited the file since it was installed: none, merges when the edit merges cleanly with the incoming change, conflicts when it does not.
• A library ("@builtin", "@combat", the @ optional): the pin move and its commits, with counts in summary: the library files that change, and the files of this world whose references move with the pin (moving). Those files read references moved in status and are committed with the library's marker. Pass { files = true } for the lists: each changed library file with its diff, and the moving paths.

modified lists up front each file you edited (its bytes differ from the version installed, or it is a file of your own) and have not committed that the update touches, { path, outcome, by? } (by names the session that wrote the change), with outcome merges when your edit and the incoming change merge cleanly and conflicts when the file would hold conflict markers. zeromind.update applies over them and names them again in its warnings.

more is true when the origin holds more commits in the range than the 200 listed; commits_error says why the list stops short when a version of the install could not be read. opts.ref reviews the update to another branch or commit of the origin.

Apply the update with zeromind.update(unit).