@bli-cockpit/cli 0.2.82 → 0.2.84

package/dist/commands/local-args-tower-search.js

@@ -4,8 +4,9 @@
  * Its own sibling of `local-args-tower.ts` rather than folded into
  * `local-args-tower-pages.ts` or `-docs-msg.ts`: search is not one surface's
  * verb, it is the door OVER all of them — documents, messages, issues, meeting
- * notes and memory — and putting it under any one family's doc comment would
- * say something untrue about what it reads.
+ * notes, the caller's own mail and calendar (BLI-3880), and memory — and
+ * putting it under any one family's doc comment would say something untrue
+ * about what it reads.
  *
  * The query is a POSITIONAL, not a flag, because that is how every search
  * command a person has ever typed works (`grep`, `rg`, `gh search`). Several
@@ -13,8 +14,20 @@
  * behaves the way it looks, without demanding quotes.
  */
 import { optionalNonEmpty, optionalPositiveInteger, optionalUrl, parseNamedArgs, } from "./local-arg-values.js";
-/** The five corpora. Kept here so an unknown kind is refused BEFORE a round trip. */
-export const SEARCH_KINDS = ["doc", "msg", "issue", "note", "memory"];
+/**
+ * Every corpus. Kept here so an unknown kind is refused BEFORE a round trip,
+ * and mirrors `SEARCH_KINDS` in the dashboard — nothing in the type system ties
+ * the two lists together.
+ */
+export const SEARCH_KINDS = [
+    "doc",
+    "msg",
+    "issue",
+    "note",
+    "mail",
+    "cal",
+    "memory",
+];
 export function parseSearchArgs(args) {
     const values = parseNamedArgs(args, {
         allowedFlags: ["--home", "--dashboard-url", "--kind", "--limit", "--json"],

package/dist/commands/local-command-shapes-search.js

@@ -0,0 +1,18 @@
+/**
+ * The shape of `cockpit search` (BLI-3728; split out of
+ * `local-command-shapes.ts` by BLI-3880).
+ *
+ * Its own module for the reason the verb itself has one
+ * (`local-args-tower-search.ts`): search is not one surface's verb, it is the
+ * door OVER all of them, so it sits beside the surface families rather than
+ * inside any of them. Two more corpora also pushed the shape file past this
+ * repo's readability ceiling, and a member with a paragraph of its own is
+ * exactly the member to lift out first.
+ *
+ * `local-command-shapes.ts` imports this type and keeps `SearchCommandShape`
+ * in the `LocalCommand` union, so nothing that reads a parsed command changed.
+ * A new module here must also join `scripts/build-public-cli.mjs`
+ * `runtimeFiles` — but this one is types only, erased at build, and the CLI's
+ * own runtime-file assert is what proves it either way.
+ */
+export {};

package/dist/commands/memory-hook-counts.js

@@ -47,6 +47,7 @@ export function readMemoryHookCounts(options) {
             hook_timeouts_24h: window.timeouts,
             hook_printed_24h: window.printed,
             hook_failed_24h: window.failed,
+            hook_skipped_trivial_24h: window.skippedTrivial,
         },
         reason: "ok",
     };

package/dist/commands/ops.js

@@ -144,6 +144,9 @@ async function runOpsStatus(command, io, tower) {
         // misses.
         memory_hook_runs_24h: memory?.hooks?.totals?.runs ?? null,
         memory_hook_timeouts_24h: memory?.hooks?.totals?.timeouts ?? null,
+        // BLI-3881: runs the hook declined to search for. A SUBSET of runs, so
+        // `runs - skipped_trivial` is how many turns actually asked the door.
+        memory_hook_skipped_trivial_24h: memory?.hooks?.totals?.skippedTrivial ?? null,
         memory_hook_devices_reporting: memory?.hooks?.reporting ?? null,
     })}`);
     return unhealthy.length > 0 ? 1 : 0;

package/dist/commands/public-root.js

@@ -15,7 +15,7 @@ export async function runCockpitCli(argv, io) {
   }
 
   if (command === "--version" || command === "-V" || command === "version") {
-    writeLine(io?.stdout ?? process.stdout, "0.2.82");
+    writeLine(io?.stdout ?? process.stdout, "0.2.84");
     return 0;
   }
 

package/dist/commands/search.js

@@ -29,14 +29,21 @@ import { writeLine } from "./cli-io.js";
 const TAG = "[search cli]";
 const READ_DEADLINE_MS = 30_000;
 /** Group headings, in the order a person reads them. Mirrors the overlay. */
+// Mirrors `SEARCH_KIND_LABELS` / `SEARCH_KINDS` in the dashboard
+// (BLI-3880 added mail and cal). A kind the door returns that is missing here
+// still prints — upper-cased — rather than vanishing, which is why the map is
+// keyed loosely: an older CLI against a newer door must show the group, not
+// swallow it.
 const KIND_LABELS = {
     doc: "DOCUMENTS",
     msg: "MESSAGES",
     issue: "ISSUES",
     note: "MEETING NOTES",
+    mail: "MAIL",
+    cal: "CALENDAR",
     memory: "MEMORY",
 };
-const KIND_ORDER = ["doc", "msg", "issue", "note", "memory"];
+const KIND_ORDER = ["doc", "msg", "issue", "note", "mail", "cal", "memory"];
 export async function runSearch(command, io) {
     const door = await openAgentDoor("search", command, io);
     const params = new URLSearchParams({ q: command.query });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bli-cockpit/cli",
-  "version": "0.2.82",
+  "version": "0.2.84",
   "private": false,
   "type": "module",
   "bin": {
@@ -27,8 +27,8 @@
     "test": "node dist/cli.js --help && node ../../scripts/assert-public-cli-routing.mjs && node ../../scripts/assert-public-cli-verb-help.mjs && node ../../scripts/assert-public-cli-runtime-files.mjs && node ../../scripts/assert-public-cli-no-fleet-posts.mjs && node ../../scripts/assert-public-package-pack.mjs --workspace=@bli-cockpit/cli"
   },
   "dependencies": {
-    "@bli-cockpit/memory-mcp": "0.1.14",
-    "@bli-cockpit/mcp": "0.1.16",
-    "@bli-cockpit/telemetry-core": "0.1.33"
+    "@bli-cockpit/memory-mcp": "0.1.16",
+    "@bli-cockpit/mcp": "0.1.18",
+    "@bli-cockpit/telemetry-core": "0.1.34"
   }
 }