@passioncode-ai/passioncode 0.1.4

package/CHANGELOG.md

@@ -0,0 +1,73 @@
+# Changelog
+
+## 0.1.4 - 2026-09-29
+
+### Security
+
+- The package is `@passioncode-ai/passioncode`, in the npm organisation that PassionCode.ai
+  owns. The bare name `passioncode` was unclaimed, so whoever registered it would have been
+  what the self-update checks. The hook now watches the scoped name, and `trust.json` names
+  the organisation's publisher.
+
+### Changed
+
+- Install and update with `npx @passioncode-ai/passioncode@latest update`.
+- A `v*` tag releases and publishes from GitHub Actions (`.github/workflows/release.yml`),
+  the same pipeline as the adapter.
+
+## 0.1.3 - 2026-09-29
+
+- Observatory Log 0.12.2 (Observatory 0.8.1): the engine's `full agent` recognises the copy this
+  launcher installs instead of adding a second one, and `tracking-resources` no longer triggers on
+  creation requests.
+
+### Security
+
+- The session-start hook no longer runs whatever is published under the npm name
+  `passioncode`. The name was unclaimed (`npm view passioncode` answered E404), so
+  whoever registered it would have had code run on every machine with the plugin. The
+  daily probe now records the latest version together with its npm maintainers and
+  publishing account (`npm view passioncode version maintainers _npmUser --json`); the
+  hook updates only when every one of them is in `plugin/passioncode/trust.json`, and
+  otherwise spawns nothing and names who published it. The list ships empty: until the
+  maintainers add their npm account, nothing updates on its own.
+- The update it runs is pinned — `npx --yes passioncode@<verified version> update` — so
+  what was checked is what runs, not whatever `@latest` points at a moment later.
+
+### Fixed
+
+- A failed update check is shown once in the session-start line instead of never; the
+  same error is not repeated every session.
+- A background update is recorded (`updatingSince`) when it starts, so a second session
+  start within ten minutes does not start a second one.
+- The old single-member marketplaces (`fabric-agent-adapter`, `observatory-log`) are
+  retired once the member's `@passioncode` plugin is verified and nothing else installed
+  comes from them: the `extraKnownMarketplaces` entry leaves `~/.claude/settings.json`
+  (backed up in the quarantine) and `claude plugin marketplace remove` unregisters it —
+  otherwise Claude Code re-registered it, with autoUpdate, and installing from it would
+  bring a second channel back. `passioncode restore` re-adds both. `status` names any
+  that are left.
+- Vendoring no longer needs the maintainer's own checkouts: a member whose `checkout`
+  is absent is shallow-cloned from `repo` at `ref` over SSH (`--clone` or
+  `PASSIONCODE_VENDOR_CLONE=1` forces it). The payload's marketplace entries carry
+  `displayName` and `author`, and the `$schema` URLs are ones that resolve.
+
+## 0.1.2 - 2026-09-29
+
+- Fabric Agent Adapter 0.4.2: the kit's `LoopbackHTTPServer` binds without a reverse DNS
+  lookup, a garbled pid file reads as unknown, and every SKILL.md front matter parses as
+  strict YAML (0.4.1).
+
+## 0.1.1 - 2026-09-29
+
+- `update --dry-run` says the plan changed nothing instead of reporting it as done.
+  0.1.0 was tagged but never published.
+
+## 0.1.0 - 2026-09-28
+
+- First release: Fabric Agent Adapter 0.4.0 and Observatory Log 0.12.1 as Claude Code
+  plugins from one local marketplace, and through the `~/.agents/skills` hub for every
+  other agent.
+- Replaces the old single-member plugin installs, and moves shadowing
+  `~/.claude/skills` entries and working-tree hub links into a restorable quarantine.
+- Once-a-day update check at session start with a background update (`update.auto`).

package/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2026 PassionCode.ai
+
+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:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+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.
+

package/README.md

@@ -0,0 +1,69 @@
+# passioncode
+
+> **PassionCode.ai — The agent-agnostic operating system for AI-native teams.**
+
+Every PassionCode.ai agent skill, for Claude Code and every other agent on your machine,
+installed and updated as one set:
+
+```bash
+npx @passioncode-ai/passioncode@latest update
+```
+
+| Member | Skills |
+|---|---|
+| 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 |
+
+Only PassionCode.ai products are members. Agents that people build for themselves stay
+out of it, even when they implement Fabric protocols.
+
+## How it installs
+
+- **Claude Code** gets plugins from a local marketplace named `passioncode` at
+  `~/.passioncode/current` — no GitHub access needed. A plugin that was installed from
+  its old single-member marketplace (`fabric-agent-adapter@fabric-agent-adapter`,
+  `observatory-log@observatory-log`) is replaced once the new one is verified, and that
+  marketplace is unregistered and taken out of `settings.json` once nothing installed
+  comes from it.
+- **Every other agent** (Cursor, Codex, Gemini, OpenCode, Kiro, Windsurf, Goose, …) gets
+  the same skills through `~/.agents/skills`, linked from each channel that exists on
+  the machine.
+- Nothing is written to `~/.claude/skills`: a plain copy there shadows the plugin. Such
+  copies, and hub entries that pointed at a repository's working tree, are moved into
+  `~/.passioncode/quarantine/` — `npx passioncode restore` puts them back.
+- Each version is an immutable release under `~/.passioncode/releases/<version>`.
+
+## Staying current
+
+At every Claude Code session start the `passioncode` plugin checks npm at most once a
+day and, when a newer set is out **and every npm account that publishes it is in the
+plugin's `trust.json`**, updates to that exact version in the background — it takes
+effect in the next session. A version published by anyone else is named and not
+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 update --dry-run
+npx passioncode uninstall
+```
+
+## Release (maintainers)
+
+1. Tag every member at the version to ship; set `ref` to that tag in `family.json`.
+2. Bump `version` in `package.json` and `plugin/passioncode/.claude-plugin/plugin.json`
+   (a test holds them and the CHANGELOG in sync), add the CHANGELOG section.
+3. The npm account that publishes must be listed in `plugin/passioncode/trust.json`
+   (`npmPublishers`), and be the package's only kind of maintainer — otherwise every
+   installed hook refuses the update and says so.
+4. Merge, then tag the merge commit `vX.Y.Z` and push the tag. `.github/workflows/release.yml`
+   validates, checks the tag against both manifests, creates the GitHub release from the
+   CHANGELOG section, vendors every member **from its own repository** at its pinned tag,
+   runs the tests, installs the packed tarball from a clean `HOME`, publishes
+   `@passioncode-ai/passioncode` and waits until npm serves it. It runs when the repository
+   variables `RELEASE_ENABLED` and `PUBLISH_NPMJS` are `true`; npm auth is trusted publishing
+   (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.

package/SECURITY.md

@@ -0,0 +1,42 @@
+# Security
+
+Report vulnerabilities privately to the maintainers of the `passioncode-ai` organization.
+
+What `passioncode update` touches: `~/.passioncode/` (releases, state, quarantine,
+logs); Claude Code's plugin registry through the `claude plugin` CLI only;
+`~/.agents/skills/<member skill>` and `<agent channel>/<member skill>` links; and
+`~/.claude/skills/<member skill>`, which it moves into the quarantine once the plugin
+that replaces it is verified. For a member's old single-member marketplace
+(`legacyMarketplaces` in `family.json`), once that plugin is verified and nothing else
+installed comes from it, it also moves the `extraKnownMarketplaces` entry out of
+`~/.claude/settings.json` (a copy of the file is kept in the quarantine) and runs
+`claude plugin marketplace remove <name>`. It never deletes: every move is listed in
+`~/.passioncode/quarantine/<run>/moved.json` and undone by `passioncode restore`.
+
+## The self-update and who it trusts
+
+The SessionStart hook reads `~/.passioncode/state.json` and, at most once a day, starts
+`npm view @passioncode-ai/passioncode version maintainers _npmUser --json`, detached, logging to
+`~/.passioncode/logs/`. It records the latest version, the package's npm maintainers
+and the account that published that version.
+
+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`);
+- the version is a plain `x.y.z`.
+
+It then runs `npx --yes @passioncode-ai/passioncode@<that exact version> update --quiet`, detached, so
+the version that was checked is the version that runs. In every other case it spawns
+nothing: a version from an account outside the list is reported in one line naming the
+account ("… not a trusted PassionCode publisher — not installing"); a name nobody has
+published (npm E404) is silent; a failed check is shown once.
+
+`trust.json` ships **empty**, so auto-update stays inert until the maintainers name the
+npm account(s) that publish PassionCode. Adding an account there is a release decision:
+it is reviewed like code and ships in the package. A person who wants no background
+updates at all runs `npx passioncode config set update.auto off`.
+
+The published package carries skill text only; the vendor step refuses to build when it
+finds a credential-shaped string, or when the self plugin has no valid `trust.json`.

package/bin/passioncode.js

@@ -0,0 +1,65 @@
+#!/usr/bin/env node
+'use strict';
+const L = require('../lib/launcher');
+
+const HELP = `passioncode — every PassionCode.ai skill, for every agent on this machine
+
+  npx @passioncode-ai/passioncode@latest update [--dry-run] [--json]   install or update the whole set
+  npx passioncode status [--json]                       what is installed where
+  npx passioncode restore                               put back what the last update moved aside
+  npx passioncode config set update.auto on|off         background updates at session start
+  npx passioncode uninstall                             remove the set (quarantined items stay restorable)
+
+Claude Code gets plugins from the local "passioncode" marketplace; other agents get
+the same skills through ~/.agents/skills. Restart your agent after an update.`;
+
+function main(argv) {
+  const [cmd = 'help', ...rest] = argv;
+  const json = rest.includes('--json');
+  const quiet = rest.includes('--quiet');
+  const out = (value, text) => process.stdout.write(json ? JSON.stringify(value, null, 2) + '\n' : text + '\n');
+  try {
+    if (cmd === 'update' || cmd === 'install') {
+      const r = L.update({ dryRun: rest.includes('--dry-run') });
+      const failed = r.steps.filter((s) => s.outcome === 'failed');
+      if (!quiet || failed.length) {
+        out(r, [
+          ...r.steps.map((s) => `${s.outcome.padEnd(8)} ${s.kind.padEnd(11)} ${s.detail}${s.error ? `\n         ${s.error}` : ''}`),
+          '',
+          failed.length ? `${failed.length} step(s) failed — the rest were applied. Re-run after fixing, or \`passioncode restore\`.` : rest.includes('--dry-run') ? `Plan for PassionCode.ai ${r.version}: nothing was changed.` : `PassionCode.ai ${r.version}: done. Restart your agent — skills load at session start.`,
+          r.moved.length ? `${r.moved.length} item(s) moved aside, restorable with \`passioncode restore\`.` : '',
+        ].filter(Boolean).join('\n'));
+      }
+      return failed.length ? 1 : 0;
+    }
+    if (cmd === 'status') {
+      const s = L.status();
+      out(s, [
+        `installed ${s.installed || 'nothing'} · package ${s.package || '?'} · latest on npm ${s.latest || 'not checked'}${s.auto ? ' · auto-update on' : ' · auto-update off'}`,
+        ...s.members.map((m) => `${m.name.padEnd(22)} ${String(m.version).padEnd(8)} claude: ${m.claude}${m.legacy.length ? ` (+ legacy ${m.legacy.join(', ')})` : ''}${m.legacyMarketplaces.length ? ` (+ legacy marketplace ${m.legacyMarketplaces.join(', ')})` : ''} · hub: ${m.hub.filter((h) => h.ok).length}/${m.hub.length}${m.shadows.length ? ` · SHADOW: ${m.shadows.join(', ')}` : ''}`),
+      ].join('\n'));
+      return 0;
+    }
+    if (cmd === 'restore') {
+      const r = L.restore();
+      out(r, r.length ? `Restored:\n  ${r.join('\n  ')}` : 'Nothing to restore.');
+      return 0;
+    }
+    if (cmd === 'config' && rest[0] === 'set') {
+      out(L.setConfig({ key: rest[1], value: rest[2] }), `update.auto = ${rest[2]}`);
+      return 0;
+    }
+    if (cmd === 'uninstall') {
+      const r = L.uninstall();
+      out(r, r.length ? `Removed:\n  ${r.join('\n  ')}` : 'Nothing was installed.');
+      return 0;
+    }
+    process.stdout.write(HELP + '\n');
+    return cmd === 'help' || cmd === '--help' || cmd === '-h' ? 0 : 2;
+  } catch (error) {
+    process.stderr.write(`passioncode: ${error.message}\n`);
+    return 1;
+  }
+}
+
+process.exit(main(process.argv.slice(2)));

package/family.json

@@ -0,0 +1,45 @@
+{
+  "name": "passioncode",
+  "owner": "passioncode-ai",
+  "displayName": "PassionCode.ai",
+  "description": "Every PassionCode.ai agent skill, for Claude Code and every other agent on the machine, updated as one set.",
+  "members": [
+    {
+      "name": "fabric-agent-adapter",
+      "displayName": "Fabric Agent Adapter",
+      "repo": "passioncode-ai/fabric-agent-adapter",
+      "checkout": "~/DATA/fabric-agent-adapter",
+      "ref": "v0.4.2",
+      "kind": "plugin",
+      "path": "plugins/fabric-agent-adapter",
+      "legacyPluginIds": [
+        "fabric-agent-adapter@fabric-agent-adapter"
+      ],
+      "legacyMarketplaces": [
+        "fabric-agent-adapter"
+      ]
+    },
+    {
+      "name": "observatory-log",
+      "displayName": "Observatory Log",
+      "repo": "passioncode-ai/project-observatory-dashboard",
+      "checkout": "~/DATA/project-observatory-open-source",
+      "ref": "v0.8.1",
+      "kind": "plugin",
+      "path": "observatory/engine/skill/plugins/observatory-log",
+      "legacyPluginIds": [
+        "observatory-log@observatory-log"
+      ],
+      "legacyMarketplaces": [
+        "observatory-log"
+      ]
+    },
+    {
+      "name": "passioncode",
+      "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."
+    }
+  ]
+}