@passioncode-ai/passioncode 0.1.4 → 0.1.7

package/CHANGELOG.md

@@ -1,5 +1,62 @@
 # Changelog
 
+## 0.1.7 - 2026-09-29
+
+- Observatory Log 0.12.3 (Observatory v0.8.2) in the set: source-available license and PassionCode.ai metadata; no behaviour change.
+
+## 0.1.6 - 2026-09-29
+
+### Fixed
+
+- **A version published from GitHub is trusted.** npm records a trusted-publishing (OIDC)
+  release as `GitHub Actions <npm-oidc-no-reply@github.com>`; the hook read that as an
+  unreadable account and would have refused every release the workflow publishes. It is now
+  recognised by its email as `github-actions-oidc`, which `trust.json` lists; a look-alike
+  name with another email is not. Maintainers are still checked one by one.
+- `vendor.mjs` reads `PASSIONCODE_VENDOR_CLONE` and `PASSIONCODE_GIT_BASE` from the
+  environment it is given, so a CI step's clone mode no longer leaks into the tests.
+- The release job waits up to 10 minutes for npm to serve a new version (5 was too short).
+
+0.1.5 was tagged but its release job failed on the leak above; it was never published.
+
+## 0.1.5 - 2026-09-29
+
+### Added
+
+- `working-in-passioncode`, a skill in the self plugin: the organisation's working rules —
+  the org map, landing, nightly CI and why a blocked run is not green, handoffs,
+  decisions, ids and leases, secrets, licensing, the privacy gate, releases and pins —
+  reach every contributor's agent instead of living only in org-index. It points to
+  org-index as the source of truth; detail is in its `references/releasing.md` and
+  `references/publishing.md`. Trigger and scenario evals are in
+  `test/evals/working-in-passioncode/`; `test/skill.test.js` holds every self-plugin skill
+  to the Agent Skills standard (strict front matter, description budget, references
+  linked, no home paths). The hub links it like any member's skill (`status` showed
+  `passioncode hub: 0/0` because the self plugin had no skill).
+- Fabric Agent Adapter 0.4.3: source-available license, one contract pin (`a5a2709`),
+  neutral examples, and hand-offs to the neighbouring agent-stack and make-skill skills.
+
+### Changed
+
+- **License.** The launcher is source-available under
+  `PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0`, with a
+  commercial license on request (contact@passioncode.ai). Versions up to and including
+  v0.1.4 were released under MIT and remain available under it. Contributions come in
+  under `CLA.md` (new `CONTRIBUTING.md` and PR template). The payload's marketplace
+  lists each member under its own manifest's license instead of a hard-coded `MIT`.
+- `family.json` names no machine paths. Members are cloned from their repositories at
+  their tags; a maintainer's local clones are an environment override:
+  `PASSIONCODE_CHECKOUT_ROOT=<dir>` reads `<dir>/<repository name>`, and
+  `PASSIONCODE_CHECKOUT_<MEMBER>=<path>` names one clone kept under another name. A
+  `checkout` key in `family.json` is refused.
+
+### Fixed
+
+- `passioncode status` described the payload beside the CLI — from a checkout, whatever
+  was last vendored there — instead of what is installed. It now reads the release
+  `~/.passioncode/current` points at, reports the payload version separately as
+  `package`, and says which it described (`source`).
+
 ## 0.1.4 - 2026-09-29
 
 ### Security

package/LICENSE

@@ -1,22 +1,155 @@
-MIT License
+Copyright (c) 2026 Siarhei Sheleh
 
-Copyright (c) 2026 PassionCode.ai
+This software is source-available, not open source. You may use it under
+either of the two licenses below, at your option:
 
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
+  1. PolyForm Noncommercial License 1.0.0
+     SPDX: PolyForm-Noncommercial-1.0.0
+  2. PolyForm Internal Use License 1.0.0
+     SPDX: LicenseRef-PolyForm-Internal-Use-1.0.0
 
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
+In short: individuals and noncommercial organisations may use, change and
+share it for noncommercial purposes; any company may use it, and change it,
+for its own internal operations. Distributing it commercially, or building
+this software or its code into a product or service you provide to others,
+needs a separate commercial license: contact@passioncode.ai.
+This summary is not part of either license; the texts below govern.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+Versions up to and including v0.1.4 of this repository were released under the MIT
+License; those releases remain available under MIT.
 
+Required Notice: Copyright (c) 2026 Siarhei Sheleh (https://passioncode.ai)
+
+================================================================================
+
+# PolyForm Noncommercial License 1.0.0
+
+<https://polyformproject.org/licenses/noncommercial/1.0.0>
+
+## Acceptance
+
+In order to get any license under these terms, you must agree to them as both strict obligations and conditions to all your licenses.
+
+## Copyright License
+
+The licensor grants you a copyright license for the software to do everything you might do with the software that would otherwise infringe the licensor's copyright in it for any permitted purpose.  However, you may only distribute the software according to [Distribution License](#distribution-license) and make changes or new works based on the software according to [Changes and New Works License](#changes-and-new-works-license).
+
+## Distribution License
+
+The licensor grants you an additional copyright license to distribute copies of the software.  Your license to distribute covers distributing the software with changes and new works permitted by [Changes and New Works License](#changes-and-new-works-license).
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you also gets a copy of these terms or the URL for them above, as well as copies of any plain-text lines beginning with `Required Notice:` that the licensor provided with the software.  For example:
+
+> Required Notice: Copyright Yoyodyne, Inc. (http://example.com)
+
+## Changes and New Works License
+
+The licensor grants you an additional copyright license to make changes and new works based on the software for any permitted purpose.
+
+## Patent License
+
+The licensor grants you a patent license for the software that covers patent claims the licensor can license, or becomes able to license, that you would infringe by using the software.
+
+## Noncommercial Purposes
+
+Any noncommercial purpose is a permitted purpose.
+
+## Personal Uses
+
+Personal use for research, experiment, and testing for the benefit of public knowledge, personal study, private entertainment, hobby projects, amateur pursuits, or religious observance, without any anticipated commercial application, is use for a permitted purpose.
+
+## Noncommercial Organizations
+
+Use by any charitable organization, educational institution, public research organization, public safety or health organization, environmental protection organization, or government institution is use for a permitted purpose regardless of the source of funding or obligations resulting from the funding.
+
+## Fair Use
+
+You may have "fair use" rights for the software under the law. These terms do not limit them.
+
+## No Other Rights
+
+These terms do not allow you to sublicense or transfer any of your licenses to anyone else, or prevent the licensor from granting licenses to anyone else.  These terms do not imply any other licenses.
+
+## Patent Defense
+
+If you make any written claim that the software infringes or contributes to infringement of any patent, your patent license for the software granted under these terms ends immediately. If your company makes such a claim, your patent license ends immediately for work on behalf of your company.
+
+## Violations
+
+The first time you are notified in writing that you have violated any of these terms, or done anything with the software not covered by your licenses, your licenses can nonetheless continue if you come into full compliance with these terms, and take practical steps to correct past violations, within 32 days of receiving notice.  Otherwise, all your licenses end immediately.
+
+## No Liability
+
+***As far as the law allows, the software comes as is, without any warranty or condition, and the licensor will not be liable to you for any damages arising out of these terms or the use or nature of the software, under any kind of legal claim.***
+
+## Definitions
+
+The **licensor** is the individual or entity offering these terms, and the **software** is the software the licensor makes available under these terms.
+
+**You** refers to the individual or entity agreeing to these terms.
+
+**Your company** is any legal entity, sole proprietorship, or other kind of organization that you work for, plus all organizations that have control over, are under the control of, or are under common control with that organization.  **Control** means ownership of substantially all the assets of an entity, or the power to direct its management and policies by vote, contract, or otherwise.  Control can be direct or indirect.
+
+**Your licenses** are all the licenses granted to you for the software under these terms.
+
+**Use** means anything you do with the software requiring one of your licenses.
+
+================================================================================
+
+# PolyForm Internal Use License 1.0.0
+
+<https://polyformproject.org/licenses/internal-use/1.0.0>
+
+## Acceptance
+
+In order to get any license under these terms, you must agree to them as both strict obligations and conditions to all your licenses.
+
+## Copyright License
+
+The licensor grants you a copyright license for the software to do everything you might do with the software that would otherwise infringe the licensor's copyright in it for any permitted purpose.  However, you may only make changes or new works based on the software according to [Changes and New Works License](#changes-and-new-works-license), and you may not distribute the software.
+
+## Changes and New Works License
+
+The licensor grants you an additional copyright license to make changes and new works based on the software for any permitted purpose.
+
+## Patent License
+
+The licensor grants you a patent license for the software that covers patent claims the licensor can license, or becomes able to license, that you would infringe by using the software.
+
+## Fair Use
+
+You may have "fair use" rights for the software under the law. These terms do not limit them.
+
+## Internal Business Use
+
+Use of the software for the internal business operations of you and your company is use for a permitted purpose.
+
+## No Other Rights
+
+These terms do not allow you to sublicense or transfer any of your licenses to anyone else, or prevent the licensor from granting licenses to anyone else.  These terms do not imply any other licenses.
+
+## Patent Defense
+
+If you make any written claim that the software infringes or contributes to infringement of any patent, your patent license for the software granted under these terms ends immediately. If your company makes such a claim, your patent license ends immediately for work on behalf of your company.
+
+## Violations
+
+The first time you are notified in writing that you have violated any of these terms, or done anything with the software not covered by your licenses, your licenses can nonetheless continue if you come into full compliance with these terms, and take practical steps to correct past violations, within 32 days of receiving notice.  Otherwise, all your licenses end immediately.
+
+## No Liability
+
+***As far as the law allows, the software comes as is, without any warranty or condition, and the licensor will not be liable to you for any damages arising out of these terms or the use or nature of the software, under any kind of legal claim.***
+
+## Definitions
+
+The **licensor** is the individual or entity offering these terms, and the **software** is the software the licensor makes available under these terms.
+
+**You** refers to the individual or entity agreeing to these terms.
+
+**Your company** is any legal entity, sole proprietorship, or other kind of organization that you work for, plus all organizations that have control over, are under the control of, or are under common control with that organization.  **Control** means ownership of substantially all the assets of an entity, or the power to direct its management and policies by vote, contract, or otherwise.  Control can be direct or indirect.
+
+**Your licenses** are all the licenses granted to you for the software under these terms.
+
+**Use** means anything you do with the software requiring one of your licenses.

package/README.md

@@ -13,7 +13,7 @@ npx @passioncode-ai/passioncode@latest update
 |---|---|
 | Fabric Agent Adapter | `creating-fabric-agents`, `adapting-projects-to-fabric`, `building-fabric-services` |
 | Observatory Log | `explaining-changes`, `handling-secrets`, `tracking-resources` (+ its session hooks) |
-| passioncode | the once-a-day update check |
+| passioncode | `working-in-passioncode` (the organisation's working rules, for every contributor's agent) and the once-a-day update check |
 
 Only PassionCode.ai products are members. Agents that people build for themselves stay
 out of it, even when they implement Fabric protocols.
@@ -44,7 +44,7 @@ installed ([SECURITY.md](SECURITY.md#the-self-update-and-who-it-trusts)).
 `npx passioncode config set update.auto off` makes it only say so.
 
 ```bash
-npx passioncode status      # installed version, per-member channels, shadows
+npx passioncode status      # the installed release: its members, their channels, shadows
 npx passioncode update --dry-run
 npx passioncode uninstall
 ```
@@ -66,4 +66,19 @@ npx passioncode uninstall
    (OIDC) or the `NPM_TOKEN` secret; a private member needs `MEMBERS_READ_TOKEN`.
    By hand, `npm publish` still works: `prepublishOnly` vendors from tags only (`--release`),
    refuses credential-shaped strings and runs the tests.
-5. `npx @passioncode-ai/passioncode@<version> update` on this machine; restart the agents.
+5. `npx @passioncode-ai/passioncode@<version> update` on each machine; restart the agents.
+
+Vendoring clones every member from its own repository at its tag. A maintainer with
+local clones can point the vendor at them instead — `PASSIONCODE_CHECKOUT_ROOT=<dir>`
+reads a member from `<dir>/<repository name>`, and `PASSIONCODE_CHECKOUT_<MEMBER>=<path>`
+(the member's name upper-cased, `-` as `_`) names one clone kept under another name.
+`PASSIONCODE_VENDOR_CLONE=1` ignores both. `family.json` names no machine paths.
+
+## 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.1.4 were released under the MIT
+License and remain available under it. Contributions are accepted under [CLA.md](CLA.md)
+([CONTRIBUTING.md](CONTRIBUTING.md)).

package/SECURITY.md

@@ -1,6 +1,7 @@
 # Security
 
-Report vulnerabilities privately to the maintainers of the `passioncode-ai` organization.
+Report vulnerabilities privately to contact@passioncode.ai. Do not open an issue that
+carries credentials or a working exploit.
 
 What `passioncode update` touches: `~/.passioncode/` (releases, state, quarantine,
 logs); Claude Code's plugin registry through the `claude plugin` CLI only;
@@ -25,6 +26,9 @@ The hook installs a newer version on its own only when all of these hold:
 - `update.auto` is on (the default);
 - the recorded maintainers are not empty, and every maintainer **and** the publishing
   account is listed in `trust.json` inside the plugin (`npmPublishers`);
+  a release published by this repository's `release.yml` through npm trusted publishing
+  appears as `github-actions-oidc` (npm's `npm-oidc-no-reply@github.com` identity, matched
+  by email, never by display name), and only a maintainer can register that workflow;
 - the version is a plain `x.y.z`.
 
 It then runs `npx --yes @passioncode-ai/passioncode@<that exact version> update --quiet`, detached, so

package/family.json

@@ -8,8 +8,7 @@
       "name": "fabric-agent-adapter",
       "displayName": "Fabric Agent Adapter",
       "repo": "passioncode-ai/fabric-agent-adapter",
-      "checkout": "~/DATA/fabric-agent-adapter",
-      "ref": "v0.4.2",
+      "ref": "v0.4.3",
       "kind": "plugin",
       "path": "plugins/fabric-agent-adapter",
       "legacyPluginIds": [
@@ -23,8 +22,7 @@
       "name": "observatory-log",
       "displayName": "Observatory Log",
       "repo": "passioncode-ai/project-observatory-dashboard",
-      "checkout": "~/DATA/project-observatory-open-source",
-      "ref": "v0.8.1",
+      "ref": "v0.8.2",
       "kind": "plugin",
       "path": "observatory/engine/skill/plugins/observatory-log",
       "legacyPluginIds": [
@@ -39,7 +37,7 @@
       "displayName": "PassionCode.ai",
       "kind": "self",
       "path": "plugin/passioncode",
-      "description": "Keeps the PassionCode.ai set current: a once-a-day check at session start and a background update."
+      "description": "The organisation's working rules for every contributor's agent (working-in-passioncode), and a once-a-day check that keeps the PassionCode.ai set current."
     }
   ]
 }

package/lib/launcher.js

@@ -311,11 +311,17 @@ function status({ home, claude = claudeRunner() } = {}) {
   const state = readJson(p.stateFile, {});
   let payload = null;
   try { payload = payloadManifest(); } catch (_) { /* reported as unknown */ }
+  // What is installed is the release `current` points at. The payload beside this CLI is
+  // only what an update would install — from a checkout it is whatever was last vendored
+  // there, so reading members from it described a set that is not on the machine.
+  let release = null;
+  try { release = payloadManifest(p.current); } catch (_) { /* nothing installed yet */ }
+  const described = release || payload;
   const installed = Object.keys(readJson(path.join(p.claudePlugins, 'installed_plugins.json'), { plugins: {} }).plugins || {});
   const known = readJson(path.join(p.claudePlugins, 'known_marketplaces.json'), {});
   let declared = {};
   try { declared = readSettings(p.claudeSettings).doc.extraKnownMarketplaces || {}; } catch (_) { /* reported by update */ }
-  const members = (payload ? payload.members : []).map((m) => ({
+  const members = (described ? described.members : []).map((m) => ({
     name: m.name, version: m.version,
     claude: installed.includes(`${m.name}@${MARKETPLACE}`) ? 'plugin' : (claude.available() ? 'missing' : 'no Claude Code'),
     legacy: (m.legacyPluginIds || []).filter((id) => installed.includes(id)),
@@ -323,7 +329,11 @@ function status({ home, claude = claudeRunner() } = {}) {
     hub: m.skills.map((s) => ({ skill: s, ok: linkTarget(path.join(p.hub, s)) === path.join(p.current, 'plugins', m.name, 'skills', s) })),
     shadows: m.skills.filter((s) => lstat(path.join(p.claudeSkills, s))),
   }));
-  return { installed: state.installed || null, latest: state.latest || null, checkedAt: state.checkedAt || null, package: payload ? payload.version : null, auto: (state.config || {}).auto !== false, members };
+  return {
+    installed: state.installed || (release ? release.version : null), latest: state.latest || null, checkedAt: state.checkedAt || null,
+    package: payload ? payload.version : null, source: release ? 'installed' : (payload ? 'package' : null),
+    auto: (state.config || {}).auto !== false, members,
+  };
 }
 
 function setConfig({ home, key, value }) {

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@passioncode-ai/passioncode",
-  "version": "0.1.4",
-  "description": "Every PassionCode.ai agent skill — Fabric Agent Adapter and Observatory Log — for Claude Code and every other agent on the machine, updated as one set.",
+  "version": "0.1.7",
+  "description": "Every PassionCode.ai agent skill — Fabric Agent Adapter, Observatory Log and the organisation's working rules — for Claude Code and every other agent on the machine, updated as one set.",
   "bin": {
     "passioncode": "bin/passioncode.js"
   },
@@ -21,8 +21,8 @@
   "scripts": {
     "vendor": "node scripts/vendor.mjs",
     "vendor:release": "node scripts/vendor.mjs --release",
-    "test": "node --test test/",
-    "prepublishOnly": "node scripts/vendor.mjs --release && node --test test/"
+    "test": "node --test 'test/*.test.js'",
+    "prepublishOnly": "node scripts/vendor.mjs --release && node --test 'test/*.test.js'"
   },
   "engines": {
     "node": ">=18"
@@ -32,7 +32,7 @@
     "url": "git+https://github.com/passioncode-ai/passioncode.git"
   },
   "homepage": "https://github.com/passioncode-ai/passioncode",
-  "license": "MIT",
+  "license": "PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0",
   "author": {
     "name": "PassionCode.ai",
     "url": "https://passioncode.ai/"

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

@@ -11,37 +11,37 @@
       "name": "fabric-agent-adapter",
       "displayName": "Fabric Agent Adapter",
       "source": "./plugins/fabric-agent-adapter",
-      "version": "0.4.2",
+      "version": "0.4.3",
       "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.",
       "author": {
-        "name": "passioncode-ai",
-        "url": "https://github.com/passioncode-ai"
+        "name": "PassionCode.ai",
+        "url": "https://passioncode.ai/"
       },
-      "license": "MIT"
+      "license": "PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0"
     },
     {
       "name": "observatory-log",
       "displayName": "Observatory Log",
       "source": "./plugins/observatory-log",
-      "version": "0.12.2",
+      "version": "0.12.3",
       "description": "Records what changed in a watched project at the end of every turn, and asks for the one thing a diff cannot contain: why.",
       "author": {
-        "name": "Sergey Sheleg",
-        "url": "https://sshlg.me/"
+        "name": "PassionCode.ai",
+        "url": "https://passioncode.ai/"
       },
-      "license": "MIT"
+      "license": "PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0"
     },
     {
       "name": "passioncode",
       "displayName": "PassionCode.ai",
       "source": "./plugins/passioncode",
-      "version": "0.1.4",
-      "description": "Keeps the PassionCode.ai set current: a once-a-day check at session start and a background update.",
+      "version": "0.1.7",
+      "description": "The organisation's working rules for every contributor's agent (working-in-passioncode), and a once-a-day check that keeps the PassionCode.ai set current.",
       "author": {
         "name": "PassionCode.ai",
         "url": "https://passioncode.ai/"
       },
-      "license": "MIT"
+      "license": "PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0"
     }
   ]
 }

package/payload/manifest.json

@@ -1,16 +1,16 @@
 {
   "family": "passioncode",
-  "version": "0.1.4",
+  "version": "0.1.7",
   "release": true,
   "members": [
     {
       "name": "fabric-agent-adapter",
       "displayName": "Fabric Agent Adapter",
       "repo": "passioncode-ai/fabric-agent-adapter",
-      "ref": "v0.4.2",
-      "commit": "e09551f20ed7f1f31179f04d78f04a7bafe46f40",
-      "version": "0.4.2",
-      "via": "clone of git@github.com:passioncode-ai/fabric-agent-adapter.git",
+      "ref": "v0.4.3",
+      "commit": "c1a57abd7889c3aed1b0e97b00d4e089cc53036e",
+      "version": "0.4.3",
+      "via": "clone of https://***@github.com/passioncode-ai/fabric-agent-adapter.git",
       "skills": [
         "adapting-projects-to-fabric",
         "building-fabric-services",
@@ -22,21 +22,22 @@
       "legacyMarketplaces": [
         "fabric-agent-adapter"
       ],
-      "contentHash": "sha256:3c231e211672694236563046e90087ec867c562bd82810541d43b9e395198a14",
+      "contentHash": "sha256:7074066a0046ac055a6545f44bf2729d316047710e39846ce666b254620aff34",
       "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.",
       "author": {
-        "name": "passioncode-ai",
-        "url": "https://github.com/passioncode-ai"
-      }
+        "name": "PassionCode.ai",
+        "url": "https://passioncode.ai/"
+      },
+      "license": "PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0"
     },
     {
       "name": "observatory-log",
       "displayName": "Observatory Log",
       "repo": "passioncode-ai/project-observatory-dashboard",
-      "ref": "v0.8.1",
-      "commit": "c6410a2706e6f2e3fc1e2b7b929bf8c5e116c71b",
-      "version": "0.12.2",
-      "via": "clone of git@github.com:passioncode-ai/project-observatory-dashboard.git",
+      "ref": "v0.8.2",
+      "commit": "4f3591de65cd9a28de18212d53da966405f46f22",
+      "version": "0.12.3",
+      "via": "clone of https://***@github.com/passioncode-ai/project-observatory-dashboard.git",
       "skills": [
         "explaining-changes",
         "handling-secrets",
@@ -48,30 +49,34 @@
       "legacyMarketplaces": [
         "observatory-log"
       ],
-      "contentHash": "sha256:6884e0c97f0c5da4030c5104905d8d42fed113981f8b9d4254f96000597c2159",
+      "contentHash": "sha256:0ddb7efdfd9977c55d65e58a3cd8dc9cb9da3b8eb9ab02c83e3a159ea233017b",
       "description": "Records what changed in a watched project at the end of every turn, and asks for the one thing a diff cannot contain: why.",
       "author": {
-        "name": "Sergey Sheleg",
-        "url": "https://sshlg.me/"
-      }
+        "name": "PassionCode.ai",
+        "url": "https://passioncode.ai/"
+      },
+      "license": "PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0"
     },
     {
       "name": "passioncode",
       "displayName": "PassionCode.ai",
       "repo": "passioncode-ai/passioncode",
-      "ref": "v0.1.4",
+      "ref": "v0.1.7",
       "commit": null,
-      "version": "0.1.4",
+      "version": "0.1.7",
       "via": "this repository",
-      "skills": [],
+      "skills": [
+        "working-in-passioncode"
+      ],
       "legacyPluginIds": [],
       "legacyMarketplaces": [],
-      "contentHash": "sha256:89449784f0e3917e29c3641b8d40ecedc956b4296111d2680290b9daca9218f5",
-      "description": "Keeps the PassionCode.ai set current: a once-a-day check at session start and a background update.",
+      "contentHash": "sha256:9c7431ba81678924da9764acfb828c1f6714c24facfc5aed69cb31eee413e7d1",
+      "description": "The organisation's working rules for every contributor's agent (working-in-passioncode), and a once-a-day check that keeps the PassionCode.ai set current.",
       "author": {
         "name": "PassionCode.ai",
         "url": "https://passioncode.ai/"
-      }
+      },
+      "license": "PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0"
     }
   ]
 }

package/payload/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.4.2",
+  "version": "0.4.3",
   "author": {
-    "name": "passioncode-ai",
-    "url": "https://github.com/passioncode-ai"
+    "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": "MIT",
+  "license": "PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0",
   "keywords": [
     "fabric",
     "agent",

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

@@ -1,13 +1,13 @@
 ---
 name: adapting-projects-to-fabric
 description: Use when adapting an existing agent, MCP server, A2A peer, HTTP service, or terminal CLI to the Fabric Agent Contract—choosing MCP/A2A/local-runner, scaffolding a provider bundle, or checking Fabric compatibility; also for «подключить проект к Fabric» or «сделать агента совместимым с Fabric». NOT for building the Fabric host/orchestrator, configuring an MCP client, or a brand-new agent — that is creating-fabric-agents.
-license: MIT
+license: PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0
 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.4.2"
+  author: PassionCode.ai
+  version: "0.4.3"
   contract-version: "0.1.0"
-  contract-commit: "20a818e648a4c09a60df0126d11626922e8b9094"
+  contract-commit: "a5a27092ba0dcc5facfbeae8b359146dfb403e9a"
 ---
 
 # Adapting projects to Fabric
@@ -22,6 +22,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
+  normative for what Fabric requires;
 - 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.
 
@@ -67,7 +70,7 @@ Use exactly:
 
 - contract version `0.1.0`;
 - repository `https://github.com/passioncode-ai/fabric-agent-contract`;
-- commit `20a818e648a4c09a60df0126d11626922e8b9094`.
+- commit `a5a27092ba0dcc5facfbeae8b359146dfb403e9a`.
 
 Read the pinned contract's guide
 `docs/guides/connecting-compatible-agents.md`, the selected profile specification, and

package/payload/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 = "20a818e648a4c09a60df0126d11626922e8b9094"
+CONTRACT_COMMIT = "a5a27092ba0dcc5facfbeae8b359146dfb403e9a"
 MCP_REVISION = "2026-07-28"
 A2A_VERSION = "1.0"
 LOCAL_VERSION = "fabric-local-runner/0.1"

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

@@ -1,8 +1,8 @@
 ---
 name: building-fabric-services
 description: >-
-  Use when building or running an agent as a long-lived local service with a dashboard on the
-  operator's Mac — «сделай агенту дашборд», «локальный сервис агента», «дашборд должен всегда
+  Use when building or running an agent as a long-lived local service with a dashboard on
+  a macOS machine — «сделай агенту дашборд», «локальный сервис агента», «дашборд должен всегда
   работать и не плодить копии», «где агенту хранить настройки», «подключи агента к Fabric
   Dashboards», "make this agent a local service", "always-on dashboard", "fabric-service
   protocol", "add the well-known endpoint", "migrate a service to fabric-service". Covers the
@@ -11,11 +11,11 @@ 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: MIT
+license: PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0
 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.4.2"
+  author: PassionCode.ai
+  version: "0.4.3"
   contract-version: "0.1.0"
   extension: "fabric-service/0.1"
   extension-commit: "a5a27092ba0dcc5facfbeae8b359146dfb403e9a"

package/payload/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: MIT
+license: PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0
 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.4.2"
+  author: PassionCode.ai
+  version: "0.4.3"
   contract-version: "0.1.0"
-  contract-commit: "20a818e648a4c09a60df0126d11626922e8b9094"
+  contract-commit: "a5a27092ba0dcc5facfbeae8b359146dfb403e9a"
 ---
 
 # Creating Fabric-compatible agents
@@ -30,6 +30,17 @@ Use this skill to design and build a new provider. Do not use it to:
 - claim admission: the deliverable is an admission-ready provider bundle, never a
   connected provider.
 
+## Handing off to neighbouring skills
+
+- The agent's own loop — tool calls, routing and fallback, memory, sub-agents — is
+  designed with `agent-orchestrator` (agent-stack).
+- Its eval suite beyond the step-2 observables — trajectories, judges, regression
+  fixtures from traces — is built with `agent-evals` (agent-stack).
+- Packaging the agent as an Agent Skill or Claude Code plugin goes through `make-skill`.
+
+When one of them is not installed, do that part by hand against its own documentation
+and say in the report which skill was missing.
+
 ## Step 0 — the intake grill
 
 No file is created until every row has an answer. An answer of "later" fails the grill.
@@ -82,7 +93,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 `20a818e648a4c09a60df0126d11626922e8b9094` and
+Pin exactly contract `0.1.0` at commit `a5a27092ba0dcc5facfbeae8b359146dfb403e9a` 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

package/payload/plugins/observatory-log/.claude-plugin/plugin.json

@@ -3,11 +3,11 @@
   "name": "observatory-log",
   "displayName": "Observatory Log",
   "description": "Records what changed in a watched project at the end of every turn, and asks for the one thing a diff cannot contain: why.",
-  "version": "0.12.2",
-  "license": "MIT",
+  "version": "0.12.3",
+  "license": "PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0",
   "author": {
-    "name": "Sergey Sheleg",
-    "url": "https://sshlg.me/"
+    "name": "PassionCode.ai",
+    "url": "https://passioncode.ai/"
   },
   "homepage": "https://github.com/passioncode-ai/project-observatory-dashboard",
   "keywords": [

package/payload/plugins/observatory-log/skills/explaining-changes/SKILL.md

@@ -13,9 +13,9 @@ description: >-
   message, a PR description or a changelog, and NOT for changing the typed
   registry — a registry change is `observatory_propose`, which is a different
   decision with different evidence.
-license: MIT
+license: PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0
 metadata:
-  version: "0.12.2"
+  version: "0.12.3"
 compatibility: >-
   Requires an initialized full Project Observatory installation to persist
   records. Uses its MCP server when available in the current host; the bundled

package/payload/plugins/observatory-log/skills/handling-secrets/SKILL.md

@@ -7,9 +7,9 @@ description: >-
   Keeps credential values out of prompts and command arguments, uses named slots,
   and records changes without copying values into reports. NOT for granting
   provider permissions or choosing a project's authentication architecture.
-license: MIT
+license: PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0
 metadata:
-  version: "0.12.2"
+  version: "0.12.3"
 compatibility: >-
   Requires an initialized full Project Observatory installation, Python 3.11+
   and local shell access on macOS or Linux. Provider operations additionally
@@ -29,7 +29,7 @@ names. Never ask the user to paste a credential into the conversation.
 2. Select the user's initialized `OBSERVATORY_HOME`. Run
    `python3 "$OBSERVATORY_ROOT/observatory.py" doctor`. A missing workspace
    needs the documented onboarding before secret operations.
-3. Run `python3 "$OBSERVATORY_ROOT/tools/skill_check.py" handling-secrets 0.12.2`.
+3. Run `python3 "$OBSERVATORY_ROOT/tools/skill_check.py" handling-secrets 0.12.3`.
    If stale, read the installed skill once and follow its compatible commands.
    Do not turn an unavailable version check into a retry loop.
 4. Inspect names using `tools/use_secret.py names PROJECT` or `tools/vault.py

package/payload/plugins/observatory-log/skills/tracking-resources/SKILL.md

@@ -13,9 +13,9 @@ description: >-
   figma-use), wiring analytics or pixels (ad-tracking), provisioning the resource
   with the provider's own tools, secrets (handling-secrets) or code changes inside
   the repository.
-license: MIT
+license: PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0
 metadata:
-  version: "0.12.2"
+  version: "0.12.3"
 compatibility: >-
   Requires a full Project Observatory installation with organizations.json
   configured; the observatory MCP server or its local CLI. Creating the resource

package/payload/plugins/passioncode/.claude-plugin/plugin.json

@@ -2,12 +2,12 @@
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "passioncode",
   "displayName": "PassionCode.ai",
-  "version": "0.1.4",
-  "description": "Keeps the PassionCode.ai skill set current: a once-a-day check at session start and a background update.",
+  "version": "0.1.7",
+  "description": "The organisation's working rules for every contributor's agent (working-in-passioncode), and a once-a-day check at session start that keeps the PassionCode.ai skill set current.",
   "author": {
     "name": "PassionCode.ai",
     "url": "https://passioncode.ai/"
   },
   "homepage": "https://github.com/passioncode-ai/passioncode",
-  "license": "MIT"
+  "license": "PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0"
 }

package/payload/plugins/passioncode/hooks/update-check.js

@@ -15,6 +15,22 @@ const PACKAGE = '@passioncode-ai/passioncode';
 const VERSION = /^\d+\.\d+\.\d+$/;
 const TRUST_FILE = path.join(__dirname, '..', 'trust.json');
 
+/**
+ * The identity npm records for a version published by GitHub Actions through trusted
+ * publishing (OIDC). Recognised by its email, never by the display name, which any account
+ * can copy. Only a maintainer can register a trusted publisher, and maintainers are still
+ * checked one by one, so listing this in trust.json trusts the release workflow the
+ * maintainers configured, not GitHub at large.
+ */
+const OIDC_PUBLISHER = 'github-actions-oidc';
+const OIDC_EMAIL = 'npm-oidc-no-reply@github.com';
+
+function publisherName(entry) {
+  const email = entry && typeof entry === 'object' ? entry.email : (String(entry || '').match(/<([^>]*)>/) || [])[1];
+  if (typeof email === 'string' && email.trim().toLowerCase() === OIDC_EMAIL) return OIDC_PUBLISHER;
+  return accountName(entry);
+}
+
 /** `name <email>`, `{ name, email }` or `name` → the npm account name, lowercased. */
 function accountName(entry) {
   const raw = entry && typeof entry === 'object' ? entry.name : entry;
@@ -47,7 +63,7 @@ function parseView(stdout, error) {
     latest,
     // An entry that is not a readable account name poisons the list: it cannot be trusted.
     maintainers: maintainers.includes(null) ? [] : maintainers,
-    publisher: doc._npmUser ? accountName(doc._npmUser) : null,
+    publisher: doc._npmUser ? publisherName(doc._npmUser) : null,
   };
 }
 
@@ -123,4 +139,4 @@ function decide(state, trust, now = Date.now()) {
   return { lines, spawn, stateChanges };
 }
 
-module.exports = { PACKAGE, TRUST_FILE, accountName, parseView, recordProbe, loadTrust, newer, decide };
+module.exports = { PACKAGE, OIDC_PUBLISHER, TRUST_FILE, accountName, parseView, recordProbe, loadTrust, newer, decide };

package/payload/plugins/passioncode/skills/working-in-passioncode/SKILL.md

@@ -0,0 +1,200 @@
+---
+name: working-in-passioncode
+description: >-
+  Use when working in any passioncode-ai repository — "work on a PassionCode repo", "open a PR
+  in passioncode-ai", "release", "tag a version", "which repo owns this", "bump the contract
+  pin", "publish this to the public repo", "what license do we use", «работаю в репозитории
+  PassionCode», «как тут принято», «где записать решение», «как выпустить релиз». Covers the org
+  map, landing (protected and unprotected main, fast-forward, never force-push shared work,
+  never touch another session's work), nightly CI and why a blocked run is not green,
+  handoffs, decisions, ids and leases, secrets, licensing (source-available, CLA, MIT
+  schemas), the privacy gate before anything goes public, and releases, versions and pins;
+  org-index stays the source of truth. NOT for product UX, visual design or copy (super-ux,
+  sheleg-design, copywriting), building Fabric agents or services (the fabric-agent-adapter
+  skills), or repositories outside passioncode-ai.
+license: PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0
+compatibility: Any agent that can read files and run git. The gh CLI and a clone of passioncode-ai/org-index make the checks exact; without them follow the fallbacks in the body.
+metadata:
+  author: PassionCode.ai
+---
+
+# Working in PassionCode repositories
+
+The rules of the `passioncode-ai` organisation live in one place:
+[org-index](https://github.com/passioncode-ai/org-index) (private; every member can
+read it) — `README.md` for the map, `RULES.md` for the rules, `ONBOARDING.md` for a new
+machine. This skill is the checklist that makes those rules reach you while you work.
+It summarises; it does not replace. Where it and org-index disagree, **org-index wins**;
+where a repository's own `AGENTS.md` is stricter, **that file wins**.
+
+## 1. Before the first edit
+
+1. Read the repository's `AGENTS.md` (its `CLAUDE.md` imports it). It names the role,
+   the test command and any local rule.
+2. Find who owns what you are about to change: the table in org-index `README.md`,
+   generated from `repositories.json`. Do not guess an owner from a directory name.
+3. `git fetch origin`, then work in a worktree from `origin/main` on your own branch
+   (`<who>/<topic>`, e.g. `agent/engine-update`):
+   `git worktree add ../<repo>-<topic> -b <who>/<topic> origin/main`.
+   Checkouts are shared by several sessions; never switch, reset, stash or check out
+   over one.
+4. An unmerged branch or a dirty tree you did not create is someone's work in
+   progress. Leave it; ask before touching it.
+
+No org-index clone: `gh repo clone passioncode-ai/org-index`. No access at all: say so,
+follow the repository's `AGENTS.md`, and name that you worked from it alone.
+
+## 2. Landing on main
+
+| `main` is | Land by |
+|---|---|
+| protected (today only `project-observatory-dashboard`) | a PR; the required checks green (three OS/Python combinations); linear history |
+| unprotected (every other repository) | a PR, or a fast-forward push after the repository's local gate passes |
+
+- Private repositories are on GitHub's free plan, which cannot protect a branch. The
+  rules hold there **on your word**.
+- A fast-forward means `git push origin HEAD:main` succeeds without `--force`. If
+  `main` moved, rebase your own branch, re-run the gate, then push.
+- Never force-push `main`, and never force-push a branch someone else has built on.
+- Never put a merge commit on top of someone else's unpushed work.
+- Release tags `vX.Y.Z` and contract tags `rev-N` never move. A mistake gets a new
+  version.
+- Commit subjects: imperative, at most 72 characters. An agent's commit ends with a
+  `Co-Authored-By:` trailer naming the model.
+
+## 3. Tests and CI
+
+- **The local gate is the gate.** Run the repository's test command (its `AGENTS.md`,
+  and the `test` field in `repositories.json`) before you push, and report each
+  command with its exit code.
+- Hosted CI runs **nightly at 23:00 Europe/Warsaw** on the default branch, not on every
+  push. Dispatch a hosted run by hand only for an urgent candidate; never restore
+  per-push triggers.
+- **No CI result is not a green result.** Actions for the organisation's private
+  repositories are held by the spending cap: a job that "failed in 3 s" never started.
+  Read the annotation (`gh api repos/<owner>/<repo>/check-runs/<job-id>/annotations`)
+  and report the run as blocked, never as passing.
+
+## 4. Handoffs, decisions, ids and leases
+
+- **Every task leaves a tracked handoff** in the owning repository:
+  `docs/handoffs/<date>-<topic>.md` or `docs/runs/<date>-<topic>/README.md`. It states
+  the objective, what was done, what is open, the decisions taken, the checks actually
+  run (command and exit code) and **the exact next task**. Work across repositories
+  keeps one index in org-index `docs/runs/`, naming each repository, branch and commit.
+- **Decisions.** Cross-repository ones go in `fabric/docs/adr/`; a repository's own in
+  its `docs/adr/` or `docs/DECISIONS.md`. Records are append-only; a reversal is a new
+  record.
+- **Ids.** In a repository with `.claude/agent-sync.json`, reserve an id before writing
+  it: `agent_sync.py reserve <REGISTER>` (for example `ADR` in fabric). Reading the
+  "next free id" line is not reserving it — two agents read the same number.
+- **Leases.** `fabric` and `fabric-agent-contract` guard shared files (their
+  `docs/AGENT_SYNC.md` lists them) under a git lease, a ref under
+  `refs/agent-sync/leases/` on `origin`, so both machines see it. `acquire` → edit →
+  `release`, on every path, failure included.
+- **Receipts.** A claim that will be read as true carries `file:line`, a command and
+  its output, or a test name. Documentation changes in the same change as the
+  behaviour it describes.
+
+agent-sync missing: `npx @ssheleg/agent-sync install`. If it cannot be installed, do
+not edit a guarded file — say which file and why you stopped.
+
+## 5. Secrets
+
+- Never in Git, a chat message, an issue, a command argument, a URL query string or a
+  log. `.env*` files are gitignored everywhere.
+- Each machine keeps its own credentials; nothing is copied from one person's machine
+  to another's. The operator issues a scoped credential when one is shared.
+- A leaked value is rotated **and** the leak is recorded; deleting the message is not
+  enough. With the Observatory plugin installed, its `handling-secrets` skill does this
+  by slot name without printing the value.
+
+## 6. Licensing — say it exactly
+
+| Products | License |
+|---|---|
+| `fabric-switchboard`, `project-observatory-dashboard`, `fabric-dashboards`, and the contributor tools (`passioncode`, `fabric-agent-adapter`) | `PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0`; a commercial license on request (contact@passioncode.ai) |
+| `project-observatory-contract` (the schemas) | MIT, so anyone can implement them |
+
+- Call these products **source-available**, never "open source", "open-source" or
+  "MIT". The short line: "Source-available under PolyForm Noncommercial or Internal
+  Use; commercial license on request."
+- Versions already released under MIT stay MIT, and each `LICENSE` names the last one.
+  Never claim otherwise.
+- Contributions are accepted under the repository's `CLA.md`; the PR template carries
+  the "I agree to CLA.md" box.
+- The PolyForm texts are verbatim; never edit them.
+
+Read [publishing](references/publishing.md) when adding or changing a license, a
+manifest's `license` field, `CLA.md` or a PR template.
+
+## 7. Before anything goes public
+
+A public repository, the site, the organisation profile, an npm tarball or a release
+note is public. Before it ships:
+
+- Run the repository's privacy gate. The engine's is
+  `python3 tools/check_public_release.py`; a name published on purpose goes in
+  `tools/public-identifiers.json` **with a reason** — a review decision, never a way to
+  silence a finding.
+- **The operator's personal agents never appear** on PassionCode.ai surfaces, examples,
+  evals, docs or families. Use neutral names such as `example-agent`. The launcher's
+  members are PassionCode.ai products only.
+- No absolute home paths (`/Users/<name>/…`, the operator's own project root) in code,
+  tests or public documents. Those in existing documents are the operator's layout,
+  not requirements.
+- Product metadata names **PassionCode.ai** (`https://passioncode.ai/`) as author, not a
+  person. Security reports go to contact@passioncode.ai (and GitHub private
+  vulnerability reporting where a public repository offers it).
+
+Read [publishing](references/publishing.md) before a first public release or a change
+to a public surface.
+
+## 8. Releases, versions and pins
+
+- One version, everywhere: every manifest, the plugin and the top `CHANGELOG.md` entry
+  move together. Each repository's validator or test holds them in sync.
+- A pushed `v*` tag can **publish to npm**: the launcher's and the adapter's
+  `release.yml` publish when the repository variables `RELEASE_ENABLED` and
+  `PUBLISH_NPMJS` are `true`. Check `gh variable list -R passioncode-ai/<repo>` before
+  pushing a tag; publishing is a release decision, not a side effect.
+- **Engine** (`project-observatory-dashboard`): contributors send PRs; releases are cut
+  with the maintainer's release tooling, which is maintainer-only. Machines then run
+  `project-observatory full update --check` and `--apply`.
+- **Launcher** (`passioncode`): members are tagged first, `family.json` refs point at
+  those tags, the payload is vendored from tags only.
+- **Contract pins.** `fabric-agent-contract` has no tags, so consumers pin commits, and
+  the pins disagree (org-index `BACKLOG.md` X-4). Move a pin only in a release of the
+  consumer, and only when its own validation passes against the new commit.
+
+Read [releasing](references/releasing.md) for the step-by-step of each repository's
+release.
+
+## 9. Which skill does what here
+
+The table in org-index `README.md` → "What an agent uses for each infrastructure
+project" is the map: the Observatory plugin `observatory-log` (`explaining-changes`,
+`handling-secrets`, `tracking-resources`), the `fabric-agent-adapter` plugin
+(`creating-fabric-agents`, `adapting-projects-to-fabric`, `building-fabric-services`),
+`agent-sync` for leases, and `maintaining-fabric-workspace` inside a fabric checkout.
+What the product does for its users, how it looks and how it reads are not this
+skill's: `super-ux`, `sheleg-design` and `copywriting`.
+
+## Gotchas
+
+- A private repository's hosted job "failed" in seconds: that is the spending cap, not
+  a test failure — and not a pass either.
+- With the release variables on, re-running an old release workflow once Actions is
+  back **publishes that old tag to npm**. Decide before re-running.
+- On macOS the system `python3` is 3.9, too old for the Observatory. Use a current
+  Python (`ONBOARDING.md` §2).
+- `gh auth status` can report an invalid token while `git` over SSH works. Attempt the
+  operation before calling it blocked.
+- A sentence that says "on this Mac" or names `~/…` in someone's document describes
+  the operator's machine. Do not copy it into yours.
+
+## Completion format
+
+Report: the repository and branch; the landed commit or the PR URL; each gate command
+with its exit code; the hosted CI state (ran, blocked, or nightly pending); the handoff
+path; and the one next task.

package/payload/plugins/passioncode/skills/working-in-passioncode/references/publishing.md

@@ -0,0 +1,76 @@
+# Publishing and licensing in passioncode-ai
+
+Load this before a first public release, a change to a public surface (a public
+repository, the site, the organisation profile, an npm package, a release note), or any
+change to a license, a manifest's `license` field, `CLA.md` or a PR template.
+
+## Contents
+
+- The license, file by file
+- Wording
+- The privacy gate
+- Names, paths and authorship
+
+## The license, file by file
+
+The source-available expression is
+`PolyForm-Noncommercial-1.0.0 OR LicenseRef-PolyForm-Internal-Use-1.0.0`; a commercial
+license is offered on request at contact@passioncode.ai. The schemas in
+`project-observatory-contract` are MIT instead. To relicense a repository, copy the
+`LICENSE` of one already relicensed (this launcher's, for instance) and change only the
+MIT-history sentence — the copyright line and the Required Notice stay as they are.
+
+| File | What it carries |
+|---|---|
+| `LICENSE` | the copyright line, the two licenses, a one-paragraph summary marked as not part of either license, one sentence naming which earlier releases stay MIT, the Required Notice, then both PolyForm texts verbatim |
+| `CLA.md` | the contributor license agreement, at the repository root |
+| `CONTRIBUTING.md` | says contributions are accepted under `CLA.md` |
+| `.github/pull_request_template.md` | a checkbox "I agree to CLA.md"; any existing template content is kept |
+| `package.json` | `"license"` set to the SPDX expression |
+| `.claude-plugin/plugin.json`, marketplace entries | `"license"` set to the SPDX expression |
+| SKILL.md front matter | `license:` set to the SPDX expression |
+| `pyproject.toml` | `license` as an SPDX expression (PEP 639), which needs `setuptools>=77` in `build-system` |
+| `Cargo.toml` | `license-file = "LICENSE"` instead of `license`, and `publish = false` |
+
+- The PolyForm texts are copied verbatim. Never edit, abridge or "fix" them.
+- The MIT sentence names the real last MIT release — for example "Versions up to and
+  including v0.8.1 of this repository were released under the MIT License; those
+  releases remain available under MIT." For a repository with no release: "Commits
+  before <sha> …".
+- A published MIT release stays MIT. Never write that it changed.
+
+## Wording
+
+- The products are **source-available**. Never "open source", "open-source" or "MIT"
+  for them — in a README, the site, the profile, a description or JSON-LD.
+- The short line: "Source-available under PolyForm Noncommercial or Internal Use;
+  commercial license on request."
+- The tagline is "The agent-agnostic operating system for AI-native teams." and "A
+  toolkit for AI-native teams."; the category line is "From vibe coding to passion
+  coding."
+
+## The privacy gate
+
+- The engine's gate: `python3 tools/check_public_release.py`. It scans the tree and
+  the blob history and prints categories and counts, never the matched values. The
+  maintainer adds `--private-denylist <local file>`; that list is never committed, never
+  copied into a repository and never printed.
+- A name that is published on purpose goes in `tools/public-identifiers.json` with a
+  reason. Adding one is a review decision.
+- Other public repositories run the checks their own `AGENTS.md` names. Where there is
+  none, grep your change for home paths, host names and personal names before pushing.
+
+## Names, paths and authorship
+
+- The operator's personal agents never appear on PassionCode.ai surfaces, examples,
+  evals, docs or the launcher's member list. Examples use neutral names:
+  `example-agent`, `alpha-web`, `beta-api`, `example.com`.
+- No absolute home paths in code, tests or public documents. Read the ones in older
+  documents as the operator's layout.
+- Product metadata: author and owner **PassionCode.ai**, URL `https://passioncode.ai/`.
+  The site names the author by first name only; do not add full names or biographies to
+  product surfaces.
+- Public documents do not link private repositories. org-index may be linked for the
+  map and the rules only.
+- Security and conduct contact: contact@passioncode.ai, plus GitHub private
+  vulnerability reporting on a public repository.

package/payload/plugins/passioncode/skills/working-in-passioncode/references/releasing.md

@@ -0,0 +1,97 @@
+# Releasing in passioncode-ai
+
+Load this when you cut a release, bump a version, move a pin or tag anything. Each
+repository's own `README.md` and `AGENTS.md` hold the exact commands; this file is the
+shape they share and the order that matters.
+
+## Contents
+
+- Rules for every release
+- The launcher (`passioncode`)
+- The adapter (`fabric-agent-adapter`)
+- The engine (`project-observatory-dashboard`)
+- Contract pins
+- After a release
+
+## Rules for every release
+
+1. The local gate is green **before** the tag: the repository's test command, its
+   validator, and `claude plugin validate <dir> --strict` for every plugin it ships.
+2. Every version field moves together: `package.json`, `.claude-plugin/plugin.json`,
+   `.claude-plugin/marketplace.json`, SKILL.md `metadata.version` where present, and the
+   top `CHANGELOG.md` entry. A validator or test in each repository holds them in sync.
+3. Land first, then tag the commit on `main`. A tag pushed without its branch is a
+   release that a fresh clone cannot reach.
+4. A tag never moves. If `vX.Y.Z` exists — even on a commit you would not have chosen —
+   the next release is `vX.Y.Z+1`. Check with `git ls-remote --tags origin`.
+5. Before pushing a `v*` tag, read `gh variable list -R passioncode-ai/<repo>`. With
+   `RELEASE_ENABLED` and `PUBLISH_NPMJS` both `true`, the tag publishes to npm as soon as
+   Actions runs — including a re-run after the spending cap is lifted.
+6. A GitHub release carries the version's CHANGELOG section:
+   `gh release create vX.Y.Z --title "vX.Y.Z" --notes-file <section>`.
+7. Write the handoff (objective, done, open, decisions, checks with exit codes, next
+   task) in the same change.
+
+## The launcher (`passioncode`)
+
+1. Tag every member at the version to ship, in its own repository.
+2. Set each member's `ref` in `family.json` to that tag. A member whose own release has
+   not happened yet keeps its old ref; the integrator moves it later.
+3. Bump `package.json` and `plugin/passioncode/.claude-plugin/plugin.json`, add the
+   CHANGELOG section.
+4. Vendor from tags only, from the member repositories rather than local checkouts:
+   `PASSIONCODE_VENDOR_CLONE=1 npm run vendor:release`.
+5. `claude plugin validate ./payload --strict`, then the same for each
+   `./payload/plugins/<member>`; `npm test`.
+6. Land on `main` (fast-forward), tag, push the tag.
+7. Installing the new set on a machine (`passioncode update`) is the integrator's step,
+   not the releaser's.
+
+`payload/` is generated and never committed. A local checkout is used for a member only
+when `PASSIONCODE_CHECKOUT_ROOT` (or a per-member `PASSIONCODE_CHECKOUT_<MEMBER>`)
+points at one; otherwise the member is shallow-cloned at its tag.
+
+## The adapter (`fabric-agent-adapter`)
+
+The README section "Validate this repository" is the gate:
+
+```bash
+python3 -m unittest discover -s test -v
+python3 test/validate.py
+node --test 'test/*.test.js'
+claude plugin validate ./plugins/fabric-agent-adapter --strict
+claude plugin validate . --strict
+```
+
+`test/validate.py` carries the version it expects (`VERSION`); bump it with the
+manifests. Trigger and scenario evals change before the instructional prose they test.
+
+## The engine (`project-observatory-dashboard`)
+
+- Contributors open PRs; `main` is protected and requires the three OS/Python checks.
+- The release itself — build, sign-off, wheel, `SHA256SUMS` — is cut by the maintainer's
+  release tooling, which is maintainer-only. Do not reconstruct it.
+- The privacy gate runs before every public release:
+  `python3 tools/check_public_release.py`.
+- Machines move to a release with `project-observatory full update --check`, then
+  `--apply` (verified and reversible).
+
+## Contract pins
+
+- `fabric-agent-contract` publishes no tags; consumers (fabric, the adapter, the
+  Observatory) pin a commit. The pins disagree today — org-index `BACKLOG.md` X-4 tracks
+  it.
+- Moving a pin is a compatibility change of the **consumer**: run the consumer's own
+  validation against the new contract commit (for the adapter:
+  `adapt_project.py check <bundle> --contract <checkout at the new commit>` for each
+  profile), review what changed between the two commits, and ship it as a new consumer
+  release. If the validation does not pass, leave the pin and report why.
+- `project-observatory-contract` publishes immutable `rev-N` tags; a schema `$id` change
+  needs a new `rev-N`.
+
+## After a release
+
+- The org map (`org-index/repositories.json`) changes in the same change when a role,
+  dependency or test command changed.
+- Report: the tag, the commit it points at, the GitHub release URL, the gate commands
+  with exit codes, and whether hosted CI ran, was blocked, or waits for the nightly run.

package/payload/plugins/passioncode/trust.json

@@ -1,6 +1,7 @@
 {
-  "$comment": "npm accounts allowed to publish @passioncode-ai/passioncode. The session-start hook auto-updates only to a version whose every npm maintainer and publisher is listed here; see SECURITY.md.",
+  "$comment": "Who may publish @passioncode-ai/passioncode. The session-start hook auto-updates only to a version whose every npm maintainer and publisher is listed here; see SECURITY.md. github-actions-oidc is this repository's release.yml publishing through npm trusted publishing (registered by a maintainer).",
   "npmPublishers": [
-    "ssheleg"
+    "ssheleg",
+    "github-actions-oidc"
   ]
 }