Scene Manager: Load Publish and numbered instances

Load Publish (Loaded panel) searches every asset of the project, then
loads any of its published .blend files at any version, cast in the shot
or not. The file the casting would load and the latest version on this
site are preselected; a version not on this site is requested instead.
Built on the existing wtd_list_assets / wtd_get_asset_files /
wtd_get_revisions commands.

New instances are numbered (COL_bob_01, tree_01...), counting on from the
highest number in the file (SCENE_MANAGER_INSTANCE_NAME).

README: Pick Shot only lists shots that exist in Libreflow.

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

CLAUDE.md

@@ -42,7 +42,7 @@ that contains this repo on `sys.path` and importing the repo folder name (see
   1. `blender -b --factory-startup --python dev/make_test_assets.py -- <workdir>`
   2. `python dev/fake_libreflow.py <workdir>` (keep running; restart for a clean state)
   3. `blender -b --factory-startup --python-exit-code 1 --python dev/test_scene_manager.py -- <workdir>`
-     (60 checks, "All checks passed"). `/_test/publish` and `/_test/download` simulate a new
+     (71 checks, "All checks passed"). `/_test/publish` and `/_test/download` simulate a new
      publish and a requested revision reaching this site.
   The fake server follows the real `wtdcmds` replies; check them against the real
   Libreflow when one is available.
@@ -96,6 +96,14 @@ that contains this repo on `sys.path` and importing the repo folder name (see
   `Requested`). Not tested: an actual assetize publish (it writes to production).
   New wtdcmds commands need every Libreflow session restarted (a running one keeps the
   old code and answers 404).
+- Load Publish (2026-10-28) uses only existing commands (`wtd_list_assets`,
+  `wtd_get_asset_files`, `wtd_get_revisions`): 309 assets in ~0.1 s, live-tested on
+  `car_paul` (loaded twice: `car_paul_01`, `car_paul_02`).
+- `/melvile/films/melvile` has no sequences or shots in Libreflow yet; `melvile_test` has 9.
+- Deployed Libreflow (Overseer launcher): wtdcmds must be an "extension" entry, so the
+  launcher adds `libreflow.extensions.wtdcmds:install_extensions` to
+  `KABARET_FLOW_EXT_INSTALLERS`; the package name must stay `libreflow.extensions.wtdcmds`.
+  The launcher only rebuilds its env when the project config changes: "Force update".
 
 ## Open points