@plitzi/plitzi-builder 0.38.14 → 0.38.16

package/CHANGELOG.md

@@ -1,5 +1,198 @@
 # @plitzi/plitzi-builder
 
+## 0.38.16
+
+### Patch Changes
+
+- 9cfdccb: ## Security
+
+  - **A site's credential reads nothing of the space over MCP** (`@plitzi/sdk-mcp`): the `render` token every published
+    page embeds — and a self-hosting `host` key — resolved to a grant naming the space, and the MCP served every read
+    under it: the unpublished draft, the change history with who made each change and every value before and after, the
+    functions' source, the space's private data, its action documents and connectors. Only an `agent` grant attaches a
+    space now; any other is a connection with no space (`plitzi_render` and the public guides), told so in the words
+    `NO_SPACE_ATTACHED` already uses. A deployment whose `getGrant` answered other scopes for reading must issue agent
+    grants for them.
+
+  ## Agents
+  - **`plitzi space watch`** (`@plitzi/cli`): the space read again on every save of `src/space/`, `src/plugins/`,
+    `src/data/` or `public/data/`, and only what changed said — what the save did to the space element by element, the
+    findings and warnings it brought and fixed (one that only moved down its file is the same one), a save that changed
+    nothing, or that the space stopped authoring and why. `--json` is one event a line (`ready`, `pass`, `refused`,
+    `error`), for an agent to run in the background instead of `author` and `space lint` after every edit. Each pass reads
+    the space in a process of its own (`space watch-pass`, hidden). `space lint`'s reading is `spaceFindings`, shared.
+  - **A space's activity, followed** (`@plitzi/sdk-shared`, `@plitzi/sdk-mcp`, `@plitzi/cli`): what happened on a space
+    after a cursor — its draft changed (a person in the builder, an agent, the autofix), a version went out, a server
+    action failed or was refused — and, with nothing yet, waited for, up to 50 s. One vocabulary,
+    `@plitzi/sdk-shared/activity` (`SpaceActivity`, `SpaceActivityPage`, `activityLine`, `isSpaceActivityPage`, the
+    limits); the reader's own writes left out and counted (`skippedMine`), `mine` keeps them.
+    - **`plitzi_activity { after, wait, limit, mine }`** (`@plitzi/sdk-mcp`), on the new `getActivity` adapter
+      (`SSRAdapters`). The listing budget is 78k (was 77k) for it.
+    - **`plitzi space activity [--follow] [--after <cursor>] [--mine] [--limit <n>] [--json]`** (`@plitzi/cli`), over
+      the platform's `GET /spaces/:spaceId/activity`; `--follow` stays, one page a line with `--json`, and asks again
+      when the platform does not answer.
+    - **The people in the builder see the agent work** (`@plitzi/sdk-server`, `@plitzi/sdk-shared`, `@plitzi/sdk-mcp`,
+      `@plitzi/plitzi-builder`): an agent grant carries the application the member connected (`Grant.client`,
+      `StoredSpaceToken.client`, `SSRGrant.client`), and every MCP write `SSRWriteContext.client` — the history's
+      `client` for an agent, which was never set. A collaborator may be an agent (`SubscriptionCollaborator.agent`): the
+      builder draws it as a robot, names it `Claude · for ana` (`collaboratorTitle`) in the header, on the canvas and in
+      its notices. The deployment announces it — Plitzi's joins it on a write, selects what it changed, and lets it go
+      after a minute of nothing. `activityLine` names it the same way (`Claude for ana over the MCP, …`), so
+      `plitzi space activity` says which application wrote.
+    - A tool may declare `documents: false` (`ToolSpec`): the host loads none of the space for it, and passes the call's
+      abort signal through `ToolContext.activity`.
+
+  ## Authoring
+  - **A file that does not parse is said at its line under any loader** (`@plitzi/sdk-authoring`): `moduleProblem` read
+    the first line of the error, and an esbuild transform (tsx, vitest) puts only `Transform failed with 1 error:` there
+    — the file, line and what is wrong are on the next. A line of the message that points at a file of the project is
+    now the problem (`src/space/hero.ts:139: Expected "}" but found ";"`), the project's root matched as given and as it
+    is on disk (`/var/…` and `/private/var/…` on macOS).
+
+  ## Testing
+  - **`unusedPort` is chosen where the system never hands one out** (`@plitzi/sdk-server`): it answered a port the system
+    had just handed out (`listen(0)`), from the ephemeral range every outgoing connection takes its local port from — so
+    another worker's request could take it before the test listened, and CI failed `runtime.test.ts` with `EADDRINUSE`
+    (the page server then ends the process). It is a free port below that range now, at random, checked first.
+
+  ## Docs
+  - **A self-hosted runtime's endpoints go in `data`**, as 0.38.15 moved them: `docs/en/runtimes.md`, the
+    `10-runtime` example and the website still put `served.stage` in `preAuth`, before the cross-site guard.
+  - New: `docs/en/activity.md`; `space watch` in `docs/en/agent-tooling.md`'s loop; the CLI README, the CLI skill, the
+    generated project's `AGENTS.md`, the MCP guide and README.
+
+- Updated dependencies [9cfdccb]
+  - @plitzi/plitzi-sdk@0.38.16
+  - @plitzi/sdk-auth@0.38.16
+  - @plitzi/sdk-authoring@0.38.16
+  - @plitzi/sdk-dev-tools@0.38.16
+  - @plitzi/sdk-elements@0.38.16
+  - @plitzi/sdk-event-bridge@0.38.16
+  - @plitzi/sdk-interactions@0.38.16
+  - @plitzi/sdk-navigation@0.38.16
+  - @plitzi/sdk-plugins@0.38.16
+  - @plitzi/sdk-schema@0.38.16
+  - @plitzi/sdk-shared@0.38.16
+  - @plitzi/sdk-style@0.38.16
+  - @plitzi/sdk-variables@0.38.16
+
+## 0.38.15
+
+### Patch Changes
+
+- 6cdd5cf: ## Security
+
+  - **A write another site caused is refused, cookie or none** (`@plitzi/sdk-server`, `@plitzi/sdk-shared`): the page
+    server guarded nothing it answers past `/auth` — a server action (`/_action`), a realtime publish, a space's `/fn/`
+    route, its runtime's endpoints, the deployment's own `data` stages, the adapter-only `loginPath`, `logoutPath` and
+    `exchangePath`. A plain `text/plain` POST from any page open in the same browser ran them, with the visitor's session
+    cookie when there was one (`SameSite=None` off this machine) and, in a project nobody signs in to, as whoever holds
+    the server's own credentials. Every unsafe request a browser says another site caused (`Sec-Fetch-Site: cross-site`,
+    or a foreign `Origin`) is now refused `403 reason: 'foreign'`, saying how to allow it: `crossSiteWrites.origins`
+    (with `auth`, `identity.platformOrigins` too) and `crossSiteWrites.paths` for a form other sites post to by design.
+    `Authorization`, and callers that are not browsers — webhooks, scripts — pass as before. One rule for this and the
+    sign-in check (`crossSiteRequest`, `csrf.ts`). A self-hosted runtime's endpoints now sit where the platform forwards a
+    space's — after the auth chain and this guard (`data`, was `preAuth`).
+
+  ## Testing
+  - **`page check` and `page shot` anywhere the project is served** (`@plitzi/cli`): `--url <origin>` for a second server
+    of it, staging or a deploy, instead of `npm start`'s port; `page check --space <module>` holds the pages to that space
+    instead of the project's — an agent's page — authored with `authorIsolated`.
+  - **A route with a query is checked as its page** (`@plitzi/cli`): `page check "/?v=2"` matched the query as part of
+    the path, found no page, and checked the space's "not found" page in its place.
+
+  - **What an element that chooses its children draws is checked** (`@plitzi/sdk-authoring`, `@plitzi/cli`): with
+    `choosesChildren`, the page checks owed none of its children — and checked none of them either: a dashboard drawing
+    three panels reported `checked: 1`. Each child it may draw, and what is inside one under no condition of its own,
+    now carries `shownWith` (the child it comes with) on its handle: once that child is on screen it and everything
+    named in it are owed like the rest of the page, and `checked` counts them. `onScreenIfChosen(handles, page)` lists
+    them.
+  - **A page that met a server error is looked at once more** (`@plitzi/cli`): `page check` and `verify` failed a page
+    for a `500` from somebody else's service having a bad second (`/fn/<space>/weather`), and passed on the next run with
+    nothing changed. A page whose requests got a `5xx` is checked again once; its report is the second look, and says
+    what failed the first time (`retriedAfter`). A `4xx` fails the same way twice, and is never retried.
+
+  ## Plugins
+  - **`useNotify`** (`@plitzi/plitzi-sdk`): a plugin shows the page's notifications — `notify('Deleted 79 recordings', {
+appearance: 'danger' })` — the same toasts an `addNotification` step shows, in the space's theme and `notifications`
+    look, with no trigger, flow or `window` event of the space's to wire. The step's vocabulary (`NOTIFICATION_PLACEMENTS`,
+    `NOTIFICATION_APPEARANCES`, `NOTIFICATION_DEFAULTS`) is one list in `@plitzi/sdk-shared`, read by both.
+  - **`appearance: 'danger'` looks like one** (`@plitzi/plitzi-sdk`): it reached the toast library as a type it does not
+    know, so a danger notification showed neither the error icon nor the colour `notifications.danger` sets.
+    A value a notification does not take — from a flow, or a plugin in plain JavaScript — is set aside by name and said
+    in the console, rather than shown as the default in silence (`readNotificationOptions`, `@plitzi/sdk-shared`).
+  - **`useServerAction`** (`@plitzi/plitzi-sdk`, `@plitzi/sdk-authoring`, `@plitzi/sdk-interactions`,
+    `@plitzi/sdk-server`): a plugin runs one of the space's server actions, awaited —
+    `useServerAction<typeof habitDone>('habits-done')({ id })` answers `{ ok, output }` or `{ ok: false, reason, error }`
+    — through the `runServerAction` step itself: the same access, refusals, session handling and dev-tools entry.
+    `defineAction` keeps the literal types of its `call` way in, so the input is typed by the fields it declares (the
+    required ones required); `taskAction` types both ends from the task's `run`, and `FunctionTask<T, R>` takes what
+    `run` answers. `CallInputOf` / `CallOutputOf` read them. One operation is one action, never a `case` in one route.
+    What a run answers is typed (`ServerActionStatus`): a status the server never uses reads as a run that did not
+    complete, never as one that did.
+    The key those types ride under (`CALL_TYPES`) is exported, by `@plitzi/sdk-shared` and `@plitzi/sdk-authoring` with
+    `TypedActionEntry`, `CallInputOf` and `CallOutputOf`: a package that emits declarations could not write the type of an
+    action it exports (`TS4023` on every `export const actions = [defineAction(…)]`).
+  - **A plugin is drawn on the server first** (docs): a preference per device belongs in kept state (`keepState`,
+    `paintedState`) as a bound prop, never read from `localStorage` while rendering — React discards the whole tree on the
+    mismatch, and only in the browser of whoever saved something. `@plitzi/plitzi-ui` is not the page's: a plugin
+    importing it bundles its own copy, with its own contexts and its own look. The authoring skill's `plugin-reach.md`
+    says what a plugin says and to whom: a notification, another element (an event and the space's flow), a server
+    action, shared state, other pages.
+
+  ## Realtime
+  - **A channel that retains** (`@plitzi/sdk-shared`, `@plitzi/sdk-server`, `@plitzi/sdk-elements`): declared
+    `retain: true` (with `publish: 'server'`, which authoring requires), the server keeps the latest message of each type
+    on a topic — said by `ctx.publish` or a flow's `realtime.publish` — and hands them to every page that joins, marked
+    `retained`. A page reads them as `<channel>.retained.<type>`, a plugin as `useChannel(topic).retained`, the newest of
+    a type holding whichever order they arrive in; `null` forgets a type. Kept in the store the actions' `kv` uses (beside
+    the grants, by compare-and-swap), so every replica hands out the same; a topic keeps at most 64 types and 512 KB, and
+    a publish past that is refused before anything is sent. State every screen shares is one publish and one binding —
+    no kv key, initial read or copy in `state` of the project's own. The fleet store `realtime.grants` is now
+    `realtime.kv`.
+  - **The MCP writes every field a channel takes** (`@plitzi/sdk-mcp`): `patchSettings`'s channel had no `grant` — which
+    the guide taught — nor `retain` or the limits, so an agent could not declare a private channel at all. All are there
+    now, and the guide says what `retain` is for and that `channel_<id>.retained` holds it.
+
+  ## Authoring
+  - **`plitzi explain` knows every `@plitzi` package installed** (`@plitzi/cli`): a name that was not
+    `@plitzi/sdk-authoring`'s (`createServer`, `createJsonAdapters`, `useChannel`) was answered as the project's own code,
+    to `grep` in `src/`. It is read from the published types of every one installed, through their re-exports and entry
+    points (`@plitzi/sdk-server/handlers`), and a name two packages export — `createServer` is sdk-server's and sdk-mcp's
+    — is answered with both.
+
+  - **A space module somebody else wrote, authored where it reaches nothing** (`@plitzi/sdk-authoring`):
+    `authorIsolated(file, { timeoutMs })` of `@plitzi/sdk-authoring/node` runs `authorSpace` on it in a process Node's
+    permission model holds to reading the module's folder and its packages — no file written, no process started, no
+    variable of the caller's environment — kills one that runs too long, and validates what it answers again, so a forged
+    answer gains nothing. A refusal comes back as `authorSpace` says it, with the problems as data.
+  - **Pages an agent writes, served** (`@plitzi/sdk-server`): `createAuthoringHost({ dir, frameAncestors })` serves each
+    space it is handed at an address of its own (`put(space, { id }) → /?__pt=<id>`) as a draft of its one space, kept in
+    `dir` across restarts; `drop(id)` forgets one, and anything else answers `404` saying where the pages are.
+  - **A space is chosen by host or credential** (`@plitzi/sdk-server`, docs): `getSpaceDeployment` is asked on every
+    request, and what a page fetches after it carries nothing of its address but the host — a space chosen by the page's
+    query or path lost everything it asked for, and `/_plitzi/space/<hash>.json` answered a bare `404`. The contract and
+    the README say so (the README offered "by path prefix"), and that `404` says why.
+
+  - **`plitzi explain on` says how to read what a trigger carries** (`@plitzi/sdk-authoring`): its doc sat above a
+    helper, so `explain` printed only the signature. It now leads with `[named('picked', on('onPick')), …('{{ picked.seat
+}}')]`, and the CLI skill's plugin section says the same.
+
+- Updated dependencies [6cdd5cf]
+  - @plitzi/plitzi-sdk@0.38.15
+  - @plitzi/sdk-auth@0.38.15
+  - @plitzi/sdk-authoring@0.38.15
+  - @plitzi/sdk-dev-tools@0.38.15
+  - @plitzi/sdk-elements@0.38.15
+  - @plitzi/sdk-event-bridge@0.38.15
+  - @plitzi/sdk-interactions@0.38.15
+  - @plitzi/sdk-navigation@0.38.15
+  - @plitzi/sdk-plugins@0.38.15
+  - @plitzi/sdk-schema@0.38.15
+  - @plitzi/sdk-shared@0.38.15
+  - @plitzi/sdk-style@0.38.15
+  - @plitzi/sdk-variables@0.38.15
+
 ## 0.38.14
 
 ### Patch Changes

package/dist/modules/Collaboration/CollaborationHelper.d.ts

@@ -1,4 +1,4 @@
-import { SubscriptionCollaboratorElementState } from '@plitzi/sdk-shared';
+import { SubscriptionCollaborator, SubscriptionCollaboratorElementState } from '@plitzi/sdk-shared';
 /**
  * The coordinate protocol between collaborators, both ends of it in one place.
  *
@@ -51,3 +51,8 @@ declare const resolveElementState: (elementState: SubscriptionCollaboratorElemen
     selected: string | undefined;
 };
 export { collaboratorAnchorSelector, readCursorAnchor, resolveCursorPosition, resolveElementState };
+/**
+ * What a collaborator is called on the canvas, in the header and in the notices: a person by their name, an agent by
+ * its application and whom it works for (`Claude · for ana`).
+ */
+export declare const collaboratorTitle: ({ user, agent }: Pick<SubscriptionCollaborator, "user" | "agent">) => string;

package/dist/modules/Collaboration/CollaborationHelper.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/modules/Collaboration/components/CollaboratorAvatar/CollaboratorAvatar.d.ts

@@ -4,7 +4,10 @@ export type CollaboratorAvatarProps = {
     color?: string;
     firstName: string;
     surName: string;
+    /** An agent writing over the MCP: drawn as one, not as a person's initials. */
+    agent?: boolean;
+    title?: string;
 };
-/** The collaborator's initials in their presence color, as shown in the app header. */
-declare const CollaboratorAvatar: ({ ref, color, firstName, surName }: CollaboratorAvatarProps) => import('react').JSX.Element;
+/** The collaborator's initials in their presence color, as shown in the app header — or, for an agent, a robot. */
+declare const CollaboratorAvatar: ({ ref, color, firstName, surName, agent, title }: CollaboratorAvatarProps) => import('react').JSX.Element;
 export default CollaboratorAvatar;

package/dist/package.json.d.ts

@@ -1,6 +1,6 @@
 declare const _default: {
   "name": "@plitzi/plitzi-builder",
-  "version": "0.38.14",
+  "version": "0.38.16",
   "homepage": "./",
   "license": "AGPL-3.0",
   "files": [