pidge-cli 0.9.1 → 0.9.2

package/README.md

@@ -28,6 +28,10 @@ then gets the answer as JSON — no webhook, no polling loop to write.
 > install**; and the timeout clock is monotonic. `operating_contract` is **advisory** —
 > Pidge is a relay: you declare how you operate, the human registers their expectation
 > and *sees* if you honor it; nothing is forced.
+>
+> **v0.9.2**: `contract set` no longer prints the channel JSON (which echoed the key) —
+> stdout now carries only the `operating_contract`, so the key never lands in an agent's
+> transcript/logs.
 
 ## Setup in one command (v0.8.0 — the claim flow)
 

package/bin/pidge.js

@@ -919,8 +919,17 @@ async function runContract() {
     die(`pidge: contract set failed (network): ${e.message}`, 2);
   }
   checkManifestNews(res);
-  console.log(body);
   if (!(res.status >= 200 && res.status < 300)) die(`pidge: contract set failed (${res.status}): ${body}`, 2);
+  // stdout = ONLY the operating_contract, never the raw channel JSON. The
+  // /channels PATCH echoes the whole channel — INCLUDING "key":"hld_…" — and
+  // dumping it would land this agent's OWN key in its stdout/transcript/logs
+  // (the one thing the whole claim flow exists to avoid). Print just the contract.
+  let parsedBody = {};
+  try { parsedBody = JSON.parse(body); } catch { /* leave {} */ }
+  console.log(JSON.stringify({
+    operating_contract: parsedBody.operating_contract || {},
+    operating_contract_ignored: parsedBody.operating_contract_ignored
+  }, null, 2));
   console.error(`pidge: declared ${key}=${JSON.stringify(value)} (ADVISORY, never policy — the human sees if you honor it; Pidge enforces nothing)`);
   process.exit(0);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pidge-cli",
-  "version": "0.9.1",
+  "version": "0.9.2",
   "description": "Send rich, actionable iPhone notifications to a human and block until they answer. Built for AI agents.",
   "keywords": [
     "pidge",