@passioncode-ai/passioncode 0.1.26 → 0.1.28

package/CHANGELOG.md

@@ -1,5 +1,49 @@
 # Changelog
 
+## 0.1.28 - 2026-10-05
+
+The launcher meets the organization's
+[product lifecycle contract](https://github.com/passioncode-ai/fabric-workspace/blob/main/knowledge/lifecycle.md):
+findings F13, F14, F15 and F17 of the 2026-10-03 lifecycle audit. Observatory Log moves to
+Project Observatory 0.16.0.
+
+### Changed
+
+- **Observatory Log is pinned at `v0.16.0`** (plugin 0.16.0; it was `v0.15.0`, plugin 0.15.0),
+  the Project Observatory 0.16.0 skills. The skills' text is unchanged and follows the release:
+  agent memory now checks an access binding on every call, embeds remotely only with the
+  operator's per-project consent, and can be erased with a receipt (`full forget`).
+
+### Fixed
+
+- **One update at a time (LC-03, F14).** `update`, `restore` and `uninstall` take
+  `~/.passioncode/update.lock`; a second one refuses with exit 1 and names the holder, so a
+  background update and a manual one no longer interleave their `claude plugin` writes.
+- **One `npm view` for sessions started together (F13).** The SessionStart hook claims
+  `~/.passioncode/probe.pending` before it starts the probe; the probe removes it after recording,
+  and a marker older than five minutes is taken over.
+- **Releases no longer accumulate (LC-11, LC-15, F15).** An update keeps the release it installed
+  and the one it replaced, and removes older releases and partial copies left by a killed update
+  (`prune` step; a dry run plans it).
+- **A release proves its provenance (F17).** `vendor --release` refuses a member whose tag does not
+  name the plugin version it carries. A member whose repository's tags version another product
+  may declare `refVersions: "repository"` with the plugin `version` it expects; the bytes at that
+  tag must carry that version, and the manifest records `refVersions` so the pair reads as the
+  repository's release, not the plugin's. No member declares it yet: at the current pins every tag
+  names its plugin version (Observatory Log `v0.16.0` carries 0.16.0), and whether Observatory Log
+  should use it when the two diverge again is the open operator decision PC-04.
+- `AGENTS.md` gains a `## Lifecycle` section: the background footprint with the SessionStart
+  hook's cost and cadence (LC-09) and build retention (LC-15).
+
+## 0.1.27 - 2026-10-04
+
+### Changed
+
+- **Fabric Agent Adapter is pinned at `v0.6.3`** (it was `v0.6.2`). `building-fabric-services`
+  and `creating-fabric-agents` say that every credential an agent or service uses comes from
+  Project Observatory, by name: `use_secret.py run --vault-only` for an agent, `use_secret.py
+  serve` for a long-running service, never a `.env` or a key file beside it.
+
 ## 0.1.26 - 2026-10-04
 
 ### Changed

package/README.md

@@ -53,7 +53,8 @@ out of it, even when they implement Fabric protocols.
 - Updates create no skill copies in `~/.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-ai/passioncode@latest restore` puts them back.
-- Each version is an immutable release under `~/.passioncode/releases/<version>`.
+- Each version is an immutable release under `~/.passioncode/releases/<version>`; an update
+  keeps the release it replaced for rollback and removes older ones.
 
 ## Staying current
 

package/SECURITY.md

@@ -16,7 +16,9 @@ deleted: a recovery record is written before the move in
 `~/.passioncode/quarantine/<run>/moved.json`. `restore` processes the latest batch,
 checkpoints completed entries and refuses to overwrite a conflicting user replacement.
 `uninstall` removes owned links/plugins, clears the active release and disables
-automatic updates; it retains release copies and recovery records. A failed removal
+automatic updates; it retains the current and previous release copies and recovery
+records. Each update removes the launcher's own older releases (its output, reinstallable
+from npm) and keeps the one it replaced for rollback. A failed removal
 returns a nonzero exit code. See the [CLI recovery contract](docs/reference/cli.md).
 
 ## The self-update and who it trusts

package/family.json

@@ -8,7 +8,7 @@
       "name": "fabric-agent-adapter",
       "displayName": "Fabric Agent Adapter",
       "repo": "passioncode-ai/fabric-agent-adapter",
-      "ref": "v0.6.2",
+      "ref": "v0.6.3",
       "kind": "plugin",
       "path": "plugins/fabric-agent-adapter",
       "legacyPluginIds": [
@@ -22,7 +22,7 @@
       "name": "observatory-log",
       "displayName": "Observatory Log",
       "repo": "passioncode-ai/project-observatory-dashboard",
-      "ref": "v0.15.0",
+      "ref": "v0.16.0",
       "kind": "plugin",
       "path": "observatory/engine/skill/plugins/observatory-log",
       "legacyPluginIds": [

package/lib/launcher.js

@@ -67,6 +67,94 @@ function symlinkAtomic(target, at) {
   fs.renameSync(tmp, at);
 }
 
+// --- one update at a time (lifecycle contract LC-03) ---------------------------------------
+// update, restore and uninstall all write installed_plugins.json, the hub and state.json. A
+// background update (started by the session hook) and a manual one used to interleave their
+// `claude plugin` writes. They now take one lock; the second refuses and names the holder.
+const O_EXLOCK = 0x20; // BSD/macOS open(2) flag: take flock(LOCK_EX); absent from fs.constants
+
+class UpdateRunning extends Error {
+  constructor(pid, file) {
+    super(`Another PassionCode update is already running (${pid ? `process ${pid}` : 'another process'} holds ${file}); let it finish, then retry.`);
+    this.pid = pid;
+  }
+}
+
+function readPid(file) {
+  try { const text = fs.readFileSync(file, 'utf8').trim(); return /^\d{1,10}$/.test(text) ? Number(text) : null; } catch (_) { return null; }
+}
+
+function alive(pid) {
+  try { process.kill(pid, 0); return true; } catch (error) { return error.code === 'EPERM'; }
+}
+
+/**
+ * Take ~/.passioncode/update.lock. On macOS it is a kernel flock (released when the holder dies,
+ * so it is never stale); elsewhere an exclusively created pid file whose holder must be alive.
+ * Returns `{ release() }`; throws UpdateRunning when another process holds it.
+ */
+function acquireUpdateLock(p) {
+  fs.mkdirSync(p.state, { recursive: true });
+  const file = path.join(p.state, 'update.lock');
+  if (process.platform === 'darwin') {
+    let fd;
+    try {
+      fd = fs.openSync(file, fs.constants.O_RDWR | fs.constants.O_CREAT | O_EXLOCK | fs.constants.O_NONBLOCK, 0o600);
+    } catch (error) {
+      if (error.code === 'EAGAIN' || error.code === 'EWOULDBLOCK') throw new UpdateRunning(readPid(file), file);
+      throw error;
+    }
+    fs.ftruncateSync(fd, 0);
+    fs.writeSync(fd, String(process.pid));
+    return { release() { if (fd !== null) { fs.closeSync(fd); fd = null; } } };
+  }
+  for (let attempt = 0; attempt < 2; attempt += 1) {
+    try {
+      fs.writeFileSync(file, String(process.pid), { flag: 'wx', mode: 0o600 });
+      return { release() { if (readPid(file) === process.pid) fs.rmSync(file, { force: true }); } };
+    } catch (error) {
+      if (error.code !== 'EEXIST') throw error;
+      const pid = readPid(file);
+      if (pid && pid !== process.pid && alive(pid)) throw new UpdateRunning(pid, file);
+      // The holder is gone: move its file aside atomically, so two takers cannot both steal it.
+      try { fs.renameSync(file, `${file}.stale.${process.pid}`); fs.rmSync(`${file}.stale.${process.pid}`, { force: true }); } catch (_) { /* another taker moved it */ }
+    }
+  }
+  throw new UpdateRunning(readPid(file), file);
+}
+
+function withUpdateLock(home, fn) {
+  const lock = acquireUpdateLock(paths(home));
+  try { return fn(); } finally { lock.release(); }
+}
+
+// --- release retention (LC-11, LC-15) -----------------------------------------------------------
+const semver = (v) => v.split('.').map(Number);
+function newerVersion(a, b) {
+  const pa = semver(a), pb = semver(b);
+  for (let i = 0; i < 3; i += 1) if (pa[i] !== pb[i]) return pa[i] > pb[i];
+  return false;
+}
+
+/**
+ * The release directories an update may remove: every one except the release it installed and
+ * the one it replaced (the rollback; the newest other release when it replaced none), plus any
+ * `*.partial` copy a killed update left behind (safe: the caller holds the update lock).
+ * Files, symlinks and anything not named like a release are never touched.
+ */
+function staleReleases(p, version, previous) {
+  let entries;
+  try { entries = fs.readdirSync(p.releases, { withFileTypes: true }); } catch (_) { return []; }
+  const dirs = entries.filter((e) => e.isDirectory() && !e.isSymbolicLink()).map((e) => e.name);
+  const partial = dirs.filter((n) => /^\d+\.\d+\.\d+\.\d+\.partial$/.test(n));
+  const versions = dirs.filter((n) => /^\d+\.\d+\.\d+$/.test(n));
+  let keep = previous && versions.includes(previous) && previous !== version ? previous : null;
+  if (!keep) {
+    for (const v of versions) if (v !== version && (!keep || newerVersion(v, keep))) keep = v;
+  }
+  return [...versions.filter((v) => v !== version && v !== keep), ...partial].map((n) => path.join(p.releases, n));
+}
+
 /** Claude Code's plugin CLI, overridable for tests. */
 function claudeRunner() {
   const bin = process.env.PASSIONCODE_CLAUDE || 'claude';
@@ -303,6 +391,16 @@ function update({ home, dryRun = false, claude = claudeRunner(), log = () => {}
     }
   }
 
+  // 5. The launcher's own releases: keep this one and the one it replaced, remove the rest.
+  //    They are its own output, reinstallable from npm — not the person's files, which are
+  //    only ever moved to the quarantine.
+  const stale = staleReleases(p, version, state.installed || null);
+  if (stale.length) {
+    step('prune', `remove ${stale.map((d) => path.basename(d)).join(', ')} from ${p.releases}; keep ${version} and the release before it`, () => {
+      for (const dir of stale) fs.rmSync(dir, { recursive: true, force: true });
+    });
+  }
+
   if (!dryRun) {
     if (moved.length) writeJson(path.join(quarantineDir, 'moved.json'), moved);
     // A probe or config command may have written while the plugin CLI ran.
@@ -472,4 +570,15 @@ function uninstall({ home, claude = claudeRunner() } = {}) {
   return removed;
 }
 
-module.exports = { update, restore, status, setConfig, uninstall, paths, CHANNELS, MARKETPLACE, payloadManifest, marketplaceAddArg };
+module.exports = {
+  // An invalid payload is refused before the lock creates anything under ~/.passioncode.
+  update: (opts = {}) => {
+    if (opts.dryRun) return update(opts);
+    verifyPayload(PAYLOAD(), payloadManifest());
+    return withUpdateLock(opts.home, () => update(opts));
+  },
+  restore: (opts = {}) => withUpdateLock(opts.home, () => restore(opts)),
+  uninstall: (opts = {}) => withUpdateLock(opts.home, () => uninstall(opts)),
+  status, setConfig, paths, CHANNELS, MARKETPLACE, payloadManifest, marketplaceAddArg,
+  acquireUpdateLock, UpdateRunning, staleReleases,
+};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@passioncode-ai/passioncode",
-  "version": "0.1.26",
+  "version": "0.1.28",
   "description": "The PassionCode.ai agent skill set \u2014 Fabric Agent Adapter, Observatory Log and the organisation's working rules \u2014 for Claude Code and every other agent on the machine, updated as one set.",
   "bin": {
     "passioncode": "bin/passioncode.js"

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

@@ -11,7 +11,7 @@
       "name": "fabric-agent-adapter",
       "displayName": "Fabric Agent Adapter",
       "source": "./plugins/fabric-agent-adapter",
-      "version": "0.6.2",
+      "version": "0.6.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",
@@ -23,7 +23,7 @@
       "name": "observatory-log",
       "displayName": "Observatory Log",
       "source": "./plugins/observatory-log",
-      "version": "0.15.0",
+      "version": "0.16.0",
       "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": "PassionCode.ai",
@@ -35,7 +35,7 @@
       "name": "passioncode",
       "displayName": "PassionCode.ai",
       "source": "./plugins/passioncode",
-      "version": "0.1.26",
+      "version": "0.1.28",
       "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",

package/payload/manifest.json

@@ -1,15 +1,15 @@
 {
   "family": "passioncode",
-  "version": "0.1.26",
+  "version": "0.1.28",
   "release": true,
   "members": [
     {
       "name": "fabric-agent-adapter",
       "displayName": "Fabric Agent Adapter",
       "repo": "passioncode-ai/fabric-agent-adapter",
-      "ref": "v0.6.2",
-      "commit": "4b435baac85e343b530af86d56f8b75ac406bc43",
-      "version": "0.6.2",
+      "ref": "v0.6.3",
+      "commit": "30a1148ba77fe9ed56ea98c218d10ccf2fadf084",
+      "version": "0.6.3",
       "via": "clone of https://***@github.com/passioncode-ai/fabric-agent-adapter.git",
       "skills": [
         "adapting-projects-to-fabric",
@@ -22,7 +22,7 @@
       "legacyMarketplaces": [
         "fabric-agent-adapter"
       ],
-      "contentHash": "sha256:95fab0fdf3ee1f9171fc7c07edd60313cf52ddb68bb2eb456caf1df8afde36cb",
+      "contentHash": "sha256:264191fab8632a4f720185c68f79ca74c8fba1a14e50fd2d68957a35303c9c4b",
       "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",
@@ -34,9 +34,9 @@
       "name": "observatory-log",
       "displayName": "Observatory Log",
       "repo": "passioncode-ai/project-observatory-dashboard",
-      "ref": "v0.15.0",
-      "commit": "acca5c9d293a388cd53d3a2cbdbfabf574308bb4",
-      "version": "0.15.0",
+      "ref": "v0.16.0",
+      "commit": "aa6788d51e248de54c3f7184b17206af43e0b28e",
+      "version": "0.16.0",
       "via": "clone of https://***@github.com/passioncode-ai/project-observatory-dashboard.git",
       "skills": [
         "explaining-changes",
@@ -49,7 +49,7 @@
       "legacyMarketplaces": [
         "observatory-log"
       ],
-      "contentHash": "sha256:523f50d6be43845f0ed2b5d497bac17752cbfd3333627a235ab457618cd86dd3",
+      "contentHash": "sha256:f0bfd0f79ee99d25e6c82ad5f84337de2ce09f406fb4f5036cb45e3aa20d490a",
       "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": "PassionCode.ai",
@@ -61,16 +61,16 @@
       "name": "passioncode",
       "displayName": "PassionCode.ai",
       "repo": "passioncode-ai/passioncode",
-      "ref": "v0.1.26",
+      "ref": "v0.1.28",
       "commit": null,
-      "version": "0.1.26",
+      "version": "0.1.28",
       "via": "this repository",
       "skills": [
         "working-in-passioncode"
       ],
       "legacyPluginIds": [],
       "legacyMarketplaces": [],
-      "contentHash": "sha256:01035ebeb36b330a3eabad618a5dbd6f8b826b0d008ffc3651db1c9dca932deb",
+      "contentHash": "sha256:c071f7a058bd6a8b8135ca7dd498f0b72ecd31cff1086ebbd3567611d66dbc98",
       "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",

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

@@ -3,7 +3,7 @@
   "name": "fabric-agent-adapter",
   "displayName": "Fabric Agent Adapter",
   "description": "Create new Fabric-compatible agents, build them as always-alive local services with dashboards (fabric-service/0.1), and adapt existing projects to the Fabric Agent Contract through evidence-backed MCP, A2A, or local-runner provider bundles.",
-  "version": "0.6.2",
+  "version": "0.6.3",
   "author": {
     "name": "PassionCode.ai",
     "url": "https://passioncode.ai/"

package/payload/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.6.2"
+  version: "0.6.3"
   contract-version: "0.1.0"
   contract-commit: "2ce392291c6668598d12cd38327e24696b5ca15c"
 ---

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

@@ -15,7 +15,7 @@ license: AGPL-3.0-only OR LicenseRef-PassionCode-Commercial
 compatibility: Python 3.9+ or Node.js 20+ for the kits; the probe needs Python 3.9+. launchd steps are macOS-only (Linux services use lifecycle manager none until a systemd adapter exists). Dashboard handoff optionally uses Fabric Dashboards MCP link/host_status/open; without it, report unresolved host capability. The contract checkout is optional.
 metadata:
   author: PassionCode.ai
-  version: "0.6.2"
+  version: "0.6.3"
   contract-version: "0.1.0"
   extension: "fabric-service/0.1"
   extension-commit: "2ce392291c6668598d12cd38327e24696b5ca15c"
@@ -101,8 +101,12 @@ are in [`scripts/fabric_interop.py`](scripts/fabric_interop.py) and
    digest and the process start time. *(A service ran on stale code after an edit and
    burned budget; nothing showed which build was answering.)*
 5. **State outside code.** Data and config in `~/Library/Application Support/<id>/`,
-   logs in `~/Library/Logs/<id>/`, cache in `~/Library/Caches/<id>/`; secrets in a 0600
-   file. Never inside the service's own code checkout or a release directory; a
+   logs in `~/Library/Logs/<id>/`, cache in `~/Library/Caches/<id>/`; the service's own
+   access token in a 0600 file it generates (principle 6). **Every provider credential the
+   service uses comes from Project Observatory, by name** — the plist starts the service
+   with `use_secret.py serve --consumer <label> <project> <NAME>[,<NAME>] -- <command>`, which
+   reads the vault only and records the consumer so a rotation names it; never a copy of a
+   key in a `.env`, a config file or the plist. Never inside the service's own code checkout or a release directory; a
    repository that versions the data itself is a store and is fine — declare
    `source.repository` so the probe can tell them apart. *(Deleting a checkout left a
    plist launchd retried every 10 s, and the data went with it.)*
@@ -254,7 +258,10 @@ things change and the kits implement each:
    example is [`scripts/sample-remote-service.mjs`](scripts/sample-remote-service.mjs): it runs
    with its own TLS or behind a platform router.
 2. **Secrets live on the platform:** the service token and the session key (32 bytes) are
-   platform secrets, never in the repository, a URL or an argument vector.
+   platform secrets, never in the repository, a URL or an argument vector. A provider key the
+   remote service needs is issued and kept in Project Observatory, pushed to the platform, and
+   the movement recorded with `vault.py moved --at <provider>`, so the platform's copy is
+   known rather than invisible.
 3. **Register it on the operator's computer** — the installer side, run there:
    `registerRemote({ id, name, origin, token })` / `register_remote(...)` writes the token file
    (0600) and the descriptor; pass the token from a file or stdin, never in argv. Public names

package/payload/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.6.2"
+  version: "0.6.3"
   contract-version: "0.1.0"
   contract-commit: "2ce392291c6668598d12cd38327e24696b5ca15c"
 ---
@@ -94,6 +94,13 @@ first commit:
 - an `AGENTS.md` that opens with the template's *Read first* block and closes with *After work*,
   and a `CLAUDE.md` whose first line is `@AGENTS.md`.
 
+**Every credential the agent uses comes from Project Observatory, by name**, from its first
+commit: the README's Configure section lists key NAMES; the agent finds them with
+`observatory_credentials` and runs with `use_secret.py run --vault-only` (a long-running
+service: `use_secret.py serve`), with `OBSERVATORY_VAULT_ONLY=1` in its environment. No `.env`
+of its own, no key file beside its data, no value in code, configuration or a commit. A
+workflow names the keys it needs in its checkpoint (`credentials`), never their values.
+
 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

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

@@ -3,7 +3,7 @@
   "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.15.0",
+  "version": "0.16.0",
   "license": "AGPL-3.0-only OR LicenseRef-PassionCode-Commercial",
   "author": {
     "name": "PassionCode.ai",

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

@@ -15,7 +15,7 @@ description: >-
   decision with different evidence.
 license: AGPL-3.0-only OR LicenseRef-PassionCode-Commercial
 metadata:
-  version: "0.15.0"
+  version: "0.16.0"
 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

@@ -10,7 +10,7 @@ description: >-
   provider permissions or choosing a project's authentication architecture.
 license: AGPL-3.0-only OR LicenseRef-PassionCode-Commercial
 metadata:
-  version: "0.15.0"
+  version: "0.16.0"
 compatibility: >-
   Requires an initialized full Project Observatory installation, Python 3.11+
   and local shell access on macOS or Linux. Provider operations additionally
@@ -30,7 +30,7 @@ names. Never ask the user to paste a credential into the conversation.
 2. Select the user's initialized `OBSERVATORY_HOME`. Run
    `project-observatory full doctor`. A missing workspace
    needs the documented onboarding before secret operations.
-3. Run `"$OBSERVATORY_PYTHON" "$OBSERVATORY_ROOT/tools/skill_check.py" handling-secrets 0.15.0`
+3. Run `"$OBSERVATORY_PYTHON" "$OBSERVATORY_ROOT/tools/skill_check.py" handling-secrets 0.16.0`
    (`full agent install` records that interpreter; the stock macOS `python3` is too old).
    If stale, read the installed skill once and follow its compatible commands.
    Do not turn an unavailable version check into a retry loop.

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

@@ -15,7 +15,7 @@ description: >-
   the repository.
 license: AGPL-3.0-only OR LicenseRef-PassionCode-Commercial
 metadata:
-  version: "0.15.0"
+  version: "0.16.0"
 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,7 +2,7 @@
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "passioncode",
   "displayName": "PassionCode.ai",
-  "version": "0.1.26",
+  "version": "0.1.28",
   "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",

package/payload/plugins/passioncode/hooks/probe.js

@@ -6,11 +6,15 @@ const { execFile } = require('child_process');
 const fs = require('fs');
 const os = require('os');
 const path = require('path');
-const { PACKAGE, parseView, recordProbe } = require('./update-check');
+const { PACKAGE, parseView, recordProbe, releaseProbe } = require('./update-check');
 
 const DIR = process.env.PASSIONCODE_HOME || path.join(os.homedir(), '.passioncode');
 const STATE = path.join(DIR, 'state.json');
 execFile('npm', ['view', PACKAGE, 'version', 'maintainers', '_npmUser', '--json'], { timeout: 30000 }, (error, stdout) => {
+  try { record(error, stdout); } finally { releaseProbe(DIR); } // the hook claimed probe.pending before it started us
+});
+
+function record(error, stdout) {
   let state = {};
   try { state = JSON.parse(fs.readFileSync(STATE, 'utf8')); } catch (_) { /* first run */ }
   const result = parseView(stdout, error);
@@ -20,4 +24,4 @@ execFile('npm', ['view', PACKAGE, 'version', 'maintainers', '_npmUser', '--json'
   fs.writeFileSync(tmp, JSON.stringify(next, null, 2));
   fs.renameSync(tmp, STATE);
   process.stdout.write(`${next.checkedAt} ${result.checkError ? `check failed: ${result.checkError}` : result.published ? `latest ${result.latest} by ${result.maintainers.join(', ') || '(unreadable maintainers)'}` : `${PACKAGE} is not published`}\n`);
-});
+}

package/payload/plugins/passioncode/hooks/session-start.js

@@ -9,7 +9,7 @@ const { spawn } = require('child_process');
 const fs = require('fs');
 const os = require('os');
 const path = require('path');
-const { decide, loadTrust } = require('./update-check');
+const { decide, loadTrust, claimProbe, releaseProbe } = require('./update-check');
 const { rulesLine } = require('./repo-rules');
 
 const DIR = process.env.PASSIONCODE_HOME || path.join(os.homedir(), '.passioncode');
@@ -38,8 +38,9 @@ async function main() {
   const state = read(STATE, {});
   const now = Date.now();
   const age = now - Date.parse(state.checkedAt);
-  if (!Number.isFinite(age) || age < 0 || age > DAY) {
-    await detached(process.execPath, [path.join(__dirname, 'probe.js')], 'probe.log');
+  // The marker is claimed before the spawn: sessions restored together start one probe.
+  if ((!Number.isFinite(age) || age < 0 || age > DAY) && claimProbe(DIR, now)) {
+    if (!await detached(process.execPath, [path.join(__dirname, 'probe.js')], 'probe.log')) releaseProbe(DIR);
   }
   const { lines, spawn: args, stateChanges } = decide(state, loadTrust(), now);
   if (Object.keys(stateChanges).length) {

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

@@ -102,6 +102,38 @@ function newer(a, b) {
   return false;
 }
 
+/**
+ * One probe at a time. The probe writes `checkedAt` only when npm answers (up to 30 s), so every
+ * session that starts meanwhile saw a stale check and started its own `npm view`. The hook now
+ * claims `probe.pending` with an exclusive create BEFORE it spawns; the probe removes it after it
+ * has recorded. A marker older than PROBE_STALE_MS (or dated in the future) belongs to a probe
+ * that died: it is moved aside atomically — so two hooks cannot both take it over — and claimed.
+ */
+const PROBE_MARKER = 'probe.pending';
+const PROBE_STALE_MS = 5 * 60 * 1000;
+
+function claimProbe(dir, now = Date.now()) {
+  const file = path.join(dir, PROBE_MARKER);
+  const create = () => { fs.writeFileSync(file, new Date(now).toISOString(), { flag: 'wx', mode: 0o600 }); return true; };
+  try {
+    fs.mkdirSync(dir, { recursive: true });
+    return create();
+  } catch (error) {
+    if (error.code !== 'EEXIST') return false;
+  }
+  let age;
+  try { age = now - fs.statSync(file).mtimeMs; } catch (_) { return false; } // just released: the next session checks
+  if (age >= 0 && age < PROBE_STALE_MS) return false;
+  const aside = `${file}.stale.${process.pid}`;
+  try { fs.renameSync(file, aside); } catch (_) { return false; } // another hook took it over
+  fs.rmSync(aside, { force: true });
+  try { return create(); } catch (_) { return false; }
+}
+
+function releaseProbe(dir) {
+  fs.rmSync(path.join(dir, PROBE_MARKER), { force: true });
+}
+
 function oneLine(text) { return String(text).replace(/\s+/g, ' ').trim().slice(0, 200); }
 
 /**
@@ -144,4 +176,4 @@ function decide(state, trust, now = Date.now()) {
   return { lines, spawn, stateChanges };
 }
 
-module.exports = { PACKAGE, OIDC_PUBLISHER, TRUST_FILE, accountName, parseView, recordProbe, loadTrust, newer, decide };
+module.exports = { PACKAGE, OIDC_PUBLISHER, TRUST_FILE, PROBE_MARKER, PROBE_STALE_MS, accountName, parseView, recordProbe, loadTrust, newer, decide, claimProbe, releaseProbe };