@atelic-action/ui 0.16.0 → 0.16.1

package/README.md

@@ -1,6 +1,6 @@
 # @atelic-action/ui
 
-Shared UI for the Atelic templates: the site chrome (header, menu, footer, sticky CTA bar, and credit band), the not found page and the routing that keeps it alive, the scroll spy hook, and the one base stylesheet. The marketing and artifact templates install it instead of carrying their own copies, so a chrome fix lands once and every site picks it up with `bun update`.
+Shared UI for the Atelic templates: the site chrome (header, menu, footer, sticky CTA bar, and credit band), the not found page and the routing that keeps it alive, the scroll spy hook, and the one base stylesheet. The marketing and artifact templates install it instead of carrying their own copies, so a chrome fix lands once and every site picks it up with `bun update @atelic-action/ui --latest`.
 
 The package ships source, not a build. Its TSX and CSS arrive as written and compile inside each site's own Vite. The one exception is the access gate's server side, which ships compiled (see [The Access Gate](#the-access-gate)).
 
@@ -10,6 +10,8 @@ The package ships source, not a build. Its TSX and CSS arrive as written and com
 bun add @atelic-action/ui
 ```
 
+The package is below 1.0, where a caret range admits patches only, so a site takes a new minor with `bun update @atelic-action/ui --latest`: a plain `bun update` leaves it on the minor it has and reports nothing wrong.
+
 Peer dependencies: `react` and `react-dom` at `^19.0.0`, and `lucide-react` at `^1.23.0`. Three more are optional, needed only by a site whose `vite.config.ts` imports `@atelic-action/ui/vite`: `vite`, `@tanstack/react-start`, and `@vitejs/plugin-react`. The commands the package installs run under `bun`, with `node` for the sealing command.
 
 ## Vite Config

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@atelic-action/ui",
-	"version": "0.16.0",
+	"version": "0.16.1",
 	"description": "Shared UI for the Atelic templates: site chrome, base styles, the component library, and the access gate they install",
 	"type": "module",
 	"license": "UNLICENSED",

package/src/scripts/build-gate-payload.mjs

@@ -83,8 +83,10 @@ async function deriveKey(email, salt) {
 
 /**
  * Encrypt `contentHtml` once and wrap the content key for each person.
- * `people` is [{ id, email }]; the email is the reader's secret and their
- * identity, so both survive into the payload alongside the wrap.
+ * `people` is [{ id, email }]. The email is the reader's secret, the thing
+ * their key derives from, so it never reaches the payload; nor does the id,
+ * which is often a first name. A sealed reader is an ordinal (`r1`, `r2`)
+ * and their wrap, and nothing that says who they are.
  */
 export async function sealDocument(contentHtml, people) {
 	if (typeof contentHtml !== "string" || contentHtml.length === 0) {