pi-daddy 0.40.0 → 0.40.1

package/CHANGELOG.md

@@ -12,6 +12,31 @@ the record of how the package got here and are worth keeping; they are not worth
 > the record of how the package arrived at what it does, and because the reasoning behind each one is
 > usually the clearest statement of why the current behaviour is what it is.
 
+## 0.40.1 — a `context:` capability could not be written to the ledger, so delegation was denied
+
+**A session whose grant held any `context:` id could not delegate at all.** Reported from a live session:
+
+```
+delegation refused: grants: ledger write failed, denying — TypeError: invalid ledger v3 event:
+capability decision requested must contain capability identifiers
+```
+
+`ledger-identifiers.ts` kept its OWN copy of the capability namespaces, and ADR-0078 added `context:` to the
+kernel's list without it. Every capability-decision event validates six capability arrays with that predicate,
+and a ledger write that throws denies the delegation — so the whole namespace took delegation down wherever it
+appeared, and the message named neither the namespace nor the list.
+
+0.40.0 widened it rather than causing it: held-back definitions began contributing `context:` ids to the
+generated grant, so far more sessions carry one. Anyone whose skills declare a handoff mode was affected from
+0.33.0 onward.
+
+**The ledger now derives its namespaces from the kernel's list** instead of restating them, and a test asserts
+every namespace the kernel defines is a valid ledger identifier. Adding a namespace without the ledger following
+now fails.
+
+This is the same shape this package has spent a session finding: one rule, two spellings, the guard on the
+quieter one. A validator that restates what it validates is that shape with a ledger behind it.
+
 ## 0.40.0 — the file-writing tools are gated, and a held-back definition keeps its context modes
 
 **`tool:write`, `tool:edit` and `tool:edit-diff` join `tool:bash` and `context:fork` in `DEFAULT_GATED`**, by

package/dist/kernel/ledger-identifiers.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"ledger-identifiers.d.ts","sourceRoot":"","sources":["../../src/kernel/ledger-identifiers.ts"],"names":[],"mappings":"AAKA,2GAA2G;AAC3G,wBAAgB,yBAAyB,CAAC,KAAK,EAAE,OAAO,GAAG,KAAK,IAAI,MAAM,CAEzE;AAED,8FAA8F;AAC9F,wBAAgB,6BAA6B,CAAC,KAAK,EAAE,OAAO,GAAG,KAAK,IAAI,MAAM,CAE7E;AAED,0GAA0G;AAC1G,wBAAgB,4BAA4B,CAAC,KAAK,EAAE,OAAO,GAAG,KAAK,IAAI,MAAM,CAI5E"}
+{"version":3,"file":"ledger-identifiers.d.ts","sourceRoot":"","sources":["../../src/kernel/ledger-identifiers.ts"],"names":[],"mappings":"AAyBA,2GAA2G;AAC3G,wBAAgB,yBAAyB,CAAC,KAAK,EAAE,OAAO,GAAG,KAAK,IAAI,MAAM,CAEzE;AAED,8FAA8F;AAC9F,wBAAgB,6BAA6B,CAAC,KAAK,EAAE,OAAO,GAAG,KAAK,IAAI,MAAM,CAE7E;AAED,0GAA0G;AAC1G,wBAAgB,4BAA4B,CAAC,KAAK,EAAE,OAAO,GAAG,KAAK,IAAI,MAAM,CAI5E"}

package/dist/kernel/ledger-identifiers.js

@@ -1,7 +1,26 @@
 const DISPLAY_IDENTIFIER = /^[A-Za-z0-9@*][A-Za-z0-9@*._:/-]{0,511}$/;
 const CORRELATION_IDENTIFIER = /^[A-Za-z0-9@*][A-Za-z0-9@*._:/-]{0,127}$/;
 const CAPABILITY_TAIL = /^[A-Za-z0-9@*][A-Za-z0-9@*._/-]{0,255}$/;
-const CAPABILITY_PREFIXES = ["tool:", "skill:", "agent:", "workspace:", "ext:"];
+/**
+ * The namespaces a ledger capability field may hold — **derived, not restated.**
+ *
+ * **This was a second copy of the list and it took a whole namespace down.** ADR-0078 added `context:` to
+ * `CAPABILITY_NAMESPACE_PREFIXES` and nothing added it here, so `isLedgerCapabilityIdentifier("context:summary")`
+ * was false. Every capability-decision event carries `requested`, `parentGrant`, `effective`, `denied`, `clipped`
+ * and `gatedBlocked`, all validated with this, so a session whose grant contained ANY `context:` id could not
+ * write a decision at all — and a ledger write that throws denies the delegation. The operator saw
+ * `delegation refused: grants: ledger write failed, denying — TypeError: invalid ledger v3 event: capability
+ * decision requested must contain capability identifiers`, with no indication that the cause was the namespace.
+ *
+ * 0.40.0 widened the blast radius rather than causing it: held-back definitions began contributing `context:`
+ * ids to the generated grant, so far more sessions carry one.
+ *
+ * Importing the kernel's list is the fix, and the point. This package has spent a whole session finding the same
+ * shape — one rule, two spellings, the guard on the quieter one — and a validator that restates what it
+ * validates is that shape with a ledger behind it.
+ */
+import { CAPABILITY_NAMESPACE_PREFIXES } from "./capabilities.js";
+const CAPABILITY_PREFIXES = CAPABILITY_NAMESPACE_PREFIXES;
 /** Identifier text safe to copy onto the operator's terminal; prose belongs in no ledger display field. */
 export function isLedgerDisplayIdentifier(value) {
     return typeof value === "string" && DISPLAY_IDENTIFIER.test(value);

package/dist/kernel/ledger-identifiers.js.map

@@ -1 +1 @@
-{"version":3,"file":"ledger-identifiers.js","sourceRoot":"","sources":["../../src/kernel/ledger-identifiers.ts"],"names":[],"mappings":"AAAA,MAAM,kBAAkB,GAAG,0CAA0C,CAAC;AACtE,MAAM,sBAAsB,GAAG,0CAA0C,CAAC;AAC1E,MAAM,eAAe,GAAG,yCAAyC,CAAC;AAClE,MAAM,mBAAmB,GAAG,CAAC,OAAO,EAAE,QAAQ,EAAE,QAAQ,EAAE,YAAY,EAAE,MAAM,CAAU,CAAC;AAEzF,2GAA2G;AAC3G,MAAM,UAAU,yBAAyB,CAAC,KAAc;IACtD,OAAO,OAAO,KAAK,KAAK,QAAQ,IAAI,kBAAkB,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;AACrE,CAAC;AAED,8FAA8F;AAC9F,MAAM,UAAU,6BAA6B,CAAC,KAAc;IAC1D,OAAO,OAAO,KAAK,KAAK,QAAQ,IAAI,sBAAsB,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;AACzE,CAAC;AAED,0GAA0G;AAC1G,MAAM,UAAU,4BAA4B,CAAC,KAAc;IACzD,IAAI,OAAO,KAAK,KAAK,QAAQ;QAAE,OAAO,KAAK,CAAC;IAC5C,MAAM,MAAM,GAAG,mBAAmB,CAAC,IAAI,CAAC,CAAC,SAAS,EAAE,EAAE,CAAC,KAAK,CAAC,UAAU,CAAC,SAAS,CAAC,CAAC,CAAC;IACpF,OAAO,OAAO,CAAC,MAAM,IAAI,eAAe,CAAC,IAAI,CAAC,KAAK,CAAC,KAAK,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC;AAC7E,CAAC"}
+{"version":3,"file":"ledger-identifiers.js","sourceRoot":"","sources":["../../src/kernel/ledger-identifiers.ts"],"names":[],"mappings":"AAAA,MAAM,kBAAkB,GAAG,0CAA0C,CAAC;AACtE,MAAM,sBAAsB,GAAG,0CAA0C,CAAC;AAC1E,MAAM,eAAe,GAAG,yCAAyC,CAAC;AAClE;;;;;;;;;;;;;;;;;GAiBG;AACH,OAAO,EAAE,6BAA6B,EAAE,MAAM,mBAAmB,CAAC;AAElE,MAAM,mBAAmB,GAAG,6BAA6B,CAAC;AAE1D,2GAA2G;AAC3G,MAAM,UAAU,yBAAyB,CAAC,KAAc;IACtD,OAAO,OAAO,KAAK,KAAK,QAAQ,IAAI,kBAAkB,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;AACrE,CAAC;AAED,8FAA8F;AAC9F,MAAM,UAAU,6BAA6B,CAAC,KAAc;IAC1D,OAAO,OAAO,KAAK,KAAK,QAAQ,IAAI,sBAAsB,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;AACzE,CAAC;AAED,0GAA0G;AAC1G,MAAM,UAAU,4BAA4B,CAAC,KAAc;IACzD,IAAI,OAAO,KAAK,KAAK,QAAQ;QAAE,OAAO,KAAK,CAAC;IAC5C,MAAM,MAAM,GAAG,mBAAmB,CAAC,IAAI,CAAC,CAAC,SAAS,EAAE,EAAE,CAAC,KAAK,CAAC,UAAU,CAAC,SAAS,CAAC,CAAC,CAAC;IACpF,OAAO,OAAO,CAAC,MAAM,IAAI,eAAe,CAAC,IAAI,CAAC,KAAK,CAAC,KAAK,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC;AAC7E,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-daddy",
-  "version": "0.40.0",
+  "version": "0.40.1",
   "description": "Capability governance for pi sub-agents: spawn Agent Skills (SKILL.md) definitions whose allowed-tools becomes a grant that can only narrow going down a delegation tree, enforced by pi's own --tools allowlist, with an append-only ledger.",
   "keywords": [
     "pi-package",

package/src/kernel/ledger-identifiers.ts

@@ -1,7 +1,27 @@
 const DISPLAY_IDENTIFIER = /^[A-Za-z0-9@*][A-Za-z0-9@*._:/-]{0,511}$/;
 const CORRELATION_IDENTIFIER = /^[A-Za-z0-9@*][A-Za-z0-9@*._:/-]{0,127}$/;
 const CAPABILITY_TAIL = /^[A-Za-z0-9@*][A-Za-z0-9@*._/-]{0,255}$/;
-const CAPABILITY_PREFIXES = ["tool:", "skill:", "agent:", "workspace:", "ext:"] as const;
+/**
+ * The namespaces a ledger capability field may hold — **derived, not restated.**
+ *
+ * **This was a second copy of the list and it took a whole namespace down.** ADR-0078 added `context:` to
+ * `CAPABILITY_NAMESPACE_PREFIXES` and nothing added it here, so `isLedgerCapabilityIdentifier("context:summary")`
+ * was false. Every capability-decision event carries `requested`, `parentGrant`, `effective`, `denied`, `clipped`
+ * and `gatedBlocked`, all validated with this, so a session whose grant contained ANY `context:` id could not
+ * write a decision at all — and a ledger write that throws denies the delegation. The operator saw
+ * `delegation refused: grants: ledger write failed, denying — TypeError: invalid ledger v3 event: capability
+ * decision requested must contain capability identifiers`, with no indication that the cause was the namespace.
+ *
+ * 0.40.0 widened the blast radius rather than causing it: held-back definitions began contributing `context:`
+ * ids to the generated grant, so far more sessions carry one.
+ *
+ * Importing the kernel's list is the fix, and the point. This package has spent a whole session finding the same
+ * shape — one rule, two spellings, the guard on the quieter one — and a validator that restates what it
+ * validates is that shape with a ledger behind it.
+ */
+import { CAPABILITY_NAMESPACE_PREFIXES } from "./capabilities.ts";
+
+const CAPABILITY_PREFIXES = CAPABILITY_NAMESPACE_PREFIXES;
 
 /** Identifier text safe to copy onto the operator's terminal; prose belongs in no ledger display field. */
 export function isLedgerDisplayIdentifier(value: unknown): value is string {