@plitzi/cli 0.38.11 → 0.38.13

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@plitzi/cli",
-  "version": "0.38.11",
+  "version": "0.38.13",
   "license": "AGPL-3.0",
   "description": "Command line for Plitzi: scaffold a project that renders a space, a plugin package, or an element of your own.",
   "files": [
@@ -21,14 +21,14 @@
   },
   "sideEffects": false,
   "dependencies": {
-    "@plitzi/sdk-authoring": "0.38.11",
+    "@plitzi/sdk-authoring": "0.38.13",
     "chalk": "^6.0.1",
     "commander": "^15.0.0",
     "esbuild": "^0.28.2",
     "fflate": "^0.8.3"
   },
   "devDependencies": {
-    "@plitzi/sdk-shared": "0.38.11",
+    "@plitzi/sdk-shared": "0.38.13",
     "@types/node": "^26.6.4",
     "eslint": "^9.39.5",
     "eslint-plugin-import": "^2.32.0",

package/skills/plitzi-cli/reference/functions.md

@@ -16,6 +16,10 @@ A space's own server code — TypeScript tasks its actions run as steps, and rou
   the project's own `@plitzi/sdk-server` — `npm install -D @plitzi/sdk-server isolated-vm core-js` first — and sends
   nothing to the space. Credentials are `PLITZI_CREDENTIALS={"stripe":{"apiKey":"…"}}` in `.env` — what `dev` and the
   project's own server hand `ctx.fetch({ credential })`; in the cloud, the space's Credentials.
+- **An action that only runs one task** is `taskAction(tasks.make, { trigger: { type: 'call', access: 'public' } })`
+  (`@plitzi/sdk-authoring`): its input is the task's params, its id `<namespace>-<action>`. A param says what it
+  takes — `required`, `maxLength`, `min`/`max` — and a call outside it is refused with the reason before `run`;
+  `ctx.rateLimit('make', { most: 5, perSeconds: 600, refuse: 'Wait ten minutes' })` refuses over the limit alike.
 - **A run gets 100 ms of CPU and 10 s.** A task that needs more asks with `limits: { cpuMs, wallMs }` (or
   `defineFunctions({ limits })` for all), up to the plan's ceiling; asking above it is a problem the push reports.
 - **What must happen in N seconds whether or not a page is open** — a turn that runs out, a bot's move — is

package/skills/plitzi-cli/reference/plugins.md

@@ -14,7 +14,7 @@ plitzi plugin add ticker --prop interval:number=5000 --prop paused:boolean --tri
 
 **Say its shape and it is written in it**: `--prop name:type=default` (string, number, boolean; `list`/`json` for data
 a binding fills) per attribute — typed, bindable, with a control in its panel; `--trigger onTick:count` per event and
-what a flow reads, fired with its `use<Name>Events()` hook; `--callback reset` per action a flow calls; `--headless`
+what a flow reads, fired with `usePluginTrigger(declaration)` — `fire('onTick', { count })`, typed; `--callback reset` per action a flow calls; `--headless`
 for one with nothing to see. Without them it writes a counter showing the three ways an element talks to a space.
 
 Each is a folder (`src/plugins/SeatPicker/` in a project `create` wrote):
@@ -22,13 +22,14 @@ Each is a folder (`src/plugins/SeatPicker/` in a project `create` wrote):
 | File | What it holds |
 | --- | --- |
 | `SeatPicker.tsx` | the component. Its props ARE the element's attributes; render through `RootElement` |
-| `declaration.ts` | its `type`, the `triggers` (events) it fires, the `callbacks` (actions) it answers, its default attributes — data only |
+| `declaration.ts` | `definePlugin<…Attributes>()({ type, label, attributes, triggers, callbacks })` — the events it fires, the actions it answers, its defaults; the rest derived. Data only |
 | `Settings.tsx` | its panel in the builder |
 | `index.ts` | the three put together |
 
 - **Registered by itself**: every folder of `src/plugins` is, under its name in camelCase (`SeatPicker` → `seatPicker`).
   Elsewhere the command prints the line that registers it (for `render()`, `<PlitziSdk>` or a page server).
-- **Host it** with `custom({ renderType: 'seatPicker', … })` in `src/space/` — or a Custom element in the builder.
+- **Place it** from its declaration in `src/space/`: `const seatPicker = defineElement(declaration)`,
+  then `seatPicker({ id: 'seats', … })` — what `plugin add` and `explain` print. On Plitzi, the builder adds the same.
 - **Checked like a built-in element**: its folder's `declaration.ts` is found by itself and handed to
   `authorSpace(space, { plugins })`: flows on its events, steps to its actions and its attributes are
   refused when wrong; `declaredTrigger(declaration, 'onPick')` and `declaredCallback(declaration, 'reset', { on: 'seats' })`
@@ -50,7 +51,7 @@ plitzi create packages/seat-picker --plugin --name @acme/plitzi-plugin-seat-pick
 
 Its scripts: `start` (the elements inside a space, hot-replaced), `visual`, `typecheck`, `lint`. Add more elements with
 `plugin add` from inside it — they are listed in `src/elements.ts` and `src/declarations.ts`, which the package
-publishes from. A package's element is authored as a TYPE of its own: `defineElement<SeatPickerAttributes>(declaration)`.
+publishes from. A package's element is placed the same way: `defineElement(declaration)`.
 
 ## Building and shipping (`plugin pack`, `plugin upload`)