pixlstash 1.10.0.dev2__tar.gz → 1.10.0.dev4__tar.gz

{pixlstash-1.10.0.dev2/pixlstash.egg-info → pixlstash-1.10.0.dev4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pixlstash
-Version: 1.10.0.dev2
+Version: 1.10.0.dev4
 Summary: Self-hosted picture library with AI tagging, semantic search, and a clean web UI
 Author-email: Gaute Lindkvist <lindkvis@gmail.com>
 License-Expression: GPL-3.0-only AND MIT
@@ -31,6 +31,7 @@ Requires-Dist: pillow>=12.3.0
 Requires-Dist: opencv-python>=4.13.0.92
 Requires-Dist: scipy>=1.17.1
 Requires-Dist: platformdirs>=4.9.4
+Requires-Dist: send2trash>=2.1.0
 Requires-Dist: tomli>=2.4.0
 Requires-Dist: colorlog>=6.10.1
 Requires-Dist: python-multipart>=0.0.22
@@ -146,6 +147,8 @@ the app's own user-data directory.
 > | **Windows** | `%LOCALAPPDATA%\pixlstash\downloaded_models\` |
 >
 > An internet connection is required the first time the server starts. Subsequent starts use the cached models.
+>
+> **Moving them somewhere else:** open **Model folders** on the model shelf and use **Move** on PixlStash's own folder. Every file in it is copied, verified and removed from the old location, and the new location is remembered — so nothing is downloaded again. Set `PIXLSTASH_BUILTIN_MODEL_DIR` instead if you want the folder somewhere else without moving what is already in it (a mounted model volume, typically).
 
 If you need to use a custom config path:
 
@@ -182,6 +185,8 @@ pixlstash-cli libraries rename "Existing library" "Better name"
 pixlstash-cli libraries relocate "Existing library" /new/path
 pixlstash-cli libraries detach "Existing library"
 pixlstash-cli libraries backup "Existing library" /path/to/backups/
+pixlstash-cli libraries backup "Existing library" /path/to/backups/monday.tar.zst
+pixlstash-cli libraries restore /path/to/backups/monday.tar.zst /path/to/new-library
 ```
 
 | Command | What it does |
@@ -193,18 +198,33 @@ pixlstash-cli libraries backup "Existing library" /path/to/backups/
 | `relocate` | Points an existing registration at a new path, keeping its identity and share links. |
 | `detach` | Forgets a library. **No files are removed and nothing inside the folder changes.** |
 | `backup` | Writes the library and the hub to a single archive. |
+| `restore` | Unpacks an archive into a **new** folder and makes it the library that opens. |
 
 Notes worth knowing before you need them:
 
 - `detach` refuses the **active** library. Switch to another one first.
 - Reattaching the same folder revives its original registration, including its
   share links, because a library carries a fingerprint of its own identity.
+- A backup is a **zstd-compressed tar**, named `.tar.zst` — not `.tar.gz`.
+  `--no-compress` writes a plain `.tar` instead. Given a folder, `backup`
+  invents a dated name with the right ending; given a filename, it adds the
+  right ending if you left it off. `restore` recognises an archive by its
+  contents, so a renamed file still works.
 - A backup contains `hub.db`, and therefore your login and token secrets.
   PixlStash writes it owner-readable and refuses to overwrite an existing file.
 - A backup covers the library folder. Pictures kept in **reference folders** live
   outside it and are *not* included, so back those up separately.
 - Backing up finishes any outstanding one-time snapshot cleanup first, so the
   archive never carries credentials from before your upgrade.
+- `restore` needs PixlStash stopped, and names a folder that is empty or does
+  not exist yet — it never writes over a library. Because the archive holds the hub,
+  restoring also brings back the password and API tokens that library was
+  using, so your current ones are replaced.
+- **`restore` does not delete your current setup.** It *moves*
+  `server-config.json` and `hub.db` into a dated `pre-restore-*` folder beside
+  themselves and prints the launch command for each, so
+  `pixlstash-server --server-config <pre-restore-*>/server-config.json` reopens
+  what you had. Your old library folder is never touched.
 
 #### Which form to type
 
@@ -215,6 +235,13 @@ the environment PixlStash is installed into is active.
   `python -m pixlstash.cli libraries list`
 - **Docker Compose**, for a running service (paths are inside the container):
   `docker compose exec pixlstash pixlstash-cli libraries list`
+- **Desktop app** (AppImage, deb, .dmg, installer): the app is its own CLI, so
+  `/path/to/PixlStash.AppImage cli libraries list` works whether or not the app
+  is running. Turn on Settings › Backend › Desktop › **Shell command** to get a
+  `pixlstash` command in `~/.local/bin` and type `pixlstash libraries list`
+  instead. Either form targets the desktop app's own hub; there is no need to
+  pass `--hub`. Settings › Libraries always shows the exact command for your
+  install.
 - **A different hub** than the default: put global options *before* `libraries`,
   e.g. `pixlstash-cli --hub /path/to/hub.db libraries list`. Without `--hub` the
   CLI uses the standard config location, which is what you want almost always.
@@ -296,7 +323,7 @@ Edit the file and restart the server to apply changes.
 | `require_local_for_write` | `true` | When `true`, full login (username/password and ALL-scope tokens) is only permitted from local network addresses (RFC 1918 / loopback). READ-only share tokens are always accepted from any IP. Set to `false` to allow full login from any IP. |
 | `trusted_proxies` | `[]` | List of proxy IP addresses whose `X-Forwarded-For` header should be trusted for real-client-IP detection. See [Sharing and remote access](#sharing-and-remote-access) below. |
 
-At startup the server detects its own LAN IP and automatically allows it on any port. This means the Vite dev server works over LAN (`http://192.168.1.5:5173` → `http://192.168.1.5:9537`) without any extra configuration, as long as network access is enabled via `host`.
+At startup the server detects its own LAN IP and automatically allows it on any port. This means the Vite dev server works over LAN (`http://<lan-ip>:5173` → `http://<lan-ip>:9537`) without any extra configuration, as long as network access is enabled via `host`.
 
 Use `cors_origins` only if you need to allow origins on a different machine entirely.
 
@@ -511,15 +538,80 @@ Detailed installation instructions on <a href="http://pixlstash.dev/upgrade.html
 
 PixlStash supports built-in plugins and user-created plugins.
 
+### With the CLI (recommended)
+
+```bash
+pixlstash-cli plugins available                     # what is published
+pixlstash-cli plugins available caption             # ...matching a word
+pixlstash-cli plugins install hello_world_stamp     # from the plugins repository
+pixlstash-cli plugins install ./my_captioner.zip    # a zip of a plugin folder
+pixlstash-cli plugins install ./my_captioner/       # an extracted folder
+pixlstash-cli plugins install ./my_filter.py        # a single module
+pixlstash-cli plugins test ./my_captioner.py       # does it load and render?
+pixlstash-cli plugins list
+pixlstash-cli plugins remove my_captioner
+```
+
+`plugins available` lists what
+[PixlStash-plugins](https://github.com/Pikselkroken/PixlStash-plugins) publishes,
+with each plugin's name, title, one-line summary and (where declared) author and
+licence; `*` marks one you already have. Add a word to search, and it matches
+any of those fields, so anything you can see in the listing you can search for.
+It downloads the same archive `install` does and reads it without importing
+anything, so it needs no token and runs no published code.
+
+The destination differs by kind (captioning plugin or image filter) and by
+shape, so `install` works it out from the source instead of asking you to type
+it: it reads the source without importing it, decides which base class it
+derives from, and names the installed file after the plugin's own `name`. It
+refuses a source that is not a plugin, one whose name collides with a built-in,
+and a zip whose entries would be unpacked outside the folder it is unpacked
+into.
+
+`--dry-run` prints the plan and stops, `--yes` skips the confirmation, `--force`
+replaces an existing plugin of the same name, and `--strict` turns the warnings
+into refusals. `--ref` picks a branch, tag or commit in the plugins repository
+and is ignored for local sources; it cannot point the download at a different
+repository. A plugin's `requirements.txt` is never installed unless you pass
+`--with-deps`. **Plugin code runs unsandboxed, in the server process, with your
+permissions** — install what you would run yourself.
+
+Captioning plugins load at server start, so restart PixlStash after installing
+one; image filters are re-scanned every time the Filters menu is listed.
+
+`plugins test` is for the person *writing* a captioning plugin, and it is the
+one verb that imports the plugin instead of reading it: it loads the file the
+way the server does, registers what it defines, and checks that the parameter
+schema is one the settings screen can render — so a typo costs a command rather
+than a restart. `--image PATH` runs it over one picture as well, and stops
+instead of running when the plugin reports its model is not present — though a
+plugin that downloads inside `init()` still will, since by then it is the
+plugin's code deciding.
+
+**It is a development aid, not a security scanner.** It does not tell you
+whether a plugin is safe to install — it *runs* the plugin, unsandboxed, with
+your permissions, which is exactly what the server would do. Only test a plugin
+you would have installed anyway.
+
 ### User plugin directory
 
-Place your `.py` plugin files in the platform-specific user data directory. PixlStash logs the exact path on startup.
+If you prefer to copy files by hand, they go in the platform-specific user data
+directory. PixlStash logs the exact path on startup, and
+`pixlstash-cli plugins list` prints it.
+
+| OS | Image filters | Captioning plugins |
+|----|---------------|--------------------|
+| **Linux** | `~/.local/share/pixlstash/image-plugins/user/` | `~/.local/share/pixlstash/tagger-plugins/user/` |
+| **macOS** | `~/Library/Application Support/pixlstash/image-plugins/user/` | `~/Library/Application Support/pixlstash/tagger-plugins/user/` |
+| **Windows** | `%LOCALAPPDATA%\pixlstash\pixlstash\image-plugins\user\` | `%LOCALAPPDATA%\pixlstash\pixlstash\tagger-plugins\user\` |
+
+The doubled `pixlstash\pixlstash` on Windows is not a typo: `platformdirs` puts
+the app under a vendor folder, and PixlStash passes no separate vendor name.
+This table used to show it singly, which is why copying a plugin there by hand
+appeared to do nothing.
 
-| OS | Path |
-|----|------|
-| **Linux** | `~/.local/share/pixlstash/image-plugins/user/` |
-| **macOS** | `~/Library/Application Support/pixlstash/image-plugins/user/` |
-| **Windows** | `%LOCALAPPDATA%\pixlstash\image-plugins\user\` |
+An image filter is always a single `.py` file. A captioning plugin may be a
+single `.py` file or a folder containing `__init__.py`.
 
 ### Writing a plugin
 

{pixlstash-1.10.0.dev2 → pixlstash-1.10.0.dev4}/README.md

@@ -78,6 +78,8 @@ the app's own user-data directory.
 > | **Windows** | `%LOCALAPPDATA%\pixlstash\downloaded_models\` |
 >
 > An internet connection is required the first time the server starts. Subsequent starts use the cached models.
+>
+> **Moving them somewhere else:** open **Model folders** on the model shelf and use **Move** on PixlStash's own folder. Every file in it is copied, verified and removed from the old location, and the new location is remembered — so nothing is downloaded again. Set `PIXLSTASH_BUILTIN_MODEL_DIR` instead if you want the folder somewhere else without moving what is already in it (a mounted model volume, typically).
 
 If you need to use a custom config path:
 
@@ -114,6 +116,8 @@ pixlstash-cli libraries rename "Existing library" "Better name"
 pixlstash-cli libraries relocate "Existing library" /new/path
 pixlstash-cli libraries detach "Existing library"
 pixlstash-cli libraries backup "Existing library" /path/to/backups/
+pixlstash-cli libraries backup "Existing library" /path/to/backups/monday.tar.zst
+pixlstash-cli libraries restore /path/to/backups/monday.tar.zst /path/to/new-library
 ```
 
 | Command | What it does |
@@ -125,18 +129,33 @@ pixlstash-cli libraries backup "Existing library" /path/to/backups/
 | `relocate` | Points an existing registration at a new path, keeping its identity and share links. |
 | `detach` | Forgets a library. **No files are removed and nothing inside the folder changes.** |
 | `backup` | Writes the library and the hub to a single archive. |
+| `restore` | Unpacks an archive into a **new** folder and makes it the library that opens. |
 
 Notes worth knowing before you need them:
 
 - `detach` refuses the **active** library. Switch to another one first.
 - Reattaching the same folder revives its original registration, including its
   share links, because a library carries a fingerprint of its own identity.
+- A backup is a **zstd-compressed tar**, named `.tar.zst` — not `.tar.gz`.
+  `--no-compress` writes a plain `.tar` instead. Given a folder, `backup`
+  invents a dated name with the right ending; given a filename, it adds the
+  right ending if you left it off. `restore` recognises an archive by its
+  contents, so a renamed file still works.
 - A backup contains `hub.db`, and therefore your login and token secrets.
   PixlStash writes it owner-readable and refuses to overwrite an existing file.
 - A backup covers the library folder. Pictures kept in **reference folders** live
   outside it and are *not* included, so back those up separately.
 - Backing up finishes any outstanding one-time snapshot cleanup first, so the
   archive never carries credentials from before your upgrade.
+- `restore` needs PixlStash stopped, and names a folder that is empty or does
+  not exist yet — it never writes over a library. Because the archive holds the hub,
+  restoring also brings back the password and API tokens that library was
+  using, so your current ones are replaced.
+- **`restore` does not delete your current setup.** It *moves*
+  `server-config.json` and `hub.db` into a dated `pre-restore-*` folder beside
+  themselves and prints the launch command for each, so
+  `pixlstash-server --server-config <pre-restore-*>/server-config.json` reopens
+  what you had. Your old library folder is never touched.
 
 #### Which form to type
 
@@ -147,6 +166,13 @@ the environment PixlStash is installed into is active.
   `python -m pixlstash.cli libraries list`
 - **Docker Compose**, for a running service (paths are inside the container):
   `docker compose exec pixlstash pixlstash-cli libraries list`
+- **Desktop app** (AppImage, deb, .dmg, installer): the app is its own CLI, so
+  `/path/to/PixlStash.AppImage cli libraries list` works whether or not the app
+  is running. Turn on Settings › Backend › Desktop › **Shell command** to get a
+  `pixlstash` command in `~/.local/bin` and type `pixlstash libraries list`
+  instead. Either form targets the desktop app's own hub; there is no need to
+  pass `--hub`. Settings › Libraries always shows the exact command for your
+  install.
 - **A different hub** than the default: put global options *before* `libraries`,
   e.g. `pixlstash-cli --hub /path/to/hub.db libraries list`. Without `--hub` the
   CLI uses the standard config location, which is what you want almost always.
@@ -228,7 +254,7 @@ Edit the file and restart the server to apply changes.
 | `require_local_for_write` | `true` | When `true`, full login (username/password and ALL-scope tokens) is only permitted from local network addresses (RFC 1918 / loopback). READ-only share tokens are always accepted from any IP. Set to `false` to allow full login from any IP. |
 | `trusted_proxies` | `[]` | List of proxy IP addresses whose `X-Forwarded-For` header should be trusted for real-client-IP detection. See [Sharing and remote access](#sharing-and-remote-access) below. |
 
-At startup the server detects its own LAN IP and automatically allows it on any port. This means the Vite dev server works over LAN (`http://192.168.1.5:5173` → `http://192.168.1.5:9537`) without any extra configuration, as long as network access is enabled via `host`.
+At startup the server detects its own LAN IP and automatically allows it on any port. This means the Vite dev server works over LAN (`http://<lan-ip>:5173` → `http://<lan-ip>:9537`) without any extra configuration, as long as network access is enabled via `host`.
 
 Use `cors_origins` only if you need to allow origins on a different machine entirely.
 
@@ -443,15 +469,80 @@ Detailed installation instructions on <a href="http://pixlstash.dev/upgrade.html
 
 PixlStash supports built-in plugins and user-created plugins.
 
+### With the CLI (recommended)
+
+```bash
+pixlstash-cli plugins available                     # what is published
+pixlstash-cli plugins available caption             # ...matching a word
+pixlstash-cli plugins install hello_world_stamp     # from the plugins repository
+pixlstash-cli plugins install ./my_captioner.zip    # a zip of a plugin folder
+pixlstash-cli plugins install ./my_captioner/       # an extracted folder
+pixlstash-cli plugins install ./my_filter.py        # a single module
+pixlstash-cli plugins test ./my_captioner.py       # does it load and render?
+pixlstash-cli plugins list
+pixlstash-cli plugins remove my_captioner
+```
+
+`plugins available` lists what
+[PixlStash-plugins](https://github.com/Pikselkroken/PixlStash-plugins) publishes,
+with each plugin's name, title, one-line summary and (where declared) author and
+licence; `*` marks one you already have. Add a word to search, and it matches
+any of those fields, so anything you can see in the listing you can search for.
+It downloads the same archive `install` does and reads it without importing
+anything, so it needs no token and runs no published code.
+
+The destination differs by kind (captioning plugin or image filter) and by
+shape, so `install` works it out from the source instead of asking you to type
+it: it reads the source without importing it, decides which base class it
+derives from, and names the installed file after the plugin's own `name`. It
+refuses a source that is not a plugin, one whose name collides with a built-in,
+and a zip whose entries would be unpacked outside the folder it is unpacked
+into.
+
+`--dry-run` prints the plan and stops, `--yes` skips the confirmation, `--force`
+replaces an existing plugin of the same name, and `--strict` turns the warnings
+into refusals. `--ref` picks a branch, tag or commit in the plugins repository
+and is ignored for local sources; it cannot point the download at a different
+repository. A plugin's `requirements.txt` is never installed unless you pass
+`--with-deps`. **Plugin code runs unsandboxed, in the server process, with your
+permissions** — install what you would run yourself.
+
+Captioning plugins load at server start, so restart PixlStash after installing
+one; image filters are re-scanned every time the Filters menu is listed.
+
+`plugins test` is for the person *writing* a captioning plugin, and it is the
+one verb that imports the plugin instead of reading it: it loads the file the
+way the server does, registers what it defines, and checks that the parameter
+schema is one the settings screen can render — so a typo costs a command rather
+than a restart. `--image PATH` runs it over one picture as well, and stops
+instead of running when the plugin reports its model is not present — though a
+plugin that downloads inside `init()` still will, since by then it is the
+plugin's code deciding.
+
+**It is a development aid, not a security scanner.** It does not tell you
+whether a plugin is safe to install — it *runs* the plugin, unsandboxed, with
+your permissions, which is exactly what the server would do. Only test a plugin
+you would have installed anyway.
+
 ### User plugin directory
 
-Place your `.py` plugin files in the platform-specific user data directory. PixlStash logs the exact path on startup.
+If you prefer to copy files by hand, they go in the platform-specific user data
+directory. PixlStash logs the exact path on startup, and
+`pixlstash-cli plugins list` prints it.
+
+| OS | Image filters | Captioning plugins |
+|----|---------------|--------------------|
+| **Linux** | `~/.local/share/pixlstash/image-plugins/user/` | `~/.local/share/pixlstash/tagger-plugins/user/` |
+| **macOS** | `~/Library/Application Support/pixlstash/image-plugins/user/` | `~/Library/Application Support/pixlstash/tagger-plugins/user/` |
+| **Windows** | `%LOCALAPPDATA%\pixlstash\pixlstash\image-plugins\user\` | `%LOCALAPPDATA%\pixlstash\pixlstash\tagger-plugins\user\` |
+
+The doubled `pixlstash\pixlstash` on Windows is not a typo: `platformdirs` puts
+the app under a vendor folder, and PixlStash passes no separate vendor name.
+This table used to show it singly, which is why copying a plugin there by hand
+appeared to do nothing.
 
-| OS | Path |
-|----|------|
-| **Linux** | `~/.local/share/pixlstash/image-plugins/user/` |
-| **macOS** | `~/Library/Application Support/pixlstash/image-plugins/user/` |
-| **Windows** | `%LOCALAPPDATA%\pixlstash\image-plugins\user\` |
+An image filter is always a single `.py` file. A captioning plugin may be a
+single `.py` file or a folder containing `__init__.py`.
 
 ### Writing a plugin
 

{pixlstash-1.10.0.dev2 → pixlstash-1.10.0.dev4}/frontend/package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "pixlstash-frontend",
-  "version": "1.10.0-dev.2",
+  "version": "1.10.0-dev.4",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "pixlstash-frontend",
-      "version": "1.10.0-dev.2",
+      "version": "1.10.0-dev.4",
       "dependencies": {
         "@mdi/font": "^7.4.47",
         "axios": "^1.18.0",

{pixlstash-1.10.0.dev2 → pixlstash-1.10.0.dev4}/frontend/package.json

@@ -1,7 +1,7 @@
 {
   "name": "pixlstash-frontend",
   "private": true,
-  "version": "1.10.0-dev.2",
+  "version": "1.10.0-dev.4",
   "type": "module",
   "scripts": {
     "dev": "vite",

{pixlstash-1.10.0.dev2 → pixlstash-1.10.0.dev4}/pixlstash/app.py

@@ -211,34 +211,60 @@ def _force_utf8_streams():
             )
 
 
-def main():
-    _force_utf8_streams()
-    parser = argparse.ArgumentParser(description=f"Run the {APP_NAME} server.")
+def build_parser() -> argparse.ArgumentParser:
+    """Return the argument parser for the server entry point."""
+    parser = argparse.ArgumentParser(
+        prog=f"{APP_NAME}-server",
+        description=(
+            f"Run the {APP_NAME} server. In a source checkout, where the "
+            "entry point is not on PATH, the same options are accepted by "
+            f"`python -m {APP_NAME}.app`."
+        ),
+        epilog=(
+            "Every option acts during startup and the server then runs "
+            "normally, except --clear-embeddings, which does its work and "
+            "exits. Libraries and plugins are managed with a separate "
+            f"command, `{APP_NAME}-cli`."
+        ),
+    )
     parser.add_argument(
         "--server-config",
         type=str,
         default=SERVER_CONFIG_PATH,
-        help="Path to server config file.",
+        metavar="PATH",
+        help=(
+            "Path to the server config file, which is created on first run "
+            f"if it is missing (default: {SERVER_CONFIG_PATH})."
+        ),
     )
     parser.add_argument(
         "--remove-password",
         action="store_true",
-        help="Cause the server to recreate the password on next login.",
-    )
-    parser.add_argument(
-        "--retag-and-embed",
-        action="store_true",
-        help="Re-tag all images and refresh text embeddings in the database.",
+        help=(
+            "Clear the stored username and password hash and log out every "
+            "signed-in session, so the next sign-in sets them again. The "
+            "server starts as usual afterwards."
+        ),
     )
     parser.add_argument(
         "--clear-embeddings",
         action="store_true",
-        help="Clear all text embeddings for all images (does not touch tags).",
+        help=(
+            "Clear every picture's text and image embeddings, then exit "
+            "without starting the server. Tags are not touched, and the "
+            "embeddings are recomputed in the background the next time the "
+            "server runs."
+        ),
     )
     parser.add_argument(
         "--bootstrap",
         action="store_true",
-        help=("Run interactive first-run setup for storage path, port, and HTTPS."),
+        help=(
+            "Run the interactive first-run setup — storage path, port, HTTPS, "
+            "then the username and password — even if a config file already "
+            "exists, and start the server afterwards. It needs a terminal: "
+            "with stdin redirected the setup is skipped."
+        ),
     )
     parser.add_argument(
         "--cleanup-missing-pictures",
@@ -259,7 +285,12 @@ def main():
             "Example: --path-map /mnt/photos:/data/photos"
         ),
     )
-    args = parser.parse_args()
+    return parser
+
+
+def main():
+    _force_utf8_streams()
+    args = build_parser().parse_args()
 
     ran_bootstrap = _bootstrap_server_config(args.server_config, force=args.bootstrap)
     Server.DEFAULT_CLEANUP_MISSING_PICTURES = bool(args.cleanup_missing_pictures)

{pixlstash-1.10.0.dev2 → pixlstash-1.10.0.dev4}/pixlstash/auth.py

@@ -116,6 +116,28 @@ READ_BLOCKED_GET_PATHS: frozenset[str] = frozenset(
         # sidecar naming. A folder/filesystem endpoint, so READ tokens (handed
         # out to view a shared gallery) must not reach it.
         "/api/v1/reference-folders/detect-sidecars",
+        # Names the tagger-plugin folder on the server's disk, and returns
+        # plugin import errors whose text can carry any path the failing plugin
+        # reached for. The authz gate declares it LOCAL_OWNER_ONLY; it is here
+        # as well because that is the pattern filesystem/browse already sets,
+        # and because AUTHZ_GATE_ENFORCING is a documented one-line rollback —
+        # without this entry, taking it would hand the folder straight back to
+        # every share token.
+        "/api/v1/taggers/plugin-diagnostics",
+        # The plugin list carries the caller's own tagger_settings, which is
+        # user settings exactly like /users/me/config above — a plugin may
+        # declare a free-text parameter and the owner may have typed a path
+        # into it. Gate policy is OWNER_ONLY; same belt-and-braces reasoning.
+        "/api/v1/taggers",
+        # Found by the derivation in tests/test_authz_host_capability_16_3.py
+        # ::test_every_untemplated_locality_get_is_on_the_read_blocked_belt,
+        # not by anyone reading this list: it is LOCAL_OWNER_ONLY at the gate
+        # and serves the move queue's source and destination folders, so with
+        # the gate rolled back a READ token read host paths straight out of it.
+        # Its two templated siblings on the same tier cannot be expressed here
+        # at all — this frozenset matches literal paths — and stay the recorded
+        # follow-up.
+        "/api/v1/model-moves",
     }
 )