@passioncode-ai/fabric-agent-adapter 0.5.2 → 0.5.4

package/README.md

@@ -6,20 +6,18 @@
 
 # Fabric Agent Adapter
 
-> **PassionCode.ai — The agent-agnostic operating system for AI-native teams.**
-
-**From vibe coding to passion coding.** PassionCode.ai moves the control point from
-managing agents one by one to operating Projects. Fabric Agent Adapter is the portable
-on-ramp: it helps an existing repository become a compatible, replaceable Provider
-without moving the Project onto one proprietary agent runtime.
+**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 — three 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.
 
 [![npm](https://img.shields.io/npm/v/%40passioncode-ai%2Ffabric-agent-adapter)](https://www.npmjs.com/package/@passioncode-ai/fabric-agent-adapter)
 [![validate](https://github.com/passioncode-ai/fabric-agent-adapter/actions/workflows/validate.yml/badge.svg)](https://github.com/passioncode-ai/fabric-agent-adapter/actions/workflows/validate.yml)
-[![license](https://img.shields.io/badge/license-source--available-blue.svg)](LICENSE)
+[![license](https://img.shields.io/badge/license-AGPL--3.0%20or%20commercial-blue.svg)](LICENSE)
 
-Portable Agent Skills that make any agent Fabric-compatible, for the
-[Fabric Agent Contract](https://github.com/passioncode-ai/fabric-agent-contract):
-`adapting-projects-to-fabric`, `creating-fabric-agents` and
+The skills are `adapting-projects-to-fabric`, `creating-fabric-agents` and
 `building-fabric-services`.
 
 `building-fabric-services` makes an agent a long-lived local service with a dashboard
@@ -52,17 +50,26 @@ For provider bundles the adapting skill helps an agent author:
 The skill never treats generated files as admission. Fabric contract `0.1.0` does not
 yet ship the host registry/runtime needed to connect and authorize a live provider.
 
-## Install
+## Quick start for a new teammate
 
-The repository and the npm package are public; neither path needs an account.
+### Install
 
-npm — no GitHub access required:
+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`,
+then restart your agents. Alone, without any account:
 
 ```bash
 npx @passioncode-ai/fabric-agent-adapter        # installs every skill into the agents hub ~/.agents/skills
 npx @passioncode-ai/fabric-agent-adapter --prune-shadow   # remove ~/.claude/skills copies that shadow the plugin
 ```
 
+Claude Code plugin marketplace:
+
+```text
+/plugin marketplace add passioncode-ai/fabric-agent-adapter
+/plugin install fabric-agent-adapter@fabric-agent-adapter
+```
+
 Generic Agent Skills clients:
 
 ```bash
@@ -71,13 +78,62 @@ npx skills add passioncode-ai/fabric-agent-adapter --skill creating-fabric-agent
 npx skills add passioncode-ai/fabric-agent-adapter --skill building-fabric-services
 ```
 
-Claude Code plugin marketplace:
+### Configure
 
-```text
-/plugin marketplace add passioncode-ai/fabric-agent-adapter
-/plugin install fabric-agent-adapter@fabric-agent-adapter
+Nothing: no account, no key, no environment variable. A service built with the kit creates
+its own token file (mode 600) in its data directory.
+
+### MCP
+
+The adapter is not an MCP server; it builds them. Its sample service serves every capability
+as the MCP tool of its name (`fabric-interop/0.1`), so the proof is a real client calling one.
+With Python 3.9+ and the Claude Code CLI, in a throwaway directory and a temporary MCP config
+(your own Claude Code configuration is not read or written):
+
+```bash
+KIT=plugins/fabric-agent-adapter/skills/building-fabric-services/scripts   # or ~/.agents/skills/building-fabric-services/scripts
+DATA=$(mktemp -d); SERVICES=$(mktemp -d); WORK=$(mktemp -d)
+python3 "$KIT/sample_service.py" serve --port 47190 --data-dir "$DATA" &
+python3 "$KIT/sample_service.py" register --port 47190 --data-dir "$DATA" --services-dir "$SERVICES"
+python3 "$KIT/check_service.py" sample --services-dir "$SERVICES"   # exit 0: no FAIL
+# Register the service for one client run; the token goes in a header, never in argv.
+python3 - "$DATA/service.token" "$WORK/mcp.json" <<'EOF'
+import json, os, sys
+token = open(sys.argv[1]).read().strip()
+with os.fdopen(os.open(sys.argv[2], os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o600), "w") as f:
+    json.dump({"mcpServers": {"sample": {"type": "http", "url": "http://127.0.0.1:47190/mcp",
+               "headers": {"Authorization": "Bearer " + token}}}}, f)
+EOF
+(cd "$WORK" && claude -p "Call the tool mcp__sample__sample_echo with text 'ping' and reply with only the text it returns." \
+  --strict-mcp-config --mcp-config "$WORK/mcp.json" --allowedTools mcp__sample__sample_echo --max-turns 3 < /dev/null)
+# -> ping
+kill %1
+```
+
+Verified 2026-09-30 with Claude Code 2.1.285: 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.
+
+### Develop
+
+There is no build step and no dependency beyond Python 3.9+ and Node.js:
+
+```bash
+npm test                     # validate.py, the Python unit tests, the Node kit tests
+python3 -m unittest discover -s test -v
+python3 test/validate.py
+claude plugin validate ./plugins/fabric-agent-adapter --strict
+claude plugin validate . --strict
 ```
 
+`test/validate.py` reads every SKILL.md front matter as strictly as a YAML parser does; an
+unquoted value holding `: ` fails it. `python3 test/validate.py --frontmatter <SKILL.md ...>`
+checks copies installed elsewhere, such as `~/.agents/skills/*/SKILL.md`. Start in
+[AGENTS.md](AGENTS.md); contributions follow [CONTRIBUTING.md](CONTRIBUTING.md).
+
 ## Use
 
 Ask the agent explicitly:
@@ -118,42 +174,12 @@ python3 "$SKILL_DIR/scripts/adapt_project.py" check /path/to/project \
 Scaffolding is non-destructive by default. It writes only the paths declared in the
 [delivery brief](docs/evidence/specs/2026-08-27-brief.md) and refuses collisions.
 
-## Verify one service (newcomer path)
-
-After installing (above), with Python 3.9+ and no other dependency:
-
-```bash
-KIT=plugins/fabric-agent-adapter/skills/building-fabric-services/scripts   # or ~/.agents/skills/building-fabric-services/scripts
-DATA=$(mktemp -d); SERVICES=$(mktemp -d)
-python3 "$KIT/sample_service.py" serve --port 47190 --data-dir "$DATA" &
-python3 "$KIT/sample_service.py" register --port 47190 --data-dir "$DATA" --services-dir "$SERVICES"
-python3 "$KIT/check_service.py" sample --services-dir "$SERVICES"   # exit 0: no FAIL
-kill %1
-```
-
-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.
-
-## Validate this repository
-
-```bash
-python3 -m unittest discover -s test -v
-python3 test/validate.py
-claude plugin validate ./plugins/fabric-agent-adapter --strict
-claude plugin validate . --strict
-```
-
-`test/validate.py` reads every SKILL.md front matter as strictly as a YAML parser does; an
-unquoted value holding `: ` fails it. `python3 test/validate.py --frontmatter <SKILL.md ...>`
-checks copies installed elsewhere, such as `~/.agents/skills/*/SKILL.md`.
-
 ## Contract pin
 
 The one pin is [`fabric-contract.lock.json`](fabric-contract.lock.json):
 
 - version: `0.1.0`
-- commit: `2ea54f70c161c8b3bf7ec3c567735c7a2d4ce12f`
+- commit: `74d3852f122f5ca5cbc4138a201483531dfa5006`
 
 Every other mention of the contract revision — this section, the skills' metadata, the
 skill card, `adapt_project.py` — must equal it; `python3 test/validate.py` fails a tree
@@ -162,9 +188,8 @@ new adapter release, fixture review, and a complete validation run.
 
 ## License
 
-Source-available under PolyForm Noncommercial or Internal Use; commercial license on
-request (contact@passioncode.ai). SPDX:
-`PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0` — see
-[LICENSE](LICENSE). Versions up to and including v0.4.2 (on GitHub and on npm) were
-released under the MIT License and remain available under it. Contributions are accepted under
-[CLA.md](CLA.md) ([CONTRIBUTING.md](CONTRIBUTING.md)).
+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 — contact@passioncode.ai.
+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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@passioncode-ai/fabric-agent-adapter",
-  "version": "0.5.2",
+  "version": "0.5.4",
   "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'"
@@ -16,6 +16,8 @@
     "plugins",
     "README.md",
     "LICENSE",
+    "COMMERCIAL-LICENSE.md",
+    "CLA.md",
     "CHANGELOG.md",
     "SECURITY.md",
     "!**/__pycache__/**",
@@ -23,7 +25,7 @@
   ],
   "repository": "github:passioncode-ai/fabric-agent-adapter",
   "homepage": "https://github.com/passioncode-ai/fabric-agent-adapter",
-  "license": "PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0",
+  "license": "AGPL-3.0-only OR LicenseRef-PassionCode-Commercial",
   "author": {
     "name": "PassionCode.ai",
     "url": "https://passioncode.ai/"

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

@@ -3,14 +3,14 @@
   "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.5.2",
+  "version": "0.5.4",
   "author": {
     "name": "PassionCode.ai",
     "url": "https://passioncode.ai/"
   },
   "homepage": "https://github.com/passioncode-ai/fabric-agent-adapter",
   "repository": "https://github.com/passioncode-ai/fabric-agent-adapter",
-  "license": "PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0",
+  "license": "AGPL-3.0-only OR LicenseRef-PassionCode-Commercial",
   "keywords": [
     "fabric",
     "agent",

package/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.
-license: PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0
+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 private fabric-agent-contract checkout. Works without those tools in an explicitly degraded structural-check mode.
 metadata:
   author: PassionCode.ai
-  version: "0.5.2"
+  version: "0.5.4"
   contract-version: "0.1.0"
-  contract-commit: "2ea54f70c161c8b3bf7ec3c567735c7a2d4ce12f"
+  contract-commit: "74d3852f122f5ca5cbc4138a201483531dfa5006"
 ---
 
 # 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 `2ea54f70c161c8b3bf7ec3c567735c7a2d4ce12f`.
+- commit `74d3852f122f5ca5cbc4138a201483531dfa5006`.
 
 Read the pinned contract's guide
 `docs/guides/connecting-compatible-agents.md`, the selected profile specification, and
@@ -179,6 +179,27 @@ unverified surfaces. If live Fabric admission/runtime does not yet exist, the la
 remain `NOT VERIFIED`; the completed deliverable is an adaptation-ready provider bundle,
 not a connected provider.
 
+## The repository around the provider
+
+**For a PassionCode.ai repository**, the adapted project's repository follows the organization's
+[repository standard](https://github.com/passioncode-ai/fabric-workspace/blob/main/knowledge/repository-standard.md) (`knowledge/repository-standard.md`
+in the organization's knowledge base; a clone has it at `fabric-workspace/knowledge/`) from its
+first commit:
+
+- `LICENSE`, `COMMERCIAL-LICENSE.md` and `CLA.md` copied byte for byte from the knowledge base's
+  `templates/`, and `AGPL-3.0-only OR LicenseRef-PassionCode-Commercial` in every manifest and
+  every SKILL.md `license:`; `SECURITY.md` when the repository is public;
+- a README whose first heading is the full name, with `## Quick start for a new teammate`
+  (Install; Configure, key names only; MCP, the registration command and one proving tool call,
+  verified with a real client in a temporary config; Develop) and `## License`;
+- an `AGENTS.md` that opens with the template's *Read first* block and closes with *After work*,
+  and a `CLAUDE.md` whose first line is `@AGENTS.md`.
+
+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.
+
 ## Completion format
 
 Report:

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

@@ -16,7 +16,7 @@ from urllib.parse import urlparse
 
 CONTRACT_VERSION = "0.1.0"
 CONTRACT_REPOSITORY = "https://github.com/passioncode-ai/fabric-agent-contract"
-CONTRACT_COMMIT = "2ea54f70c161c8b3bf7ec3c567735c7a2d4ce12f"
+CONTRACT_COMMIT = "74d3852f122f5ca5cbc4138a201483531dfa5006"
 INTEROP_KEY = "https://fabric.passioncode.ai/agent-contract/extensions/interop/0.1"
 MCP_REVISION = "2026-07-28"
 A2A_VERSION = "1.0"

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

@@ -11,14 +11,14 @@ description: >-
   descriptor, the well-known document, the events feed and notifications; ships Python and Node
   reference kits and a live conformance probe. NOT for a one-off script or cron job, a hosted
   SaaS, the provider manifest itself (adapting-projects-to-fabric), or building Fabric Dashboards.
-license: PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0
+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). No network or package install; the contract checkout is optional.
 metadata:
   author: PassionCode.ai
-  version: "0.5.2"
+  version: "0.5.4"
   contract-version: "0.1.0"
   extension: "fabric-service/0.1"
-  extension-commit: "2ea54f70c161c8b3bf7ec3c567735c7a2d4ce12f"
+  extension-commit: "74d3852f122f5ca5cbc4138a201483531dfa5006"
 ---
 
 # Building Fabric services
@@ -209,6 +209,27 @@ 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.
 
+## The repository around the service
+
+**For a PassionCode.ai repository**, the service's repository follows the organization's
+[repository standard](https://github.com/passioncode-ai/fabric-workspace/blob/main/knowledge/repository-standard.md) (`knowledge/repository-standard.md`
+in the organization's knowledge base; a clone has it at `fabric-workspace/knowledge/`) from its
+first commit:
+
+- `LICENSE`, `COMMERCIAL-LICENSE.md` and `CLA.md` copied byte for byte from the knowledge base's
+  `templates/`, and `AGPL-3.0-only OR LicenseRef-PassionCode-Commercial` in every manifest and
+  every SKILL.md `license:`; `SECURITY.md` when the repository is public;
+- a README whose first heading is the full name, with `## Quick start for a new teammate`
+  (Install; Configure, key names only; MCP, the registration command and one proving tool call,
+  verified with a real client in a temporary config; Develop) and `## License`;
+- an `AGENTS.md` that opens with the template's *Read first* block and closes with *After work*,
+  and a `CLAUDE.md` whose first line is `@AGENTS.md`.
+
+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.
+
 ## Migrating an existing service
 
 Read [the migration reference](references/migrating-a-service.md) — the order of

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

@@ -1,6 +1,6 @@
 # fabric-service/0.1 — wire reference
 
-Pinned to `fabric-agent-contract` commit `2ea54f70c161c8b3bf7ec3c567735c7a2d4ce12f`
+Pinned to `fabric-agent-contract` commit `74d3852f122f5ca5cbc4138a201483531dfa5006`
 (`docs/specification/service.md`, DEC-0015). The contract's schemas are normative;
 this page is the working summary. Extension key:
 `https://fabric.passioncode.ai/agent-contract/extensions/service/0.1`.

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

@@ -1,13 +1,13 @@
 ---
 name: creating-fabric-agents
 description: Use when designing and building a NEW agent or provider that must be Fabric-compatible from its first commit — «создай агента, совместимого с фабрикой Passion Code», «новый агент под Fabric», "create a fabric-compatible agent", "build a new Fabric provider", "fabric-ready agent from scratch". Runs the intake grill (capability, named consumer, workflow-or-agent, MCP/A2A/local-runner profile, effect declarations), distils source projects into a knowledge pack whose recorded failures become planted eval fixtures, scaffolds the pinned contract bundle, and sets the two-clock eval expectation with the conformance report. NOT for adapting an existing project (use adapting-projects-to-fabric), building the Fabric host or orchestrator, or generic agent design where Fabric compatibility is not part of the request.
-license: PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0
+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 private fabric-agent-contract checkout. 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.5.2"
+  version: "0.5.4"
   contract-version: "0.1.0"
-  contract-commit: "2ea54f70c161c8b3bf7ec3c567735c7a2d4ce12f"
+  contract-commit: "74d3852f122f5ca5cbc4138a201483531dfa5006"
 ---
 
 # Creating Fabric-compatible agents
@@ -80,6 +80,25 @@ that would show it met, written now, before the implementation. The input corpus
 authored now: it grows from real traces once the provider runs, and the step-1 fixtures
 are its seed because a source project's recorded failures count as production.
 
+**For a PassionCode.ai repository**, the new agent's repository follows the organization's
+[repository standard](https://github.com/passioncode-ai/fabric-workspace/blob/main/knowledge/repository-standard.md) (`knowledge/repository-standard.md`
+in the organization's knowledge base; a clone has it at `fabric-workspace/knowledge/`) from its
+first commit:
+
+- `LICENSE`, `COMMERCIAL-LICENSE.md` and `CLA.md` copied byte for byte from the knowledge base's
+  `templates/`, and `AGPL-3.0-only OR LicenseRef-PassionCode-Commercial` in every manifest and
+  every SKILL.md `license:`; `SECURITY.md` when the repository is public;
+- a README whose first heading is the full name, with `## Quick start for a new teammate`
+  (Install; Configure, key names only; MCP, the registration command and one proving tool call,
+  verified with a real client in a temporary config; Develop) and `## License`;
+- an `AGENTS.md` that opens with the template's *Read first* block and closes with *After work*,
+  and a `CLAUDE.md` whose first line is `@AGENTS.md`.
+
+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.
+
 ## Step 3 — scaffold the provider bundle
 
 Reuse the sibling skill's scaffolder against the new skeleton with the profile chosen at
@@ -93,7 +112,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 `2ea54f70c161c8b3bf7ec3c567735c7a2d4ce12f` and
+Pin exactly contract `0.1.0` at commit `74d3852f122f5ca5cbc4138a201483531dfa5006` 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