@adminiumjs/adminium 0.3.44 → 0.3.45

package/skills/adminium/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-add-ons/references/catalogue/add-ons.md

@@ -8,19 +8,19 @@ Workspace settings → Add-ons.
 
 | Key | Version | Package | Fingerprint file |
 |---|---|---|---|
-| `barcode-labels` | 1.0.16 | `https://downloads.adminium.dev/add-ons/barcode-labels/barcode-labels-1.0.16.tgz` | `barcode-labels-1.0.16.tgz.integrity` holding `sha512-s8mkkvRKLl0X7IyMMKl01JGUg0tQSJdARksRNPpKn2Um99Jr5HL/+gIv8+c73tRiATkJLZT+ragLyKqY2XJ3Vg==` |
-| `customiser` | 1.0.16 | `https://downloads.adminium.dev/add-ons/customiser/customiser-1.0.16.tgz` | `customiser-1.0.16.tgz.integrity` holding `sha512-TkEHRSl0QraAIvwAquzcpvD/N2kvBBIsDJAbWATEOJR4JS5OW8wSW8anXXUPPRhYlE/bG+Y/dh/XBLpdwCfr9Q==` |
-| `design-studio` | 1.0.16 | `https://downloads.adminium.dev/add-ons/design-studio/design-studio-1.0.16.tgz` | `design-studio-1.0.16.tgz.integrity` holding `sha512-vaaZwyYnACQR8W4FdEo2IHSAsPWT4cz3HBfpu5gEFJH7+OEui4vNGPazhjnimublD1PbLdSMjfNDUZ1qmle6Nw==` |
-| `forms` | 1.0.16 | `https://downloads.adminium.dev/add-ons/forms/forms-1.0.16.tgz` | `forms-1.0.16.tgz.integrity` holding `sha512-KQYlxoIhr+I05wTE0VHQw0UumRqoyQ6HiqL/WO7mSy5oBlP3y2uMp1j4XmkGzSAGRFIJUgYtUuLyBChi404HrA==` |
-| `holiday-calendars` | 1.0.16 | `https://downloads.adminium.dev/add-ons/holiday-calendars/holiday-calendars-1.0.16.tgz` | `holiday-calendars-1.0.16.tgz.integrity` holding `sha512-yvJ0GaOQpEfpuzOk9KoF6oPPViyOrn64JkzhPOfCeHZ+rtWEfpoFFegejKvj2KY9E8r2YQrm8VkeGB2VoYzIVQ==` |
-| `import-canva` | 1.0.16 | `https://downloads.adminium.dev/add-ons/import-canva/import-canva-1.0.16.tgz` | `import-canva-1.0.16.tgz.integrity` holding `sha512-Ychlv9NV0YAfYlbeFsdYCT57emuUPw5El2JLv8z2xaf5e00Ysy/qBgKhUcsAQM+nEBOlNUsULfSYgtQ2bWAFbA==` |
-| `inventory` | 1.0.16 | `https://downloads.adminium.dev/add-ons/inventory/inventory-1.0.16.tgz` | `inventory-1.0.16.tgz.integrity` holding `sha512-s3rP/qpvo1CIaoGoLJrOs+drYFttomkj6zmXKOd4OtMd26Ng54d5rWGe42vlCH0tWlvFDMe/nsqaX5YuDNWlaA==` |
-| `invoices` | 1.0.16 | `https://downloads.adminium.dev/add-ons/invoices/invoices-1.0.16.tgz` | `invoices-1.0.16.tgz.integrity` holding `sha512-r9Kf7oH2ahTfS5JWr+xRhBjCNiY/m+bCBgtQk3AP20eEpAnn8uTJhPW4dSuEWP31de2JBI+jwncbmbi+mFenTA==` |
-| `offers` | 1.0.16 | `https://downloads.adminium.dev/add-ons/offers/offers-1.0.16.tgz` | `offers-1.0.16.tgz.integrity` holding `sha512-KtfYMAD4AnUbJ6JAx/Vq2zFUz7q58T0y6F7pwK/kRu5uYSwCQbC6eBZgbASqB7kPyYRqST1JUQG8d6BHNL9cjw==` |
-| `payments-paypal` | 1.0.16 | `https://downloads.adminium.dev/add-ons/payments-paypal/payments-paypal-1.0.16.tgz` | `payments-paypal-1.0.16.tgz.integrity` holding `sha512-/ckUeG6BcF1c1Lz8B1pxxmkmXQWLOhEmu8tz/HDNmuEnj/Dj8UWTcS7QM8WPmXZ6gNBWtGBa8U0c1CmTcAb8bA==` |
-| `payments-stripe` | 1.0.16 | `https://downloads.adminium.dev/add-ons/payments-stripe/payments-stripe-1.0.16.tgz` | `payments-stripe-1.0.16.tgz.integrity` holding `sha512-5fm4RI5tzPIwHjArNIphcHNyVnNplzikB7xwEvHEiKdUEjkydIw1yPIh8LFrspS8ElJE0h/IjcSFfBXaH9R0hg==` |
-| `personalizer` | 1.0.16 | `https://downloads.adminium.dev/add-ons/personalizer/personalizer-1.0.16.tgz` | `personalizer-1.0.16.tgz.integrity` holding `sha512-EdEnytndfCxTpKViPL3sZ+nyGCgGPLfXLu+3VsfKxA/SJmeRu8lc39t5xEHKq1GeGKgETM/qiZ9Vtj6rPq+7mg==` |
-| `shipping-dhl` | 1.0.16 | `https://downloads.adminium.dev/add-ons/shipping-dhl/shipping-dhl-1.0.16.tgz` | `shipping-dhl-1.0.16.tgz.integrity` holding `sha512-8jUC33J5KHxvYm+E4r+PGPwHqKAF6bciLCYeyzFTBfuGdn1M5cNclmDwTJzDZshbGHY0YtT+/hXa9LPGcHi26w==` |
+| `barcode-labels` | 1.0.17 | `https://downloads.adminium.dev/add-ons/barcode-labels/barcode-labels-1.0.17.tgz` | `barcode-labels-1.0.17.tgz.integrity` holding `sha512-wd+3864kt8AalTEOJP9ThLBuIpoSB54LjrazlKSh94YsKp6Qee8K9brnq7NF5/7bDFPIAHeFGO0gu86stVwadQ==` |
+| `customiser` | 1.0.17 | `https://downloads.adminium.dev/add-ons/customiser/customiser-1.0.17.tgz` | `customiser-1.0.17.tgz.integrity` holding `sha512-G0fcoC6t663a7jlYb+S8ZYLfwntmCmaC0M9Thw015RaPxNERW3GtXCadjHWSzJaiIgNcxvs4ftLX/A69KcCt4Q==` |
+| `design-studio` | 1.0.17 | `https://downloads.adminium.dev/add-ons/design-studio/design-studio-1.0.17.tgz` | `design-studio-1.0.17.tgz.integrity` holding `sha512-dXY4aC+uHXG1y6v4Jh7zplXxQXMG5DefQztEbEBgkVKg9IcMIj9tuQdEzPboMLSeuYBCfgTMAgd1zOgGuwlT4g==` |
+| `forms` | 1.0.17 | `https://downloads.adminium.dev/add-ons/forms/forms-1.0.17.tgz` | `forms-1.0.17.tgz.integrity` holding `sha512-MSEW5VjcV6cvLEfhKmZzkXS9AoenvIsBKiGYTPulQ28wHjDols8C8DW9UngXAmaINcLwo8Mq/xOiHEsufnYVCw==` |
+| `holiday-calendars` | 1.0.17 | `https://downloads.adminium.dev/add-ons/holiday-calendars/holiday-calendars-1.0.17.tgz` | `holiday-calendars-1.0.17.tgz.integrity` holding `sha512-egm51UBaXW8JcCsBkuThnXmXQvae5rP2zetLNE1rPnDem5JWAADV0/QJjxYisOVyaE1Yj6BRdLotyJF7pMUpaw==` |
+| `import-canva` | 1.0.17 | `https://downloads.adminium.dev/add-ons/import-canva/import-canva-1.0.17.tgz` | `import-canva-1.0.17.tgz.integrity` holding `sha512-YKGFA482J2bnI56AdNzO8D2cvjCtbu0T5+RrxVWtKL0CYSqz/o+E0NShSAkGT94CGXxeoMKElLQoJAUTKhpKYQ==` |
+| `inventory` | 1.0.17 | `https://downloads.adminium.dev/add-ons/inventory/inventory-1.0.17.tgz` | `inventory-1.0.17.tgz.integrity` holding `sha512-Eu4YH/1KZe0Ai11K8PJyU6rsB4FUg7ZbFIt6XW/1YLFcOFth97OJ2LXruciSucXs3l6j/5RURwNqcrcLrpTVGw==` |
+| `invoices` | 1.0.17 | `https://downloads.adminium.dev/add-ons/invoices/invoices-1.0.17.tgz` | `invoices-1.0.17.tgz.integrity` holding `sha512-u6bFbBpBru1FK/9LBAT1GJTDjkJmGWBNgMqSB2ce1yz3B4Obp09pZAK7sb2RCNPMDrIGCSMuCqcMHEsBrf9FxA==` |
+| `offers` | 1.0.17 | `https://downloads.adminium.dev/add-ons/offers/offers-1.0.17.tgz` | `offers-1.0.17.tgz.integrity` holding `sha512-+ABEAawIJ1HWfLLRbGCF3p/Lhm3JQS1r51s/jp/CWEUarn2DpRaitI2LGpHnEUHf8XkUjdRFBtOMDYqeZ4ckSg==` |
+| `payments-paypal` | 1.0.17 | `https://downloads.adminium.dev/add-ons/payments-paypal/payments-paypal-1.0.17.tgz` | `payments-paypal-1.0.17.tgz.integrity` holding `sha512-pIuGC7IxXXZ0kMquZ6MaGsTLGFehTae+a6olZefOEHwM2oat176HGua0smFYtd2G767Nqe2l+cOEJJ0JRnxwFw==` |
+| `payments-stripe` | 1.0.17 | `https://downloads.adminium.dev/add-ons/payments-stripe/payments-stripe-1.0.17.tgz` | `payments-stripe-1.0.17.tgz.integrity` holding `sha512-1ZV3zDYAyUZgGGVcCD7Xmq+02TO9nX64eFpaSCKf5O6OOO9bmgDC327x3H1hO17sJAPdeLtDsqOphFXjGw3FXw==` |
+| `personalizer` | 1.0.17 | `https://downloads.adminium.dev/add-ons/personalizer/personalizer-1.0.17.tgz` | `personalizer-1.0.17.tgz.integrity` holding `sha512-yjqUnLK366g6zAaxA1gR3qsASrcp2e81yWNE0aiBT6SMgppnv2K3D3707RBTlhbzPLuQYCTmmWI7cvALO8HJ8A==` |
+| `shipping-dhl` | 1.0.17 | `https://downloads.adminium.dev/add-ons/shipping-dhl/shipping-dhl-1.0.17.tgz` | `shipping-dhl-1.0.17.tgz.integrity` holding `sha512-01OKLiajWXt33TYLMaaQWPwMQHzxuL1zV/Xul2bOv3UgSPPHp/7zCOtGIxGLLEkihD7fwxXc61W16XqDzlpeWg==` |
 
 The key is what an app writes in `manifest/add-ons.json`. To give `adminium app try` an add-on,
 put its `.tgz` and a `.tgz.integrity` file holding the fingerprint above in one folder and pass

package/skills/adminium-add-ons/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-add-ons/references/guides/INDEX.md

@@ -25,13 +25,13 @@
 | `references/guides/emails--what-queues-a-row.md` | What queues a row | 6745 |
 | `references/guides/emails--messages-about-changes.md` | Messages about changes | 4152 |
 | `references/guides/emails--messages-about-a-row-that-is-removed.md` | Messages about a row that is removed | 4950 |
-| `references/guides/emails--sending.md` | Sending | 4071 |
+| `references/guides/emails--sending.md` | Sending | 4391 |
 | `references/guides/emails--held-messages.md` | Held messages | 1454 |
 | `references/guides/emails--attachments.md` | Attachments | 1887 |
 | `references/guides/emails--the-templates.md` | The templates | 1273 |
 | `references/guides/emails--variables.md` | Variables | 7565 |
 | `references/guides/emails--variables--the-person-a-staff-column-names.md` | Variables — The person a staff column names | 1053 |
-| `references/guides/emails--emails-that-list-rows.md` | Emails that list rows | 5462 |
+| `references/guides/emails--emails-that-list-rows.md` | Emails that list rows | 7245 |
 | `references/guides/emails--links.md` | Links | 850 |
 | `references/guides/emails--upgrading.md` | Upgrading | 1762 |
 | `references/guides/postings--overview.md` | Rows that post into an add-on's ledger | 874 |

package/skills/adminium-add-ons/references/guides/emails--emails-that-list-rows.md

@@ -105,3 +105,33 @@ empty draws no image.
 A code is a door credential. Its text stays inside the sealed message while it waits in the mail
 queue, never in the job's plain payload, and the rules for [codes](https://docs.adminium.dev/guides/apps/emails/#variables) hold for a QR code as
 for any other value: one that opens a shared link goes only to the person it belongs to.
+
+### Pictures from a row
+
+An image may show the picture a row keeps in a [file column](https://docs.adminium.dev/reference/manifest/#files-in-a-column):
+a repair's photo in the message about the repair. Its `fileId` is the column, as one placeholder
+and nothing else, for a row the message reads through one of the outbox's links (or a row one of
+them points at):
+
+```json
+{ "block": "email.image", "data": { "fileId": "{{job.photo}}", "alt": "Your repair" } }
+```
+
+The column is a `text` column with a `file` rule that takes pictures (`png`, `jpeg`, `gif` or
+`webp`), holding one file. It is never a secret, personal or withheld column: those are refused
+when the app is installed, as is a row the message does not read, a row of a list
+(`{{row.photo}}`), and a placeholder beside other text or with a backup.
+
+Each message checks its picture against the row it reads it through before it is queued. The file
+must be an upload that row has claimed (not one waiting to be saved, not another row's, whatever
+id the column holds), not in the bin, a png, jpeg, gif or webp, and at most **2 MB**. Only a
+picture that passes travels with the message, as an image inside it (`cid:`), the way a picture
+from Files does, and it is weighed again when the message is delivered: one grown past 2 MB since
+is not sent.
+
+A picture that does not pass is left out, and the message goes without it. With
+`"required": true` the message is not sent instead, and says why: "Not sent: the picture
+{{job.photo}} is not a file of this row" ("holds no picture", "is a file that is gone", "is not a
+picture (png, jpeg, gif or webp)", "is larger than 2 MB", "is not shown to this reader"). A
+message about no row at all fails as for any value: "Not sent: nothing fills {{job.photo}}".
+Needs Adminium 0.3.45.

package/skills/adminium-add-ons/references/guides/emails--sending.md

@@ -32,6 +32,7 @@ Then the row's status changes, with a sentence in its error column:
 | `failed` | Email is not set up on this server | Set up email, then queue the row again. |
 | `failed` | Not sent: the email lists rows from a table or link that is not there | A list's table, link or column is gone, for example renamed. See [Emails that list rows](https://docs.adminium.dev/guides/apps/emails/#emails-that-list-rows). |
 | `failed` | Not sent: {{…}} holds more than a QR code carries (64 bytes) | A code drawn as a QR code is longer than one carries. See [QR codes](https://docs.adminium.dev/guides/apps/emails/#qr-codes). |
+| `failed` | Not sent: the picture {{…}} *reason* | A `required` picture from a row could not be shown: no file in the column, another row's file, one in the bin, no picture, larger than 2 MB, or not shown to this reader. See [Pictures from a row](https://docs.adminium.dev/guides/apps/emails/#pictures-from-a-row). |
 | `failed` | Not sent: the values before the change are more than the outbox keeps | See [Messages about changes](https://docs.adminium.dev/guides/apps/emails/#messages-about-changes). |
 | `failed` | The email could not be prepared | Something else went wrong; the server log says what. |
 | `failed` | Not delivered: *reason* | The mail server refused it for good, after its retries. |

package/skills/adminium-app/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-app/references/guides/INDEX-2.md

@@ -62,13 +62,13 @@
 | `references/guides/emails--what-queues-a-row.md` | What queues a row | 6745 |
 | `references/guides/emails--messages-about-changes.md` | Messages about changes | 4152 |
 | `references/guides/emails--messages-about-a-row-that-is-removed.md` | Messages about a row that is removed | 4950 |
-| `references/guides/emails--sending.md` | Sending | 4071 |
+| `references/guides/emails--sending.md` | Sending | 4391 |
 | `references/guides/emails--held-messages.md` | Held messages | 1454 |
 | `references/guides/emails--attachments.md` | Attachments | 1887 |
 | `references/guides/emails--the-templates.md` | The templates | 1273 |
 | `references/guides/emails--variables.md` | Variables | 7565 |
 | `references/guides/emails--variables--the-person-a-staff-column-names.md` | Variables — The person a staff column names | 1053 |
-| `references/guides/emails--emails-that-list-rows.md` | Emails that list rows | 5462 |
+| `references/guides/emails--emails-that-list-rows.md` | Emails that list rows | 7245 |
 | `references/guides/emails--links.md` | Links | 850 |
 | `references/guides/emails--upgrading.md` | Upgrading | 1762 |
 | `references/guides/public-access--overview.md` | An app's public access | 539 |

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

@@ -27,7 +27,7 @@
 | `references/guides/manifest-by-task--values-adminium-fills-in.md` | Values Adminium fills in | 2712 |
 | `references/guides/manifest-by-task--things-a-manifest-cannot-do.md` | Things a manifest cannot do | 941 |
 | `references/guides/sample-data--overview.md` | Sample data | 414 |
-| `references/guides/sample-data--adding-it.md` | Adding it | 3778 |
+| `references/guides/sample-data--adding-it.md` | Adding it | 4036 |
 | `references/guides/sample-data--sample-times-that-follow-the-calendar.md` | Sample times that follow the calendar | 2543 |
 | `references/guides/sample-data--rows-for-an-add-on-the-app-names.md` | Rows for an add-on the app names | 4975 |
 | `references/guides/sample-data--sample-people.md` | Sample people | 1893 |
@@ -40,7 +40,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/settings--overview.md` | An app's settings page | 769 |

package/skills/adminium-app/references/guides/emails--emails-that-list-rows.md

@@ -105,3 +105,33 @@ empty draws no image.
 A code is a door credential. Its text stays inside the sealed message while it waits in the mail
 queue, never in the job's plain payload, and the rules for [codes](https://docs.adminium.dev/guides/apps/emails/#variables) hold for a QR code as
 for any other value: one that opens a shared link goes only to the person it belongs to.
+
+### Pictures from a row
+
+An image may show the picture a row keeps in a [file column](https://docs.adminium.dev/reference/manifest/#files-in-a-column):
+a repair's photo in the message about the repair. Its `fileId` is the column, as one placeholder
+and nothing else, for a row the message reads through one of the outbox's links (or a row one of
+them points at):
+
+```json
+{ "block": "email.image", "data": { "fileId": "{{job.photo}}", "alt": "Your repair" } }
+```
+
+The column is a `text` column with a `file` rule that takes pictures (`png`, `jpeg`, `gif` or
+`webp`), holding one file. It is never a secret, personal or withheld column: those are refused
+when the app is installed, as is a row the message does not read, a row of a list
+(`{{row.photo}}`), and a placeholder beside other text or with a backup.
+
+Each message checks its picture against the row it reads it through before it is queued. The file
+must be an upload that row has claimed (not one waiting to be saved, not another row's, whatever
+id the column holds), not in the bin, a png, jpeg, gif or webp, and at most **2 MB**. Only a
+picture that passes travels with the message, as an image inside it (`cid:`), the way a picture
+from Files does, and it is weighed again when the message is delivered: one grown past 2 MB since
+is not sent.
+
+A picture that does not pass is left out, and the message goes without it. With
+`"required": true` the message is not sent instead, and says why: "Not sent: the picture
+{{job.photo}} is not a file of this row" ("holds no picture", "is a file that is gone", "is not a
+picture (png, jpeg, gif or webp)", "is larger than 2 MB", "is not shown to this reader"). A
+message about no row at all fails as for any value: "Not sent: nothing fills {{job.photo}}".
+Needs Adminium 0.3.45.

package/skills/adminium-app/references/guides/emails--sending.md

@@ -32,6 +32,7 @@ Then the row's status changes, with a sentence in its error column:
 | `failed` | Email is not set up on this server | Set up email, then queue the row again. |
 | `failed` | Not sent: the email lists rows from a table or link that is not there | A list's table, link or column is gone, for example renamed. See [Emails that list rows](https://docs.adminium.dev/guides/apps/emails/#emails-that-list-rows). |
 | `failed` | Not sent: {{…}} holds more than a QR code carries (64 bytes) | A code drawn as a QR code is longer than one carries. See [QR codes](https://docs.adminium.dev/guides/apps/emails/#qr-codes). |
+| `failed` | Not sent: the picture {{…}} *reason* | A `required` picture from a row could not be shown: no file in the column, another row's file, one in the bin, no picture, larger than 2 MB, or not shown to this reader. See [Pictures from a row](https://docs.adminium.dev/guides/apps/emails/#pictures-from-a-row). |
 | `failed` | Not sent: the values before the change are more than the outbox keeps | See [Messages about changes](https://docs.adminium.dev/guides/apps/emails/#messages-about-changes). |
 | `failed` | The email could not be prepared | Something else went wrong; the server log says what. |
 | `failed` | Not delivered: *reason* | The mail server refused it for good, after its retries. |

package/skills/adminium-app/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

package/skills/adminium-app/references/guides/sample-data--adding-it.md

@@ -48,5 +48,8 @@ What happens when you confirm:
   its sample rows out once that table holds real ones. See
   [A menu two apps share](https://docs.adminium.dev/guides/apps/shared-menu/#sample-data-on-a-shared-menu).
 
-The card then reads **Loaded**, with the number of records and the date. An app's sample data can
-be loaded once at a time: remove it before adding it again.
+The card then reads **Loaded**, with the number of records and the date. It reads so only once the
+whole add has finished, the samples of the add-ons added with it too:
+`GET /api/v1/apps/<key>/sample-data` answers `loaded: false` while the add is queued or running,
+however many records are in by then (Adminium 0.3.45 and later). An app's sample data can be loaded
+once at a time: remove it before adding it again.

package/skills/adminium-app/references/manifest/INDEX.md

@@ -16,7 +16,7 @@
 | `references/manifest/requiredschema--tables.md` | requiredSchema — Tables | 3445 |
 | `references/manifest/requiredschema--columns.md` | requiredSchema — Columns | 7568 |
 | `references/manifest/requiredschema--columns-2.md` | requiredSchema — Columns (part 2) | 2212 |
-| `references/manifest/requiredschema--column-rules.md` | requiredSchema — Column rules | 7280 |
+| `references/manifest/requiredschema--column-rules.md` | requiredSchema — Column rules | 7394 |
 | `references/manifest/requiredschema--column-rules-2.md` | requiredSchema — Column rules (part 2) | 7581 |
 | `references/manifest/requiredschema--column-rules-3.md` | requiredSchema — Column rules (part 3) | 6333 |
 | `references/manifest/requiredschema--column-rules-4.md` | requiredSchema — Column rules (part 4) | 7046 |
@@ -24,11 +24,11 @@
 | `references/manifest/requiredschema--column-rules-6.md` | requiredSchema — Column rules (part 6) | 7818 |
 | `references/manifest/requiredschema--column-rules-7.md` | requiredSchema — Column rules (part 7) | 6589 |
 | `references/manifest/requiredschema--column-rules-8.md` | requiredSchema — Column rules (part 8) | 7742 |
-| `references/manifest/requiredschema--column-rules-9.md` | requiredSchema — Column rules (part 9) | 7750 |
-| `references/manifest/requiredschema--column-rules-10.md` | requiredSchema — Column rules (part 10) | 7164 |
-| `references/manifest/requiredschema--column-rules-11.md` | requiredSchema — Column rules (part 11) | 7808 |
+| `references/manifest/requiredschema--column-rules-9.md` | requiredSchema — Column rules (part 9) | 7540 |
+| `references/manifest/requiredschema--column-rules-10.md` | requiredSchema — Column rules (part 10) | 7006 |
+| `references/manifest/requiredschema--column-rules-11.md` | requiredSchema — Column rules (part 11) | 7715 |
 | `references/manifest/requiredschema--column-rules-12.md` | requiredSchema — Column rules (part 12) | 7788 |
-| `references/manifest/requiredschema--column-rules-13.md` | requiredSchema — Column rules (part 13) | 4926 |
+| `references/manifest/requiredschema--column-rules-13.md` | requiredSchema — Column rules (part 13) | 6600 |
 | `references/manifest/requiredschema--moments.md` | requiredSchema — Moments | 2748 |
 | `references/manifest/requiredschema--capacity.md` | requiredSchema — Capacity | 7647 |
 | `references/manifest/requiredschema--capacity-2.md` | requiredSchema — Capacity (part 2) | 5558 |
@@ -81,7 +81,7 @@
 | `references/manifest/emails--a-survey-s-link.md` | Emails — A survey's link | 4389 |
 | `references/manifest/emails--held-messages.md` | Emails — Held messages | 2873 |
 | `references/manifest/emails--emailtemplates.md` | Emails — emailTemplates | 7062 |
-| `references/manifest/emails--emailtemplates-2.md` | Emails — emailTemplates (part 2) | 4763 |
+| `references/manifest/emails--emailtemplates-2.md` | Emails — emailTemplates (part 2) | 5774 |
 | `references/manifest/people.md` | People | 979 |
 | `references/manifest/people-2.md` | People (part 2) | 7597 |
 | `references/manifest/public-access.md` | Public access | 2014 |

package/skills/adminium-app/references/manifest/emails--emailtemplates-2.md

@@ -21,6 +21,18 @@ message is delivered, only of a code column, and only for a code of at most 64 b
 [withhold](https://docs.adminium.dev/reference/manifest/#withheld-columns) or share-code rules keep from the message's recipient is printed
 empty, in every form, its QR code included.
 
+An `email.image` block may show the picture a row keeps in a [file column](https://docs.adminium.dev/reference/manifest/#files-in-a-column):
+`"fileId": "{{<link>.<column>}}"`, the whole value, for a row one of the outbox's links names (or
+`<link>.<base>`, a row it points at). The column is a `text` column whose `file.accept` takes a
+picture (`png`, `jpeg`, `gif`, `webp`), and is never secret, personal (marked, or guessed from its
+name) or withheld; `{{row.…}}`, a placeholder beside other text or with a backup, and a row the
+message does not read are refused. Each message checks the file against the row (an upload that
+row has claimed, not in the bin, a picture, at most 2 MB) and sends only a file that passes, as an
+inline image weighed again at delivery. One that does not is left out, or, with
+`"required": true` on the image, the message fails and says why. See
+[Pictures from a row](https://docs.adminium.dev/guides/apps/emails/#pictures-from-a-row). Needs Adminium 0.3.45
+(`email.rowPicture`).
+
 #### Blocks sent only with a value
 
 A block's `data` may carry `onlyWith` or `onlyWithout`, the name of one variable the template

package/skills/adminium-app/references/manifest/requiredschema--column-rules-10.md

@@ -2,6 +2,32 @@
 
 # Manifest spec: requiredSchema — Column rules
 
+A `{ "table", "column" }` setting, wherever a rule reads one (a default, a limit's size, a move's
+condition, a moment's time), names a table that holds **one row**: the outbox's
+[`settings.table`](https://docs.adminium.dev/reference/manifest/#outbox), or a table that stands alone, with no foreign key of its own, none
+pointing at it, and no states, limits or booking. Adminium reads that row when the rule runs. A
+moment, a state condition or a stamp's amount that finds two rows there reads nothing rather than
+guess which one is meant.
+
+#### Copies that follow
+
+A plain `copy` is taken when the row is written. With `"follow": true` it keeps in step: when the
+row it copies from changes, every row that copies it takes the new value in the same write. A
+hotel stay's extras copy the stay's nights and guests, so breakfast for two over three nights
+becomes breakfast for three over four the moment the stay changes.
+
+```json
+{ "ref": "nights", "type": "int", "nullable": true,
+  "rules": { "copy": { "via": "stay_id", "from": "nights", "mode": "always", "follow": true } } }
+```
+
+The copy is written, then every formula over it, then the totals it moves are settled into the
+row it follows (the stay's total, tax and balance), before the change commits; if any of that is
+refused, nothing is kept. A paid stay whose balance would fall below zero is refused
+`409` `BALANCE_EXCEEDED`.
+
+The rules that keep a follow sound:
+
 - it always wins (`mode: "always"`), and follows one level: the column it copies does not itself
   follow another row;
 - it never follows a total, a balance or a stamp, nor a formula over one: those change without a
@@ -73,14 +99,3 @@ code on a ticket. The browser never names the codes row itself; Adminium finds i
                                    { "column": "valid_until", "notBefore": "today", "orEmpty": true }],
                          "scope": [{ "column": "event_id", "equals": "event_id", "orEmpty": true }] } } }
 ```
-
-| Field | Rule |
-|---|---|
-| `from` | The nullable `text` column of this row the code is typed into, up to 64 characters, with no rule of its own that decides it. |
-| `table`, `column` | The codes table, and its `text` column the code is found by. The rule's own column is a nullable foreign key to `table`. `column` finds one row: it is `unique`, a [`code`](https://docs.adminium.dev/reference/manifest/#column-rules) column, or unique together with the `scope` columns in one of the table's [sets](https://docs.adminium.dev/reference/manifest/#columns-unique-together). It is compared as a code, so it has `normalize: "code"` unless it is a `code` column. Never the code a shared link opens its row with. |
-| `where` | Up to 4 conditions on the codes row: `{ "column", "eq" }`; `{ "column", "notBefore": "now" or "today", "orEmpty"? }`, a date or time not yet past (`valid_until`); `{ "column", "notAfter": "now" or "today", "orEmpty"? }`, one already reached (`valid_from`). `orEmpty` lets an empty column pass. |
-| `scope` | 1–2 `{ "column", "equals", "orEmpty"? }`: the codes row's `column` equals this row's `equals` column (this show's codes). With `orEmpty`, a codes row whose `column` is empty matches any (a code good for every show). |
-
-A typed code is read the way codes are kept: upper case, spaces and dashes left out. A column
-Adminium [makes codes in](https://docs.adminium.dev/reference/manifest/#column-rules) reads it as a claim does, its prefix put back, `O` as `0`,
-`I` and `L` as `1`. Two stored codes that fold alike are told apart by the exact spelling.

package/skills/adminium-app/references/manifest/requiredschema--column-rules-11.md

@@ -2,6 +2,17 @@
 
 # Manifest spec: requiredSchema — Column rules
 
+| Field | Rule |
+|---|---|
+| `from` | The nullable `text` column of this row the code is typed into, up to 64 characters, with no rule of its own that decides it. |
+| `table`, `column` | The codes table, and its `text` column the code is found by. The rule's own column is a nullable foreign key to `table`. `column` finds one row: it is `unique`, a [`code`](https://docs.adminium.dev/reference/manifest/#column-rules) column, or unique together with the `scope` columns in one of the table's [sets](https://docs.adminium.dev/reference/manifest/#columns-unique-together). It is compared as a code, so it has `normalize: "code"` unless it is a `code` column. Never the code a shared link opens its row with. |
+| `where` | Up to 4 conditions on the codes row: `{ "column", "eq" }`; `{ "column", "notBefore": "now" or "today", "orEmpty"? }`, a date or time not yet past (`valid_until`); `{ "column", "notAfter": "now" or "today", "orEmpty"? }`, one already reached (`valid_from`). `orEmpty` lets an empty column pass. |
+| `scope` | 1–2 `{ "column", "equals", "orEmpty"? }`: the codes row's `column` equals this row's `equals` column (this show's codes). With `orEmpty`, a codes row whose `column` is empty matches any (a code good for every show). |
+
+A typed code is read the way codes are kept: upper case, spaces and dashes left out. A column
+Adminium [makes codes in](https://docs.adminium.dev/reference/manifest/#column-rules) reads it as a claim does, its prefix put back, `O` as `0`,
+`I` and `L` as `1`. Two stored codes that fold alike are told apart by the exact spelling.
+
 Every miss is one answer: no such code, a code switched off, expired, another show's, or two that
 fold alike are all refused `422` `VALIDATION_FAILED` on the typed column with the code `unknown`
 (through the public API, `PUBLIC_WRITE_REFUSED` with `reason: "unknown"`), so a guesser learns no
@@ -87,28 +98,3 @@ what makes a new code:
 { "ref": "code", "type": "text", "nullable": true,
   "rules": { "code": { "length": 8, "renew": { "on": { "column": "holder_customer_id", "changed": true } } } } }
 ```
-
-`on` is one trigger or a list of 2–3: `{ "column", "changed": true }`, any change of another
-column of the row, or `{ "column", "values" }`, that column moving to one of 1–16 values (a
-transfer accepted). The watched column is not a code itself, not `json` or `blob`, and a `changed`
-trigger watches a column a person changes or a stamp writes (a holder stamped in as an offer is
-taken renews too).
-
-The new code is written in the same statement as the change: the old one stops as the write
-commits, and every session a [token link](https://docs.adminium.dev/reference/manifest/#a-persons-own-rows) on that column opened stops with
-it. What never renews: a create (it makes a code anyway), an import or other history, a change that
-sends back the value the row already holds, and a server action that writes the code itself (a
-[new link](https://docs.adminium.dev/reference/manifest/#a-rows-own-link)). A [timed move's](https://docs.adminium.dev/reference/manifest/#timed-moves) `set` renews like any other change.
-Undoing a change of hands renews once more, so neither the old code nor the one handed on works
-after it; see [Undo of a move](https://docs.adminium.dev/reference/manifest/#undo-of-a-move). A renewed code is never shown to a public caller
-in the change's reply, and only to staff who may read the table.
-
-#### Stamps
-
-A stamp writes a value when a row is created, or when another column changes to one of a list of
-values: the time a patient checked in, who took a payment.
-
-```json
-{ "ref": "checked_in_at", "type": "timestamptz", "nullable": true,
-  "rules": { "stamp": { "set": "now", "on": { "column": "status", "values": ["checked_in"] } } } }
-```

package/skills/adminium-app/references/manifest/requiredschema--column-rules-12.md

@@ -2,6 +2,31 @@
 
 # Manifest spec: requiredSchema — Column rules
 
+`on` is one trigger or a list of 2–3: `{ "column", "changed": true }`, any change of another
+column of the row, or `{ "column", "values" }`, that column moving to one of 1–16 values (a
+transfer accepted). The watched column is not a code itself, not `json` or `blob`, and a `changed`
+trigger watches a column a person changes or a stamp writes (a holder stamped in as an offer is
+taken renews too).
+
+The new code is written in the same statement as the change: the old one stops as the write
+commits, and every session a [token link](https://docs.adminium.dev/reference/manifest/#a-persons-own-rows) on that column opened stops with
+it. What never renews: a create (it makes a code anyway), an import or other history, a change that
+sends back the value the row already holds, and a server action that writes the code itself (a
+[new link](https://docs.adminium.dev/reference/manifest/#a-rows-own-link)). A [timed move's](https://docs.adminium.dev/reference/manifest/#timed-moves) `set` renews like any other change.
+Undoing a change of hands renews once more, so neither the old code nor the one handed on works
+after it; see [Undo of a move](https://docs.adminium.dev/reference/manifest/#undo-of-a-move). A renewed code is never shown to a public caller
+in the change's reply, and only to staff who may read the table.
+
+#### Stamps
+
+A stamp writes a value when a row is created, or when another column changes to one of a list of
+values: the time a patient checked in, who took a payment.
+
+```json
+{ "ref": "checked_in_at", "type": "timestamptz", "nullable": true,
+  "rules": { "stamp": { "set": "now", "on": { "column": "status", "values": ["checked_in"] } } } }
+```
+
 | Field | Rule |
 |---|---|
 | `set` | What is written; see the table below. |
@@ -52,28 +77,3 @@ A public write stamps like any other write, except `user-name` and `user-id`: a
 nobody, so they write nothing. What it knows of the person is their own signed-in row, which is
 what `claim` reads. For an automation, `user-name` is the rule's name. Sample data, an app's seed
 rows and undo stamp nothing, since a stamp of today's time over history would be false.
-
-A file somebody brings in is different: each line is their own create or their own change. A
-stamp is written into a column the line leaves out or leaves empty, as it would be for a save
-(`now` is the moment of the import, `user-id` and `user-name` are the person who brought the
-file, a `byOrigin` column gets its `staff` value). So a role that may not write `received_at`
-still brings a list of enquiries in, and each row says when it arrived. A value the line does
-carry is kept, where a save would lose it to the stamp: the day an old enquiry really came is
-the file's to say. Whether the person may say it is their role's create limit, which refuses a
-file that carries a column they may not give a new row. A line that changes a stored row (an
-import that updates the rows it matches) fires the stamps a change by hand would, against the
-row as stored: moving a status stamps its moment once, and the same file brought in again
-stamps nothing. A stamped column takes
-no `copy`, `default`, `sequence`, `format`, `code`, `rollup`, `formula`, `lookup`, `band` or `perNight` as
-well, and a stamp watches a column other than its own.
-
-A stamp that works out a moment again whenever what it reads changes: a stay may be cancelled
-free until 48 hours before 15:00 on its arrival day, and moving the arrival moves the deadline.
-
-```json
-{ "ref": "cancel_by", "type": "timestamptz", "nullable": true,
-  "rules": { "stamp": {
-    "set": { "moment": { "column": "arrive", "time": { "table": "settings", "column": "arrive_from" },
-                         "minus": { "hours": { "table": "settings", "column": "cancel_hours" } } } },
-    "on": { "columns": ["arrive"] } } } }
-```

package/skills/adminium-app/references/manifest/requiredschema--column-rules-13.md

@@ -2,6 +2,31 @@
 
 # Manifest spec: requiredSchema — Column rules
 
+A file somebody brings in is different: each line is their own create or their own change. A
+stamp is written into a column the line leaves out or leaves empty, as it would be for a save
+(`now` is the moment of the import, `user-id` and `user-name` are the person who brought the
+file, a `byOrigin` column gets its `staff` value). So a role that may not write `received_at`
+still brings a list of enquiries in, and each row says when it arrived. A value the line does
+carry is kept, where a save would lose it to the stamp: the day an old enquiry really came is
+the file's to say. Whether the person may say it is their role's create limit, which refuses a
+file that carries a column they may not give a new row. A line that changes a stored row (an
+import that updates the rows it matches) fires the stamps a change by hand would, against the
+row as stored: moving a status stamps its moment once, and the same file brought in again
+stamps nothing. A stamped column takes
+no `copy`, `default`, `sequence`, `format`, `code`, `rollup`, `formula`, `lookup`, `band` or `perNight` as
+well, and a stamp watches a column other than its own.
+
+A stamp that works out a moment again whenever what it reads changes: a stay may be cancelled
+free until 48 hours before 15:00 on its arrival day, and moving the arrival moves the deadline.
+
+```json
+{ "ref": "cancel_by", "type": "timestamptz", "nullable": true,
+  "rules": { "stamp": {
+    "set": { "moment": { "column": "arrive", "time": { "table": "settings", "column": "arrive_from" },
+                         "minus": { "hours": { "table": "settings", "column": "cancel_hours" } } } },
+    "on": { "columns": ["arrive"] } } } }
+```
+
 An offer that lasts as many hours as the settings row says, but never past the show's doors:
 
 ```json

package/skills/adminium-app/references/manifest/requiredschema--column-rules-9.md

@@ -17,6 +17,26 @@ is the text between it and its neighbour, so a guest with no last name is "Mia",
 result is trimmed, and empty when every column is. A join is the whole formula of its column,
 never a part of a sum.
 
+A join with a `normalize` rule is kept as the rule says, the way a typed value is. A sample
+request's `address_key`, a join over the postcode and the first line kept as a code, is
+`SL71BT12QUAYSTREET` however the address is typed, so a `unique` key on it refuses the same
+address in another case:
+
+```json
+{ "ref": "address_key", "type": "text", "maxLength": 160, "nullable": true, "unique": true,
+  "rules": { "formula": { "join": ["postcode", "address_line1"] }, "normalize": "code" } }
+```
+
+It is kept so wherever the join is worked out: a create, an edit of a column it reads, a total
+that moves under it, and an update that fills it for the rows already there. A row written
+before keeps its key until one of those works it out again. Needs Adminium 0.3.45; before it,
+only a join over a running number was kept so, and any other kept as it was worked out.
+
+An app that works its formulas out itself, in a demo with no server, keeps the same value by
+passing the column's rules to the evaluator: `evaluateFormula(expr, row, scale, formulaKeepOf(column))`
+from `@adminium/manifest` applies the `normalize` rule, then cuts a join to the column's length,
+as the server does. Needs `@adminium/manifest` 0.3.45.
+
 A join that reads personal data lands it only in a personal column. A guest's first and last
 names beside their email read as personal by their names, so the joined name needs
 `"personal": true` too; without it the check refuses the manifest. The same holds for a `copy`
@@ -108,29 +128,3 @@ made:
 The same three settings (the last two) are what `sequence.startSetting` and `format.prefixSetting`
 read. A column with a `default` rule is nullable: when there is nothing to read, it stays empty
 rather than taking a made-up value. An update never refills it.
-
-A `{ "table", "column" }` setting, wherever a rule reads one (a default, a limit's size, a move's
-condition, a moment's time), names a table that holds **one row**: the outbox's
-[`settings.table`](https://docs.adminium.dev/reference/manifest/#outbox), or a table that stands alone, with no foreign key of its own, none
-pointing at it, and no states, limits or booking. Adminium reads that row when the rule runs. A
-moment, a state condition or a stamp's amount that finds two rows there reads nothing rather than
-guess which one is meant.
-
-#### Copies that follow
-
-A plain `copy` is taken when the row is written. With `"follow": true` it keeps in step: when the
-row it copies from changes, every row that copies it takes the new value in the same write. A
-hotel stay's extras copy the stay's nights and guests, so breakfast for two over three nights
-becomes breakfast for three over four the moment the stay changes.
-
-```json
-{ "ref": "nights", "type": "int", "nullable": true,
-  "rules": { "copy": { "via": "stay_id", "from": "nights", "mode": "always", "follow": true } } }
-```
-
-The copy is written, then every formula over it, then the totals it moves are settled into the
-row it follows (the stay's total, tax and balance), before the change commits; if any of that is
-refused, nothing is kept. A paid stay whose balance would fall below zero is refused
-`409` `BALANCE_EXCEEDED`.
-
-The rules that keep a follow sound:

package/skills/adminium-app/references/manifest/requiredschema--column-rules.md

@@ -21,6 +21,6 @@ change or delete is theirs from then on.
 | `format` | `{ "from", "prefix"?, "prefixSetting"?, "pad"? }` | A `text` column written from a running number of the same row, gapless or not: the prefix, then the digits padded with zeros (`INV-0042`). See [Numbers without gaps](https://docs.adminium.dev/reference/manifest/#numbers-without-gaps). |
 | `code` | `{ "length", "prefix"?, "renew"?, "hiddenFromStaff"?, "givenByLedger"? }` | A short random code, unique in the column. `renew` makes a new one when the row changes hands; see [Codes that renew](https://docs.adminium.dev/reference/manifest/#codes-that-renew). `length` is 4–16; `prefix` is upper case, up to 6 characters plus an optional `-` (`MR-`). A create that leaves it out or empty gets one, a sample row or an import too; a code they bring is kept, but a sample's code for a shared link's `column` is always made anew. A code is no secret by its rule alone: a name that reads like one (`share_token`) keeps it one, unless `secret: false` says otherwise or it is the column a shared link opens a row by, on a table the install made, which staff who read the table see. The public sees a code only where an entry's `select` names it, and a shared link's never. The audit log and the automation logs say `[code]` in its place, and the assistant never reads it. `hiddenFromStaff: true`: a code no desk hands out (an online order's own link) is left out of every staff read, for every role and Super Admin too: rows, exports, live updates and the history. The link still opens its row, and the app's emails still carry it to the row's holder. Such a code is kept as a shared link's code is, whether or not an entry claims by it yet: no column copies it (a `copy`, a stamp's copy, a formula), no total keeps it as the newest child row's value (`rollup.latest`), no `codeLast4` keeps its last four, no posting copies it into a ledger (its `map`, from the row or its parent), and no public entry shows, filters or orders by it. The manifest check refuses each one, and so does the server when somebody saves such a rule on the schema or makes such an API endpoint (`ENDPOINT_SHARE_CODE_READ`). A rule never carries it: a rule's step or e-mail template that names it (`{{record.x}}`, `{{x}}`, `{{was.x}}`, a linked row's `{{link.x}}`) is refused by the validator and when a rule is saved, the column named. `givenByLedger: true`, on a table of an add-on: a row the add-on's own [ledger](https://docs.adminium.dev/reference/manifest/#ledgers) adds may bring its code (an older gift card, under the code its holder has always had). It is kept when it is the prefix, then 4 to 16 capital letters and digits, fits the column and no other row has it, and refused otherwise; with none given Adminium makes one. No person's save gains anything by it, and a change never writes a code. |
 | `formula` | an expression | A number worked out from the row's other columns on every write. See [Formulas](https://docs.adminium.dev/reference/manifest/#formulas). |
-| `normalize` | `"trim"`, `"email"` or `"code"` | How a `text` value is kept: `trim` without spaces at either end, `email` trimmed and in lower case, `code` compared as a code (upper case, spaces and dashes left out) when a person types one; see [Typed codes](https://docs.adminium.dev/reference/manifest/#typed-codes). |
+| `normalize` | `"trim"`, `"email"` or `"code"` | How a `text` value is kept: `trim` without spaces at either end, `email` trimmed and in lower case, `code` compared as a code (upper case, spaces and dashes left out) when a person types one; see [Typed codes](https://docs.adminium.dev/reference/manifest/#typed-codes). On a [`join`](https://docs.adminium.dev/reference/manifest/#joined-text) column the joined text is kept that way. |
 | `lookup` | `{ "from", "table", "column", "where"?, "scope"? }` | A foreign key filled from a code a person types into another column: a discount code, a presale code. See [Typed codes](https://docs.adminium.dev/reference/manifest/#typed-codes). |
 | `band` | `{ "table", "min", "max"?, "value", "scope"?, "over"? }` | A foreign key filled with the band a number of the row falls in: a line's quantity among its product's price breaks, an order's weight among the delivery bands. See [Bands](https://docs.adminium.dev/reference/manifest/#bands). |

package/skills/adminium-design/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-mobile/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-project/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,