@passioncode-ai/passioncode 0.2.16 → 0.2.18

package/CHANGELOG.md

@@ -1,5 +1,22 @@
 # Changelog
 
+## 0.2.18 - 2026-10-21
+
+### Changed
+
+- **Fabric Agent Adapter is pinned at `v0.39.1`** (it was `v0.39.0`): fixes from a review of 0.39.0. The service
+  probe no longer crashes on a usage count that is not a number, the Python and Node kits read such counts as the
+  contract does, the documentation and the messages people read carry no em dash, and the dashboard kit is 1.1.1.
+
+## 0.2.17 - 2026-10-20
+
+### Changed
+
+- **Fabric Agent Adapter is pinned at `v0.39.0`** (it was `v0.38.0`): the kits follow contract `c55f2d5`. A partner's
+  publisher key is trusted only in the organization contexts its scope names (FAC-SEM-122), a partner may sit innermost
+  in a delegation chain (DEC-0090), and a usage report counts calls with unknown tokens in `unmeasuredCalls`
+  (DEC-0091).
+
 ## 0.2.16 - 2026-10-20
 
 ### Changed

package/family.json

@@ -8,7 +8,7 @@
       "name": "fabric-agent-adapter",
       "displayName": "Fabric Agent Adapter",
       "repo": "passioncode-ai/fabric-agent-adapter",
-      "ref": "v0.38.0",
+      "ref": "v0.39.1",
       "kind": "plugin",
       "path": "plugins/fabric-agent-adapter",
       "legacyPluginIds": [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@passioncode-ai/passioncode",
-  "version": "0.2.16",
+  "version": "0.2.18",
   "description": "Set up PassionCode.ai on a computer with one command — the apps from their verified releases, their MCP servers for every coding agent and the PassionCode.ai skills — and check and repair it with the same command or `doctor`.",
   "bin": {
     "passioncode": "bin/passioncode.js"

package/payload/.claude-plugin/marketplace.json

@@ -11,7 +11,7 @@
       "name": "fabric-agent-adapter",
       "displayName": "Fabric Agent Adapter",
       "source": "./plugins/fabric-agent-adapter",
-      "version": "0.38.0",
+      "version": "0.39.1",
       "description": "Create new Fabric-compatible agents, build them as always-alive local services with dashboards (fabric-service/0.1), and adapt existing projects to the Fabric Agent Contract through evidence-backed MCP, A2A, or local-runner provider bundles; and teach a coding agent to work in a project through Fabric (fabric-mcp, fabric_whoami, claim and release), with Claude Code session hooks.",
       "author": {
         "name": "PassionCode.ai",
@@ -35,7 +35,7 @@
       "name": "passioncode",
       "displayName": "PassionCode.ai",
       "source": "./plugins/passioncode",
-      "version": "0.2.16",
+      "version": "0.2.18",
       "description": "Set up and check PassionCode.ai on a computer with one command (setting-up-passioncode), the organisation's working rules for every contributor's agent (working-in-passioncode), and a once-a-day check that keeps the PassionCode.ai set current.",
       "author": {
         "name": "PassionCode.ai",

package/payload/manifest.json

@@ -1,15 +1,15 @@
 {
   "family": "passioncode",
-  "version": "0.2.16",
+  "version": "0.2.18",
   "release": true,
   "members": [
     {
       "name": "fabric-agent-adapter",
       "displayName": "Fabric Agent Adapter",
       "repo": "passioncode-ai/fabric-agent-adapter",
-      "ref": "v0.38.0",
-      "commit": "15dfe5219d4475905752808ba0e30cebb41f1d74",
-      "version": "0.38.0",
+      "ref": "v0.39.1",
+      "commit": "92037c3e0d27f4888806a1c4ae5b36167de50067",
+      "version": "0.39.1",
       "via": "clone of https://***@github.com/passioncode-ai/fabric-agent-adapter.git",
       "skills": [
         "adapting-projects-to-fabric",
@@ -23,7 +23,7 @@
       "legacyMarketplaces": [
         "fabric-agent-adapter"
       ],
-      "contentHash": "sha256:cdb6bad86a59877d1b72304d634e30a2378093ec6a6e4e96117bcb37fdc0ea0c",
+      "contentHash": "sha256:4200dac01fb7296bd45ee2b52ff5a0fcec02e7e80bbb971c02f569feab84c1cb",
       "description": "Create new Fabric-compatible agents, build them as always-alive local services with dashboards (fabric-service/0.1), and adapt existing projects to the Fabric Agent Contract through evidence-backed MCP, A2A, or local-runner provider bundles; and teach a coding agent to work in a project through Fabric (fabric-mcp, fabric_whoami, claim and release), with Claude Code session hooks.",
       "author": {
         "name": "PassionCode.ai",
@@ -62,9 +62,9 @@
       "name": "passioncode",
       "displayName": "PassionCode.ai",
       "repo": "passioncode-ai/passioncode",
-      "ref": "v0.2.16",
+      "ref": "v0.2.18",
       "commit": null,
-      "version": "0.2.16",
+      "version": "0.2.18",
       "via": "this repository",
       "skills": [
         "setting-up-passioncode",
@@ -72,7 +72,7 @@
       ],
       "legacyPluginIds": [],
       "legacyMarketplaces": [],
-      "contentHash": "sha256:402f4ab121c4b1e9e81d23c1bf4cdc7178933e720621c51723cd32a937009719",
+      "contentHash": "sha256:6c506bf0504dbaa41ce2768e6205e8beba1bffff41c054e53b4eec230d7b5b3e",
       "description": "Set up and check PassionCode.ai on a computer with one command (setting-up-passioncode), the organisation's working rules for every contributor's agent (working-in-passioncode), and a once-a-day check that keeps the PassionCode.ai set current.",
       "author": {
         "name": "PassionCode.ai",

package/payload/plugins/fabric-agent-adapter/.claude-plugin/plugin.json

@@ -3,7 +3,7 @@
   "name": "fabric-agent-adapter",
   "displayName": "Fabric Agent Adapter",
   "description": "Create new Fabric-compatible agents, build them as always-alive local services with dashboards (fabric-service/0.1), and adapt existing projects to the Fabric Agent Contract through evidence-backed MCP, A2A, or local-runner provider bundles; and teach a coding agent to work in a project through Fabric (fabric-mcp, fabric_whoami, claim and release), with Claude Code session hooks.",
-  "version": "0.38.0",
+  "version": "0.39.1",
   "author": {
     "name": "PassionCode.ai",
     "url": "https://passioncode.ai/"

package/payload/plugins/fabric-agent-adapter/skills/adapting-projects-to-fabric/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: adapting-projects-to-fabric
-description: Use when adapting an existing agent, MCP server, A2A peer, HTTP service, or terminal CLI to the Fabric Agent Contract—choosing MCP/A2A/local-runner, scaffolding a provider bundle, or checking Fabric compatibility; also for «подключить проект к Fabric» or «сделать агента совместимым с Fabric». NOT for building the Fabric host/orchestrator, configuring an MCP client, or a brand-new agent — that is creating-fabric-agents.
+description: Use when adapting an existing agent, MCP server, A2A peer, HTTP service, or terminal CLI to the Fabric Agent Contract (choosing MCP/A2A/local-runner, scaffolding a provider bundle, or checking Fabric compatibility); also for «подключить проект к Fabric» or «сделать агента совместимым с Fabric». NOT for building the Fabric host/orchestrator, configuring an MCP client, or a brand-new agent (that is creating-fabric-agents).
 license: AGPL-3.0-only OR LicenseRef-PassionCode-Commercial
 compatibility: Requires filesystem access and Python 3.9+. Exact schema checks additionally need git, Node.js, pnpm, and the pinned fabric-agent-contract checkout (a public repository). Works without those tools in an explicitly degraded structural-check mode.
 metadata:
   author: PassionCode.ai
-  version: "0.38.0"
+  version: "0.39.1"
   contract-version: "0.1.0"
-  contract-commit: "07042181bfae2a481aa0da1a5651f24c76669c48"
+  contract-commit: "c55f2d5a11c9a0197e958e87212fca7ae1154769"
 ---
 
 # Adapting projects to Fabric
@@ -23,9 +23,9 @@ Use this skill to adapt or assess a provider project. Do not use it to:
 - design the Fabric host, registry, scheduler, admission service, or project binding runtime;
 - add an MCP server to Claude Code, Codex, or an agent gateway;
 - answer wire-level MCP or A2A questions (transports, sessions, auth handshakes, task
-  states on the wire) — that is `agent-interop` (agent-stack); the pinned contract stays
+  states on the wire): that is `agent-interop` (agent-stack); the pinned contract stays
   normative for what Fabric requires;
-- design a new agent from scratch — that is the sibling skill creating-fabric-agents;
+- design a new agent from scratch: that is the sibling skill creating-fabric-agents;
 - claim admission merely because generated files or a valid manifest exist.
 
 If the project has only a browser interface and no stable API, MCP/A2A surface, or CLI,
@@ -70,7 +70,7 @@ Use exactly:
 
 - contract version `0.1.0`;
 - repository `https://github.com/passioncode-ai/fabric-agent-contract`;
-- commit `07042181bfae2a481aa0da1a5651f24c76669c48`.
+- commit `c55f2d5a11c9a0197e958e87212fca7ae1154769`.
 
 This is the default for new bundles. When checking an issued legacy bundle, preserve its
 explicit supported lock and use that exact clean checkout. Never silently upgrade or
@@ -133,14 +133,14 @@ Preserve the chosen ownership boundary:
   heartbeat, and partial results without relying on ambient accounts.
 
 Keep model selection and provider-internal reasoning outside the Fabric contract. Expose
-typed outcomes, evidence, artifacts, and protocol-visible state—not chain-of-thought.
+typed outcomes, evidence, artifacts, and protocol-visible state, not chain-of-thought.
 Treat all provider output as untrusted until schemas and semantic assertions pass.
 
 ### 4b. Announce an agent that is not a service
 
 An agent Fabric reaches as a CLI or a stdio MCP server gets a provider entry, written by
 its installer with [`scripts/fabric_provider.py`](scripts/fabric_provider.py) and removed
-by its uninstaller — argv arrays only, env values as `secret-ref:` references, never the
+by its uninstaller: argv arrays only, env values as `secret-ref:` references, never the
 id of an existing service, and a `providerId` equal to the manifest's `provider.id`. Load [provider entries](references/provider-entry.md). An
 agent that runs as a service uses a descriptor instead (`building-fabric-services`).
 
@@ -174,8 +174,8 @@ python3 <skill-dir>/scripts/adapt_project.py check <project-root> \
 ```
 
 The local check also refuses two lifecycle faults (LC-19, LC-21): a Claude Code plugin in
-the project that declares a stdio MCP server — it starts in every session that enables the
-plugin; serve it over HTTP from one resident process or register it at project scope — and a
+the project that declares a stdio MCP server (it starts in every session that enables the
+plugin; serve it over HTTP from one resident process or register it at project scope), and a
 credential in a launch argument or a URL query, where every process and every log can read it.
 Fix both at their cause; never weaken the check.
 
@@ -214,11 +214,11 @@ operator's four steps:
 4. type the code it shows in the chat with the bot.
 
 In a group shared with other bots the channel follows OC-14…OC-17 (DEC-0035): it stays silent
-unless addressed — `/command@ThisBot`, a reply to its own message or a press of its own button; a
-bare `/command` in a group is not addressed — and a channel nobody receives on is `degraded`
+unless addressed (`/command@ThisBot`, a reply to its own message or a press of its own button; a
+bare `/command` in a group is not addressed), and a channel nobody receives on is `degraded`
 (`receiver-missing`). Say so in the proposal when the operator means to bind a shared group.
 
-Record the answer — `accepted`, `declined` or `later` — in the agent's state and the
+Record the answer (`accepted`, `declined` or `later`) in the agent's state and the
 conformance report, and do not ask again; an agent that serves `surfaces.operatorChannel` also
 shows it as `proposal` in its status document. Creating the bot, storing the token and enabling the
 channel are the operator's action: never create the bot, ask for or store the token's value, or
@@ -246,7 +246,7 @@ first commit:
 org-index `scripts/check_format.py` reports 0 findings for it before it is called done. **An agent
 someone builds for themselves is not a PassionCode.ai repository:** its licence is its owner's
 choice, nothing about it is published or listed by the organization, and none of these files is
-required of it — though the verified MCP quick start is still how anyone learns to drive it.
+required of it, though the verified MCP quick start is still how anyone learns to drive it.
 
 ## Completion format
 
@@ -263,7 +263,7 @@ Report:
 Never summarize the outcome as “Fabric-compatible” unless all required admission gates
 passed against a real provider and the project binding is valid.
 
-## Dashboard handoff — also for consumers
+## Dashboard handoff: also for consumers
 
 When handing a registered service dashboard to a person, or writing the generated
 agent's completion/notification instructions, read and apply

package/payload/plugins/fabric-agent-adapter/skills/adapting-projects-to-fabric/references/dashboard-links.md

@@ -1,4 +1,4 @@
-# Dashboard links — producer and consumer rule
+# Dashboard links: producer and consumer rule
 
 Read when an agent creates a dashboard, implements `<tool> dashboard`, or hands
 an existing Fabric service dashboard to a person. This also applies to generated

package/payload/plugins/fabric-agent-adapter/skills/adapting-projects-to-fabric/references/provider-entry.md

@@ -3,7 +3,7 @@
 Normative source: the Fabric Agent Contract's `docs/specification/provider.md`
 (`fabric-provider/0.1`, DEC-0016, rulings DEC-0017) at the commit this plugin pins.
 
-An agent Fabric reaches as a CLI or a stdio MCP server — not a long-running service —
+An agent Fabric reaches as a CLI or a stdio MCP server (not a long-running service)
 is announced by one entry, `providers/<id>.json`, in the same root as the services
 directory:
 
@@ -34,17 +34,17 @@ python3 scripts/fabric_provider.py remove example-agent      # the uninstaller
 
 `--stdio` takes the rest of the line as the argument array; there is no shell string. An entry may carry
 `run.mcp.stdio.scope` (DEC-0044): `project` (started for the sessions of a project that binds it) or `on-demand`;
-`session` — a server in every coding session — is refused (FAC-SEM-056, LC-19). The validator accepts the field; the
+`session` (a server in every coding session) is refused (FAC-SEM-056, LC-19). The validator accepts the field; the
 writer does not set it until Fabric reads it. An argument that carries a credential is refused
 (LC-21, FAC-SEM-057): a key goes in `env` as a `secret-ref:<name>`, never in argv.
 
 It refuses, with one sentence that never quotes a value:
 
 - a manifest that does not resolve, or whose `provider.id` is not the entry's
-  `providerId` — the two URIs are compared as URIs (FAC-SEM-014);
+  `providerId`: the two URIs are compared as URIs (FAC-SEM-014);
 - an id that is already a service in `services/` (FAC-SEM-013);
 - an env value that is not `secret-ref:<name>`, or a reference that has the shape of a
-  credential itself — a token prefix, a private key, a JWT (FAC-SEM-015: a value is
+  credential itself: a token prefix, a private key, a JWT (FAC-SEM-015: a value is
   checked by its form; name patterns apply to names);
 - a URL other than `http://127.0.0.1:<port>/mcp`, a manifest path that is not an
   absolute or `~/` path to `fabric-agent.json`, a shell-string command, unknown fields.

package/payload/plugins/fabric-agent-adapter/skills/adapting-projects-to-fabric/scripts/adapt_project.py

@@ -21,10 +21,10 @@ import fabric_secrets as _secrets  # noqa: E402 - the contract's credential dete
 
 CONTRACT_VERSION = "0.1.0"
 CONTRACT_REPOSITORY = "https://github.com/passioncode-ai/fabric-agent-contract"
-CONTRACT_COMMIT = "07042181bfae2a481aa0da1a5651f24c76669c48"
+CONTRACT_COMMIT = "c55f2d5a11c9a0197e958e87212fca7ae1154769"
 # #region supported-contract-revisions — docs: README.md#contract-pin
 # Only this declaration may name a legacy revision in live files.
-SUPPORTED_CONTRACT_COMMITS = (CONTRACT_COMMIT, "d8146cfb0a1c74fc6432284c4356bb0c864b37b5", "82e163665e156a08aa3b92e4711015582c06162c", "1636fa97262f4a26e2086572d540c2ee701e0010", "f00a7685e3861c27f7899c033fb850a145a1708f", "a046f57cf46ea9e3da57ff8ce6a3ed4d26d8774b", "fe55fc67cba1a9e34a736da7d148d4fe2a8fbfa0", "b291bf09e0a9f9fd3c16cf540832cd021203b7d1", "0cacd08b0e95b6abf131eae1206b60792138bc3c", "2eb91c00e852d9c31d804310d38fad91589fcbac", "8e49fbd5fbbf230e32c1969cd24ac3c22422f0a5", "a83bec6b47776af688402c18efec507143061f68", "52da526d7cc1e063d74c5b520dbc03d0ace15246", "78b2da018d2c4bd9ac1bde1dc3b7f1a110a175f5", "623bf61358c339cb10297807b3f024b5d9f1f327", "23f9fda4c05f8a3852246ee98d4f2adf74ed0875", "9091d3d6606b0c4b5591a38c3674356a01fd7f55", "df55c8c54a23251342a7ee57ba95642b7eb39e61", "2ce392291c6668598d12cd38327e24696b5ca15c")
+SUPPORTED_CONTRACT_COMMITS = (CONTRACT_COMMIT, "07042181bfae2a481aa0da1a5651f24c76669c48", "d8146cfb0a1c74fc6432284c4356bb0c864b37b5", "82e163665e156a08aa3b92e4711015582c06162c", "1636fa97262f4a26e2086572d540c2ee701e0010", "f00a7685e3861c27f7899c033fb850a145a1708f", "a046f57cf46ea9e3da57ff8ce6a3ed4d26d8774b", "fe55fc67cba1a9e34a736da7d148d4fe2a8fbfa0", "b291bf09e0a9f9fd3c16cf540832cd021203b7d1", "0cacd08b0e95b6abf131eae1206b60792138bc3c", "2eb91c00e852d9c31d804310d38fad91589fcbac", "8e49fbd5fbbf230e32c1969cd24ac3c22422f0a5", "a83bec6b47776af688402c18efec507143061f68", "52da526d7cc1e063d74c5b520dbc03d0ace15246", "78b2da018d2c4bd9ac1bde1dc3b7f1a110a175f5", "623bf61358c339cb10297807b3f024b5d9f1f327", "23f9fda4c05f8a3852246ee98d4f2adf74ed0875", "9091d3d6606b0c4b5591a38c3674356a01fd7f55", "df55c8c54a23251342a7ee57ba95642b7eb39e61", "2ce392291c6668598d12cd38327e24696b5ca15c")
 # #endregion supported-contract-revisions
 INTEROP_KEY = "https://fabric.passioncode.ai/agent-contract/extensions/interop/0.1"
 MCP_REVISION = "2026-07-28"

package/payload/plugins/fabric-agent-adapter/skills/building-fabric-services/SKILL.md

@@ -3,7 +3,7 @@ name: building-fabric-services
 description: >-
   Use when handing out or opening a Fabric service dashboard, building a local agent service on a
   macOS machine, making an ONLINE agent or dashboard (https origin, the remote placement) a
-  Fabric service, or letting a service answer a Project's board requests — «сделай агенту дашборд»,
+  Fabric service, or letting a service answer a Project's board requests: «сделай агенту дашборд»,
   «локальный сервис агента», «подключи агента к Fabric Dashboards», «отвечать на запросы с доски проекта»,
   "make this agent a local service", "make an online dashboard a Fabric service", "add the
   well-known endpoint", «расходы агента на модели». Covers fabric-service/0.1:
@@ -18,10 +18,10 @@ license: AGPL-3.0-only OR LicenseRef-PassionCode-Commercial
 compatibility: Python 3.9+ or Node.js 20+ for the kits; the probe needs Python 3.9+. launchd steps are macOS-only; Linux services install a systemd user unit and Windows ones a per-user Scheduled Task with the kits' writers. Dashboard handoff optionally uses Fabric Dashboards MCP link/host_status/open; without it, report unresolved host capability. The contract checkout is optional.
 metadata:
   author: PassionCode.ai
-  version: "0.38.0"
+  version: "0.39.1"
   contract-version: "0.1.0"
   extension: "fabric-service/0.1"
-  extension-commit: "07042181bfae2a481aa0da1a5651f24c76669c48"
+  extension-commit: "c55f2d5a11c9a0197e958e87212fca7ae1154769"
 ---
 
 # Building Fabric services
@@ -29,7 +29,7 @@ metadata:
 A **service** is an agent that keeps running on the operator's computer: it holds
 state, answers other agents, and shows a dashboard. This skill makes one that is
 always alive, comes back after a restart, never runs twice, keeps its state through a
-reinstall, and appears in Fabric Dashboards by itself — the `fabric-service/0.1`
+reinstall, and appears in Fabric Dashboards by itself: the `fabric-service/0.1`
 extension of the Fabric Agent Contract (DEC-0015).
 
 Every rule below exists because a real service on this estate broke it. Treat them as
@@ -41,15 +41,15 @@ re-deriving a rule.
 Use it to create a service, to bring an existing local server under the protocol, or
 to review one. Do not use it for:
 
-- a script, a cron job or a one-shot CLI — nothing stays running, so there is nothing
+- a script, a cron job or a one-shot CLI: nothing stays running, so there is nothing
   to supervise; a launchd `StartInterval` job needs no descriptor;
 - a hosted product with no agent behind it. An online agent or dashboard that should appear in
-  Fabric IS in scope: it is the remote placement — read [Online services](#online-services--the-remote-placement);
-- the provider manifest and admission bundle — that is `adapting-projects-to-fabric`
+  Fabric IS in scope: it is the remote placement; read [Online services](#online-services-the-remote-placement);
+- the provider manifest and admission bundle: that is `adapting-projects-to-fabric`
   (a service that is also a provider does both);
 - the Fabric Dashboards app itself.
 
-## Step 0 — is it a service?
+## Step 0: is it a service?
 
 It is a service when at least one is true: other agents call it while the operator is
 away; it runs jobs longer than one request; it owns a store other tools read; the
@@ -65,7 +65,7 @@ Answer before writing code, and record the answers in the project README:
 | What it stores | the store, where it lives (Step 2, rule 5), and what survives uninstall |
 | What it tells the operator | the events worth a notification (Step 5) |
 
-## Step 1 — choose the surfaces
+## Step 1: choose the surfaces
 
 | Caller | Surface | Why |
 |---|---|---|
@@ -84,7 +84,8 @@ effect nobody saw, have their own codes and a key per caller (DEC-0087). Read
 [the interop reference](references/interop.md) before writing an MCP tool; the helpers
 are in [`scripts/fabric_interop.py`](scripts/fabric_interop.py) and
 [`scripts/fabric-interop.mjs`](scripts/fabric-interop.mjs). When the callers are agents of the estate, the
-service checks each call's delegation token (DEC-0039): read [the delegation reference](references/delegation.md);
+service checks each call's delegation token (DEC-0039; a partner's agent carries the partner innermost, DEC-0090):
+read [the delegation reference](references/delegation.md);
 the verifier is [`scripts/fabric_delegation.py`](scripts/fabric_delegation.py) /
 [`scripts/fabric-delegation.mjs`](scripts/fabric-delegation.mjs). A service on the operator's machines that
 applies the estate record (DEC-0055) verifies each revision first and trusts only the keys it certifies, and runs an
@@ -102,14 +103,14 @@ responder in its own process: [`scripts/fabric_hub.py`](scripts/fabric_hub.py) f
 every step and stops on `fenced`, `lease_expired` or `authority_changed` (Node: `fabric-hub.mjs`, `fabric-board.mjs`).
 The request body is data behind the service's own input gate. Read [the board reference](references/board.md).
 
-## Step 2 — the non-negotiables
+## Step 2: the non-negotiables
 
 1. **Loopback only.** Bind `127.0.0.1`. Refuse any `Host` other than
    `127.0.0.1:<port>`, `localhost:<port>`, `[::1]:<port>`; refuse a foreign `Origin` and
-   `Sec-Fetch-Site: cross-site` — on every path, the well-known one included.
+   `Sec-Fetch-Site: cross-site`, on every path, the well-known one included.
    *(A throwaway `python -m http.server` bound to every interface served a source tree to the local network.)*
 2. **One copy, locked before any side effect.** Take the exclusive lock on
-   `<data>/service.lock` first — before resuming jobs, starting a scheduler, migrating
+   `<data>/service.lock` first, before resuming jobs, starting a scheduler, migrating
    a store or even creating a token. Held → print one sentence naming the holder's pid
    and exit **75**. Binding the port is not a lock. Under launchd the kit backs off
    in-process first (up to 300 s), so a duplicate is a few starts an hour, not a
@@ -126,11 +127,11 @@ The request body is data behind the service's own input gate. Read [the board re
 5. **State outside code.** Data and config in `~/Library/Application Support/<id>/`,
    logs in `~/Library/Logs/<id>/`, cache in `~/Library/Caches/<id>/`; the service's own
    access token in a 0600 file it generates (principle 6). **Every provider credential the
-   service uses comes from Project Observatory, by name** — the plist starts the service
+   service uses comes from Project Observatory, by name**: the plist starts the service
    with `use_secret.py serve --consumer <label> <project> <NAME>[,<NAME>] -- <command>`, which
    reads the vault only and records the consumer so a rotation names it; never a copy of a
    key in a `.env`, a config file or the plist. Never inside the service's own code checkout or a release directory; a
-   repository that versions the data itself is a store and is fine — declare
+   repository that versions the data itself is a store and is fine; declare
    `source.repository` so the probe can tell them apart. *(Deleting a checkout left a
    plist launchd retried every 10 s, and the data went with it.)*
 6. **Tokens stay in files and headers.** Mode 0600, owner-checked, never a symlink;
@@ -138,16 +139,16 @@ The request body is data behind the service's own input gate. Read [the board re
    one-time login code, never the token.
 7. **`degraded` is always present.** An empty list asserts full health; `ready` with a
    non-empty list is a lie the kit corrects to `degraded`.
-8. **Atomic writes.** Temporary file, fsync, rename — for the store's side files, the
+8. **Atomic writes.** Temporary file, fsync, rename, for the store's side files, the
    descriptor and the token.
 
-## Step 3 — build it with the kit
+## Step 3: build it with the kit
 
 Copy the kit into the service (each is one self-contained file): Python
 [`scripts/fabric_service.py`](scripts/fabric_service.py), Node
 [`scripts/fabric-service.mjs`](scripts/fabric-service.mjs). Both share file formats, and
 their locks exclude each other. The complete worked example is
-[`scripts/sample_service.py`](scripts/sample_service.py) — read it before writing a
+[`scripts/sample_service.py`](scripts/sample_service.py); read it before writing a
 handler.
 
 Startup order is the part that goes wrong; keep it exactly:
@@ -156,7 +157,7 @@ Startup order is the part that goes wrong; keep it exactly:
 import fabric_service as fs
 
 dirs = fs.service_dirs("example-agent")
-lock = fs.hold_single_instance(dirs["data"])        # 1. lock — exits 75 if held (backs off first under launchd)
+lock = fs.hold_single_instance(dirs["data"])        # 1. lock: exits 75 if held (backs off first under launchd)
 token = fs.ensure_token(dirs["data"] / "service.token")  # 2. only now touch state
 log = fs.JsonlEventLog(dirs["data"] / "events.jsonl")    #    (or a view over your own log)
 codes = fs.LoginCodes(dirs["data"] / "auth")
@@ -171,12 +172,12 @@ On every request call `check_request(port, host, origin, sec_fetch_site)` and an
 
 | Route | Auth | Kit |
 |---|---|---|
-| `GET /.well-known/fabric-service` | none, guard still applies | `build_well_known(...)` — from memory, under 100 ms |
+| `GET /.well-known/fabric-service` | none, guard still applies | `build_well_known(...)`, from memory, under 100 ms |
 | `GET /fabric/v1/events?after=&limit=` | service token | `events_page(fetch, after, parse_limit(limit))` |
 | `POST /fabric/v1/login-code` | service token | `LoginCodes.issue()` |
 | `GET /fabric/v1/login?code=` | the code | `LoginCodes.redeem(code)` → `Set-Cookie: session_cookie_header(...)`, 302 to the dashboard |
 
-`SIGTERM` drains in-flight work, then exits — 10 s at most, inside `ExitTimeOut`
+`SIGTERM` drains in-flight work, then exits: 10 s at most, inside `ExitTimeOut`
 (`fs.Drain` / `new Drain()`: `with drain.work():` refuses new work once a stop began);
 interrupted work resumes on the next start. Log through `RotatingLog` (5 × 5 MB, 0600)
 and call `cap_stdout_log` once at start.
@@ -186,18 +187,18 @@ in Python; jobs live in `fabric_interop.JobStore(dirs["data"] / "jobs")`, create
 the lock like every other piece of state. Add `"mcp": {"path": "/mcp", "transport":
 "streamable-http", "capabilities": [...]}` to the well-known surfaces, and point the
 descriptor's `fabricManifest` at a manifest whose service key names this
-`<id>.<instance>` — `sample_service.py register` shows both.
+`<id>.<instance>`; `sample_service.py register` shows both.
 
-## Step 4 — install it
+## Step 4: install it
 
 The installer, not the service, owns the plist and the descriptor. Sequence:
 
-1. `write_descriptor(descriptor)` — refuses a port or `id.instance` another descriptor
-   claims. A preview or branch copy is a second **instance**, never a second id — and it is
+1. `write_descriptor(descriptor)`: refuses a port or `id.instance` another descriptor
+   claims. A preview or branch copy is a second **instance**, never a second id, and it is
    one more service the operator sees, probes and gets notified by. Verify a release with its
    own doctor or self-check before it replaces `default`; a temporary instance is uninstalled
    (`launchd_uninstall`, `remove_descriptor`) as soon as its check is done, not left running.
-2. `launchd_plist(...)` then `launchd_install(...)` — writes and lints the plist,
+2. `launchd_plist(...)` then `launchd_install(...)`: writes and lints the plist,
    `bootout` and waits for the unload, `bootstrap` with retries on the transient I/O
    error, then polls the well-known document until it answers with **this** identity.
    A label the operator disabled stays disabled: only a first install enables.
@@ -216,7 +217,7 @@ rewrites the plist and restarts. Read [the lifecycle reference](references/lifec
 for the plist fields, the release layout, log rotation, behaving under a host lifecycle broker
 and the Linux and Windows supervisors.
 
-## Step 5 — the dashboard and the events
+## Step 5: the dashboard and the events
 
 The dashboard is a same-origin page: no inline script, strict CSP, polling that pauses
 while the operator types or a dialog is open, one panel's failure never blanks the
@@ -234,10 +235,10 @@ and declare it with `extensions=fs.dashboard_extension()`. Read
 declaration and how to upgrade a dashboard built before the kit: an upgrade you may make yourself,
 which the plugin's session-start notice offers in a repository that owns the service.
 
-The events feed is a **view over the log you already keep** — a jobs table, a JSONL
-journal — not a second store. Each event is one sentence a person reads; set
+The events feed is a **view over the log you already keep** (a jobs table, a JSONL
+journal), not a second store. Each event is one sentence a person reads; set
 `notify: true` only when the operator must decide, or something failed or degrades their
-work — once per episode, with a `subject` and a `link` to the page that resolves it. A
+work, once per episode, with a `subject` and a `link` to the page that resolves it. A
 question's kind says so (`*.awaiting_*`, `*.approval_*`, `human_step.opened`). The service
 raises no banners of its own: the host is the one channel. Read
 [the events reference](references/events-and-notifications.md) for mapping an existing
@@ -252,9 +253,9 @@ A service whose store holds what the operator decided keeps **settings backups**
 directory, restores only on a fresh database and never overwrites. Read
 [the settings backups reference](references/settings-backups.md).
 
-## Step 6 — verify
+## Step 6: verify
 
-Run the probe against the live service — it reads the descriptor, then checks every
+Run the probe against the live service: it reads the descriptor, then checks every
 rule it can reach and says which it could not:
 
 ```bash
@@ -267,7 +268,7 @@ events auth and shape, single-use login, state outside code, instance lock, plis
 launchd pid equals answering pid, `dashboard.declared` (ED-9), and the `interop.*` rules:
 manifest link, capability list, tools equal to the manifest, job tools, unknown job, trace
 propagation, event trace pairs, and `board.responder` for a service that declares the project board) and exits 1 on
-any `FAIL`. A `NOT_RUN` is not a pass —
+any `FAIL`. A `NOT_RUN` is not a pass;
 name it in the report. A service with a dashboard also runs the layout probe,
 `node <skill-dir>/scripts/check_dashboard_layout.mjs --service <id>` (WebKit at 360, 480, 768
 and 1280 px; needs Playwright, else `NOT_RUN`).
@@ -276,7 +277,7 @@ Then prove the lock: start a second copy by hand against the same data directory
 must exit 75 while the first keeps serving. Prove recovery: `kill -9` the launchd pid;
 the well-known document must answer again with a new pid within about 15 seconds.
 
-## Packing and signing it — `fabric-package/1`
+## Packing and signing it: `fabric-package/1`
 
 To hand an agent to another machine or an organization, pack it as one folder (contract DEC-0050, DEC-0051). Write the
 author's `fabric.package.json` (the descriptive fields; for an agent `resultSignal` and `evals` with the receipt of the
@@ -312,11 +313,11 @@ first commit:
 org-index `scripts/check_format.py` reports 0 findings for it before it is called done. **An agent
 someone builds for themselves is not a PassionCode.ai repository:** its licence is its owner's
 choice, nothing about it is published or listed by the organization, and none of these files is
-required of it — though the verified MCP quick start is still how anyone learns to drive it.
+required of it, though the verified MCP quick start is still how anyone learns to drive it.
 
-## Online services — the remote placement
+## Online services: the remote placement
 
-An agent or a dashboard that runs online — on a platform, a server, a hosted app — becomes a
+An agent or a dashboard that runs online (on a platform, a server, a hosted app) becomes a
 Fabric service with the same four routes and one descriptor on the operator's computer
 (`placement: "remote"`, DEC-0019). Nothing about launchd, the lock or loopback applies; three
 things change and the kits implement each:
@@ -327,7 +328,7 @@ things change and the kits implement each:
 | Well-known | only for the token; otherwise `401` with an **empty** body | `wellKnownAllowed('remote', …)` / `well_known_allowed` |
 | Session | `__Host-fabric_session`, `Secure`; codes in memory, the key from a platform secret so sessions survive a deploy | `remoteSessionCookieHeader`, `new LoginCodes(null, 120, { store: new MemoryCodeStore(), key })` |
 
-1. **Serve the four routes** in the app that already exists — not beside it. The complete worked
+1. **Serve the four routes** in the app that already exists, not beside it. The complete worked
    example is [`scripts/sample-remote-service.mjs`](scripts/sample-remote-service.mjs): it runs
    with its own TLS or behind a platform router.
 2. **Secrets live on the platform:** the service token and the session key (32 bytes) are
@@ -335,7 +336,7 @@ things change and the kits implement each:
    remote service needs is issued and kept in Project Observatory, pushed to the platform, and
    the movement recorded with `vault.py moved --at <provider>`, so the platform's copy is
    known rather than invisible.
-3. **Register it on the operator's computer** — the installer side, run there:
+3. **Register it on the operator's computer**, the installer side, run there:
    `registerRemote({ id, name, origin, token })` / `register_remote(...)` writes the token file
    (0600) and the descriptor; pass the token from a file or stdin, never in argv. Public names
    only in public artifacts: a private service is registered by a local descriptor and nowhere
@@ -349,7 +350,7 @@ behaviour a host shows, rotation, a multi-process platform, and what a host will
 
 ## Migrating an existing service
 
-Read [the migration reference](references/migrating-a-service.md) — the order of
+Read [the migration reference](references/migrating-a-service.md): the order of
 changes that keeps the service answering throughout, and what each existing service on
 this estate needs.
 
@@ -366,14 +367,14 @@ this estate needs.
   against [the protocol reference](references/protocol.md); the probe is the judge.
 - **No contract checkout:** the protocol reference is pinned to the extension commit
   in this skill's metadata; do not reconstruct fields from memory.
-- **Fabric Dashboards not installed:** nothing changes — the service is complete
+- **Fabric Dashboards not installed:** nothing changes; the service is complete
   without a host; the descriptor waits for one.
 
 ## Gotchas
 
 - `lsof` shows `*:<port>` or `0.0.0.0` → the bind is wrong even if the Host check works.
 - A health probe that only checks HTTP 200 accepts any program on the port. Compare
-  `service.id` and `service.instance` — two services here once defaulted to ports
+  `service.id` and `service.instance`: two services here once defaulted to ports
   another service already held.
 - `launchctl bootstrap` right after `bootout` fails with I/O error 5 until the unload
   finishes; wait, then retry.
@@ -396,7 +397,7 @@ the probe table verbatim with every `NOT_RUN` explained; the lock and kill-9 res
 with pids; and the one next command. Never call a service conformant while the probe
 reports a `FAIL`.
 
-## Dashboard handoff — also for consumers
+## Dashboard handoff: also for consumers
 
 When handing a registered service dashboard to a person, or writing the generated
 agent's completion/notification instructions, read and apply

package/payload/plugins/fabric-agent-adapter/skills/building-fabric-services/assets/dashboard-kit/demo.html

@@ -65,7 +65,7 @@
           <tbody>
             <tr><td class="fd-mono">job-7f3a91</td><td>example.summarize</td><td><span class="fd-chip fd-s-info"><span class="fd-dot"></span>Running</span></td><td><time>2026-10-11 17:02</time></td><td class="fd-num">12 480</td><td class="fd-num">$0.031</td><td class="fd-mono">4bf92f3577b34da6a3ce929d0e0e4736</td></tr>
             <tr><td class="fd-mono">job-7f3a90</td><td>example.translate</td><td><span class="fd-chip fd-s-ok"><span class="fd-dot"></span>Done</span></td><td><time>2026-10-11 16:40</time></td><td class="fd-num">8 002</td><td class="fd-num">$0.019</td><td class="fd-mono">00f067aa0ba902b74bf92f3577b34da6</td></tr>
-            <tr><td class="fd-mono">job-7f3a8f</td><td>example.review</td><td><span class="fd-chip fd-s-warn"><span class="fd-dot"></span>Needs you</span></td><td><time>2026-10-11 15:12</time></td><td class="fd-num">2 210</td><td class="fd-num">—</td><td class="fd-mono">a3ce929d0e0e47364bf92f3577b34da6</td></tr>
+            <tr><td class="fd-mono">job-7f3a8f</td><td>example.review</td><td><span class="fd-chip fd-s-warn"><span class="fd-dot"></span>Needs you</span></td><td><time>2026-10-11 15:12</time></td><td class="fd-num">2 210</td><td class="fd-num">none</td><td class="fd-mono">a3ce929d0e0e47364bf92f3577b34da6</td></tr>
           </tbody>
         </table>
       </div>

package/payload/plugins/fabric-agent-adapter/skills/building-fabric-services/assets/dashboard-kit/fabric-button.js

@@ -1,4 +1,4 @@
-/* fabric-dashboard-kit@1.1.0 · Fabric's button (Fabric Agent Contract DEC-0040, FB-1…FB-8, FL-1…FL-6)
+/* fabric-dashboard-kit@1.1.1 · Fabric's button (Fabric Agent Contract DEC-0040, FB-1…FB-8, FL-1…FL-6)
    Load it same-origin, after fabric-dashboard.css, with the service it opens Fabric on:
      <script src="fabric-button.js" defer data-service="example-agent.default" data-service-name="Example Agent"
              data-project="project-a" data-project-name="Project A"></script>
@@ -10,7 +10,7 @@
 (function (root) {
   'use strict';
 
-  var VERSION = '1.1.0';
+  var VERSION = '1.1.1';
   var COOKIE = 'fabric_button';
   var GET_FABRIC = 'https://passioncode.ai/fabric';
   var ABSENT_AFTER_MS = 1500;
@@ -212,7 +212,7 @@
       return a;
     });
     var note = el(doc, 'p', { 'class': 'fd-fabric-button-note', role: 'note' });
-    note.appendChild(doc.createTextNode('Fabric is not installed — get it at '));
+    note.appendChild(doc.createTextNode('Fabric is not installed. Get it at '));
     note.appendChild(el(doc, 'a', { href: GET_FABRIC, target: '_blank', rel: 'noopener', 'class': 'fd-fabric-button-get' }, 'passioncode.ai/fabric'));
     note.hidden = !absent;
     menu.appendChild(note);

package/payload/plugins/fabric-agent-adapter/skills/building-fabric-services/assets/dashboard-kit/fabric-dashboard.css

@@ -1,4 +1,4 @@
-/* fabric-dashboard-kit@1.1.0 · fabric-dashboard/0.1 (Fabric Agent Contract DEC-0036)
+/* fabric-dashboard-kit@1.1.1 · fabric-dashboard/0.1 (Fabric Agent Contract DEC-0036)
    A Fabric service dashboard shown inside a host pane: usable from 360 CSS px up, navigation always
    reachable, wide content in its own scroll box, one vertical scroller, appearance from the host.
    Copy this file next to fabric-dashboard.js; do not edit it in place. Put the page's own rules in

package/payload/plugins/fabric-agent-adapter/skills/building-fabric-services/assets/dashboard-kit/fabric-dashboard.js

@@ -1,4 +1,4 @@
-/* fabric-dashboard-kit@1.1.0 · fabric-dashboard/0.1 (Fabric Agent Contract DEC-0036)
+/* fabric-dashboard-kit@1.1.1 · fabric-dashboard/0.1 (Fabric Agent Contract DEC-0036)
    Load it same-origin with <script src="fabric-dashboard.js" defer></script>: no inline script, no
    eval, nothing from a CDN. It applies the host's appearance (ED-6, ED-8), folds navigation that
    does not fit into a More menu (ED-3), makes wide boxes keyboard-reachable (ED-4) and keeps
@@ -8,7 +8,7 @@
   'use strict';
 
   var KIT = 'fabric-dashboard-kit';
-  var VERSION = '1.1.0';
+  var VERSION = '1.1.1';
   /* fabric-dashboard-kit:theme-ids:begin */
   var THEMES = ['graphite', 'fabric', 'paper', 'forest', 'ocean', 'ember', 'contrast'];
 /* fabric-dashboard-kit:theme-ids:end */