@adminiumjs/adminium 0.3.44 → 0.3.45

package/skills/adminium-project/references/projects/deploy--docker.md

@@ -12,7 +12,7 @@ RUN npm ci
 COPY . .
 RUN npx --no-install adminium build && rm -rf node_modules
 
-FROM ghcr.io/mosofi/adminium:0.3.44
+FROM ghcr.io/mosofi/adminium:0.3.45
 COPY --from=build --chown=node:node /project/ /project/
 ENV ADMINIUM_PROJECT_DIR=/project
 ```

package/skills/adminium-project/references/projects/deploy--upgrading-adminium.md

@@ -5,8 +5,8 @@
 The version is pinned in two places, and they must agree:
 
 ```bash
-npm install --save-exact @adminiumjs/adminium@0.3.44
-# then change the Dockerfile's FROM tag to 0.3.44
+npm install --save-exact @adminiumjs/adminium@0.3.45
+# then change the Dockerfile's FROM tag to 0.3.45
 npm run check                # this is what compares the two
 npm run build
 ```

package/skills/adminium-project/references/projects/folder--package-json.md

@@ -11,7 +11,7 @@
     "check": "adminium check",
     "pull": "adminium pull"
   },
-  "dependencies": { "@adminiumjs/adminium": "0.3.44" },
+  "dependencies": { "@adminiumjs/adminium": "0.3.45" },
   "devDependencies": { "esbuild": "^0.28.0", "@types/react": "^19.2.0" }
 }
 ```

package/skills/adminium-project/references/projects/pull-and-check--check.md

@@ -12,7 +12,7 @@ npm run check
 ✓ database "main" has a usable URL
 ✓ 20 page file(s), 1 schema file(s) and 2 list file(s) are valid
 ✓ 2 hook(s) and 1 action(s) load
-✓ the Dockerfile builds on @adminiumjs/adminium 0.3.44, the version package.json installs
+✓ the Dockerfile builds on @adminiumjs/adminium 0.3.45, the version package.json installs
 ```
 
 It checks, without connecting to anything:

package/skills/adminium-surface/references/cli/overview.md

@@ -15,7 +15,7 @@ the only correct install spec (`npx @adminiumjs/adminium`); the binary it
 installs is `adminium`. The unscoped npm name `adminium` is an unrelated
 third-party package, so never run `npx adminium`.
 
-On a server, add the version (`npx @adminiumjs/adminium@0.3.44 start`). Without
+On a server, add the version (`npx @adminiumjs/adminium@0.3.45 start`). Without
 one, npx installs any newer release it finds, and with no terminal attached it
 does so without asking. See
 [A VPS without Docker](https://docs.adminium.dev/self-hosting/vps/) for a pinned install under systemd,

package/skills/adminium-surface/references/guides/INDEX.md

@@ -75,7 +75,7 @@
 | `references/guides/roles-and-staff-access--personal-data.md` | Personal data | 1375 |
 | `references/guides/roles-and-staff-access--edits-limited-to-some-columns.md` | Edits limited to some columns | 2384 |
 | `references/guides/roles-and-staff-access--reads-limited-to-some-columns.md` | Reads limited to some columns | 2210 |
-| `references/guides/roles-and-staff-access--people-who-only-use-the-app.md` | People who only use the app | 2504 |
+| `references/guides/roles-and-staff-access--people-who-only-use-the-app.md` | People who only use the app | 2974 |
 | `references/guides/roles-and-staff-access--someone-without-access.md` | Someone without access | 902 |
 | `references/guides/roles-and-staff-access--signing-in-on-the-app-s-own-address.md` | Signing in on the app's own address | 1762 |
 | `references/guides/orders-with-lines--overview.md` | An order with its lines | 1439 |

package/skills/adminium-surface/references/guides/roles-and-staff-access--people-who-only-use-the-app.md

@@ -22,7 +22,11 @@ is sent to the app instead of the dashboard:
   into such a column (`POST /api/v1/files/<id>/copy`: a photo a past order has, chosen again; judged
   by the target table's own create or update, never by a files-wide right), read a file back with
   the record that holds it, and throw away one of their own uploads no record holds yet; the list of
-  files and the rest of the file routes stay the dashboard's.
+  files and the rest of the file routes stay the dashboard's. A screen of their app may show an
+  add-on's [record panel](https://docs.adminium.dev/reference/manifest/#a-panel-on-another-tables-record) too (a design kit's panel on an order
+  line): its code (`GET /api/v1/add-ons/<add-on>/panels/<panel>/bundle`) is served for an add-on
+  connected to their app, and still only for a row they reach, with a grant on the panel's table
+  and the panel's own permission (`page:@<panel>:view` in the app's role). Needs Adminium 0.3.45.
 - the [assistant](https://docs.adminium.dev/guides/llm-assist/milo/#on-an-apps-own-staff-address), when an administrator
   has given their role the assistant permission: its button is on the app's staff screens, and it
   answers about their app's data within what their roles read. An app's manifest cannot grant