0.2.66: Fabric Agent Adapter v0.60.0 (PC-109)

CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## 0.2.66 - 2026-11-03
+
+### Changed
+
+- **Fabric Agent Adapter is pinned at `v0.60.0`** (it was `v0.59.0`): a board responder finds a slot the operator moves
+  back to it, once Fabric offers that move, and claims it without a take-back; `pack`, `sign` and `verify` say why a
+  provider manifest is refused; working-with-fabric reads a filed row's answer and says when an accepted request is
+  left behind by a move; Python's package kit refuses `NaN` and `Infinity` as the Node kit does (PC-109).
+
 ## 0.2.65 - 2026-11-03
 
 ### Fixed

docs/backlog.md

@@ -114,3 +114,4 @@ derives its common backlog from [backlog-sources.json](backlog-sources.json).
 | PC-106 | Release 0.2.63: Fabric Agent Adapter `v0.59.0` (FAA-191, portable from day 0) | done 2026-11-03: PR [#216](https://github.com/passioncode-ai/passioncode/pull/216) (`d64a385`), `npm test` 203 pass, tag `v0.2.63`, release run 41596699909 green (validate on Node and Windows, release, publish), npm `@passioncode-ai/passioncode@0.2.63`; `update` installed it here and the plugin cache's `fabric-agent-adapter/0.59.0/skills` equals the adapter tag's (`diff -rq` empty, 174 files) | [adapter CHANGELOG 0.59.0](https://github.com/passioncode-ai/fabric-agent-adapter/blob/v0.59.0/CHANGELOG.md) |
 | PC-107 | Copy risks left from the PC-105 product reading on `0c8436f` (none false): the plan's train lines ("The release train (<name>) was not saved: run it with --yes, or answer in a terminal." and "The saved release train was not forgotten: ...") advise `--yes` or a terminal also after a `--dry-run`, where both still only plan, and in a no-terminal plan with installs they stand next to the plan footer's own "Run it with --yes"; on a machine whose only open checks are warnings (an app ahead of its train pin, an MCP server not yet onboarded) the headline now says "The checks below still stand." while the closing line says "No problems." (it counts FAILs), and that closing line has no strings.md row. Decide both through copywriting and Copylot: for a `--dry-run` say "run it without --dry-run", drop the train sentence's advice when the footer follows, and name warnings in the closing line or register it as it is. From the PC-105 seam reading round 2 on `638162e`: `trainNotSaved` uses the string `none` in band (`lib/setup.js:126`, `:133`) and render reads it as "forget" (`:320`, `:337`); the CLI maps `--train none` to null (`bin/passioncode.js:51`) and no train is named `none`, but `lib/trains.js` does not reserve the name, so a train file `none.json` would print as "forget the saved release train"; reserve `none` there. From the PC-105 unit reading round 2: `words()` in `test/strings.test.js` reduces only placeholders without nested braces (a loud false positive is possible, never a silent pass), and its longer-row check reads only the longer row's start line, not a continuation line of a multi-line template; `test/help.test.js` reads every `/^--name` regex in `bin/passioncode.js` as a setup flag (a pattern flag of another command would be named under setup); replace placeholders until none is left, test containment over the whole window, read the patterns only inside `parseSetupArgs`. From the PC-105 product reading round 3 on `0b316c1`: one declined answer labels its open checks "Open now:" when it named a train (it is `planOnly`) and "Still open:" when it did not (`lib/setup.js:364`); choose the label as `exitCode` does (a declined run is a run). From the 0.2.65 product reading round 2 on `9732bd5`: the train form of both install notes ("...; skipped unless you ask for it (npx @passioncode-ai/passioncode@latest setup --train <name> --with fabric)" and its "not installed" form, `lib/setup.js` humanSteps) has no row of its own in `docs/brand/strings.md`, whose rows show only the `(--with ${pr.id})` form; register it or note the bracket in those rows | open 2026-11-03: P3 | PC-105 product reading on `0c8436f` (`lib/setup.js:337-340`, `:371`) |
 | PC-108 | Left from the 0.2.65 readings (PC-94 and PC-97, none a regression): an install taken with the repairs answered no still runs the skill and MCP update the install needs (`lib/setup.js` update step), so the repairs question was partly overruled, and SCN-009 does not say so; a declined usable train over an unusable saved one prints "No problems." where plain `doctor` reports a FAIL (`lib/setup.js` closing line; documented only in cli.md); a run that excludes an app with `--without` and still has its check open is not told `setup`, and a declined one is told plain `setup`, which re-offers what was excluded; no Windows test drives a declined run; the `if (note)` guard in humanSteps and the plan's unselected `–` lines are pinned by no test (widening and pre-existing mutants survive); the em dash guard: widening mutants (template escape, division after a string or `]`, tilde fence, word reset), keyword-as-property read as a regular expression, a `2.` or 4-column `-` line splitting a paragraph CommonMark keeps whole, nested headings or breaks at 4+ columns, a pipe-less table row, 0x20_14 and binary spellings and a call argument on a later line (named in the header) | open 2026-11-03: P3 | 0.2.65 unit, seam and product readings rounds 3 to 7 (`43ff5de` to `6c10e2d`) |
+| PC-109 | Release 0.2.66: Fabric Agent Adapter `v0.60.0` (FAA-165, FAA-193, FAA-169, FAA-172) | open 2026-11-03: the release PR, tag `v0.2.66`, the local install checked against the tag | [adapter CHANGELOG 0.60.0](https://github.com/passioncode-ai/fabric-agent-adapter/blob/v0.60.0/CHANGELOG.md) |

family.json

@@ -8,7 +8,7 @@
       "name": "fabric-agent-adapter",
       "displayName": "Fabric Agent Adapter",
       "repo": "passioncode-ai/fabric-agent-adapter",
-      "ref": "v0.59.0",
+      "ref": "v0.60.0",
       "kind": "plugin",
       "path": "plugins/fabric-agent-adapter",
       "legacyPluginIds": [

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@passioncode-ai/passioncode",
-  "version": "0.2.65",
+  "version": "0.2.66",
   "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"

plugin/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.65",
+  "version": "0.2.66",
   "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",