List and download a profile's LSI, from the library and the CLI

[sadit]

Each profile in profiles-1.1 has its LSI beside it as <nickname>-lsi.zip, but list_remote_profiles hides them on purpose (#51), so the only way to get one was to build the URL by hand. This adds the missing path, in the library first and the CLI on top of it.

Library

• list_remote_lsi(; repo, tag, url): the release's LSIs, in the same shape as list_remote_profiles. name is the nickname of the profile each one belongs to ("es" for es-lsi.zip).
• download_lsi(nick; repo, tag, dest, url, force): downloads <nick>-lsi.zip into ~/.textsearch/lsi/<nick>.zip, apart from profiles/ because it is not a profile. It checks nothing itself; load_lsi is still the one that refuses a wrong profile.
• lsi_summary(path): (profile_id, name, repo, tag, outdim, maxoutdim, scaling) read from the manifest, without loading the projection. That makes the binding check cheap (a manifest read against dequantizing up to 300 MB).
• Listing and downloading share a single implementation for profiles and LSIs, and file:// counts as a direct URL, as the app already treated it.

p = load_profile(download_profile("es"))
lsi = load_lsi(download_lsi("es"), p; outdim=64)

CLI

LSIs are listed beside the profiles, in their own section, and every management command handles them:

$ textsearch list --remote
Remote profiles (sadit/TextSearch.jl @ profiles-1.1):
  en (50.5 MB) -> …/en.zip
  …
Remote LSI projections (sadit/TextSearch.jl @ profiles-1.1):
  en (297.1 MB) -> …/en-lsi.zip
  …

command	what it does with the LSI
list / list --remote	two sections, profiles and LSI; --profiles / --lsi narrow it. Locally it flags an LSI not bound to its profile, or whose profile isn't installed
download es --lsi	profile + LSI; keeps an already-installed profile. Checks the profile_id: if the LSI names another profile, it removes it and says so
install ./es-lsi.zip	recognizes an LSI by its manifest and installs it into lsi/ as es. Refuses it if the installed es isn't the profile it was fitted against; with no profile it's accepted and list shows it as waiting. Replacing a profile the installed LSI no longer matches prints a note
info es	new line: lsi: installed, outdim=256 -> …, or bound to another / not installed
info es --lsi, or info <path to an LSI>	the LSI itself: profile it names (id, repo @ tag), whether it's installed and bound, outdim, scaling
uninstall es [--force]	removes the profile and its LSI (one without its profile can't be loaded); --lsi removes only the LSI

Why the refusals: an LSI against the wrong profile doesn't fail, it answers wrongly, so it can't be left installed where a consumer would load it.

Verified

• Against the real release (TEXTSEARCH_HOME sandboxed): list --remote shows the 7 profiles and the 7 LSIs in separate sections. download eu, install eu-lsi.zip, list, info eu --lsi, info <path>, uninstall eu --lsi [--force], download eu --lsi and uninstall eu --force behave as described.
• App: 279/279 tests pass. The new ones need no network: a local release over file://, with an LSI bound to another profile. They cover the list sections, download --lsi, install (bound, refused, waiting for its profile), info --lsi / on a path, and uninstall with and without --lsi.
• Library: the full suite passes, Aqua included. New tests: lsi_summary (directory and zip), download_lsi (lsi/ destination, force), and list_remote_lsi on the mock.
• Tutorial and app README updated.

🤖 Generated with Claude Code