@passioncode-ai/passioncode 0.2.1 → 0.2.4

package/payload/plugins/fabric-agent-adapter/skills/building-fabric-services/scripts/fabric_service.py

@@ -49,9 +49,10 @@ DASHBOARD_EXTENSION_KEY = "https://fabric.passioncode.ai/agent-contract/extensio
 DASHBOARD_KIT = "fabric-dashboard-kit@1.1.0"
 REFERENCE_THEMES = ("graphite", "fabric", "paper", "forest", "ocean", "ember", "contrast")
 EXIT_ALREADY_RUNNING = 75
-# Lifecycle contract (fabric-workspace knowledge/lifecycle.md). A launchd-supervised copy that finds
-# the lock held backs off in-process for this long before its exit 75 (LC-03, F8): under KeepAlive
-# with ThrottleInterval 10 that is a few starts an hour instead of one every 10 s.
+# Lifecycle rules: references/lifecycle.md, the rule for this kit's users, which implements the public
+# contract's service specification (Lifecycle). A launchd-supervised copy that finds the lock held backs
+# off in-process for this long before its exit 75 (LC-03, F8): under KeepAlive with ThrottleInterval 10
+# that is a few starts an hour instead of one every 10 s.
 SUPERVISOR_ENV = "FABRIC_SERVICE_SUPERVISOR"
 LOCK_WAIT_SUPERVISED_SECONDS = 300.0
 LOCK_BACKOFF_FIRST_SECONDS = 0.5

package/payload/plugins/fabric-agent-adapter/skills/creating-fabric-agents/SKILL.md

@@ -5,9 +5,9 @@ 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.30.0"
+  version: "0.32.1"
   contract-version: "0.1.0"
-  contract-commit: "f00a7685e3861c27f7899c033fb850a145a1708f"
+  contract-commit: "1636fa97262f4a26e2086572d540c2ee701e0010"
 ---
 
 # Creating Fabric-compatible agents
@@ -123,7 +123,7 @@ python3 <plugin-dir>/skills/adapting-projects-to-fabric/scripts/adapt_project.py
 The effect class is declared, never defaulted: ask the author what the agent does outside itself when the request
 does not say. Cost presets are only for a run whose cost varies; their amounts come from the author or measured runs.
 
-Pin exactly contract `0.1.0` at commit `f00a7685e3861c27f7899c033fb850a145a1708f` and
+Pin exactly contract `0.1.0` at commit `1636fa97262f4a26e2086572d540c2ee701e0010` 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/fabric-agent-adapter/skills/working-with-fabric/SKILL.md

@@ -19,7 +19,7 @@ compatibility: >-
   this plugin; Codex and Kimi Code get the session-start preamble hook on the person's consent.
 metadata:
   author: PassionCode.ai
-  version: "0.30.0"
+  version: "0.32.1"
 ---
 
 # Working with Fabric

package/payload/plugins/fabric-agent-adapter/skills/working-with-fabric/references/project-board.md

@@ -1,9 +1,10 @@
 # The project board (`fabric-project-comms/0.1`, the `com.*` tools)
 
 Read this when the session starts in a project a Fabric hub serves, when the person asks about board mail, when you
-need something from another Project, or when you wait for an answer. The rule itself has one home: PassionCode's
-knowledge base, [agents-first.md, "The project board"](https://github.com/passioncode-ai/fabric-workspace/blob/main/knowledge/agents-first.md#the-project-board).
-This page is how a coding agent with this plugin follows it; where the two differ, that page wins.
+need something from another Project, or when you wait for an answer. This page is the rule a coding agent with this
+plugin follows. Inside PassionCode.ai it implements the knowledge base's
+[agents-first.md, "The project board"](https://github.com/passioncode-ai/fabric-workspace/blob/main/knowledge/agents-first.md#the-project-board)
+(private to the organization), and is kept in step with it; nothing behind that link is needed to follow this page.
 
 ## Contents
 
@@ -46,6 +47,26 @@ capability (a plain question may be `kind: "message"`), in a new thread whose pa
   SendMessage between sessions. agent-sync leases guard files; they carry no asks.
 
 A request the board stored has not been carried out. Only its state (`completed`, `failed_known`) says what happened.
+`settledBy: "owner"` on a request (DEC-0081) means the estate owner settled it after its responder was gone: read it as
+the owner's attestation, not the responder's.
+
+**`held` (DEC-0079).** The operator holds that thread, that Project or that capability, and the board refuses new
+work there with `held`, which is always retryable. Tell the person what is held. Retry later, the pause growing, with
+the **same idempotency key and arguments**. Never post the ask into another thread or to another Project to get around
+the hold. Reads, cancels and replies to work already started are never held.
+
+**A problem for another Project: a structured finding (DEC-0080).** Send one only when the running Fabric's
+`com.submit` input schema lists `finding`; otherwise send a plain message. A finding carries:
+
+- `severity`: `info`, `warning` or `blocking`;
+- `consequence`: one sentence on what it breaks;
+- `affects`: the backlog rows (`{repository, path, id}`) or host tasks it touches;
+- a `dedupeKey` that stays the same for the same problem.
+
+Its idempotency key is at least 128 random bits (for example 32 hex characters from a cryptographic generator), kept
+on every retry. A receipt with `repeated: true` and a fresh key means that finding already stands on the board: its
+thread may not be the one you named, and nothing new was posted. Never put a `{redacted: true}` item into a finding you
+send.
 
 ## The project directory
 

package/payload/plugins/fabric-agent-adapter/skills/working-with-fabric/scripts/fabric_session.py

@@ -60,7 +60,7 @@ WATCH_MAX_BACKOFF_S = 900
 SESSION_ID = re.compile(r"[A-Za-z0-9._:-]{1,128}")
 LOOPBACK_ORIGIN = re.compile(r"http://127\.0\.0\.1:(\d{1,5})")
 LOCAL_ORIGIN = re.compile(r'"origin": "http://(?:127\.0\.0\.1|localhost)')
-VERSION = "0.30.0"
+VERSION = "0.32.1"
 HOSTS = {"claude": "Claude Code", "codex": "Codex", "kimi": "Kimi Code"}
 # A session Fabric launched. FABRIC_LAUNCHED_SESSION=1 is the marker Fabric is asked to set (need D6); the others are
 # what Fabric already gives a launched session (fabric sessionBundle.ts): only their NAMES are looked at, never a value

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.1",
+  "version": "0.2.4",
   "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/hooks/repo-rules.js

@@ -5,13 +5,18 @@
  * wiki.passioncode.ai/knowledge) and the repository's AGENTS.md before its first edit, and after
  * the work updates the knowledge base page that owns any cross-repository fact it changed. A rule
  * an agent has to remember is a rule it forgets in the one repository where it mattered, so the
- * session start says it, in one line, and only where it applies. Anything unexpected (no git, no
- * origin, a slow git) prints nothing: a reminder must never cost a session.
+ * session start says it, in one line, and only where it applies. The same line names the two Fabric
+ * principles that govern how the work moves — 10, a free agent takes the next task, and 11, a project
+ * moves in releases and every run leaves a lesson — by their anchors in principles.md, so the
+ * knowledge base's rules §4 reaches every session without each AGENTS.md restating it. Anything
+ * unexpected (no git, no origin, a slow git) prints nothing: a reminder must never cost a session.
  */
 const { execFileSync } = require('child_process');
 
 const KNOWLEDGE = 'fabric-workspace/knowledge/';
 const KNOWLEDGE_WEB = 'https://wiki.passioncode.ai/knowledge';
+const PRINCIPLE_10 = `${KNOWLEDGE}principles.md#10-a-free-agent-takes-the-next-task`;
+const PRINCIPLE_11 = `${KNOWLEDGE}principles.md#11-a-project-moves-in-releases-and-every-run-leaves-a-lesson-the-next-one-reads`;
 
 /** The GitHub organization an origin URL belongs to, when it is passioncode-ai; else null. */
 function orgOf(url) {
@@ -32,7 +37,7 @@ function originOf(dir) {
 /** The one line to print at session start in `dir`, or null. */
 function rulesLine(dir) {
   if (!orgOf(originOf(dir))) return null;
-  return `[passioncode] passioncode-ai repository: read the knowledge base (${KNOWLEDGE} or ${KNOWLEDGE_WEB}), then this repository's AGENTS.md, before the first edit; after the work, update the knowledge base page that owns any cross-repository fact you changed; edit each canonical task source declared in docs/backlog-sources.json and publish the derived workspace backlog.`;
+  return `[passioncode] passioncode-ai repository: read the knowledge base (${KNOWLEDGE} or ${KNOWLEDGE_WEB}), then this repository's AGENTS.md, before the first edit; work by Fabric principle 10, a free agent takes the next task (a wait goes on a watcher, stop only at a human gate; ${PRINCIPLE_10}), and principle 11, a project moves in releases and every run leaves a lesson the next one reads (${PRINCIPLE_11}); after the work, update the knowledge base page that owns any cross-repository fact you changed; edit each canonical task source declared in docs/backlog-sources.json and publish the derived workspace backlog.`;
 }
 
-module.exports = { KNOWLEDGE, KNOWLEDGE_WEB, orgOf, rulesLine };
+module.exports = { KNOWLEDGE, KNOWLEDGE_WEB, PRINCIPLE_10, PRINCIPLE_11, orgOf, rulesLine };

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

@@ -124,6 +124,15 @@ Also, before the first edit:
 - **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.
+- **A free agent takes the next task** (Fabric [principle 10](https://github.com/passioncode-ai/fabric-workspace/blob/main/knowledge/principles.md#10-a-free-agent-takes-the-next-task)).
+  A finished unit is followed by the next task from the board or the handoff, in the same turn.
+  Every wait (a review, CI, a merge, a peer, a scheduled time) goes on a watcher that acts when it
+  clears, and one that can outlive the session goes on a durable trigger. Stop only at a human gate:
+  a sign-in, a consent, a payment, a secret a person types, spend above the limit, a recorded decision.
+- **A project moves in releases; every run leaves a lesson** (Fabric [principle 11](https://github.com/passioncode-ai/fabric-workspace/blob/main/knowledge/principles.md#11-a-project-moves-in-releases-and-every-run-leaves-a-lesson-the-next-one-reads)).
+  A finding gets an id in the owning register and is fixed in the next release with every other
+  open item; only the five-entry hotfix lane ships alone. Questions go out in rounds. Read the
+  retrospectives before work and write the lesson after it.
 
 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.