@cello-protocol/cli 0.0.91 → 0.0.92

package/dist/parity-commands.d.ts

@@ -152,7 +152,7 @@ export declare function gatewayConfigGet(celloDir: string, key: string, opts: Pa
  * row written) and answers `needs_confirmation` — only then do we prompt, and only then do we
  * re-send with `confirmed: true`.
  *
- * There is deliberately NO `--yes` flag (M9C-D16). A flag that lets a script confirm a loosening is
+ * There is deliberately NO `--yes` flag (M9B-D16). A flag that lets a script confirm a loosening is
  * the environment-variable bypass with a friendlier name, and removing that bypass is the sibling
  * decision (D-5). If stdin is not a TTY there is no human here, so the answer is no.
  */
@@ -160,7 +160,7 @@ export declare function gatewayConfigSet(celloDir: string, key: string, value: s
 /** What a confirmation attempt actually resolved to. `no_tty` is NOT `no` — see F3 above. */
 export type ConfirmAnswer = "yes" | "no" | "no_tty";
 /**
- * `cello policy log` → cello_policy_log (DOD-M9C-AUDIT-1, policy D-11).
+ * `cello policy log` → cello_policy_log (DOD-M9B-AUDIT-1, policy D-11).
  *
  * Ships with the enforcement flip by decision: it is the answer to "did this new error come from
  * the security layer or from my own change?" — a lookup instead of a guess.

package/dist/parity-commands.js

@@ -336,7 +336,7 @@ export function settingsGet(celloDir, key, opts) {
 export function settingsSet(celloDir, key, value, opts) {
     return ipcCommand(celloDir, IPC_METHODS["settings-set"], { key, value }, opts);
 }
-// ─── DOD-M9C-SURFACE-1: the security layer's control surface (policy D-4) ──────────────────────
+// ─── DOD-M9B-SURFACE-1: the security layer's control surface (policy D-4) ──────────────────────
 //
 // NOT agent-scoped: the security layer screens every message on this machine regardless of which
 // agent is selected, so its config is per-INSTALL. Passing agentScoped=false keeps `cello config`
@@ -358,7 +358,7 @@ export function gatewayConfigGet(celloDir, key, opts) {
  * row written) and answers `needs_confirmation` — only then do we prompt, and only then do we
  * re-send with `confirmed: true`.
  *
- * There is deliberately NO `--yes` flag (M9C-D16). A flag that lets a script confirm a loosening is
+ * There is deliberately NO `--yes` flag (M9B-D16). A flag that lets a script confirm a loosening is
  * the environment-variable bypass with a friendlier name, and removing that bypass is the sibling
  * decision (D-5). If stdin is not a TTY there is no human here, so the answer is no.
  */
@@ -430,7 +430,7 @@ async function confirmAtTty(question) {
     return answer === "y" || answer === "yes" ? "yes" : "no";
 }
 /**
- * `cello policy log` → cello_policy_log (DOD-M9C-AUDIT-1, policy D-11).
+ * `cello policy log` → cello_policy_log (DOD-M9B-AUDIT-1, policy D-11).
  *
  * Ships with the enforcement flip by decision: it is the answer to "did this new error come from
  * the security layer or from my own change?" — a lookup instead of a guess.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cello-protocol/cli",
-  "version": "0.0.91",
+  "version": "0.0.92",
   "private": false,
   "type": "module",
   "engines": {
@@ -17,7 +17,7 @@
     "package.json"
   ],
   "dependencies": {
-    "@cello-protocol/daemon": "0.0.90",
+    "@cello-protocol/daemon": "0.0.91",
     "@cello-protocol/protocol-types": "0.0.33"
   },
   "devDependencies": {