Asobu 0.1.5

Share an instance as a file or as a code

Sharing now asks which, in the same two doors as the new-instance and sign-in
sheets. The left one saves the zip that already existed, which any launcher can
open. The right one asks Asobu for an eight character code that lasts a week.

A code is a list of files identified by hash and by nothing else. Importing one
resolves each hash at Modrinth, then asks CurseForge by fingerprint about
whatever is left, and downloads from there. The manifest contains no addresses,
so a code cannot make somebody else's launcher fetch a file of the sharer's
choosing; the worst it can name is something that does not exist, which is
reported rather than skipped.

Only mods, resource packs, shaders and data packs travel. Worlds and config stay
put: a world is not the recipient's to receive, and config is where people keep
server addresses and passwords.

Paths are checked again here even though the server checked them when the code
was made. The two are not the same trust, and this is the side that creates
files. A path that escapes the instance is the difference between a shared pack
and a way to write anywhere on a stranger's disk.

Verified against the live API end to end: a code comes back and lasts seven
days, asking again returns the same code with its week wound forward, a renamed
copy shares as the original, adding one mod produces a different code, and
withdrawing one takes it away. Separately, seventeen checks that config and
saves never leave the machine and that eight hostile paths are refused.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>