@passioncode-ai/fabric-agent-adapter 0.58.0 → 0.59.0

package/CHANGELOG.md

@@ -1,5 +1,49 @@
 # Changelog
 
+## 0.59.0 (2026-11-03)
+
+Portable from day 0 (FAA-191, RM-36): on top of 0.58.0's source and instance, every new agent gets a data home, a
+data kind and an uptime category, and a new private agent a `LICENSE` naming its copyright holder, from its first commit, and runs the transfer
+audit at every release until the contract's export (CT-194) replaces it.
+
+### Added
+
+- creating-fabric-agents' intake grill asks three more rows: **Does it run around the clock?** (uptime category A, a
+  cloud host from the first release, Heroku unless a reason names another, from the cloud Fabric-server template once
+  its repository exists; or B, a local service only), **Whose data does it keep?** (kind U, data of people outside the
+  owner's team, never in the source, a copy or its tests; or O; in doubt U) and **Who holds the copyright?**
+- Step 2 gives the data a home of its own, `<agent>-data` (a folder beside the checkout or a private repository of
+  that name), and the README names the data kind and the uptime category; an agent someone builds for themselves gets
+  a `LICENSE` naming the holder (all rights reserved unless the owner gives other terms).
+- Step 5: every release runs `fabric_source_check.py check` as the transfer audit, in Git mode on the checkout and
+  with `--every-file` on a clean copy of what Git would commit (building-fabric-services' `references/package.md`).
+  references/source-and-instance.md adds why never the checkout (its ignored configuration and dependency folders
+  `--every-file` reads too), and that a `LICENSE` whose holder is on the owner's list is named in
+  `.fabric-source-ignore`, since authorship travels with the source.
+- references/source-and-instance.md (both skills): *The data home and its kind*; references/where-agents-run.md:
+  *Uptime: A or B* and a checklist line. building-fabric-services' Step 0 answers carry the same (data kind, data
+  home, uptime, holder, the audit per release).
+- Scenario evals `portable-from-day-zero` (creating-fabric-agents) and `new-service-names-data-and-uptime`
+  (building-fabric-services), a trigger, and `test/test_portable_from_day_zero_prose.py` pinning the prose to them.
+
+### Changed
+
+- The eval `own-agent-licence-is-the-owners-choice` expects a `LICENSE` naming the holder; still no AGPL or
+  commercial licence files unasked. The shared operator-channel reference and building-fabric-services say the same
+  for an agent built new, and that the kit files the adapter copies in keep their own licence
+  (`AGPL-3.0-only OR LicenseRef-PassionCode-Commercial`); adapting-projects-to-fabric leaves an existing agent's
+  licence as it is.
+- where-agents-run.md: Heroku is the default host of an A agent unless it runs in the person's or an organization's
+  PassionCode cloud or is sold; an A agent's data lives in a durable store, never the host's own folder (source-and-instance.md's
+  data home says the same for a host that does not keep its disk), and on a host with no Fabric hub it answers only
+  what reaches its own origin.
+- building-fabric-services' gotchas are shorter (the same rules); `test_fabric_kit` runs its by-path load with `-B`.
+
+### Upgrading
+
+- Nothing to change for an existing agent: an adapted project keeps its licence, data and release checks as they
+  are. A new one answers the three grill rows before its first commit.
+
 ## 0.58.0 (2026-11-03)
 
 Portable agents, part 1 (FAA-188, RM-36): an agent keeps its source apart from its instance from its first commit, and

package/package.json

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

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

@@ -5,7 +5,7 @@ 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.58.0"
+  version: "0.59.0"
   contract-version: "0.1.0"
   contract-commit: "3830a3353923e20f826d466610e1c479f120bec0"
 ---
@@ -242,7 +242,8 @@ relayed, DEC-0121). An agent with neither stops nor notify events skips this ste
 repository standard (`knowledge/repository-standard.md`) from its first commit: the licence files,
 the README quick start verified with a real client, `AGENTS.md` and `CLAUDE.md`, listed in the
 shared reference above. An agent someone builds for themselves is not a PassionCode.ai repository:
-its licence is its owner's choice and none of those files is required of it.
+its licence is its owner's choice and none of those files is required of it (an agent built new with
+creating-fabric-agents carries a `LICENSE` naming its holder; an existing one keeps what it has).
 
 ## Completion format
 

package/plugins/fabric-agent-adapter/skills/adapting-projects-to-fabric/references/operator-channel-and-repository.md

@@ -63,4 +63,7 @@ the project).
 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, except that an agent built new carries a `LICENSE` naming the copyright holder (all rights reserved
+unless the owner gives other terms), as does a new private agent built for a client; files the adapter copies in (the service kit, the dashboard kit) keep their own
+licence, `AGPL-3.0-only OR LicenseRef-PassionCode-Commercial` ([COMMERCIAL-LICENSE.md](https://github.com/passioncode-ai/fabric-agent-adapter/blob/main/COMMERCIAL-LICENSE.md)).
+The verified MCP quick start is still how anyone learns to drive it.

package/plugins/fabric-agent-adapter/skills/adapting-projects-to-fabric/references/source-and-instance.md

@@ -13,6 +13,7 @@ on it.
 ## Contents
 
 - [The layout](#the-layout)
+- [The data home and its kind](#the-data-home-and-its-kind)
 - [The check](#the-check)
 
 ## The layout
@@ -31,7 +32,7 @@ on it.
   (an organization's) is a sibling instance, `<id>.<instance>`, never a folder inside the personal one
   (`references/estate-record.md` of that skill).
 - **Ignore the instance in the source**: `.gitignore` names the real configuration (`config/*.json` with
-  `!config/*.example.json`), an instance folder that sits inside the checkout during development, and what running
+  `!config/*.example.json`), an instance folder an existing project still keeps inside the checkout, and what running
   the agent leaves (`__pycache__/`, `*.pyc`), which the check would otherwise report as binary in Git mode.
 - **State documents are instance data.** A handoff, a decision log or a backlog about this codebase is source
   documentation; a record of what this installation did (runs, conversations, the owner's notes, a journal) lives in
@@ -47,6 +48,27 @@ on it.
   keeps the scaffold's sentinel, and a person's name or account is never written there. The adapter moves both when the
   contract decides how an instance renames them (FAA-188 part 2).
 
+## The data home and its kind
+
+- **The data has a home of its own from the first commit: `<agent>-data`.** For an agent that is not a kit service it
+  is a folder beside the checkout, never inside it, and `<AGENT>_DATA_DIR` names it (its default is
+  `../<agent>-data`); a kit service keeps the kit's folders above. When the owner keeps the data in Git, it goes to a
+  separate private repository named `<agent>-data`, never to the source's repository. On a cloud host that does not
+  keep its disk across a restart (Heroku and the like, an uptime A agent's default), the data home is a durable store
+  the same variable names (a database, an object store, that private repository); the folder and the kit's folders
+  serve a machine whose disk persists. A copy of the agent starts with an empty home of its own and never connects
+  to the original's.
+- **The README names the kind of the data.** **U**: the agent keeps data of people outside the owner's team
+  (messages, support requests, reviews, customers' answers); it never enters the source, a copy or its tests, and the
+  source holds only the schema and synthetic fixtures (its real-trace corpus and replay samples live in the data
+  home). **O**: it keeps none (a tool or service for other agents, the
+  owner's reports, runs and media); its working data still goes to the data home. When in doubt, the kind is U.
+- **Every release runs the transfer audit.** `fabric_source_check.py check <project-root>` in Git mode, and
+  `check <clean-copy> --every-file` on a clean copy of what Git would commit (`git ls-files --cached --others
+  --exclude-standard`, as building-fabric-services' `references/package.md` makes it; never the checkout itself, whose ignored
+  configuration and dependency folders `--every-file` reads too), each exit 0, with the owner's list or its absence recorded, until the contract's export (CT-194)
+  replaces it.
+
 ## The check
 
 `fabric_source_check.py check` reads the files the source would carry (what Git would commit: tracked files and
@@ -124,7 +146,10 @@ python3 <plugin-dir>/skills/adapting-projects-to-fabric/scripts/fabric_source_ch
   repository is not read; `--every-file` and a folder outside Git read its files, its `.git` left out. An exception line (`!`) is refused, since what it would
   bring back would go unread. Name the files, or a folder that holds
   only synthetic vectors, never a whole source folder (a nested repository checked in its own tree is the one
-  exception), and say why on the line above. A file `pack` refuses by its name cannot ship in a package: a public
+  exception), and say why on the line above. The `LICENSE` is the other: its copyright line names the holder, which is
+  authorship and travels with the source, so when the holder is on the owner's list the licence file is named in the ignore
+  file by its own path (`LICENSE`, `LICENSE.md`) with that reason (`# the copyright holder is authorship and travels with the source`); no other file of the
+  owner's is. A file `pack` refuses by its name cannot ship in a package: a public
   certificate is renamed `*.crt`; a project `.npmrc` that holds no credential may be named in the ignore file, with
   that reason, for the source check (the line then hides whatever is added to it later, so keep it credential-free),
   and `pack` still refuses it, so a package is made from a copy without it (its

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

@@ -14,7 +14,7 @@ license: AGPL-3.0-only OR LicenseRef-PassionCode-Commercial
 compatibility: Python 3.9+ or Node.js 20+ for the kits (Node.js 22+ for a Linux service's instance lock); 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.58.0"
+  version: "0.59.0"
   contract-version: "0.1.0"
   extension: "fabric-service/0.1"
   extension-commit: "3830a3353923e20f826d466610e1c479f120bec0"
@@ -63,6 +63,7 @@ Answer before writing code, and record the answers in the project README:
 | Port | one number; run the claim check below before choosing it |
 | Who calls it | the named agents or people, and through which surface (Step 1) |
 | What it stores | the store, where it lives (Step 2, rule 5), and what survives uninstall |
+| Data and uptime | kind U or O, kit folders, a durable store or `<id>-data`, uptime A or B; a new agent's `LICENSE` holder, transfer audit per release (creating-fabric-agents) |
 | What it tells the operator | the events worth a notification (Step 5) |
 
 ## Step 1: choose the surfaces
@@ -353,9 +354,9 @@ first commit:
 
 Whoever owns the repository, an agent with a page gets the dashboard rule block in its `AGENTS.md`
 (below). 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.
+someone builds for themselves is not a PassionCode.ai repository:** its licence is its owner's choice, the organization
+publishes and lists nothing about it, of these files one built new needs only a `LICENSE` naming its copyright holder (copied kit files keep
+theirs), and the verified MCP quick start teaches anyone to drive it.
 
 ## Online services: the remote placement
 
@@ -418,20 +419,16 @@ this estate needs.
 ## 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
-  another service already held.
-- `launchctl bootstrap` right after `bootout` fails with I/O error 5 until the unload
-  finishes; wait, then retry.
+- A health probe that only checks HTTP 200 accepts any program on the port: compare
+  `service.id` and `service.instance`.
+- `launchctl bootstrap` right after `bootout` fails with I/O error 5: wait for the unload, then retry.
 - Under launchd `PATH` is bare. Pin the interpreter by absolute path; set `PATH`
   explicitly in the plist; never copy the whole shell environment into it.
-- A plist pointing at a worktree or a checkout breaks the day it moves. Point it at a
-  release.
-- `http.server.HTTPServer` asks the resolver for its FQDN between `bind()` and
-  `listen()`. With a slow resolver (a macOS CI runner, a Mac offline) the port is bound
-  but silent: connects time out instead of being refused. Use `fs.LoopbackHTTPServer`.
-- `logging.basicConfig` called twice: the second call is a no-op, so a server's own
-  log file stays empty. Configure logging once, in the entry point.
+- A plist pointing at a worktree or checkout breaks when it moves: point it at a release.
+- `http.server.HTTPServer` resolves its FQDN between `bind()` and `listen()`: with a slow
+  resolver (a macOS CI runner, a Mac offline) the port is bound but silent. Use `fs.LoopbackHTTPServer`.
+- `logging.basicConfig` called twice: the second is a no-op, the server's log file
+  stays empty. Configure logging once, in the entry point.
 - Hand-made `.plist.bak` files in `~/Library/LaunchAgents` are never cleaned up; keep
   backups elsewhere.
 

package/plugins/fabric-agent-adapter/skills/building-fabric-services/scripts/kit.json

@@ -1,6 +1,6 @@
 {
  "name": "fabric-service-kit",
- "version": "0.58.0",
+ "version": "0.59.0",
  "about": "The service kit's modules in dependency order: a module imports only modules listed before it. Written by fabric_kit.py build; edit the order and layers by hand, never the digests.",
  "python": [
   {
@@ -4408,6 +4408,96 @@
    "fabric-openrouter.mjs": "6041f3ab30f516658e1dbab4897a651cc8509b2136cfa8e769802c6b40ec2f35",
    "fabric-package.schema.json": "2ba799f576fad0f608029223c4ccccd122152f1c5dbfa8ce8b31cd63ac92ad44",
    "share-registration.schema.json": "34b3997eeaf936ebc861342a23045634a7c18c19f01d7ed4198310d81989f5b0"
+  },
+  "0.59.0": {
+   "fabric_jsvalue.py": "12888a2c934a885d35999ac9782eaedc8d04946d9775213344a235a8814d3d28",
+   "fabric_time.py": "588f383da4ac6a243ea95b6ffc3a0aa99ca94245732dc4937734f190b7af4ae9",
+   "fabric_identifiers.py": "0fd814d521ac3aa39907458265870753046a73f48af3d8581ab864b93b211607",
+   "fabric_secrets.py": "1d0191f0ec108fdc68345056b8c574b1f691509d1c353e41d98bfd58a59e8d3c",
+   "fabric_crypto.py": "9c34aee20dbe4d6742e4fdbaab68ceb934bbe7dbd3a904c0010824ace16cdeaa",
+   "fabric_base.py": "f62bcc2ed9912660fa875d27a09f60867260cc4925f79873501fd9620be59611",
+   "fabric_platform.py": "a9350dff55ef0fb3a23cdb4d0320a15868b15a8deb10d2eb74d72c58740c284b",
+   "fabric_paths.py": "8a1ee742f80f436e9f28c61b4f049a9545de2a9e0d66bfc61faa6ee5d1ba3734",
+   "fabric_estate_rules.py": "8b36a7f4108d9c2b1fb38c8bff344778c807bed631a99b4a563ecb0a49c10b1c",
+   "fabric_estate.py": "b3cd56dcb86e04d252980322ac8054da1aaef24ac64690f7aa80e7c765ee6f60",
+   "fabric_mandate.py": "050c43d0166a7dfba82e29c4e978f05c364cf6da06d0a781bd023a566777c17b",
+   "fabric_delegation.py": "716f0ff7ac01095f54b24970beac1962128e8ff33026b243fc0467876142ab03",
+   "fabric_share.py": "da36a466426fc29dd7dd40013167f3959a18375f8fedd228bf64f298cec1040c",
+   "fabric_ceremonies.py": "a59e83cf4adb2669a9b98008e3d3a0cba991a35cbff97bc604fc82fe81cfd49f",
+   "fabric_package_schema.py": "e623f0408d38e3343ed66222fb812907c6c52e1a286eb1c1176ab2e64640c9ad",
+   "fabric_package.py": "ff533f1b3f92b4ea0f532fcec50b68c610d47549930eef8ad5247692a64dfb3c",
+   "fabric_protocols.py": "42529a7df4d753544d2e37a18ec81266d6e1e80477cb8558a3ab521416d45791",
+   "fabric_actions.py": "ae21d1199614c4f74d1dcd1e0a87107a9d52434cd9e2d64aa24a7b1e196fb723",
+   "fabric_connections.py": "7de55cb7d808f756d650effabfaa12027d40a5bd5d2f6d448c32969d47529ecb",
+   "fabric_a2a.py": "8b01502131215bb4de1c01866187c56e99b791543923ed8577535573db33b919",
+   "fabric_page_links.py": "1b57ea573c550e2f90d1ec3edcc655917ceaa0db9dd1635fccf422ec3024d25e",
+   "fabric_lock.py": "ba2399d2137c7a7791b7133b9db9cca36693f4eb7e30955b25a75ade814e95ba",
+   "fabric_usage.py": "5cc2e03ccc5b06e81987ed7bc3eead7a7e6cbf1a7cb8e05c6c64315eed9d91b6",
+   "fabric_backups.py": "1f3f0d7ecf361b29e9101e07f1c53e5dc304d598bf26fd59ec89f16b9fed2420",
+   "fabric_descriptor.py": "a6d7a4a38186f7ef527d16218bbf96e39e255f9547be668adcfbec063dabb7ed",
+   "fabric_context.py": "6ae311ddc7217a4aff915e7ce2646486931acd128462b7bebe4a52bbb5fbb6c7",
+   "fabric_auth.py": "71115d18c67b7b806cb57b64b77e01ad97fc0e63e6f49ee850f778123617d905",
+   "fabric_events.py": "cd94b186e2a8f8cb4ad2b6bd44d83ec5021933075e28c5d655f387f16dff42b8",
+   "fabric_logs.py": "86dc55bfafa2a57264722e2403510a249b95de0e4a722b2e4bc3948e3bd93da9",
+   "fabric_supervisors.py": "3c5b2e8c310738720b1c1b779be4710e90251013d9be4c68f9952edc0bf55d5f",
+   "fabric_service.py": "a2e813469a47d4d3eea996628635c8903007498bdb6a1ae032a7a5ce6f49fe2f",
+   "fabric_profiles.py": "26e21ec29c016000f8ca8053b7b489184854a73be1b7fdc0a18d12990203db9b",
+   "fabric_interop_rules.py": "82c079a4d9421ea2cd10c1dfa8e1c447b80d5e0dcc8d52d52415bf028e34c91e",
+   "fabric_interop.py": "8f7e43bf01fa5e969d7d819f4b0188b9acfd846f6f85a37ea139e550d61e4e6c",
+   "fabric_hub.py": "b9ac852e601b1d54cf61351677a628afc69faeed7d1fc74ebe541c1cf38e0c2a",
+   "fabric_board_shapes.py": "0a0e8d3d40e33dfd8c457aedb85330b2ff25f8c49a33eb6cbd5a5cc8a5007f7e",
+   "fabric_board_link.py": "e8d2310e5f53c75e4bf642c3d980b2faba692731eaf56ec245cea05446e38bef",
+   "fabric_board_slots.py": "a3c705cded822103703a6c2d734bcd505fcd1d6c0293150c77dfa266fd416d53",
+   "fabric_board_session.py": "9032c04fbafb63fd93809b494518aaa039215abef973ad181d960350beb56a9f",
+   "fabric_board_fixture.py": "69761ce205ec640762ec9b591c6903e5a87f844e8d423b041681924027e39d1e",
+   "fabric_board.py": "34c1200860040aa61cdd35f911f70d34d64b4a5cd91f892328d1169e4a89d8cd",
+   "fabric_http.py": "80e22ae0bba91de13a94d64b595108b39c58f16f7b4137f3a48bdd9503f424fe",
+   "fabric_openrouter.py": "d06a40f83f2fb8bd441ab3485ae882f1fbdd9cd7a9c1ec175eb47cb8ae2cce81",
+   "fabric-jsvalue.mjs": "dfbdb8c41584972c9389750a41719374a1cfc5652ed438dd1623025190b0106e",
+   "fabric-time.mjs": "3ff932069038a720df1c68c6492976906737b2e67e5c12d9c81c418597f661de",
+   "fabric-identifiers.mjs": "a18c2a501a4aa170bfd3d99e571ad6b7662649b4d3b9d2a540c002ea42811bbf",
+   "fabric-secrets.mjs": "6ad8ab18ac899ecc2384e8ec6a3fb689b92be3b9a5ce3a59b92a37d52da5d766",
+   "fabric-crypto.mjs": "038e03689701e3c9721a1e7f8e0a4d02a52d6a5d1661b0dc84035edc3ebbfcf6",
+   "fabric-base.mjs": "7804b2df7715dbbf9702a9b61b6b8cef2110f9a52b04cabd8fb0a66458d87512",
+   "fabric-platform.mjs": "a8119d95ebba4d589a9e401f5d6fc8dda62d59d44e4c1ff811d97fac3771ac0c",
+   "fabric-paths.mjs": "aa630d611e748a899e7043480f4a4e46b444f2e15ff945f30c2fbef21c1ceea5",
+   "fabric-estate-rules.mjs": "7476be71174aa5b1026134f2b335abf647feaa55584e2f9de8618e3054aa8e1e",
+   "fabric-estate.mjs": "e8a2e62d2313121e6cb502f6e6abad94d1d546a44b4d9b3ce2be29e7808e8cf3",
+   "fabric-mandate.mjs": "deaab2bfb929d1bd35ae1bad71e7b9ad9902cc23b8eb51819ed592fd80eddf95",
+   "fabric-delegation.mjs": "04eaf6cd1786d4309a253a27dbdb05e27b408cb511aa41b1633a96634b775e65",
+   "fabric-share.mjs": "bfb26581c21ad984c2a337da02429f9f3a165cc582f8ba48de4d3dfb7d163a59",
+   "fabric-ceremonies.mjs": "117d4374c9e95c930a38de7adbd4323774798f4fe6ec6f24afcd6f2c7298ca44",
+   "fabric-package-schema.mjs": "cd28092375db0fc21ffab1f0bb7794f7f8979ee08c64d3b9faf4b3845357caa6",
+   "fabric-package.mjs": "13913ea6d12056c3a31b8222b6c4aab8395941fe519913692e1a06d8672e1c88",
+   "fabric-protocols.mjs": "5fd8765fdd3e507cc85c108492682bf5cbb4ae08873245c50374fb01d33c75e4",
+   "fabric-actions.mjs": "06e42f5e24c96311d5417d0d1effa93479ef7128a7ab139903b2bcf59253f6be",
+   "fabric-connections.mjs": "303432e547ce563e90ca9ffcd827f5612f51d3582929834e1add0fdaf6485dcc",
+   "fabric-a2a.mjs": "51b72fe1d80649d659fcad3a8f96370db3476c4a7b30cbabd8522c138be69346",
+   "fabric-page-links.mjs": "a8834926e9d4bbf7c4857f551451d2ebf6ac8873bbccaaf89c5e30cf45b17ee6",
+   "fabric-lock.mjs": "ac219ab0a326d5c43c7c4c255e0c3843d4794de795a60e3af661e7d5350ea052",
+   "fabric-usage.mjs": "1c4d18004639409624ac3516a02f2b60bbf55abdb612e9a96c37e83666eb87a7",
+   "fabric-backups.mjs": "cfd8c9085e3d597a783099c2bd2ffe2f3faa0daaadab46dedd30523894cfeb06",
+   "fabric-descriptor.mjs": "243bbce42989f67c4c5ec6b7659e201b3f9a1c08c71d429d88ec934d870f5104",
+   "fabric-context.mjs": "1112d695e872f9825cbc94f08484974bff3880087bc29b8be59f885f03e8f7be",
+   "fabric-auth.mjs": "782c2aa732f8320f604194660117640a7ea145e12b8155c04e88cef7c516a5b3",
+   "fabric-events.mjs": "c463d6ffcae24229a5c608d8fcea4268d2ccc5024b19fa10e5a452284068fa71",
+   "fabric-logs.mjs": "58467e5719c16e099d05bbedec47a95712506ab03c33f3cd4be1252e8498a946",
+   "fabric-supervisors.mjs": "d45c38de0cb3ed85e083496c2d3c51dab004454accdd87f4762a512a6d442573",
+   "fabric-service.mjs": "6aa673657427211b491a9b63f94b9847a7e6aa3ee1b7353e1af11f46469803a3",
+   "fabric-profiles.mjs": "314376cf2deb87f235fb18b11d3b532e211f585b9af0a9302b5f4cc39971b532",
+   "fabric-interop-rules.mjs": "e4f8b133138e27353a7976c0360bd1653c90daed43b3f843f85a19f14f5e9221",
+   "fabric-interop.mjs": "ee7e6d32be1f42e6d21a943b8886652352408c49c6404d9749b8a02dc3901e92",
+   "fabric-hub.mjs": "c005115a864cfd67daa4862097bb14acfe5a60bf653897e5bf8a570dd80f1070",
+   "fabric-board-shapes.mjs": "c1db7b7bd0d58d82bb6d8dfbc3cd1547a256a333052d367e82ff1b3edf2804d7",
+   "fabric-board-link.mjs": "b1ac329b65b679193b94b81fe735922e14427ed540ba910b1a815ce3447e3220",
+   "fabric-board-slots.mjs": "43eb7ceb6c62989a4eb4b2089d1808e2c3cf8f873fcf9216fcb4c285e5b39eb4",
+   "fabric-board-session.mjs": "04aa920b24a379157c55ebe3de516eb8b46bd0b0db50e4b883528d4ede7ed978",
+   "fabric-board-fixture.mjs": "83c4b7e33ee47b68385faf2569d38d5c8a0c5cb0f8656090f41e1b0eed2f436e",
+   "fabric-board.mjs": "0d75c3e27a0b791bdbc35b2e93b3299e5831d3ab3003ce441e6268397e32b448",
+   "fabric-http.mjs": "9f899829073470b9c2b449605a9371b773848eec4e3a0122ed4ccde5eddcdb4b",
+   "fabric-openrouter.mjs": "6041f3ab30f516658e1dbab4897a651cc8509b2136cfa8e769802c6b40ec2f35",
+   "fabric-package.schema.json": "2ba799f576fad0f608029223c4ccccd122152f1c5dbfa8ce8b31cd63ac92ad44",
+   "share-registration.schema.json": "34b3997eeaf936ebc861342a23045634a7c18c19f01d7ed4198310d81989f5b0"
   }
  },
  "data": {

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

@@ -5,7 +5,7 @@ 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.58.0"
+  version: "0.59.0"
   contract-version: "0.1.0"
   contract-commit: "3830a3353923e20f826d466610e1c479f120bec0"
 ---
@@ -57,6 +57,9 @@ No file is created until every row has an answer. An answer of "later" fails the
 | **Which profile?** | `mcp` when Fabric owns planning and retries and the capability has a schema; `a2a` when the provider owns its task lifecycle end to end; `local-runner` when it is a terminal agent Fabric drives. When unsure, the sibling skill's profile-selection reference is the decision record |
 | **What effects?** | declare anything money-, deletion-, or publication-adjacent now; the host's floor and grants are designed against these declarations, and one discovered late invalidates the admission |
 | **Where does it run, for whom?** | this machine, the person's cloud or an organization's, and in which contexts (`personal`, `org:<id>`): one instance per context, its secrets, spend and journal never crossing into another. Record which capabilities need the person's machine and what they answer when it is off (references/where-agents-run.md) |
+| **Does it run around the clock?** | the uptime category, decided now: **A** when a capability must answer while the owner's machine is off or asleep (a schedule, a chat, callers outside the machine): the agent gets a cloud host from its first release, Heroku unless a reason names another (the person's or an organization's cloud, or PassionCode's for a paid agent), built as an online service (building-fabric-services, the remote placement) and started from the cloud Fabric-server template once that template's repository exists; **B** when nothing needs it then: a local service only, no cloud, reading an A agent's data through that agent's MCP or API. The README names the category (references/where-agents-run.md) |
+| **Whose data does it keep?** | the kind of its data, named in the README: **U** when it keeps data of people outside the owner's team (messages, support requests, reviews, customers' answers), which never enters the source, a copy of it or its tests: the source holds the schema and synthetic fixtures, and a copy starts with an empty store of its own; **O** when it keeps none (a tool or service for other agents, the owner's reports, runs and media). In doubt, U. Either way the data lives in `<agent>-data` (a kit service: the kit's folders; on a cloud host: a durable store), apart from the source, from the first commit (references/source-and-instance.md) |
+| **Who holds the copyright?** | the holder the agent's `LICENSE` names: a new private agent (built for its owner or for a client) gets a `LICENSE` naming that holder in its first commit, all rights reserved unless the owner gives other terms; a public product keeps its own licence (a PassionCode.ai repository: the organization's, step 2) |
 | **Which models?** | per lane (planning, replies, volume work, media): a primary, a fallback of another vendor, an open-vendor model where it reads what users send, the input kinds each reads, declared as classes in the profile (references/models-and-providers.md) |
 | **Who pays?** | one key per agent and context with its own ceiling, from the estate's key manager, read from the environment; checked before every call; a personal key never pays for an organization |
 | **How does it learn?** | decisions recorded with reasons, one trace per turn, every failure a planted fixture first, history replayed, learnings proposed and never self-approved (references/orchestration-and-learning.md) |
@@ -111,8 +114,11 @@ are its seed because a source project's recorded failures count as production.
 repository standard (`knowledge/repository-standard.md`) from its first commit: the licence files,
 the README quick start verified with a real client, `AGENTS.md` and `CLAUDE.md`, as
 [the operator channel and the repository standard](references/operator-channel-and-repository.md)
-lists them. An agent someone builds for themselves is not a PassionCode.ai repository: its licence
-is its owner's choice and none of those files is required of it.
+lists them. An agent someone builds for themselves, or a private agent built for a client, is not a PassionCode.ai repository: its licence
+is its owner's choice and none of those files is required of it, but its first commit carries a `LICENSE` naming
+the copyright holder the grill recorded (all rights reserved unless the owner gives other terms); it covers the
+holder's own files, and the kit files the adapter copies in keep their own licence (AGPL-3.0-only OR
+LicenseRef-PassionCode-Commercial).
 
 **Every credential the agent uses is read by name, never held as a value**, from its first commit:
 the README's Configure section lists key NAMES. With Project Observatory installed, the agent finds
@@ -127,7 +133,9 @@ never their values.
 **The source stays apart from the instance**, from the first commit: instance values (the
 repository address of the owner's account, folders, the owner, accounts, hosts) live in a configuration outside the repository, read through a
 named variable with a neutral default and a committed `*.example`; records, logs and state documents live in the
-instance folder; fixtures use neutral ids. Load [the source and the instance](references/source-and-instance.md). The
+instance folder; fixtures use neutral ids. Its data has a home of its own from the same commit, the one the grill recorded: `<agent>-data` (a folder beside the
+checkout, or a private repository of that name; a kit service: the kit's folders; on a cloud host: a durable store), and the README names the data kind (U or O) and the uptime
+category (A or B) from the grill. Load [the source and the instance](references/source-and-instance.md). The
 sibling's `scripts/fabric_source_check.py check <project-root>` finds instance data in the tree without repeating it;
 run it with the owner's list of their own strings, or record that none was given (the owner's own home name, when it is neutral, has one or two letters, or holds a space, `.`, `_`, `-` or `'`, is declared there with `home: <name>` first; a container's, a cloud image's or a CI runner's user that only the image uses, such as `node` or `vscode`, is never declared); the skeleton is done when it exits 0 and the owner has reviewed it (a floor, not a secret scanner; without the sibling or Python 3.9+, record the check as NOT_RUN, as in step 3). Handing the source over stays the owner's act.
 
@@ -172,7 +180,8 @@ reference). An agent that is not a service is announced with a provider entry
 If the agent keeps running on the operator's computer (it answers other agents, runs
 long jobs or shows a dashboard), build it as a service with the sibling skill
 `building-fabric-services`: its instance lock, launchd plist, descriptor, well-known
-document and events feed are part of this step, not a later retrofit. If that skill is
+document and events feed are part of this step, not a later retrofit. An uptime A agent is built with the same
+skill as an online service (its remote placement: the https origin, keys as the platform's secrets). If that skill is
 absent, apply the `fabric-service/0.1` rules from the pinned contract's
 `docs/specification/service.md` by hand and mark its probe `NOT_RUN`.
 
@@ -190,8 +199,11 @@ lets the output decide what counts as success.
 
 Run the sibling skill's `check` (structural, then exact when the contract checkout is
 available) and complete `fabric/FABRIC-CONFORMANCE.md` with dated receipts, exactly as
-its workflow steps 5–7 prescribe, and run its `fabric_source_check.py check` again (exit 0); this skill adds no
-second verification path on purpose. Then record one expectation the report must carry:
+its workflow steps 5–7 prescribe, and run its `fabric_source_check.py check` again (exit 0). Every release of the
+agent runs it too, in Git mode on the checkout and with `--every-file` on the clean copy a transfer would carry (what
+Git would commit, as building-fabric-services' `references/package.md` makes it), as the transfer audit (each exit 0, with the owner's list or
+its absence recorded) until the contract's export (CT-194) replaces it; this skill adds no second verification path
+on purpose. Then record one expectation the report must carry:
 
 > When a Fabric host admits this provider, it enters under a **canary binding** (a
 > checker on its output and a budget cap), regardless of who wrote it. Unsupervised

package/plugins/fabric-agent-adapter/skills/creating-fabric-agents/references/operator-channel-and-repository.md

@@ -63,4 +63,7 @@ the project).
 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, except that an agent built new carries a `LICENSE` naming the copyright holder (all rights reserved
+unless the owner gives other terms), as does a new private agent built for a client; files the adapter copies in (the service kit, the dashboard kit) keep their own
+licence, `AGPL-3.0-only OR LicenseRef-PassionCode-Commercial` ([COMMERCIAL-LICENSE.md](https://github.com/passioncode-ai/fabric-agent-adapter/blob/main/COMMERCIAL-LICENSE.md)).
+The verified MCP quick start is still how anyone learns to drive it.

package/plugins/fabric-agent-adapter/skills/creating-fabric-agents/references/source-and-instance.md

@@ -13,6 +13,7 @@ on it.
 ## Contents
 
 - [The layout](#the-layout)
+- [The data home and its kind](#the-data-home-and-its-kind)
 - [The check](#the-check)
 
 ## The layout
@@ -31,7 +32,7 @@ on it.
   (an organization's) is a sibling instance, `<id>.<instance>`, never a folder inside the personal one
   (`references/estate-record.md` of that skill).
 - **Ignore the instance in the source**: `.gitignore` names the real configuration (`config/*.json` with
-  `!config/*.example.json`), an instance folder that sits inside the checkout during development, and what running
+  `!config/*.example.json`), an instance folder an existing project still keeps inside the checkout, and what running
   the agent leaves (`__pycache__/`, `*.pyc`), which the check would otherwise report as binary in Git mode.
 - **State documents are instance data.** A handoff, a decision log or a backlog about this codebase is source
   documentation; a record of what this installation did (runs, conversations, the owner's notes, a journal) lives in
@@ -47,6 +48,27 @@ on it.
   keeps the scaffold's sentinel, and a person's name or account is never written there. The adapter moves both when the
   contract decides how an instance renames them (FAA-188 part 2).
 
+## The data home and its kind
+
+- **The data has a home of its own from the first commit: `<agent>-data`.** For an agent that is not a kit service it
+  is a folder beside the checkout, never inside it, and `<AGENT>_DATA_DIR` names it (its default is
+  `../<agent>-data`); a kit service keeps the kit's folders above. When the owner keeps the data in Git, it goes to a
+  separate private repository named `<agent>-data`, never to the source's repository. On a cloud host that does not
+  keep its disk across a restart (Heroku and the like, an uptime A agent's default), the data home is a durable store
+  the same variable names (a database, an object store, that private repository); the folder and the kit's folders
+  serve a machine whose disk persists. A copy of the agent starts with an empty home of its own and never connects
+  to the original's.
+- **The README names the kind of the data.** **U**: the agent keeps data of people outside the owner's team
+  (messages, support requests, reviews, customers' answers); it never enters the source, a copy or its tests, and the
+  source holds only the schema and synthetic fixtures (its real-trace corpus and replay samples live in the data
+  home). **O**: it keeps none (a tool or service for other agents, the
+  owner's reports, runs and media); its working data still goes to the data home. When in doubt, the kind is U.
+- **Every release runs the transfer audit.** `fabric_source_check.py check <project-root>` in Git mode, and
+  `check <clean-copy> --every-file` on a clean copy of what Git would commit (`git ls-files --cached --others
+  --exclude-standard`, as building-fabric-services' `references/package.md` makes it; never the checkout itself, whose ignored
+  configuration and dependency folders `--every-file` reads too), each exit 0, with the owner's list or its absence recorded, until the contract's export (CT-194)
+  replaces it.
+
 ## The check
 
 `fabric_source_check.py check` reads the files the source would carry (what Git would commit: tracked files and
@@ -124,7 +146,10 @@ python3 <plugin-dir>/skills/adapting-projects-to-fabric/scripts/fabric_source_ch
   repository is not read; `--every-file` and a folder outside Git read its files, its `.git` left out. An exception line (`!`) is refused, since what it would
   bring back would go unread. Name the files, or a folder that holds
   only synthetic vectors, never a whole source folder (a nested repository checked in its own tree is the one
-  exception), and say why on the line above. A file `pack` refuses by its name cannot ship in a package: a public
+  exception), and say why on the line above. The `LICENSE` is the other: its copyright line names the holder, which is
+  authorship and travels with the source, so when the holder is on the owner's list the licence file is named in the ignore
+  file by its own path (`LICENSE`, `LICENSE.md`) with that reason (`# the copyright holder is authorship and travels with the source`); no other file of the
+  owner's is. A file `pack` refuses by its name cannot ship in a package: a public
   certificate is renamed `*.crt`; a project `.npmrc` that holds no credential may be named in the ignore file, with
   that reason, for the source check (the line then hides whatever is added to it later, so keep it credential-free),
   and `pack` still refuses it, so a package is made from a copy without it (its

package/plugins/fabric-agent-adapter/skills/creating-fabric-agents/references/where-agents-run.md

@@ -16,6 +16,7 @@ The normative rules are the Fabric Agent Contract's, at the commit this plugin p
 - [Connecting a machine or a cloud to the estate](#connecting-a-machine-or-a-cloud-to-the-estate)
 - [Sharing an agent into an organization](#sharing-an-agent-into-an-organization)
 - [Running while the laptop is closed](#running-while-the-laptop-is-closed)
+- [Uptime: A or B](#uptime-a-or-b)
 - [Selling an agent](#selling-an-agent)
 - [The checklist](#the-checklist)
 
@@ -85,13 +86,33 @@ checked, and removes the instance from the next revision.
 ## Running while the laptop is closed
 
 A cloud agent keeps working with the laptop closed only if everything it needs is in the cloud: its worker, its
-secrets, its data, and a hub that can admit calls. The local Fabric hub is not a cloud hub. Design for it:
+secrets, its data, and, for the calls Fabric admits, a hub that can admit them. The local Fabric hub is not a cloud hub. Design for it:
 
 - Declare what each capability needs and where it is; a capability that needs the person's machine reports
   `pending` or `unavailable` instead of pretending, and queues within a deadline or declines.
 - Never charge for work it cannot deliver on the promised terms.
 - A test that passed on fixtures says nothing about uptime; measure the installed agent in its cloud.
 
+## Uptime: A or B
+
+Every new agent is given an uptime category on its first day, and the README names it:
+
+- **A, around the clock.** A capability must answer while the owner's machine is off or asleep: a schedule, a chat,
+  callers outside the machine. A cloud host is required from the first release; Heroku is the default, another host
+  only when a reason names it: an instance in the person's PassionCode cloud or an organization's cloud runs there
+  (the places above), and a paid agent stays in PassionCode's cloud (selling an agent, below). On a host with no
+  Fabric hub it answers what reaches its own origin (its schedule, its chat, its API); a call Fabric admits needs a
+  cloud hub, as running while the laptop is closed says. The agent is an online service (building-fabric-services, the remote placement), often
+  alongside its local instance, and starts from the cloud Fabric-server template once that template's repository
+  exists. Its data lives where the cloud reaches it, in a durable store (a database, an object store, the private
+  `<agent>-data` repository), never the host's own folder, which a platform such as Heroku does not keep across a
+  restart.
+- **B, local only.** Nothing needs it while the machine sleeps: a local service and no cloud. It reads an A agent's
+  data through that agent's MCP or API, never from its store.
+
+A B agent that gains a capability that must answer around the clock becomes A for that capability; record the change
+and move only that capability to the cloud.
+
 ## Selling an agent
 
 - **A paid agent** runs in PassionCode's cloud inside its developer's organization (`org:<developer>`); each customer
@@ -108,6 +129,7 @@ secrets, its data, and a hub that can admit calls. The local Fabric hub is not a
 - Where does each instance run, and in which context? Write it in the knowledge pack.
 - Does any state, secret, log line or cache key cross contexts? It must not.
 - Which capabilities need the person's machine, and what do they answer when it is off?
+- Which uptime category is it, A (a cloud host from the first release) or B (local only)? The README names it.
 - Who pays for each call (which grant, which key)? The person's personal key never pays for an organization.
 - If it joins machines or applies the estate record: tokens from stdin or a 0600 file only, revisions verified with
   their parent.

package/plugins/fabric-agent-adapter/skills/working-with-fabric/SKILL.md

@@ -18,7 +18,7 @@ compatibility: >-
   this plugin; Codex/Kimi use command hooks; Hermes/OpenCode/OpenClaw/Pi use native context plugins after opt-in.
 metadata:
   author: PassionCode.ai
-  version: "0.58.0"
+  version: "0.59.0"
 ---
 
 # Working with Fabric

package/plugins/fabric-agent-adapter/skills/working-with-fabric/scripts/fabric_session_env.py

@@ -58,7 +58,7 @@ SESSION_ID = re.compile(r"[A-Za-z0-9._:-]{1,128}")
 LOOPBACK_ORIGIN = re.compile(r"http://127\.0\.0\.1:(\d{1,5})")
 
 
-VERSION = "0.58.0"
+VERSION = "0.59.0"
 
 
 HOSTS = {"claude": "Claude Code", "codex": "Codex", "kimi": "Kimi Code",