@passioncode-ai/fabric-agent-adapter 0.8.2 → 0.8.3

package/CHANGELOG.md

@@ -1,5 +1,32 @@
 # Changelog
 
+## 0.8.3 - 2026-10-10
+
+The contract pin moves to Fabric Agent Contract `main` `52da526` (DEC-0034 and DEC-0035, the operator
+channel), so the operator channel proposal is normative under the pin. Bundles issued under the DEC-0033,
+DEC-0031, DEC-0024, DEC-0021, DEC-0020 and DEC-0019 revisions stay valid.
+
+### Changed
+
+- **Default contract pin `78b2da0` → `52da526d7cc1e063d74c5b520dbc03d0ace15246`** (FAA-15). `78b2da0`
+  (DEC-0033) joins `SUPPORTED_CONTRACT_COMMITS`. The revisions between add the `fabric-operator-channel/0.1`
+  profile (DEC-0034, OC-1…OC-13; DEC-0035, OC-14…OC-17 for shared groups), its status schema
+  `operator-channel-status.schema.json` and the optional well-known `surfaces.operatorChannel`. Nothing in the
+  provider manifest or the MCP, A2A and local-runner profiles changes, and every descriptor and well-known
+  document the kits write stays valid; the kits do not serve the channel yet. Checked: `npm test`; both
+  compiled-schema arms against clean checkouts at `2ce3922` and `52da526`; descriptors written by the sample
+  service (`none` and `launchd`) validate against the new `service-descriptor.schema.json`.
+- **The operator channel proposal is no longer "newer than the pin".** `creating-fabric-agents` step 6 and
+  `adapting-projects-to-fabric` step 8 cite DEC-0034 under the pin, show the recorded answer as `proposal` in
+  the channel status document when the agent serves `surfaces.operatorChannel`, check that document against
+  the pinned `operator-channel-status.schema.json`, and keep the channel's runtime rules `NOT_RUN` (the probe
+  has no rule for them). For a channel bound in a group shared with other bots they name OC-14…OC-17: silent
+  unless addressed; a bare `/command` in a group is not addressed. Scenario evals `operator-channel-proposal`
+  changed first.
+- **`references/protocol.md`** summarises what the pin carries: the Windows services folder, the `systemd`
+  and `task-scheduler` managers, Windows paths and token files (DEC-0032, DEC-0033), and
+  `surfaces.operatorChannel` (DEC-0034).
+
 ## 0.8.2 - 2026-10-10
 
 The Python service kit runs on Windows and Linux (contract DEC-0032, DEC-0033), and the contract pin moves to the DEC-0033 merge.

package/README.md

@@ -191,7 +191,7 @@ Scaffolding is non-destructive by default. It writes only the paths declared in
 The default pin for new bundles is [`fabric-contract.lock.json`](fabric-contract.lock.json):
 
 - version: `0.1.0`
-- commit: `78b2da018d2c4bd9ac1bde1dc3b7f1a110a175f5`
+- commit: `52da526d7cc1e063d74c5b520dbc03d0ace15246`
 
 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
@@ -218,8 +218,8 @@ FABRIC_CONTRACT_OLD=/path/to/legacy-contract FABRIC_CONTRACT_NEW=/path/to/curren
 ```
 
 Without both environment variables, those tests explicitly skip as `NOT_RUN`.
-This source checkout is 0.8.2. 0.8.1 is the latest published GitHub/npm release (2026-10-08; 0.7.0 was never
-released); 0.8.2 is published by its `v0.8.2` tag. Source delivery does not update installed skills or live sessions.
+This source checkout is 0.8.3. 0.8.2 is the latest published GitHub/npm release (2026-10-10; 0.7.0 was never
+released); 0.8.3 is published by its `v0.8.3` tag. Source delivery does not update installed skills or live sessions.
 
 ## License
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@passioncode-ai/fabric-agent-adapter",
-  "version": "0.8.2",
+  "version": "0.8.3",
   "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.",
-  "version": "0.8.2",
+  "version": "0.8.3",
   "author": {
     "name": "PassionCode.ai",
     "url": "https://passioncode.ai/"

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

@@ -5,9 +5,9 @@ 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.8.2"
+  version: "0.8.3"
   contract-version: "0.1.0"
-  contract-commit: "78b2da018d2c4bd9ac1bde1dc3b7f1a110a175f5"
+  contract-commit: "52da526d7cc1e063d74c5b520dbc03d0ace15246"
 ---
 
 # Adapting projects to Fabric
@@ -70,7 +70,7 @@ Use exactly:
 
 - contract version `0.1.0`;
 - repository `https://github.com/passioncode-ai/fabric-agent-contract`;
-- commit `78b2da018d2c4bd9ac1bde1dc3b7f1a110a175f5`.
+- commit `52da526d7cc1e063d74c5b520dbc03d0ace15246`.
 
 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
@@ -200,11 +200,18 @@ operator's four steps:
 3. run the agent's link command;
 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`
+(`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
-conformance report, and do not ask again. Creating the bot, storing the token and enabling 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
-enable the channel yourself. DEC-0034 is newer than the default pin: cite it by that path and id, and keep
-channel conformance `NOT_RUN` until the pin carries it. An agent with neither stops nor notify
+enable the channel yourself. The default pin carries DEC-0034 and DEC-0035: a served status document is checked
+against the pinned `schemas/operator-channel-status.schema.json`; the channel's runtime rules have
+no probe rule here yet, so report them `NOT_RUN`. An agent with neither stops nor notify
 events skips this step.
 
 ## The repository around the provider

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

@@ -16,10 +16,10 @@ from urllib.parse import urlparse
 
 CONTRACT_VERSION = "0.1.0"
 CONTRACT_REPOSITORY = "https://github.com/passioncode-ai/fabric-agent-contract"
-CONTRACT_COMMIT = "78b2da018d2c4bd9ac1bde1dc3b7f1a110a175f5"
+CONTRACT_COMMIT = "52da526d7cc1e063d74c5b520dbc03d0ace15246"
 # #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, "623bf61358c339cb10297807b3f024b5d9f1f327", "23f9fda4c05f8a3852246ee98d4f2adf74ed0875", "9091d3d6606b0c4b5591a38c3674356a01fd7f55", "df55c8c54a23251342a7ee57ba95642b7eb39e61", "2ce392291c6668598d12cd38327e24696b5ca15c")
+SUPPORTED_CONTRACT_COMMITS = (CONTRACT_COMMIT, "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/plugins/fabric-agent-adapter/skills/building-fabric-services/SKILL.md

@@ -16,10 +16,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 use lifecycle manager none until a systemd adapter exists). 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.8.2"
+  version: "0.8.3"
   contract-version: "0.1.0"
   extension: "fabric-service/0.1"
-  extension-commit: "78b2da018d2c4bd9ac1bde1dc3b7f1a110a175f5"
+  extension-commit: "52da526d7cc1e063d74c5b520dbc03d0ace15246"
 ---
 
 # Building Fabric services

package/plugins/fabric-agent-adapter/skills/building-fabric-services/references/protocol.md

@@ -1,15 +1,17 @@
 # fabric-service/0.1 — wire reference
 
-Pinned to `fabric-agent-contract` commit `78b2da018d2c4bd9ac1bde1dc3b7f1a110a175f5`
-(`docs/specification/service.md`, DEC-0015; the usage report DEC-0021). The contract's schemas are normative;
+Pinned to `fabric-agent-contract` commit `52da526d7cc1e063d74c5b520dbc03d0ace15246`
+(`docs/specification/service.md`, DEC-0015; the usage report DEC-0021; Windows and Linux supervision
+DEC-0032 and DEC-0033; the operator channel DEC-0034 and DEC-0035). The contract's schemas are normative;
 this page is the working summary. Extension key:
 `https://fabric.passioncode.ai/agent-contract/extensions/service/0.1`.
 
 ## Descriptor — written by the installer
 
 Directory: macOS `~/Library/Application Support/ai.passioncode.fabric/services/`,
-Linux `${XDG_DATA_HOME:-~/.local/share}/passioncode-fabric/services/`, or
-`FABRIC_SERVICES_DIR`. File `<id>.<instance>.json`, mode 0600, atomic.
+Linux `${XDG_DATA_HOME:-~/.local/share}/passioncode-fabric/services/`, Windows
+`%LOCALAPPDATA%\passioncode-fabric\services\` (DEC-0032), or `FABRIC_SERVICES_DIR`.
+File `<id>.<instance>.json`, mode 0600 (on Windows a protected ACL), atomic.
 
 | Field | Rule |
 |---|---|
@@ -17,10 +19,10 @@ Linux `${XDG_DATA_HOME:-~/.local/share}/passioncode-fabric/services/`, or
 | `id`, `instance` | `^[a-z][a-z0-9-]{1,62}$`, `^[a-z][a-z0-9-]{0,31}$` (default `default`); the pair is unique per machine |
 | `name`, `summary` | ≤ 80 and ≤ 200 characters |
 | `origin` | `http://127.0.0.1:<port>`; the port is a machine-wide claim |
-| `auth` | `tokenFile` (0600); `header` default `Authorization` with `scheme` `Bearer`; any other header carries the raw token with `scheme: "none"` |
-| `lifecycle` | `manager` `launchd` (then `label` and `plist`) or `none` |
+| `auth` | `tokenFile` (0600; on Windows a protected ACL — owner and every granting entry the current user, SYSTEM or Administrators: service.md *Windows token files*, DEC-0032, DEC-0033); `header` default `Authorization` with `scheme` `Bearer`; any other header carries the raw token with `scheme: "none"` |
+| `lifecycle` | `manager` `launchd` (then `label` and `plist`), `systemd` (then `unit`, a `systemctl --user` unit), `task-scheduler` (then `task`, a per-user Scheduled Task) or `none`; `unit` and `task` are refused beside any other manager (DEC-0032). The Python kit and the probe accept all four; the Node kit still accepts only `launchd` and `none` (FAA-16) |
 | `paths` | `data` (required), `logs[]`, optional `config`, `cache` |
-| `commands` | only `doctor` and `update`, argument arrays whose first item is an absolute or `~/` path |
+| `commands` | only `doctor` and `update`, argument arrays whose first item is an absolute or `~/` path (Windows: also `C:\…`, `C:/…` or `~\…`, never a network share — DEC-0032) |
 | `source.repository`, `fabricManifest` | optional |
 | `installedAt`, `installedBy` | when and by which installer version |
 
@@ -48,7 +50,10 @@ No auth; the Host/Origin guard applies; answered from memory in under 100 ms.
 - `build` needs `commit` or `digest` (`sha256:<64 hex>`).
 - `summary`: at most six tiles; `attention: true` counts toward the host's badge.
 - `surfaces.events` is required; `dashboard` and `mcp` when the service has them; `usage`
-  (DEC-0021) when the service reports its spend — see [the usage reference](usage.md).
+  (DEC-0021) when the service reports its spend — see [the usage reference](usage.md);
+  `operatorChannel.path` (DEC-0034) when the service has an operator channel — its status
+  document follows the contract's `operator-channel-status.schema.json` and is token-protected
+  like the events feed. The kits do not serve it yet.
 
 ## Events page — `GET /fabric/v1/events?after=<cursor>&limit=<n>`
 

package/plugins/fabric-agent-adapter/skills/creating-fabric-agents/SKILL.md

@@ -5,9 +5,9 @@ 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. Ships in one plugin with adapting-projects-to-fabric, whose scripts it reuses.
 metadata:
   author: PassionCode.ai
-  version: "0.8.2"
+  version: "0.8.3"
   contract-version: "0.1.0"
-  contract-commit: "78b2da018d2c4bd9ac1bde1dc3b7f1a110a175f5"
+  contract-commit: "52da526d7cc1e063d74c5b520dbc03d0ace15246"
 ---
 
 # Creating Fabric-compatible agents
@@ -119,7 +119,7 @@ python3 <plugin-dir>/skills/adapting-projects-to-fabric/scripts/adapt_project.py
   --schema-base <immutable-base-uri>
 ```
 
-Pin exactly contract `0.1.0` at commit `78b2da018d2c4bd9ac1bde1dc3b7f1a110a175f5` and
+Pin exactly contract `0.1.0` at commit `52da526d7cc1e063d74c5b520dbc03d0ace15246` and
 read the pinned guide before implementing protocol details. If this skill is installed
 without its sibling, the scaffolder is absent: create the bundle by hand from the pinned
 contract's `docs/guides/connecting-compatible-agents.md` and mark the structural check
@@ -179,11 +179,18 @@ operator's four steps:
 3. run the agent's link command;
 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`
+(`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 in the
-report, and do not ask again. Creating the bot, storing the token and enabling the channel are the
+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 enable the
-channel yourself. DEC-0034 is newer than the default pin: cite it by that path and id, and keep
-channel conformance `NOT_RUN` until the pin carries it. An agent with neither stops nor notify
+channel yourself. The default pin carries DEC-0034 and DEC-0035: a served status document is checked against
+the pinned `schemas/operator-channel-status.schema.json`; the channel's runtime rules have no
+probe rule here yet, so report them `NOT_RUN`. An agent with neither stops nor notify
 events skips this step.
 
 ## Completion format