@passioncode-ai/passioncode 0.2.59 → 0.2.60

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## 0.2.60 - 2026-11-03
+
+### Fixed
+
+- The `setting-up-passioncode` skill states setup's exit codes: a step or a check that failed exits 1,
+  and a plan (`--dry-run`, or a run without a terminal and without `--yes` that would change something;
+  a `--json` run never asks) exits 0 even when a check fails, so an agent reads `after.summary` and `plan`; exit 1 with no
+  JSON is a runtime error (PC-102). The README says a `--json` run never asks, names the repairs
+  question beside the one per app, and says a terminal run with nothing to ask saves a train at once. `doctor --dry-run` is refused with exit 2 before any check, now under test.
+
 ## 0.2.59 - 2026-11-03
 
 ### Changed

package/README.md

@@ -44,7 +44,7 @@ secret into a product's own hidden prompt, starting Docker for Fabric, and resta
 
 1. **Install** (Node 18 or newer; the Claude Code CLI on `PATH` for the plugins):
    `npx @passioncode-ai/passioncode@latest setup`, then restart your agents. In a terminal it asks
-   one question per app; `--yes` accepts the plan, `--with`/`--without <ids>` choose apps
+   one question per app and one for the repairs (a `--json` run never asks); `--yes` accepts the plan, `--with`/`--without <ids>` choose apps
    (`switchboard`, `dashboards`, `observatory`, `inbox`, `fabric`), `--no-apps` sets up the skills
    and MCP only, `--dry-run` shows the plan. Apps are installed on macOS; on other systems setup
    names each download page, and on Windows `doctor` reads which version of each app is installed. Skills only: `npx @passioncode-ai/passioncode@latest update`.
@@ -118,7 +118,7 @@ the versions in [`trains/organization-r1.json`](trains/organization-r1.json), re
 and `doctor` then compares every app with its pin (offline too) in an `app.<id>` line per app and
 one `train` line. An app newer than its pin is reported and left alone (a damaged one, or one whose version cannot be read, is reinstalled from the latest
 release): the train never takes an app back, because its data may not open in an older release. `setup --train none` returns to the
-latest releases. Either change is saved with `--yes` or in a terminal; without both it is only shown as a plan. A named
+latest releases. Either change is saved with `--yes` or in a terminal (after its answers, or at once when there is nothing to ask; a `--json` run never asks); without either it is only shown as a plan. A named
 train is not saved when every offer in the terminal (at least one of them defaulting to yes) is
 answered no, while `--train none` is saved on any answer. The skills are pinned by the launcher release itself (`family.json`). Which
 version each app pins is the train's record in fabric-workspace

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@passioncode-ai/passioncode",
-  "version": "0.2.59",
+  "version": "0.2.60",
   "description": "Set up PassionCode.ai on a computer with one command: the apps from their verified releases, their MCP servers for every coding agent and the PassionCode.ai skills. Check and repair it with the same command or `doctor`.",
   "bin": {
     "passioncode": "bin/passioncode.js"

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

@@ -35,7 +35,7 @@
       "name": "passioncode",
       "displayName": "PassionCode.ai",
       "source": "./plugins/passioncode",
-      "version": "0.2.59",
+      "version": "0.2.60",
       "description": "Set up and check PassionCode.ai on a computer with one command (setting-up-passioncode), 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,6 +1,6 @@
 {
   "family": "passioncode",
-  "version": "0.2.59",
+  "version": "0.2.60",
   "release": true,
   "members": [
     {
@@ -62,9 +62,9 @@
       "name": "passioncode",
       "displayName": "PassionCode.ai",
       "repo": "passioncode-ai/passioncode",
-      "ref": "v0.2.59",
+      "ref": "v0.2.60",
       "commit": null,
-      "version": "0.2.59",
+      "version": "0.2.60",
       "via": "this repository",
       "skills": [
         "setting-up-passioncode",
@@ -72,7 +72,7 @@
       ],
       "legacyPluginIds": [],
       "legacyMarketplaces": [],
-      "contentHash": "sha256:bba0f14b5775c1b003c996f9fad9d33c17f914c6e2e9d119e0b25d979365e01b",
+      "contentHash": "sha256:0b01afb4625a683f52d803769cca28ebedcd9d854f07f055a1afa2b88977c2ee",
       "description": "Set up and check PassionCode.ai on a computer with one command (setting-up-passioncode), 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/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.2.59",
+  "version": "0.2.60",
   "description": "Set up and check PassionCode.ai on a computer with one command (setting-up-passioncode), 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/skills/setting-up-passioncode/SKILL.md

@@ -32,6 +32,11 @@ npx --yes @passioncode-ai/passioncode@latest setup --yes --json
   repairs what is wrong (skills, MCP registrations, an outdated or damaged app that is not
   running, a stopped service its supervisor owns), checks again and returns JSON.
 - A healthy machine: an empty `actions` list, exit 0. Running it again is always safe.
+- Exit 0: no step and no check failed; 1: a step or a check failed; 2: bad arguments. A plan
+  (`planOnly: true`: `--dry-run`, or a run without `--yes` that would change something, since a
+  `--json` run never asks) changes nothing and exits 0 even when a check fails: read
+  `after.summary` and `plan`, not the exit code alone. Exit 1 with no JSON on stdout is a runtime
+  error: report its stderr line and the exit code.
 - Use `--with <ids>` / `--without <ids>` for a subset (`switchboard`, `dashboards`,
   `observatory`, `inbox`, `fabric`), `--no-apps` for skills and MCP only, `--dry-run` to show
   the plan first. Fabric is an early preview and needs Docker (or OrbStack) and the Supabase CLI;