@passioncode-ai/fabric-agent-adapter 0.39.0 → 0.39.1

package/CHANGELOG.md

@@ -1,5 +1,50 @@
 # Changelog
 
+## 0.39.1 - 2026-10-21
+
+Fixes from two rounds of blind review of 0.39.0 (FAA-64).
+
+### Fixed
+
+- **The probe no longer crashes on a usage report it is checking.** `check_service.py` compared `unpricedCalls` and
+  `unmeasuredCalls` raw, so `null` or a string raised `TypeError`, and a 400-digit cost raised `OverflowError`; either
+  stopped the whole probe before its other rules ran. Its FAC-SEM-025 arithmetic is now the kit's `usage_findings`, one
+  implementation held to the contract's vectors.
+- **The Python and Node kits answer FAC-SEM-025 as the contract does, message for message.** Both read each count as
+  the contract's `toNumber(x ?? 0)`, each date and project id with `show`, a cost as JavaScript holds the number (an
+  integer beyond a double is Infinity, which is never close to a sum), and a whole number written `5.0` as a count.
+  Python compared raw values and read `5.0` as 0; Node threw on an object such as `{"toString": 1}` in a count, a date
+  or a project id. The vectors now carry each finding's message and both kits compare it: 183 new report cases (208)
+  set every count and the cost of a day and of its first model to eleven values the schema refuses, plus three days
+  with no model rows and four dates and ids that are objects or numbers; eight new cases are the report's JSON text,
+  which each kit parses itself (a 400-digit integer, `1e400`, `2^53 + 1`, `5.0`). The field list is the contract's at this pin,
+  written in the generator.
+- **Messages a person reads carry no em dash**: the probe, the dashboard-kit notice, the board's retry hint and the
+  package refusal (Python and Node alike), the installer and the `npx` CLI, the sample service's page, the session
+  hooks' unread and status lines (`2 unread on the project board: com.list`) and the dashboard kit's Fabric button
+  (`Fabric is not installed. Get it at passioncode.ai/fabric`; kit **1.1.1**, so a service's kit copy is offered the
+  upgrade). The live documentation, evals and the kit's demo page were rewritten the same way.
+
+### Added
+
+- Tests for the producer side of DEC-0091 in both kits: receipts with `tokens_measured=False` through
+  `usage_report`, the day and model `unmeasuredCalls`, none on `byProject`, the probe clean, and the refusal of a
+  non-boolean flag.
+- Evals: the spend scenario expects unknown tokens in `unmeasuredCalls`; a new scenario covers a partner's package
+  and calls (DEC-0090).
+- `interop.md` and `usage.md` say a job whose usage is sent as `null` or `partial` is recorded with
+  `tokens_measured=False`; `estate-record.md` says a service updates its copied kit before a revision carries
+  `publisherScopes` (an older copy trusts a partner's key in every context); FAC-SEM-122 in its header and DEC-0091 in
+  protocol.md's FAC-SEM-025 row.
+- `test/validate.py` fails on U+2014 in the live documentation, the evals, the installer, the CLI and the kit's demo,
+  and when README states which version a checkout is or which release is the latest (it said 0.21.0 until now); both
+  checks have tests. The compiled-revision tests name the two contract revisions they need when they skip.
+
+### Raised with the contract (not changed here)
+
+- `chainOf` names a `{sub, partner}` node by its `org:` id, and job ownership and idempotency keys do not include the
+  partner. The kits follow `c55f2d5` until the contract decides (board thread `6e66a023`, FAA-64).
+
 ## 0.39.0 - 2026-10-20
 
 ### Changed
@@ -12,7 +57,8 @@
 - **Unmeasured tokens are named** (DEC-0091, contract CT-62). `make_usage_receipt(..., tokens_measured=False)` /
   `makeUsageReceipt(..., { tokensMeasured: false })` writes `tokensMeasured: false`; the report counts such calls in
   `unmeasuredCalls` on the day and the model row, and FAC-SEM-025 in both kits and `check_service.py` refuses a row
-  with more unmeasured calls than calls or a day whose count is not its models' sum. Three new usage vectors (25).
+  with more unmeasured calls than calls or a day whose count is not its models' sum. Four new usage vectors (25; this
+  line said three until 0.39.1).
 - **A partner in the delegation chain** (DEC-0090, contract CT-58). Both verifiers take `{partner: "org:<id>"}` as the
   innermost actor under at least one agent: it counts toward the depth limit and ends the chain, and the checked chain
   lists it by its `org:` id. Outermost, with an `act` beneath, `personal` or an `ORG:` prefix is `malformed-chain`.

package/README.md

@@ -8,7 +8,7 @@
 
 **Fabric Agent Adapter** makes any agent Fabric-compatible. Fabric is PassionCode.ai's
 product, the CEO AI agent: you talk to Fabric, and it chooses, binds and runs the agents that
-do the work. This adapter is how an agent becomes one Fabric can bind — four Agent Skills,
+do the work. This adapter is how an agent becomes one Fabric can bind: four Agent Skills,
 Python and Node reference kits and a live conformance probe for the
 [Fabric Agent Contract](https://github.com/passioncode-ai/fabric-agent-contract). It also works
 on its own: the skills, kits and probe need no Fabric install.
@@ -51,8 +51,8 @@ is the board-first workflow.
 
 `building-fabric-services` makes an agent a long-lived local service with a dashboard
 that is always alive, runs as one copy, keeps its state through a reinstall and appears
-in Fabric Dashboards by itself — the `fabric-service/0.1` extension. It also makes an **online** agent
-or dashboard — an `https` origin on a platform — a Fabric service (the remote placement, DEC-0019): the same
+in Fabric Dashboards by itself: the `fabric-service/0.1` extension. It also makes an **online** agent
+or dashboard (an `https` origin on a platform) a Fabric service (the remote placement, DEC-0019): the same
 four routes behind the token, a `__Host-` session cookie, and one descriptor on the operator's computer;
 `scripts/sample-remote-service.mjs` is the complete example. It ships Python and
 Node reference kits (`scripts/fabric_service.py`, `scripts/fabric-service.mjs`), a
@@ -68,8 +68,8 @@ python3 plugins/fabric-agent-adapter/skills/building-fabric-services/scripts/che
 
 The dashboard itself is built from the **dashboard kit** (`assets/dashboard-kit/`, `fabric-dashboard/0.1`,
 contract DEC-0036): one stylesheet and one script that keep the page usable from 360 CSS px inside a host
-pane beside the agent console — navigation that folds into a More menu, wide tables in their own scroll
-box, sticky chrome at most 120 px — with seven WCAG AA themes (light and dark) that follow the host's
+pane beside the agent console (navigation that folds into a More menu, wide tables in their own scroll
+box, sticky chrome at most 120 px) with seven WCAG AA themes (light and dark) that follow the host's
 `fabric_appearance` cookie. `scripts/dashboard_kit.py install|status` copies and checks it,
 `scripts/check_dashboard_layout.mjs` measures a rendered page in WebKit at 360, 480, 768 and 1280 px
 (Playwright; `NOT_RUN` without it), and the probe's `dashboard.declared` checks the declaration. The
@@ -117,7 +117,7 @@ yet ship the host registry/runtime needed to connect and authorize a live provid
 ### Install
 
 With the [PassionCode.ai launcher](https://github.com/passioncode-ai/passioncode) the adapter
-comes with every other PassionCode.ai skill — `npx @passioncode-ai/passioncode@latest update`,
+comes with every other PassionCode.ai skill: `npx @passioncode-ai/passioncode@latest update`,
 then restart your agents. Alone, without any account:
 
 ```bash
@@ -175,8 +175,8 @@ kill %1
 
 Verified 2026-10-01 from the published npm package 0.5.4 (`npx` into a throwaway hub, `KIT`
 pointing at the installed skill) with Claude Code 2.1.286: the probe reported 27 rules, 0 FAIL;
-the CLI connected to the sample over streamable HTTP, called `sample.echo` and printed `ping`. The probe prints one line per rule —
-`PASS`, `FAIL` or `NOT_RUN` with its evidence — and exits 1 on any `FAIL`; run it against your
+the CLI connected to the sample over streamable HTTP, called `sample.echo` and printed `ping`. The probe prints one line per rule
+(`PASS`, `FAIL` or `NOT_RUN` with its evidence) and exits 1 on any `FAIL`; run it against your
 own service by its id once its installer has written the descriptor.
 `FABRIC_REAL_CLIENT=1 python3 -m unittest discover -s test -p test_real_client.py` repeats the connection check
 (every sample tool listed, no model call) in the test suite.
@@ -264,8 +264,8 @@ The default pin for new bundles is [`fabric-contract.lock.json`](fabric-contract
 - version: `0.1.0`
 - commit: `c55f2d5a11c9a0197e958e87212fca7ae1154769`
 
-Every other mention of the default contract revision — this section, the skills' metadata, the
-skill card, `adapt_project.py` — must equal it; `python3 test/validate.py` fails a tree
+Every other mention of the default contract revision (this section, the skills' metadata, the
+skill card, `adapt_project.py`) must equal it; `python3 test/validate.py` fails a tree
 where one does not. The sole live legacy exception is the immutable
 `SUPPORTED_CONTRACT_COMMITS` declaration in the scaffolder: previously issued bundles
 keep their selected legacy lock and require that exact clean contract checkout. The
@@ -288,14 +288,16 @@ FABRIC_CONTRACT_OLD=/path/to/legacy-contract FABRIC_CONTRACT_NEW=/path/to/curren
   python3 -m unittest discover -s test -p test_contract_revisions.py -v
 ```
 
-Without both environment variables, those tests explicitly skip as `NOT_RUN`.
-This source checkout is 0.21.0. 0.20.0 is the latest published GitHub/npm release (2026-10-12; 0.7.0 and 0.11.0
-were never released); 0.21.0 is published by its `v0.21.0` tag. Source delivery does not update installed skills or live sessions.
+`FABRIC_CONTRACT_OLD` is a checkout of the legacy fixtures' revision (`OLD` in `test/test_contract_revisions.py`) and
+`FABRIC_CONTRACT_NEW` one of the pin; each needs `pnpm install --frozen-lockfile` in its own folder (pnpm refuses a
+symlinked `node_modules`). Without both environment variables, those tests explicitly skip as `NOT_RUN`, naming the
+two revisions. What each version changed and when it was released is in [CHANGELOG.md](CHANGELOG.md). Source delivery
+does not update installed skills or live sessions.
 
 ## License
 
 Open source under the [GNU AGPL-3.0](LICENSE). A [commercial license](COMMERCIAL-LICENSE.md) is
-available for use that does not meet the AGPL's terms — [passioncode.ai/business](https://passioncode.ai/business/).
+available for use that does not meet the AGPL's terms: [passioncode.ai/business](https://passioncode.ai/business/).
 Versions before 0.5.3 were released under PolyForm Noncommercial or Internal Use (v0.4.3 to
 v0.5.2) and MIT (v0.4.2 and earlier); each keeps the licence it was released under.
 Contributions are accepted under [CLA.md](CLA.md) ([CONTRIBUTING.md](CONTRIBUTING.md)).

package/bin/fabric-agent-adapter.js

@@ -26,7 +26,7 @@ Usage:
   npx @passioncode-ai/fabric-agent-adapter [--force]
       install every skill into the agents hub ~/.agents/skills
   npx @passioncode-ai/fabric-agent-adapter --target claude [--force]
-      plain copy into ~/.claude/skills — refused while the plugin is installed
+      plain copy into ~/.claude/skills (refused while the plugin is installed)
   npx @passioncode-ai/fabric-agent-adapter --prune-shadow
       remove plain ~/.claude/skills copies that shadow the installed plugin
   npx @passioncode-ai/fabric-agent-adapter --help
@@ -124,7 +124,7 @@ function main(argv) {
 
   const { skillRoot, names } = skillNames();
   if (!names.length) {
-    console.error(`error: no skills found under ${skillRoot} — corrupted package?`);
+    console.error(`error: no skills found under ${skillRoot}; corrupted package?`);
     return 1;
   }
   const home = os.homedir();
@@ -132,7 +132,7 @@ function main(argv) {
 
   if (prune) {
     if (!hasPlugin) {
-      console.error(`error: the ${PLUGIN_ID} plugin is not installed, so a copy in ~/.claude/skills is not a shadow — nothing removed.`);
+      console.error(`error: the ${PLUGIN_ID} plugin is not installed, so a copy in ~/.claude/skills is not a shadow; nothing removed.`);
       return 1;
     }
     pruneShadows(home, names);
@@ -151,8 +151,8 @@ function main(argv) {
       // One owner per artefact on disk: a plain copy over someone else's link freezes the skill
       // at this version, and its owner stops updating it. --force does not override this.
       console.log(owner === 'launcher'
-        ? `skip: ${name} at ${dest} is managed by the PassionCode launcher — update it with: npx @passioncode-ai/passioncode@latest update`
-        : `skip: ${name} at ${dest} is a link managed elsewhere — remove the link first to install a copy here`);
+        ? `skip: ${name} at ${dest} is managed by the PassionCode launcher; update it with: npx @passioncode-ai/passioncode@latest update`
+        : `skip: ${name} at ${dest} is a link managed elsewhere; remove the link first to install a copy here`);
       continue;
     }
     if (fs.existsSync(dest) && !force) {
@@ -166,7 +166,7 @@ function main(argv) {
   if (target === 'agents' && !hasPlugin) {
     console.log(`Claude Code reads plugins, not the hub:\n  claude plugin marketplace add ${REPO} && claude plugin install ${PLUGIN_ID}`);
   }
-  console.log('Restart your agent — skills load at session start.');
+  console.log('Restart your agent: skills load at session start.');
   return 0;
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@passioncode-ai/fabric-agent-adapter",
-  "version": "0.39.0",
+  "version": "0.39.1",
   "description": "Create Fabric-compatible agents, run them as always-alive local services with dashboards (fabric-service/0.1), and adapt existing projects to the Fabric Agent Contract. This package is the installer CLI.",
   "scripts": {
     "test": "python3 test/validate.py && python3 -m unittest discover -s test -q && node --test 'test/*.test.mjs'"

package/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.39.0",
+  "version": "0.39.1",
   "author": {
     "name": "PassionCode.ai",
     "url": "https://passioncode.ai/"

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

@@ -1,11 +1,11 @@
 ---
 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.39.0"
+  version: "0.39.1"
   contract-version: "0.1.0"
   contract-commit: "c55f2d5a11c9a0197e958e87212fca7ae1154769"
 ---
@@ -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,
@@ -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/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/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/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,7 +18,7 @@ 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.39.0"
+  version: "0.39.1"
   contract-version: "0.1.0"
   extension: "fabric-service/0.1"
   extension-commit: "c55f2d5a11c9a0197e958e87212fca7ae1154769"
@@ -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 |
 |---|---|---|
@@ -103,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
@@ -127,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;
@@ -139,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:
@@ -157,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")
@@ -172,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.
@@ -187,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.
@@ -217,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
@@ -235,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
@@ -253,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
@@ -268,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`).
@@ -277,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
@@ -313,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:
@@ -328,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
@@ -336,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
@@ -350,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.
 
@@ -367,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.
@@ -397,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/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>