@plitzi/sdk-shared 0.38.7 → 0.38.8

package/CHANGELOG.md

@@ -1,5 +1,189 @@
 # @plitzi/sdk-shared
 
+## 0.38.8
+
+### Patch Changes
+
+- 1b45aae: ## The CLI's commands are named after what they act on
+
+  Every command sits under the thing it acts on — `plitzi element move`, never a bare `move` that could mean anything —
+  and only what acts on the project as a whole or the account stays at the top:
+
+  | Before                                       | Now                                                                |
+  | -------------------------------------------- | ------------------------------------------------------------------ |
+  | `where`, `edit`, `remove`, `move`            | `element where`, `element edit`, `element remove`, `element move`  |
+  | `check`, `shot`, `import`                    | `page check`, `page shot`, `page import`                           |
+  | `space`, `pull`, `push`, `lint`, `fix`       | `space use`, `space pull`, `space push`, `space lint`, `space fix` |
+  | `add plugin`, `pack plugin`, `upload plugin` | `plugin add`, `plugin pack`, `plugin upload`                       |
+  | `add runtime`                                | `runtime add`                                                      |
+  | `pack source`                                | `source pack`                                                      |
+  | `update` (alias of `upgrade`)                | `upgrade`                                                          |
+
+  `create`, `verify`, `doctor`, `upgrade`, `explain`, `feedback`, `login`, `logout` and `whoami` stay at the top, beside
+  `functions`, `runtime`, `data` and `skills`. There are no aliases: a name asked for at the top that is a group's command
+  answers where it is — `There is no plitzi push: it is one of plitzi space push, plitzi runtime push, plitzi functions
+push` — read off the commands themselves. A project's scripts (`lint:space`, `check`, `shot`) call the new names;
+  `plitzi upgrade --write` updates the ones the CLI wrote.
+
+  ## Agents load less to do the same (RFC 0025)
+  - **The MCP lists the operations vocabulary once.** A connection with a space listed ~69k tokens of tools before an
+    agent did anything — the operations schema five times. `plitzi_apply` carries it; `plitzi_render` lists only its
+    operations' types beside it (and keeps the whole schema on a guest connection, where it is alone). The listing is
+    now ~18k tokens.
+  - **`plitzi_validate` is `plitzi_apply`'s `dryRun`**, which already answered the same; the `validate` function, its
+    `validateShape` and `ValidateInput` are gone from `@plitzi/sdk-mcp`.
+  - **`plitzi_apply` looks at the page it would leave**: `look: 'html' | 'image' | 'accessibility' | 'both'` (with
+    `pageRef`, `viewport`, `fullPage`) renders it — with `dryRun`, as the batch would leave it, nothing saved; without, as
+    saved. Check, look and save with the operations written twice, not four times.
+  - **`plitzi_look` is the one way to see a saved page** — its accessibility outline (the default: text, cheap), its HTML
+    or a PNG; `plitzi_preview` and `plitzi_screenshot` are gone. It is always offered: without a browser service it answers
+    the HTML and says so.
+  - **`plitzi_describe_operation { type }`** answers one operation's schema, or every type there is; a type that does not
+    exist is answered with the nearest one.
+  - `closest` is exported from `@plitzi/sdk-authoring`: the nearest of a closed list of names.
+  - **`plitzi element where <id | class | words>`** answers where the project's code writes an element — the file, the line and
+    the call itself — asked of the code as it is now, so it follows an element wherever somebody moved it. A class is
+    found by its name or by the variable that holds it (`nav-link`, `navLink`).
+  - **`plitzi element edit <id> --set key=value --remove key`** writes attributes in that call (`content` where the factory takes
+    it first), keeping each one's kind, formatted as the project formats, and keeps the change only if the space still
+    authors with every value there. Behind both, `locateElements` in `@plitzi/sdk-authoring`: every element with the call
+    that wrote it.
+  - A generated project's `AGENTS.md` says to ask `where` instead of keeping a note of where things are.
+  - **`plitzi doctor` says one fact once**: packages installed from the same place, and packages behind the same version,
+    are one line each — on a project installed from local tarballs, ~1,050 tokens of output became ~330.
+  - **A mistake costs one line.** An operation type that does not exist is answered with the nearest one; a field an
+    operation, an element, a binding or a flow step does not have is refused naming the one meant — it used to be dropped,
+    and `prop` for `props` answered success having applied nothing. An element type spelt with other capitals
+    (`Heading`) is read as the catalog spells it and said in `warnings`.
+  - **The same batch refused twice is not run a third time** (`REPEATED_BATCH`), and the second refusal says so; `plitzi
+edit` does the same, kept in the project's `tmp/refusals.json`.
+  - **`plitzi_apply`'s `look` renders a batch through the path a save takes** (`draftBatch`): a
+    `repeatElement` expanded, what has one reading read, the same refusals.
+  - **Each skill is a core an agent reads every time, and references it opens when the task names one.** The core —
+    what it is for, the rules that go wrong most, a table routing each task to its one file — is held to 1,500 tokens:
+    `plitzi-authoring` went from ~4,000 to ~920 (every rule kept in `reference/rules.md`, the recipes indexed in
+    `reference/recipes.md`, every reference in `reference/index.md`), `plitzi-cli` from ~4,000 to ~820 (projects,
+    plugins and troubleshooting are references of their own), `plitzi-render` from ~3,100 to ~1,050.
+  - **Intent tools on the MCP**: `plitzi_set_attributes`, `plitzi_set_classes` (classes added or removed, the rest
+    kept), `plitzi_bind_attribute`, `plitzi_place_component`, `plitzi_add_page` — a few parameters, the element by its ref alone (the
+    page is found, a ref that does not exist answered with the nearest), checked and saved as `plitzi_apply` saves, and
+    answered in a line with the next step.
+  - **An element may only wear a class the space has, or the batch declares**: `plitzi_apply` used to save one nothing
+    defines — rendered unstyled, said by nobody. It is refused naming the nearest class.
+  - **`plitzi explain` answers any export of `@plitzi/sdk-authoring`** — `pageFamily`, `styles`, `SpaceSpec` — with its
+    signature and the first paragraph of its doc, read from the `.d.ts` the project installed: a few dozen tokens where an
+    agent used to search ~180k of published types.
+  - **`plitzi element where --by id|class|text`** reads a query one way; without it, the first reading that matches is answered
+    and every other one that matched is said with its count and the command for it — a query that means two things is
+    never answered as one. `plitzi element edit` reads its element by id alone.
+  - **A helper written once and called for many elements** is told apart: `locateElements` answers each element's
+    `through` — the calls of the author's code that led to the one that wrote it — so `plitzi element where` says which other
+    elements the same call writes and the call that leads to this one alone, and `plitzi element edit` changes a value the helper
+    is handed where it is handed (`pageHead('about-head', 'About us')`), refuses an edit of a call that writes several
+    elements unless `--every` says so, and never writes `content` beside words given as the factory's first argument.
+  - `plitzi explain` of a name that is the project's own says where to read it.
+  - **Nothing a write does is silent.** `plitzi_apply` answers `effects`: every change the batch made, read off the space
+    before and after it (elements added or removed by subtree, attributes, classes, moves, styles, settings, connectors,
+    actions), with a note where a changed attribute is one a binding computes; a batch that changed nothing says so, and
+    a store with no persister leads the warnings as `NOT saved: …`. The intent tools answer those `effects`, whether it
+    was `saved` and what was already so, refuse to take off a class the element does not wear and to write a value under
+    a binding. `plitzi element edit` reads the whole space before and after the edit (`plitzi element readings`, in a fresh process),
+    prints every change, and puts the files back when anything changed that was not asked, naming it; it refuses an
+    attribute a binding computes, and `plitzi element where` marks those `Bound`. `canonicalJson` (`@plitzi/sdk-shared`) is
+    what every before-and-after comparison is made with. Authoring keeps deep enough a call stack (64 frames) that a
+    helper inside a helper is still told apart.
+  - `locateElements` answers the parts of every component too, in the component (`rootId` is its id): `plitzi element where`
+    and `plitzi element edit` reach an element inside a component as they reach one on a page or a layout.
+
+  ## Fixed
+  - **A layout no longer mounts twice when the page hydrates.** An element with `runtime: 'server'` was wrapped in its
+    static shell while hydrating and handed back without it — under another key — on the next render, so React tore
+    down everything under it and built it again. With a server provider around a layout (an `apiContainer` that draws
+    no markup of its own), the whole layout's DOM was replaced on every page, and every `motion` arrival in it played
+    twice: a visible flicker on load. The shell now stays around the element on both sides of hydration, under the same
+    key, and only stops freezing (`frozen`).
+  - **A component's instance is written somewhere.** `component(…)` — and each child it places in a slot — rebuilt its
+    spec with a spread and lost the marker of where the author wrote it: `plitzi element where` could not place an instance and
+    `plitzi element edit` refused it. The original marker is carried (`carryWrittenAt`); `where` finds the words an instance
+    hands its component, and `edit` writes an instance's props.
+  - `plitzi element edit` follows a value read off a list the call is repeated for (`item.question` in
+    `QUESTIONS.flatMap(item => …)`) to the one entry that holds it, in the file the list is written in; when the shared
+    value is not a literal it says where it comes from instead of offering `--every`.
+  - **`plitzi page check --element` says which class wins.** Each property more than one of the element's classes sets, at
+    rest: the value shown, the class it comes from and what the others say — or that they all set it so. Which wins is
+    asked of the page, each class taken off for a moment; a style change is verified in text, not with a picture.
+  - **`plitzi element where` reads more.** By words it finds every word an element says (`words` on `WrittenElement`: content,
+    `label`, `title`, `alt`, `placeholder`, binding templates, an instance's props); by class it says where the class
+    is declared (`locateClasses` in `@plitzi/sdk-authoring`); an element repeated over a list says which list, and its
+    file; a page or a layout is placed at the object it is declared as.
+  - **`plitzi element edit` edits a page** by the attributes `where` shows (`seoPageTitle` written as `seoTitle`;
+    `PAGE_SPEC_FIELDS` in `@plitzi/sdk-authoring`), refusing `layout` and `seoEnabled`, which are no field of their own;
+    and a value read in more than one place (a list entry a nav and a menu both draw) changes them all only with
+    `--every`, each named.
+  - **A component prop of a type that does not exist is refused** (`prop-type-unknown`, with the types there are):
+    `type: 'string'` was accepted at run time, offered by no editor and checked against nothing. `BUILTIN_PARAM_TYPES`
+    in `@plitzi/sdk-shared` is the list, and `BuiltinParamType` is derived from it.
+  - **`plitzi element remove <id>` and `plitzi element move <id> --before|--after <id>`** take an element out of the code that writes
+    it, or reorder it among its siblings — following a section a helper returns to the helper's call — checked as
+    `edit` is: a removal may take only the element and what it holds, a move only reorder its parent, or the file goes
+    back. Styles and imports only the removed call used go with it, named; a helper left unread is said.
+  - **`plitzi verify`** runs the project's checks — author (no warning), lint:space, typecheck, lint, format — and every
+    page with no parameter, and prints only what fails; a page it could not open is said as not checked. Generated
+    projects get `npm run verify`, and their `AGENTS.md` names it as the way to leave the project passing.
+  - **A component's refusal says where it is written** (by its root's call).
+  - **`check --element`** says a class changes nothing on the element only when every property it sets stays without
+    it, and names the other elements the class is on: changing the class changes them; taking it off this element does
+    not.
+  - **An element's generated selector and binding ids are named after its id**, under its parent's place, not after its
+    position among its siblings: a move renames nothing. Every space written in code gets new generated names once —
+    the same rules, so nothing a visitor sees changes.
+  - A change of an element's children is said as what came, went or moved (`faq moved — now after hero, before pricing`).
+  - **`plitzi page check --click <id>`** clicks one element and says what changed — flows run and how each step ended, the
+    page it went to, what scrolled, what is shown now and what no longer is, the state — or that nothing did, in those words; a flow that
+    succeeded while nothing on the page changed is said as that. A click that could not be made, or a flow that failed,
+    fails the check.
+  - **A refusal of the authored space's gate says where**: each of the validator's errors (`UNRESOLVED_INTERACTION_TARGET`,
+    `UNRESOLVED_BINDING_SOURCE`, …) carries the file and line of the element it is about, and a name nothing answers to is
+    offered the nearest element that answers the step it was for (`openModal('search')` → `search-modal`, not the
+    `search-q` field), or the few that do. `SchemaValidationError` gains `missing` and `wantedBy` (`@plitzi/sdk-schema`).
+  - **`plitzi element where` finds the words a list's rows show** when the list is handed them as data (`items:
+[...PLANS]`), and says the list they are the entries of and its file (`Its rows are the entries of PLANS
+(src/space/enterprise/content.ts)`).
+  - `plitzi page check --click` says what is **shown** now and what no longer is (drawn, wherever the page is scrolled),
+    not "on screen".
+  - `plitzi upgrade` says packages installed locally in one line past three, and a skill rewritten within the same
+    version as that, not `0.38.7 → 0.38.7`.
+  - **What `element edit`, `remove` and `move` read back goes through the gate `npm run author` does**: a change that
+    leaves the space refused — a flow still opening a modal that was removed — is put back, the refusal said with where.
+    `element remove` refuses before writing when another element's flows act on what it takes away, and says what it
+    took once, by the outermost element (`search-modal removed, with 18 inside`). Moving an element beside itself is
+    refused as nothing to do.
+  - **An id, a plugin folder or a data file written a letter off is offered the nearest one** (`element where`, `edit`,
+    `remove`, `move`, `plugin pack`, `data describe`).
+  - **A project file that does not load is said at its file and line** — `src/space/hero.ts:139: Expected ','` — by the
+    server, `npm run author` and every CLI command, never as a stack (`ProjectModuleError` and `moduleProblem` in
+    `@plitzi/sdk-authoring/node`).
+  - **`plitzi verify` stops at the first failure** — one broken file fails every later step the same way — and says the
+    rest as not run (`--keep-going` runs them anyway); `--no-pages` no longer fails a run that passed.
+  - **`plitzi space fix` no longer drops attributes written one level too deep**: `attributes: { value: 5 }` where
+    `value: 5` was meant is put in its place (a new `unwrap` fix), not removed with what it said.
+  - **`plitzi explain <type>` explains the project's own elements** (`src/plugins/`), and `plugin add` prints how to place
+    one with the attributes it was declared with.
+  - **`plitzi data describe` says an object keyed by data once**, as a map of one shape with how many keys, so a file of
+    five hundred articles reads as one.
+  - **`plitzi page check` says a path no page answers before opening it**, with the paths the pages do answer — never a
+    redirect home read as a page for signed-in visitors.
+  - **`copyToClipboard(text)`**, a utility step (`@plitzi/sdk-interactions`, built with `copyToClipboard` in
+    `@plitzi/sdk-authoring`): a "Copy link" button had no step to write with. A browser that gives the page no clipboard
+    fails the step, so a toast after it is never said of a copy that was not made.
+  - **`plitzi explain` lists the values a param takes only when it is a choice** (`select`): `setState`'s `value` read
+    as `'true' | 'false'`, the examples of a free value taken for its only ones.
+  - **`plitzi page check --click` says what the page said** — a toast or an alert, `said: "Link copied"` — and **a form
+    the browser held back**, with the field and the browser's reason, never as a click that changed nothing.
+  - **`plitzi page check --click <id> --fill <id>=<value>`** fills fields before the click as a visitor does (typed, an
+    option chosen, a box ticked), so a form's success flow is checked, not only its refusal when empty. A container of
+    several fields is refused with their ids; a field filled inside another element says whose it is.
+
 ## 0.38.7
 
 ### Patch Changes

package/dist/authoring/declare.d.ts

@@ -64,7 +64,7 @@ export interface ElementDeclarationData {
     /**
      * Whether the element is behaviour rather than content — a clock that fires a flow, a listener — and draws nothing on
      * a page (at most a tag in the builder, to have something to select). Read by the page checks (`inspectPage`,
-     * `plitzi check`), which would otherwise wait for it to be on screen and report it hidden.
+     * `plitzi page check`), which would otherwise wait for it to be on screen and report it hidden.
      */
     drawsNothing?: boolean;
     content?: {

package/dist/authoring/index.mjs

@@ -1,6 +1,6 @@
 import { toBuilderParams as e, toInteractionCallback as t, toInteractionCallbacks as n } from "./builder.mjs";
 import { elementDeclaration as r, valuesOf as i } from "./declare.mjs";
-import { hiddenParams as a, invalidParams as o, missingRequiredParams as s, reconcileParams as c } from "./paramSpec.mjs";
-import { BUILTIN_ELEMENT_CALLBACKS as l, SCROLL_CALLBACKS as u, applyElementCallback as d, getElementCallback as f } from "./elementCallbacks.mjs";
-import { spaceCallbacks as p } from "./spaceCallbacks.mjs";
-export { l as BUILTIN_ELEMENT_CALLBACKS, u as SCROLL_CALLBACKS, d as applyElementCallback, r as elementDeclaration, f as getElementCallback, a as hiddenParams, o as invalidParams, s as missingRequiredParams, c as reconcileParams, p as spaceCallbacks, e as toBuilderParams, t as toInteractionCallback, n as toInteractionCallbacks, i as valuesOf };
+import { BUILTIN_PARAM_TYPES as a, hiddenParams as o, invalidParams as s, missingRequiredParams as c, reconcileParams as l } from "./paramSpec.mjs";
+import { BUILTIN_ELEMENT_CALLBACKS as u, SCROLL_CALLBACKS as d, applyElementCallback as f, getElementCallback as p } from "./elementCallbacks.mjs";
+import { spaceCallbacks as m } from "./spaceCallbacks.mjs";
+export { u as BUILTIN_ELEMENT_CALLBACKS, a as BUILTIN_PARAM_TYPES, d as SCROLL_CALLBACKS, f as applyElementCallback, r as elementDeclaration, p as getElementCallback, o as hiddenParams, s as invalidParams, c as missingRequiredParams, l as reconcileParams, m as spaceCallbacks, e as toBuilderParams, t as toInteractionCallback, n as toInteractionCallbacks, i as valuesOf };

package/dist/authoring/paramSpec.d.ts

@@ -1,5 +1,6 @@
 import { InteractionParamType } from '../types';
-export type BuiltinParamType = 'text' | 'textarea' | 'select' | 'boolean' | 'number' | 'scalar' | 'json' | 'elementIds';
+export declare const BUILTIN_PARAM_TYPES: readonly ["text", "textarea", "select", "boolean", "number", "scalar", "json", "elementIds"];
+export type BuiltinParamType = (typeof BUILTIN_PARAM_TYPES)[number];
 export interface BuiltinParam {
     type: BuiltinParamType;
     description: string;

package/dist/authoring/paramSpec.mjs

@@ -1,17 +1,26 @@
 import { hasValidToken as e } from "../helpers/twigWrapper/tokens/hasValidToken.mjs";
 //#region src/authoring/paramSpec.ts
-var t = (e, t, n) => {
+var t = [
+	"text",
+	"textarea",
+	"select",
+	"boolean",
+	"number",
+	"scalar",
+	"json",
+	"elementIds"
+], n = (e, t, n) => {
 	let r = [];
 	for (let [i, a] of Object.entries(n)) a.when && e[i] !== void 0 && !a.when(t) && r.push(i);
 	return r;
-}, n = (e, t, n) => {
+}, r = (e, t, n) => {
 	let r = [];
 	for (let [i, a] of Object.entries(n)) a.required && e[i] === void 0 && (!a.when || a.when(t)) && r.push(i);
 	return r;
-}, r = (e) => e.trim() !== "" && Number.isFinite(Number(e)), i = (t) => typeof t == "string" && e(t), a = (e, t) => {
+}, i = (e) => e.trim() !== "" && Number.isFinite(Number(e)), a = (t) => typeof t == "string" && e(t), o = (e, t) => {
 	switch (t.type) {
 		case "boolean": return typeof e == "boolean";
-		case "number": return typeof e == "number" || typeof e == "string" && r(e);
+		case "number": return typeof e == "number" || typeof e == "string" && i(e);
 		case "select": return typeof e == "string" && (!t.options || t.options.includes(e));
 		case "scalar": return typeof e == "string" || typeof e == "number" || typeof e == "boolean";
 		case "json": return typeof e == "string" || typeof e == "number" || typeof e == "boolean" || typeof e == "object" && !!e;
@@ -20,23 +29,23 @@ var t = (e, t, n) => {
 		case "elementIds": return Array.isArray(e) && e.every((e) => typeof e == "string");
 		default: return !0;
 	}
-}, o = (e, t, n) => {
+}, s = (e, t, n) => {
 	let r = [];
-	for (let [o, s] of Object.entries(n)) {
-		let n = e[o];
-		n === void 0 || i(n) || s.when && !s.when(t) || a(n, s) || r.push({
-			key: o,
+	for (let [i, s] of Object.entries(n)) {
+		let n = e[i];
+		n === void 0 || a(n) || s.when && !s.when(t) || o(n, s) || r.push({
+			key: i,
 			expected: s.type,
 			got: n === null ? "null" : typeof n,
 			...s.options ? { options: s.options } : {}
 		});
 	}
 	return r;
-}, s = (e, t, n) => {
+}, c = (e, t, n) => {
 	let r = {};
 	for (let [i, a] of Object.entries(e)) (!n || i in t) && (r[i] = a);
 	for (let [e, n] of Object.entries(t)) n.default === void 0 || r[e] !== void 0 || n.when && !n.when(r) || (r[e] = n.default);
 	return r;
 };
 //#endregion
-export { t as hiddenParams, o as invalidParams, n as missingRequiredParams, s as reconcileParams };
+export { t as BUILTIN_PARAM_TYPES, n as hiddenParams, s as invalidParams, r as missingRequiredParams, c as reconcileParams };

package/dist/devTools/chrome.d.ts

@@ -1,6 +1,6 @@
 /**
  * The attribute every piece of the dev tools' own chrome carries — the badge, the panel — so whatever looks at the
- * page rather than at the tools can leave it out: `plitzi shot` and `plitzi check` hide it, and a picture of a page is
+ * page rather than at the tools can leave it out: `plitzi page shot` and `plitzi page check` hide it, and a picture of a page is
  * a picture of the page.
  */
 export declare const DEV_TOOLS_ATTRIBUTE = "data-plitzi-devtools";

package/dist/helpers/canonicalJson.d.ts

@@ -0,0 +1,6 @@
+/**
+ * A value as JSON with every object's keys in order, so two values that say the same thing in another order read the
+ * same: what a before-and-after comparison is made with, where a key moved is not a change. `undefined` reads
+ * `undefined`.
+ */
+export declare const canonicalJson: (value: unknown) => string;

package/dist/helpers/canonicalJson.mjs

@@ -0,0 +1,5 @@
+import { isRecord as e } from "./isRecord.mjs";
+//#region src/helpers/canonicalJson.ts
+var t = (t) => t === void 0 ? "undefined" : JSON.stringify(t, (t, n) => e(n) ? Object.fromEntries(Object.keys(n).toSorted().map((e) => [e, n[e]])) : n);
+//#endregion
+export { t as canonicalJson };

package/dist/network/spaceEvents.d.ts

@@ -90,7 +90,7 @@ export declare const spaceEventSchemas: {
     }, z.core.$strip>;
     /**
      * A plugin installed — or installed again at a new address, which is how a new version arrives: from the builder,
-     * or from `plitzi upload plugin` with no builder open. An open builder loads it without a reload.
+     * or from `plitzi plugin upload` with no builder open. An open builder loads it without a reload.
      */
     readonly SPACE_ADD_PLUGIN: z.ZodObject<{
         plugin: z.ZodObject<{

package/dist/project/layout.d.ts

@@ -145,7 +145,7 @@ export interface ProjectLayoutOptions {
 export declare const pluginTypeOf: (folder: string) => string;
 /**
  * The file an element's folder is built from, wherever the folder is — its `index.ts`, or `index.tsx` — or nothing
- * when it has neither, or both: what `plitzi pack plugin` builds a folder from, as the server does.
+ * when it has neither, or both: what `plitzi plugin pack` builds a folder from, as the server does.
  */
 export declare const elementEntry: (dir: string) => string | undefined;
 /**

package/dist/project/layout.mjs

@@ -195,7 +195,7 @@ var v = {
 		action: "move",
 		from: `${n}/${c}`,
 		to: `${n}/${a}`
-	})] : [y("plugin-declaration-missing", `${n}/`, `${n}/ has no ${a}: ${s}.`, `Write ${n}/${a} — export default { type: '${o}', … } — as npx plitzi add plugin writes one beside the component it makes.`)];
+	})] : [y("plugin-declaration-missing", `${n}/`, `${n}/ has no ${a}: ${s}.`, `Write ${n}/${a} — export default { type: '${o}', … } — as npx plitzi plugin add writes one beside the component it makes.`)];
 }, B = (e, t) => {
 	if (!x.test(t)) return [te(t)];
 	let n = `${i}/${t}`, r = M(t), a = ne(S(m.join(e, n)).files, t);
@@ -205,14 +205,14 @@ var v = {
 			accepted: o,
 			code: "plugin-entry-missing",
 			lost: `the server cannot build the plugin ${r}`,
-			write: `Write ${n}/index.ts exporting the component by default${a ? ` — export { default } from './${a}';` : ""} — as npx plitzi add plugin writes it. Every folder of ${i}/ is a plugin: code several plugins share goes outside it (src/shared/).`
+			write: `Write ${n}/index.ts exporting the component by default${a ? ` — export { default } from './${a}';` : ""} — as npx plitzi plugin add writes it. Every folder of ${i}/ is a plugin: code several plugins share goes outside it (src/shared/).`
 		}),
 		...R(e, {
 			folder: `${n}/${s}`,
 			accepted: ["index.ts"],
 			code: "plugin-functions-entry-missing",
 			lost: `none of the plugin's server half runs (its routes under /fn/plugins/${r}/)`,
-			write: `Write ${n}/${s}/index.ts exporting defineFunctions({ … }) by default — as npx plitzi add plugin --server writes it.`
+			write: `Write ${n}/${s}/index.ts exporting defineFunctions({ … }) by default — as npx plitzi plugin add --server writes it.`
 		}),
 		...z(e, t)
 	];
@@ -225,7 +225,7 @@ var v = {
 	type: t.type,
 	isMain: t.isMain === !0
 }] : []) : [], U = (t, n) => {
-	let r = `${p}/${n}`, i = `${r}/${c}`, a = `npx plitzi pull brings it again — or delete ${r}/, and the space renders no ${n}.`;
+	let r = `${p}/${n}`, i = `${r}/${c}`, a = `npx plitzi space pull brings it again — or delete ${r}/, and the space renders no ${n}.`;
 	if (!C(t, i, "file")) return { problem: y("vendor-manifest-missing", `${r}/`, `${r}/ has no ${c}: the server runs a built plugin by what its manifest names, so ${n} does not run.`, a) };
 	let o;
 	try {
@@ -247,7 +247,7 @@ var v = {
 }, W = (e) => {
 	let { files: t, folders: n } = S(m.join(e, i)), r = t.filter((e) => !b.has(e) && e !== "declarations.ts").map((e) => {
 		let { name: t } = m.parse(e), n = t !== "index" && N(t) || "<Name>";
-		return y("plugin-file-loose", `${i}/${e}`, `${i}/${e} is a file, and every plugin is a folder of ${i}/: the server reads nothing of it.`, `Give it a folder with an index.ts that exports it by default — ${i}/${n}/${e} and ${i}/${n}/index.ts, as npx plitzi add plugin writes them — or move it out of ${i}/.`);
+		return y("plugin-file-loose", `${i}/${e}`, `${i}/${e} is a file, and every plugin is a folder of ${i}/: the server reads nothing of it.`, `Give it a folder with an index.ts that exports it by default — ${i}/${n}/${e} and ${i}/${n}/index.ts, as npx plitzi plugin add writes them — or move it out of ${i}/.`);
 	}), a = S(m.join(e, p)).folders, o = new Set(n.filter((e) => x.test(e)).map(M)), s = a.filter((e) => o.has(e)).map((e) => y("plugin-shadowed", `${p}/${e}/`, `${e} is both ${p}/${e}/, as it was built, and a folder of ${i}/: the server runs the built one, and a change to the source shows nowhere.`, `Delete ${p}/${e}/: the source is the plugin now.`)), c = a.flatMap((t) => {
 		let n = U(e, t);
 		return "problem" in n ? [n.problem] : [];
@@ -337,7 +337,7 @@ var v = {
 		...s,
 		...c
 	];
-}, oe = (e) => w(e, n).filter((e) => !b.has(m.posix.basename(e)) && !e.endsWith(".json")).map((e) => y("data-not-json", e, `${e} is not JSON: a provider's /data/<file> and ctx.data read JSON files only, and plitzi push leaves it behind.`, `Keep it as JSON (${e.replace(/\.[^./]*$/, "")}.json), or move it out of ${n}/.`)), se = /^\.env(?:\..*)?$|\.(?:pem|key|p12|pfx|jks|keystore|sqlite3?|db|sql|dump)$|secret|credential|password|passwd|private[-_.]?key|id_rsa|id_ed25519|service[-_]?account/i, ce = (e, t) => {
+}, oe = (e) => w(e, n).filter((e) => !b.has(m.posix.basename(e)) && !e.endsWith(".json")).map((e) => y("data-not-json", e, `${e} is not JSON: a provider's /data/<file> and ctx.data read JSON files only, and plitzi space push leaves it behind.`, `Keep it as JSON (${e.replace(/\.[^./]*$/, "")}.json), or move it out of ${n}/.`)), se = /^\.env(?:\..*)?$|\.(?:pem|key|p12|pfx|jks|keystore|sqlite3?|db|sql|dump)$|secret|credential|password|passwd|private[-_.]?key|id_rsa|id_ed25519|service[-_]?account/i, ce = (e, t) => {
 	let r = w(e, l, /* @__PURE__ */ new Set(["node_modules"])), i = r.filter((e) => se.test(m.posix.basename(e))).map((e) => y("public-secret-file", e, `${e} is served to anyone who asks, as it is — everything in ${l}/ is on the internet once the project is deployed — and its name says it holds a secret, a key or a database.`, `Take it out of ${l}/: settings go in the root's .env${t === "server" ? `, data only the server reads in ${n}/` : ""}.`)), a = `${l}/data`, o = t === "server" ? r.filter((e) => e.startsWith(`${a}/`) && e.endsWith(".json")) : [], s = o.slice(0, 3).map((e) => m.posix.basename(e)), c = o.length > 0 ? [y("public-data", `${a}/`, `${a}/ holds ${String(o.length)} JSON file${o.length === 1 ? "" : "s"} (${s.join(", ")}${o.length > s.length ? ", …" : ""}), served to anyone who asks: every visitor can read all of ${o.length === 1 ? "it" : "them"}, not only what a page shows.`, `Data only the server should read goes in ${n}/ — a provider reads it on the server (runtime: 'server', query: '/data/<file>'), a function with ctx.data('<file>'), and neither serves the file. What every visitor may read can stay.`)] : [];
 	return [...i, ...c];
 }, Z = (t) => {
@@ -365,7 +365,7 @@ var v = {
 			accepted: ["index.ts"],
 			code: "runtime-entry-missing",
 			lost: "the space’s runtime does not run",
-			write: `Write ${u}/index.ts exporting defineRuntime(…) by default — npx plitzi add runtime writes one.`
+			write: `Write ${u}/index.ts exporting defineRuntime(…) by default — npx plitzi runtime add writes one.`
 		}),
 		...n.space === "local" ? re(e, i) : [],
 		...i,

package/dist/project/paths.d.ts

@@ -39,7 +39,7 @@ export declare const PLUGINS_DIR = "src/plugins";
  * and one of them, never both.
  */
 export declare const PLUGIN_ENTRIES: readonly ["index.ts", "index.tsx"];
-/** What a plugin folder declares itself in — its type, attributes, triggers — as `plitzi add plugin` writes it. */
+/** What a plugin folder declares itself in — its type, attributes, triggers — as `plitzi plugin add` writes it. */
 export declare const PLUGIN_DECLARATION_FILE = "declaration.ts";
 /** A plugin's server half, a folder of its own beside its component: built from its `index.ts`. */
 export declare const PLUGIN_FUNCTIONS_DIR = "functions";
@@ -48,7 +48,7 @@ export declare const PLUGIN_FUNCTIONS_DIR = "functions";
  * beside the manifest it was published with (`PLUGIN_MANIFEST_FILE`).
  */
 export declare const VENDOR_PLUGINS_DIR = "vendor/plugins";
-/** What `plitzi pack plugin` writes beside a plugin's bundle: its version, its files, and the elements it provides. */
+/** What `plitzi plugin pack` writes beside a plugin's bundle: its version, its files, and the elements it provides. */
 export declare const PLUGIN_MANIFEST_FILE = "plugin-manifest.json";
 /** A runtime that came across built only (a project made from a space): run as it was built. */
 export declare const RUNTIME_BUNDLE = "vendor/runtime.bundle";

package/dist/source/export.d.ts

@@ -29,7 +29,7 @@ export type SpaceExport = {
     /** The version taken out: the draft (`main`, revision 0), or a snapshot an environment holds. */
     version: Pick<SpaceVersionContents, 'environment' | 'revision' | 'snapshot'>;
     /**
-     * Which state of the draft's documents this is — its schema, style, actions and connectors — what `plitzi push`
+     * Which state of the draft's documents this is — its schema, style, actions and connectors — what `plitzi space push`
      * checks the space's draft has not moved on from. `null` for a snapshot, which no push writes.
      */
     draft: string | null;
@@ -62,7 +62,7 @@ export type SpaceExport = {
     };
     /**
      * The space's own data, by path in `src/data/` (JSON its providers read on the server, never served), and the version
-     * of it this is — what `plitzi push` checks the space's copy has not moved on from.
+     * of it this is — what `plitzi space push` checks the space's copy has not moved on from.
      */
     data: {
         version: string;

package/dist/source/import.d.ts

@@ -1,6 +1,6 @@
 import { Schema, Style } from '../types';
 /**
- * A project's space put back on Plitzi as the space's draft (docs/en/projects-from-spaces.md): what `plitzi push` sends
+ * A project's space put back on Plitzi as the space's draft (docs/en/projects-from-spaces.md): what `plitzi space push` sends
  * to `PUT /spaces/:spaceId/import`, and what it is answered. The way back of `SpaceExport` — one shape for both ends.
  */
 export declare const SPACE_IMPORT_FORMAT = 1;

package/dist/style/cssLayers.d.ts

@@ -10,7 +10,7 @@ export declare const PLUGIN_CSS_LAYER = "plitzi-sdk-plugin";
 export declare const RUNTIME_CSS_LAYER = "plitzi-sdk-runtime";
 /**
  * A plugin's stylesheet, as it ships: everything in it in {@link PLUGIN_CSS_LAYER}. Written by whatever builds a
- * plugin — a server compiling one, `plitzi pack plugin` — so every way the file later reaches a page (a `<link>` in the
+ * plugin — a server compiling one, `plitzi plugin pack` — so every way the file later reaches a page (a `<link>` in the
  * server's HTML, the SDK's assets, the builder's canvas) puts it in its place with no work of its own.
  *
  * Idempotent: a stylesheet already wrapped is returned as it is.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@plitzi/sdk-shared",
-  "version": "0.38.7",
+  "version": "0.38.8",
   "license": "AGPL-3.0",
   "files": [
     "dist",
@@ -318,6 +318,10 @@
       "types": "./dist/helpers/index.d.ts",
       "import": "./dist/helpers/index.mjs"
     },
+    "./helpers/canonicalJson": {
+      "types": "./dist/helpers/canonicalJson.d.ts",
+      "import": "./dist/helpers/canonicalJson.mjs"
+    },
     "./helpers/cookies": {
       "types": "./dist/helpers/cookies.d.ts",
       "import": "./dist/helpers/cookies.mjs"