@zibby/skills 2.0.4 → 2.0.5

package/docs/templates/sidecars.md

@@ -0,0 +1,163 @@
+---
+sidebar_position: 7
+title: sidecars & sidecarSpecs
+---
+
+# `sidecarSpecs` and `sidecars`
+
+## What it is
+
+Some agents need a long-lived service running beside them: a browser, a vector
+database, a bridge that turns a REST API into tools. Those are **sidecars**.
+
+`sidecarSpecs` carries the **whole specification** — name, a checksum-pinned
+image on Zibby's own CDN, the port, the per-tenant config it reads — rather than
+a name the platform must already know. That is what makes a brand-new
+sidecar-backed agent *a template and nothing else*.
+
+`sidecars` is the short form: a name for a sidecar the platform already ships.
+
+At deploy the control plane fetches the image, **verifies its SHA-256**, loads it
+and starts it on the internal network. The agent's run container never pulls
+anything and never dials it directly.
+
+:::caution Self-hosted only
+Sidecar hosting is not built on Zibby Cloud yet. A template that declares one is
+marked self-hosted-only and the cloud catalog will not deploy it. There is one
+exception, [below](#the-one-cloud-exception).
+:::
+
+## Syntax
+
+```js
+spec: {
+  selfHostOnly: true,
+  sidecarSpecs: [{
+    name: 'openapi-mcp',
+    version: '0.2.3',
+    s3Url: 'https://dl.zibby.app/sidecars/openapi-mcp/0.2.3.tar.gz',
+    sha256: 'caa4ebfc04acf725f3afd0afa8d0ddf942a600eea364ec821351e3f19af53b4f',
+    bytes: 2500336,                        // informational — shown in the dialog
+    arch: {
+      arm64: {
+        s3Url:  'https://dl.zibby.app/sidecars/openapi-mcp/0.2.3-arm64.tar.gz',
+        sha256: '38fe9ca08961eed8c2768e3d036da6deaf4ca2384543ea243deb9685a77ca566',
+        bytes:  2305415,
+      },
+    },
+    port: 8080,
+    healthPath: '/health',
+    warm: true,
+    requestConfigKeys: ['OPENAPI_APIS', 'API_ROOT', 'API_TOKEN'],
+  }],
+  // NO `sidecars: ['openapi-mcp']` — a full spec implies its own name.
+}
+```
+
+## Properties
+
+| Name | Type | Required | Allowed values | Default | Update behavior |
+|---|---|---|---|---|---|
+| `name` | string | **Yes** | lowercase, starts with a letter, letters/digits/hyphens, 2–31 chars. May not shadow a built-in name | — | Re-applied |
+| `port` | integer | **Yes** | 1–65535 | — | Re-applied |
+| `sha256` | string | **Yes** | 64 hex characters | — | Re-applied — a new checksum pulls a new image |
+| `s3Url` | string | **Yes** | an allow-listed host | — | Re-applied |
+| `version` | string | No | a version string you own | none | Re-applied; shown in the Update dialog |
+| `arch.<arch>` | object | No | `{ s3Url, sha256, bytes }`, validated identically | none | Re-applied |
+| `healthPath` | string | No | a path | `/health` | Re-applied |
+| `warm` | boolean | No | | `false` | Re-applied |
+| `bytes` | integer | No | **informational only** — never checked against the download | none | Card only |
+| `dataPath` | string | No | an absolute path — and it must be `/data` | none | Re-applied |
+| `dataPurpose` | string | No | `data`, `credentials` | `data` | Re-applied — decides what uninstall deletes |
+| `requestConfigKeys` | string[] | No | Env keys read **per request** from the declaring agent's own encrypted bag | `[]` | Re-applied |
+| `envKeys` | string[] | No | container-wide environment | `[]` | Re-applied |
+| `publicPaths` | string[] | No | prefixes exposed **anonymously** on your box's public origin — refused by default | none | Re-applied |
+| `storeTypes` | string[] | No | store types this sidecar serves | `[]` | Re-applied |
+| `instancePerAgent` | boolean | No | | `false` | Re-applied |
+| `memoryBytes` / `pidsLimit` | integer | No | 64 MiB – 8 GiB / 16 – 4096 | platform defaults | Re-applied |
+
+`sidecars` is simply `string[]`. A name nobody knows is skipped with a warning,
+not an error.
+
+## One shared service, many isolated tenants
+
+A sidecar is **one process hosting N isolated tenants**, not one container per
+agent. Everything that differs per agent — data *and* configuration — is
+isolated:
+
+- **Data** is keyed by a server-derived tenant key, so different tenants run in
+  parallel and the same tenant serialises.
+- **Configuration and secrets** come from `requestConfigKeys`, injected **per
+  request** from the declaring agent's encrypted Env bag — never as
+  container-wide environment.
+
+That last point is the one people get wrong. Putting an OAuth client id and
+secret in `envKeys` means two projects with different apps collide, and the fix
+is not "error on conflict" — it is per-request injection.
+
+## Gotchas
+
+:::danger A full spec implies its name
+If you declare `sidecarSpecs`, do **not** also list that name in `sidecars`.
+The name is taken from the spec. Repeating it is a second place to keep in sync.
+:::
+
+:::danger Durable state lives at `/data` — one path, every sidecar
+The `dataPath` you declare and the path your app actually writes must be the
+**same string**. Nothing cross-checks them, so a mismatch is silent: the data
+lands in the container's throwaway layer and dies with it, while the volume you
+declared sits empty. A live OAuth token store was lost exactly that way. Do not
+"fix" a mismatch by injecting a path variable — change one of them.
+:::
+
+**A checksum pins bytes, not a CPU.** There is deliberately no fallback between
+architectures: an x86 image verifies perfectly on an ARM box and then dies with
+`exec format error`. Publish and pin each architecture, or that architecture
+fails loudly.
+
+**A URL with no checksum fails closed.** The image is never loaded unverified.
+
+**A template-carried sidecar does not auto-update.** Its version belongs to you:
+it moves when your `version`/`sha256`/`s3Url` move and the user takes the
+Update. Platform-shipped sidecars follow a CDN channel instead.
+
+:::danger A sidecar with no authentication of its own must not declare `publicPaths`
+`publicPaths` exposes those prefixes **anonymously** on your box's public
+origin, with no platform authentication added. Agents and the chat assistant
+reach a sidecar over the internal network and do not need it.
+
+Declare an [`entryPoints.mcp`](./surfaces.md) with `auth: 'bearer-pat'` instead,
+and let the platform's own authenticated endpoint forward to you — it adds the
+token check, the ownership check, and per-request tenant configuration.
+
+It also costs you cloud deployability. See below.
+:::
+
+**`warm: true` is sometimes required, not an optimisation.** A sidecar is
+started by the boot pre-warmer, by a public-path proxy, or by the store router.
+An agent that is dialled directly as an MCP server matches none of those, so
+without `warm` it would never be running.
+
+**Share a spec, do not copy it.** If several templates use the same sidecar,
+import the spec from one place. Two inlined copies at different versions will
+fight, and the last deploy wins — which can silently downgrade the shared engine.
+
+## The one cloud exception
+
+A self-hosted-only template **is** deployable on Zibby Cloud when it is
+browser-host-servable — judged from the declaration, never from the name:
+
+- every carried spec is fully pinned (`name`, `version`, `port`, `s3Url`,
+  `sha256`), **and**
+- no spec declares `publicPaths`, **and**
+- the template declares an `entryPoints.mcp` pointing at one of its sidecars.
+
+One `publicPaths` entry costs the template its cloud deployability.
+
+## See also
+
+- [`surfaces` and `entryPoints`](./surfaces.md)
+- [`stores`](./stores.md) — a store type brings its own sidecar; do not name it
+  twice.
+- [Bring your own sidecar](../self-host/custom-sidecars.md) — the operator route,
+  for a service that is not a catalog agent.

package/docs/templates/stores.md

@@ -0,0 +1,113 @@
+---
+sidebar_position: 3
+title: stores
+---
+
+# `stores`
+
+## What it is
+
+Durable storage the agent needs. Declared **on a node**, not in the
+`spec` block.
+
+At deploy the platform creates (or re-uses) one store per declaration and writes
+its id into the agent's encrypted Env bag under the name you chose. Your code
+never sees an id in the template — it asks for the name and gets the resource.
+
+This is the reference implementation of the naming rule: declare a name, the
+platform binds it, the consumer resolves it late.
+
+## Syntax
+
+```js
+// nodes/ingest-node.js
+import { SKILLS } from '@zibby/core';
+
+export const ingestNode = {
+  name: 'ingest',
+  skills: [SKILLS.DATASET_STORE],        // required — see gotchas
+  stores: [
+    { name: 'knowledge_docs', type: 'docs',   description: 'Verbatim markdown archive' },
+    { name: 'knowledge_meta', type: 'sqlite', description: 'Per-document metadata',
+      schema: {
+        tables: {
+          knowledge_meta: {
+            ddl: 'CREATE TABLE IF NOT EXISTS knowledge_meta (id TEXT PRIMARY KEY, title TEXT)',
+          },
+        },
+      },
+    },
+  ],
+};
+```
+
+The minimal form is just a name and a description:
+
+```js
+stores: [{ name: 'scorecards', description: 'Per-commit engineering scorecard' }],
+```
+
+## Properties
+
+| Name | Type | Required | Allowed values | Default | Update behavior |
+|---|---|---|---|---|---|
+| `name` | string | **Yes** | lowercase, starts with a letter, letters/digits/underscore, ≤ 41 chars. **Unique across the whole agent**, not just the node | — | Re-applied (idempotent). A **new** name creates a **new** store; renaming leaves the old one behind |
+| `type` | string | No | `dataset`, `sqlite`, `file`, `docs`, `postgres` (self-hosted only) | `dataset` | Re-applied. An unknown type fails the deploy loudly |
+| `description` | string | No | any — it is what the agent's store catalogue shows the model | none | Re-applied |
+| `schema` | object | No | `{ tables: { <name>: { ddl } } }` — **`sqlite` only**. Each `ddl` must begin `CREATE TABLE IF NOT EXISTS` and the table it creates must match the key | none | Re-applied, but an existing table is never altered |
+
+## Store types
+
+| Type | Use it for |
+|---|---|
+| `dataset` | append-and-query records — the default |
+| `sqlite` | relational data with a schema you declare |
+| `file` | opaque blobs |
+| `docs` | a verbatim document archive |
+| `postgres` | a vector knowledge base (self-hosted only) |
+
+## What deploy does
+
+1. Computes a stable key from the agent, the node and the name, so re-deploying
+   re-uses the same store instead of creating another one.
+2. Creates the store if it does not exist.
+3. Writes `ZIBBY_STORE__<name> = <store id>` into the encrypted Env bag.
+4. Creates any declared SQLite tables.
+5. Seeds the node's store catalogue so the model can see what it has.
+
+At run time the store skill turns those environment entries back into names, and
+sub-graph children inherit them.
+
+## Gotchas
+
+:::danger A `stores` block on a node with no store skill is silently ignored
+The same node must also declare a store skill (`dataset-store`, or `gbrain` for
+a vector KB) in its **`skills`** array. Putting it in `optionalSkills` instead
+provisions nothing — no store, no error, no warning.
+:::
+
+**Names are unique per agent, not per node.** Two nodes cannot each declare a
+store called `results`.
+
+**If you re-point a store by hand, that wins forever.** Setting
+`ZIBBY_STORE__<name>` yourself to something other than the provisioned id tells
+the platform this is deliberate: it stops re-binding the name and stops applying
+the declared schema.
+
+**A schema on a non-SQLite store is a hard error at deploy**, not a warning.
+
+**Declared tables are created, never migrated.** If a table already exists it is
+left exactly as it is, even when your `ddl` has changed. Adding a column is your
+migration to write.
+
+**A store type brings its own service.** `postgres` pulls the vector-KB engine
+by itself — do not also name it under [`sidecars`](./sidecars.md).
+
+**`postgres` cannot be deployed on Zibby Cloud today.** Templates that need it
+are marked self-hosted-only.
+
+## See also
+
+- [Node declarations](./node-declarations.md) — the store skill is a
+  precondition, not a nicety.
+- [Sidecars](./sidecars.md)

package/docs/templates/surfaces.md

@@ -0,0 +1,184 @@
+---
+sidebar_position: 6
+title: surfaces & entryPoints
+---
+
+# `surfaces` and `entryPoints`
+
+Two blocks, one subject: **which channels your agent offers, and where each one
+lives.**
+
+- `surfaces` — *which* channels the agent's page should show.
+- `entryPoints` — *where* a channel lives when it is not served by the platform
+  itself, and every word the card shows.
+
+---
+
+## `surfaces`
+
+### What it is
+
+The deployed agent's page renders one section per interaction channel.
+`surfaces` says which of them are meaningful, so a pure knowledge-base agent
+does not show a Trigger button that does nothing.
+
+### Syntax
+
+```js
+spec: { surfaces: ['mcp', 'connect'] }
+```
+
+### Properties
+
+| Name | Type | Required | Allowed values | Default | Update behavior |
+|---|---|---|---|---|---|
+| `surfaces` | string[] | No | `cli`, `webhook`, `schedule`, `mcp`, `connect` | `['cli','webhook','schedule','mcp']` | Re-applied |
+
+| Value | Meaning |
+|---|---|
+| `cli` | started from the command line |
+| `webhook` | started by an inbound HTTP call |
+| `schedule` | started by cron |
+| `mcp` | a machine endpoint an MCP client attaches to |
+| `connect` | a public page a **human opens in a browser** to link their own account — an OAuth sign-in, a device pairing, a licence activation |
+
+`connect` is not a webhook: nothing third-party posts to it and it starts no run.
+
+Unknown values are ignored. Declaring nothing gives you the four standard
+channels — **not** all five, because `connect` is opt-in by design.
+
+### Use cases
+
+| Agent shape | Declare |
+|---|---|
+| An ordinary triggerable workflow | nothing |
+| A pure store — running it directly is a no-op, it is driven over MCP | `['mcp']` |
+| A service a person signs into, then uses from their editor | `['mcp', 'connect']` |
+
+### Gotchas
+
+Declaring `mcp` does not create an endpoint — it says the agent has one. The
+endpoint still has to exist.
+
+---
+
+## `entryPoints`
+
+### What it is
+
+For a channel that need not be served by the platform, `entryPoints` names which
+service serves it and at which path. **The URL itself is derived when the page
+is read** — from the service's resolved public mount and your installation's
+origin. No template ever writes a URL down.
+
+For `connect` it also carries every word on the card, because the renderer has
+none of its own.
+
+### Syntax
+
+An MCP endpoint the platform authenticates and forwards to a service:
+
+```js
+spec: {
+  surfaces: ['mcp'],
+  entryPoints: {
+    mcp: {
+      sidecar: 'openapi-mcp',
+      path: '/mcp',
+      auth: 'bearer-pat',
+      label: 'MCP endpoint for the APIs this agent bridges',
+    },
+  },
+}
+```
+
+A sign-in the platform drives, on an agent with no service container at all:
+
+```js
+spec: {
+  surfaces: ['mcp', 'connect'],
+  entryPoints: {
+    connect: {
+      kind: 'oauth',
+      server: 'figma',                  // a name from this agent's own remoteMcp block
+      label: 'Connect your Figma account',
+      button: 'Connect',
+      buttonDisconnect: 'Disconnect',
+      disconnectConfirm: 'Disconnect Figma? The stored sign-in is deleted.',
+      connectedLine: 'Connected to Figma as {account}.',
+    },
+    // NO `mcp` entry — the absence IS the declaration. See below.
+  },
+}
+```
+
+### Properties
+
+Only `mcp` and `connect` can be redirected. `cli`, `webhook` and `schedule` are
+platform mechanics with no alternative home.
+
+| Name | Type | Required | Allowed values | Default | Update behavior |
+|---|---|---|---|---|---|
+| `sidecar` | string | **Yes**, except for `connect` with `kind: 'oauth'` | a service this agent declares, or one the platform ships | — (entry is dropped without it) | Re-applied |
+| `path` | string | **Yes**, same exception | must start with `/`; `..` is refused | — | Re-applied |
+| `auth` | string | No | `bearer-pat`, `connect-bearer`, `none` | `connect-bearer` for `mcp`, `none` for `connect` | Re-applied |
+| `label` | string | No | any | none | Card only |
+| `kind` (connect) | string | No | `sidecar-page`, `oauth` | `sidecar-page` | Re-applied |
+| `server` (connect + `oauth`) | string | **Yes** for that kind | a name from `remoteMcp` | — | Re-applied |
+| copy (`button`, `buttonDisconnect`, `disconnectConfirm`, `disconnectedLine`, `waitingLine`, `connectedLine`, `note`) | string | No | `{account}` is substituted | none — a field you omit renders nothing | Card only |
+
+### `auth` names what the CALLER presents
+
+| Value | The caller presents |
+|---|---|
+| `bearer-pat` | a Zibby access token — the platform authenticates and forwards |
+| `connect-bearer` | the token this agent's own sign-in handed the user |
+| `none` | nothing — the surface authenticates the caller itself |
+
+:::warning A misspelt `auth` is silently corrected, not rejected
+An unrecognised value falls back to the channel's default, so a typo quietly
+describes an authentication your endpoint does not use. Spell it exactly.
+:::
+
+### An absent `entryPoints.mcp` is itself a declaration
+
+Leave it out and **the platform serves the surface itself**, at the agent's own
+authenticated MCP address, with a Zibby bearer token.
+
+That is the right choice whenever your service has no authentication of its own.
+Naming a source when you did not need to is how an endpoint gets taken away from
+the sign-in that feeds it: the declared service wins the address and answers
+every call with its own "missing token".
+
+:::tip One agent, one MCP address
+A declared MCP service takes the **whole** surface — other MCP servers attached
+to the same agent are not merged into it. If you need both, you need two agents.
+:::
+
+### Use cases
+
+| You want | Declare |
+|---|---|
+| Platform-served MCP with a Zibby token | `surfaces: ['mcp']` and nothing else |
+| MCP forwarded to your own service, platform-authenticated | `entryPoints.mcp` with `auth: 'bearer-pat'` |
+| A service that runs its own OAuth and issues its own bearer | `connect` with `auth: 'none'` **and** `mcp` with `auth: 'connect-bearer'` |
+| A hosted third-party MCP the platform signs you into | `connect` with `kind: 'oauth'`, and **no** `mcp` entry |
+
+### Gotchas
+
+**Both halves are required.** A channel must be in `surfaces` *and* have an
+`entryPoints` entry before anything is derived.
+
+**A path the proxy would not serve is never advertised.** If the mount does not
+publish it, the entry is dropped rather than shown as a dead link.
+
+**`connect-bearer` turns off the platform's own token check** on the agent's MCP
+address. Only declare it when your service really does authenticate.
+
+**Service-served entries need a self-hosted box.** A `connect` entry with
+`kind: 'oauth'` works everywhere.
+
+## See also
+
+- [`sidecars`](./sidecars.md), [`remoteMcp`](./remote-mcp.md),
+  [`requires`](./requires.md)

package/docs/templates/update-behavior.md

@@ -0,0 +1,108 @@
+---
+sidebar_position: 12
+title: Update behavior
+---
+
+# Update behavior
+
+CloudFormation tells you, per property, whether a change updates the resource in
+place or replaces it. Zibby's declaration model has the same question and four
+answers. Every properties table in this section carries the column.
+
+| Class | What happens on the next deploy |
+|---|---|
+| **Re-applied** | the platform re-runs the action — provision the store, register the sidecar, attach the endpoint, bind the server. Idempotent: nothing is duplicated and nothing working is broken |
+| **Seeded once** | written on the **first** install only. Whatever the operator set afterwards survives every Update |
+| **Card only** | reaches the catalog card and nothing else. A deployed agent never consumes it, so changing it never offers an Update |
+| **Frozen** | baked into the deployed agent when it was installed. Changing it needs a re-deploy |
+
+---
+
+## Seeded once — the list
+
+These are written on a fresh install and never again:
+
+- [`selections`](./deploy-time-config.md#selections) — a value already set is kept, and the deploy tells you so
+- [`defaultSchedule`](./deploy-time-config.md#defaultschedule) — **any** existing schedule blocks the seed, including a paused one
+- [`deployInput`](./deploy-time-config.md#deployinput) values
+- [`maxRuntimeMinutes`](./catalog-metadata.md)
+- `defaultSlug` — an agent's name is fixed at first install
+
+The rule behind all of them: **the platform never overwrites a decision you
+made.** If your agent needs an operator to change something, say so in the
+release notes; do not try to write it for them.
+
+---
+
+## Frozen — why a published fix does not reach a deployed agent
+
+:::danger This is the one that surprises people
+When you deploy an agent, the platform stores **that version's source** —
+including its `package.json` and every version range in it — against the agent.
+That copy is what runs, forever, until somebody re-deploys.
+
+So publishing a fixed package **does not reach an agent that is already
+running**. An agent installed against `^0.1.x` can never pick up a `0.2.x`. It
+does not error; the runs simply keep failing the same way.
+:::
+
+**The fix is always a re-deploy** — take the Update on the agent's page, or
+deploy the card again. There is no other route.
+
+The same is true of the agent's `deps`, and of anything else that travels inside
+the source bundle.
+
+---
+
+## What lights the "Update available" badge
+
+Two independent signals, either of which is enough:
+
+1. **The template's files changed** — a checksum over your template directory.
+2. **The declaration changed** — a per-template signature over your
+   `spec` block, minus the fields listed as *Card only*.
+
+The second exists because your `spec` block lives **outside** the
+template directory, so a metadata-only change (a sidecar version pin, a new
+`selections` picker) moves no source byte and the first signal cannot see it.
+
+The rule the badge states, and the one to test your own field against:
+
+> **Re-installing this agent from the current template would change this agent.**
+
+A field is excluded from the signal only when updating provably changes nothing
+for somebody already running it — tags, taglines, icons, capability bullets,
+sample trigger bodies, and the release notes themselves. (Notes *describing* an
+update cannot be the reason to offer one.)
+
+:::tip Why your card is not showing an update
+Two common causes:
+
+- You changed only a *Card only* field. That is working as designed — the card
+  updated, nobody was offered a re-install.
+- You added a new declared field to a template but the platform is not tracking
+  it yet. A field that is copied but not tracked only ever lands on rows written
+  for some other reason.
+:::
+
+---
+
+## Idempotency, in practice
+
+Everything in the *Re-applied* class is safe to run repeatedly:
+
+| Action | On re-deploy |
+|---|---|
+| Store provisioning | the same store is re-used; a store you re-pointed by hand stays re-pointed |
+| Sidecar registration | the same image, unless the pinned version or checksum moved |
+| `requires` attachment | an existing link is kept; a stale one is replaced; one you added by hand is adopted |
+| `remoteMcp` binding | matched by URL and left byte-for-byte, which is what keeps an OAuth grant alive |
+| Member agents | re-deployed in place; the bindings do not churn |
+
+And one thing that is not idempotent, by nature: **renaming**. A renamed store
+is a new store; a renamed `slug` is a new agent. Nothing migrates the old one.
+
+## See also
+
+- [The declaration model](./index.md)
+- [Catalog metadata](./catalog-metadata.md) — release-notes rules

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zibby/skills",
-  "version": "2.0.4",
+  "version": "2.0.5",
   "description": "Built-in skill definitions for the Zibby agent-workflow framework",
   "type": "module",
   "main": "dist/index.js",
@@ -116,10 +116,10 @@
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
     "@resvg/resvg-js": "^2.6.2",
-    "@zibby/agent-workflow": "2.0.4",
+    "@zibby/agent-workflow": "2.0.5",
     "@zibby/bin-oxlint": "^1.73.0",
     "@zibby/bin-semgrep": "^1.169.0",
-    "@zibby/skill-ids": "2.0.4",
+    "@zibby/skill-ids": "2.0.5",
     "echarts": "^6.1.0",
     "mem0ai": "npm:@zibby/mem0ai@^3.0.5",
     "zod": "^3.23.0 || ^4.0.0"
@@ -134,7 +134,7 @@
     }
   },
   "optionalDependencies": {
-    "@zibby/mcp-browser": "2.0.4",
+    "@zibby/mcp-browser": "2.0.5",
     "@zibby/mcp-memory": "*"
   },
   "devDependencies": {