busa-cli 0.54.0 → 0.60.0

package/dist/cli.js

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { i as checkForUpdate, n as pkgVersion, r as runCli } from "./run-CFGp5vuO.js";
+import { i as checkForUpdate, n as pkgVersion, r as runCli } from "./run-bQ1VIBLc.js";
 //#region src/cli.ts
 const exitCode = await runCli(process.argv.slice(2));
 const notice = await checkForUpdate("busabase-cli", pkgVersion());

package/dist/index.js

@@ -1,3 +1,3 @@
-import { a as render, i as checkForUpdate, n as pkgVersion, r as runCli, t as HELP } from "./run-CFGp5vuO.js";
+import { a as render, i as checkForUpdate, n as pkgVersion, r as runCli, t as HELP } from "./run-bQ1VIBLc.js";
 import { DEFAULT_BASE_URL, createBusabaseClient, normalizeBaseUrl } from "busabase-sdk";
 export { DEFAULT_BASE_URL, HELP, checkForUpdate, createBusabaseClient, normalizeBaseUrl, pkgVersion, render, runCli };

package/dist/{run-CFGp5vuO.js → run-bQ1VIBLc.js}

@@ -121,17 +121,17 @@ const iStringParse = (str, lang = "en") => {
 //#endregion
 //#region ../../packages/busabase-contract/src/contract/node-agent-prompt-schemas.ts
 /**
-* Per-node custom scenario prompts (`node.metadata.agentPrompts`) — the single
+* Per-node custom scenario prompts (`node.agentPrompts`) — the single
 * schema shared by BOTH write and read paths, per the node-agent-prompts
 * design (v2) §7.3:
 *
 * - Write: `busabase-cli nodes set-agent-prompts` validates a file against this
-*   schema client-side, before calling `nodes.updateMetadata` — a malformed file
-*   never reaches the network.
+*   schema client-side, before calling `nodes.updateAgentPrompts` — a malformed
+*   file never reaches the network.
 * - Read: `buildNodeAgentPrompts` (`packages/busabase-core/.../node-agent-prompts.ts`)
-*   `.safeParse`s whatever is stored in `metadata.agentPrompts` and falls back to
-*   the node type's default scenarios on failure, so a bad write (or a manual
-*   jsonb edit) can never crash the Agent Prompts dialog.
+*   `.safeParse`s whatever is stored in the node's `agentPrompts` column and
+*   ignores invalid custom entries, so a bad write (or a manual jsonb edit) can
+*   never crash the Agent Prompts dialog or hide its built-in scenarios.
 *
 * One schema, one place to edit the limits — do not duplicate this validation on
 * either side.
@@ -181,7 +181,7 @@ const customPromptDefSchema = z.object({
 	body: customPromptBodySchema
 });
 /**
-* The full `metadata.agentPrompts` array. `.max` bounds the list; the
+* The full `agentPrompts` array. `.max` bounds the list; the
 * `superRefine` catches duplicate keys with an issue path pointing at the
 * offending entry, so a CLI/server validation error names which entry and
 * which key collided instead of a bare "keys must be unique".
@@ -6849,7 +6849,16 @@ const searchResultSchema = z.object({
 	body: z.string(),
 	eyebrow: z.string(),
 	href: z.string(),
-	updatedAt: z.string().nullable()
+	updatedAt: z.string().nullable(),
+	/**
+	* The actor that created this, or null when the source cannot say.
+	*
+	* Present so a result can SHOW its author and so the author filter can be
+	* driven by clicking one — you can only filter by a creator you can actually
+	* see, which beats a free-text box you have to guess the spelling of. Null is
+	* rendered as "unknown", never as a person.
+	*/
+	createdBy: z.string().nullable().default(null)
 });
 z.object({
 	query: z.string(),
@@ -7116,6 +7125,23 @@ z.object({
 	updatedAfter: z.string().datetime({ offset: true }).optional().describe("Inclusive lower bound, ISO 8601. A UTC `Z` or an explicit offset; not a bare local time."),
 	updatedBefore: z.string().datetime({ offset: true }).optional().describe("Inclusive upper bound, ISO 8601. A UTC `Z` or an explicit offset; not a bare local time."),
 	/**
+	* Restrict to what one actor created.
+	*
+	* Every source answers from a real column, which is what made this filter
+	* shippable: records and assets carry their own `created_by`, node CONTENT
+	* reads `busabase_nodes.created_by` (added with this change, backfilled from
+	* each node's `node_create` commit), and Bases resolve through the owning
+	* node the Base query already joins for its dates and sort.
+	*
+	* A free-form actor id, not a user id — agents and API keys create things
+	* too, and filtering by "user" would silently drop everything an agent made.
+	*
+	* Nodes whose creating commit is gone have a NULL `created_by` and match no
+	* author. That is deliberate: "this row cannot tell" must not render as
+	* "nobody made it".
+	*/
+	createdBy: z.string().optional().describe("Restrict to one creator. Matches the actor id, which may be an agent or API key."),
+	/**
 	* Restrict to a subtree: this node and everything beneath it.
 	*
 	* Resolved by walking the tree in application code (`collectSubtreeIds`),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "busa-cli",
-  "version": "0.54.0",
+  "version": "0.60.0",
   "description": "Command-line client for the Busabase OpenAPI REST API. Talks to a local or remote `busabase server`. Short-name alias for busabase-cli.",
   "license": "MIT",
   "homepage": "https://github.com/busabase/busabase/tree/main/apps/busabase-cli",
@@ -33,7 +33,7 @@
   "dependencies": {
     "@zip.js/zip.js": "^2.8.20",
     "busabase-package": "workspace:*",
-    "busabase-sdk": "0.54.0",
+    "busabase-sdk": "0.60.0",
     "commander": "^14.0.0",
     "qrcode": "^1.5.4",
     "tar-stream": "^3.1.7",