@plitzi/cli 0.38.13 → 0.38.15

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@plitzi/cli",
-  "version": "0.38.13",
+  "version": "0.38.15",
   "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.13",
+    "@plitzi/sdk-authoring": "0.38.15",
     "chalk": "^6.0.1",
     "commander": "^15.0.0",
     "esbuild": "^0.28.2",
     "fflate": "^0.8.3"
   },
   "devDependencies": {
-    "@plitzi/sdk-shared": "0.38.13",
+    "@plitzi/sdk-shared": "0.38.15",
     "@types/node": "^26.6.4",
     "eslint": "^9.39.5",
     "eslint-plugin-import": "^2.32.0",

package/skills/plitzi-cli/SKILL.md

@@ -22,10 +22,11 @@ npx plitzi element where hero-cta                       # where the code writes
 npx plitzi element edit hero-cta --set content="Hi"     # an attribute written there, checked
 npx plitzi element remove ent-trust                     # an element taken out, with what only it used
 npx plitzi element move ent-faq --before ent-pricing    # an element put elsewhere among its siblings
-npx plitzi verify                               # left passing? author, lints, types, format, pages
+npx plitzi verify                               # left passing? author, lints, types, tests, format, pages
 npx plitzi page check -- /about --width 1440,390     # whether a page is whole, in text
-npx plitzi explain navigate                     # what a name means: element, step, code, any export
+npx plitzi explain navigate                     # what a name means: element, step, code, any @plitzi export
 npx plitzi doctor                               # whether the project is whole; --fix the simple parts
+npx plitzi cert                                 # HTTPS for a phone on the Wi-Fi (with HOST=0.0.0.0)
 npx plitzi upgrade                              # the project up to this CLI (--write)
 npx plitzi feedback                             # a report to Plitzi, for the person to send as a link
 ```

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

@@ -17,7 +17,8 @@ A space's own server code — TypeScript tasks its actions run as steps, and rou
   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
+  (`@plitzi/sdk-authoring`): its input is the task's params, its id `<namespace>-<action>` — and a plugin runs it typed by
+  both, `useServerAction<typeof make>(make.id)`: one operation is one task, never a `case` in one route. 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

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

@@ -14,7 +14,9 @@ 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 `usePluginTrigger(declaration)` — `fire('onTick', { count })`, typed; `--callback reset` per action a flow calls; `--headless`
+what a flow reads, fired with `usePluginTrigger(declaration)` — `fire('onTick', { count })`, typed, and read by
+naming the step: `[named('tick', on('onTick')), …({ value: '{{ tick.count }}' })]`; `--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):

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

@@ -13,6 +13,7 @@ What a project gives you, so you use it rather than rebuild it:
 | --- | --- |
 | `start` | serve it — in client mode Vite, which hot-replaces on save. The server prints only what goes wrong; `-- --verbose` adds every request |
 | `start:dev` | server mode: restarted on a save to its code; a plugin is swapped in the open page. Options in `src/config/serverOptions.ts`, actions in `src/actions/`; `plitzi/` is the CLI's, never edit it |
+| `start:dev-inspect` | `start:dev` with Node's inspector on 127.0.0.1:9229, for a debugger to attach to the server |
 | `author` | author `src/space/`: every problem at once (file:line, what to change), then the suggestions (`[suggest]`: a shorter way to the same page, the most elements saved first); `-- --json` for a tool |
 | `lint:space` | how `src/space/` is written, at file:line, and authoring's suggestions; `-- --max-warnings 0`. On purpose: `// plitzi-lint-disable-next-line <code> -- why` (a suggestion: `quiet` on its element) |
 | `npx plitzi space fix` | what `author` reports that has one fix, as a diff of your source; `--write` writes it, formatted, and keeps it only if the space then authors with it gone and nothing new |
@@ -24,7 +25,13 @@ What a project gives you, so you use it rather than rebuild it:
 | `typecheck`, `lint`, `format` | before calling a change done |
 
 **Which port.** `start` takes 8080, or the next free one — printed, and written to `tmp/dev-server.json` for `check`,
-`shot` and `visual`. `PORT` chooses one (a taken one is then an error). `/health` answers with the space's name.
+`shot`, `verify` and `visual`, with the scheme it answers on (`https` once it serves a certificate; the local one is
+accepted on this machine only). `PORT` chooses one (a taken one is then an error). `/health` answers with the space's
+name.
+
+**On a phone.** `HOST=0.0.0.0` in `.env` opens it to the network, and `plitzi cert` serves it over HTTPS (mkcert;
+`TLS_CERT`, `TLS_KEY`) — over http a phone's browser gives the page no microphone, camera or clipboard. Ask before
+either: the first lets anyone on that network open it, the second trusts an authority on the machine (its password).
 
 Data with no backend, server mode: `src/data/*.json`, never served — a provider with `runtime: 'server'` and `query:
 '/data/x.json'` reads it on the server. Client mode: `public/data/`, fetched — public. Learn a file's fields with