fruxon 0.13.2__tar.gz → 0.13.4__tar.gz

{fruxon-0.13.2 → fruxon-0.13.4}/HISTORY.md

@@ -1,5 +1,21 @@
 # History
 
+## Unreleased — A knowledge base can be consolidated
+
+Serial merge-per-conversation cannot repair a pair once both halves exist:
+each was written before the other was searchable. The backend now runs a
+pass over the whole corpus (fruxon-backend, `knowledgeBases/{kb}:consolidate`).
+
+- **New `fruxon knowledge-bases consolidate <kb>`** — embeds the base's
+  live documents, clusters those above a similarity threshold, and prints
+  the clusters. Report-only unless `--apply`, which has the base's
+  consolidator agent decide each cluster and merge it (survivor keeps the
+  union of tags, labels and source conversations; the rest are archived).
+  Waits for the report by default; `--no-wait` prints the queued run and
+  `fruxon knowledge-bases consolidation <kb> <run>` reads it later.
+- `agents executions list --trigger-type` accepts `KNOWLEDGE_CONSOLIDATION`,
+  the trigger the consolidator agent's runs carry.
+
 ## Unreleased — What a listing leaves out, and what a typo returns
 
 A patch release from a CLI trial run against a live workspace. Four defects,
@@ -208,6 +224,25 @@ workspace 2026-09-10.
   inbound wiring is unknown rather than asserting the agent cannot be reached.
   Triggers and channel bindings count exactly as before.
 
+## Unreleased — Free-text filters are called `query`
+
+The platform renamed the free-text filter on every list endpoint from `search`
+to `query` (and the storage file list from `q` to `query`), following the
+Google Cloud convention. The SDK follows on the wire and in its own names, with
+no alias — the old spellings are gone.
+
+- **Python client**: `list_agents`, `list_memories`, `list_integrations`,
+  `list_asset_documents`, `list_participants` and `list_environments` take
+  `query=` instead of `search=`, and send `?query=`. `list_participants`
+  keeps its tier rule: a `query` without an explicit `tier` searches both
+  directory tiers.
+
+- **CLI**: `--search` is now `--query` on `agents list`, `agents memory list`,
+  `integrations list`, `participants list`, `environments list` and
+  `assets documents`. The existing `-q` short alias stays on `participants list`
+  and `assets documents`. `agents topics search --query` and
+  `assets search -q` were already spelled this way.
+
 ## Unreleased — What a stage's agent will silently not do
 
 Two ways a work shape's PROCESS stage is wired wrong that the platform used to

{fruxon-0.13.2 → fruxon-0.13.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: fruxon
-Version: 0.13.2
+Version: 0.13.4
 Summary: The Fruxon SDK is a lightweight Python client for integrating with the Fruxon platform.
 Project-URL: bugs, https://github.com/fruxon-ai/fruxon-sdk/issues
 Project-URL: changelog, https://github.com/fruxon-ai/fruxon-sdk/blob/main/HISTORY.md
@@ -96,7 +96,7 @@ Execution:
 | `fruxon agents executions trace <agent> <record-id>` | Step-by-step trace of one execution — LLM/tool calls, durations. `--show-io` also prints each tool step's parameters and result (the payload lives at `steps[].result`, a sibling of `toolTrace` — whose `resultDelivery` carries sizes only). |
 | `fruxon agents executions result <agent> <record-id>` | The final output one execution produced. |
 | `fruxon agents approvals list/get/respond/cancel <agent>` | Operate a step's human-in-the-loop gate — see what a run is blocked on and answer it. `respond`/`cancel` confirm first and refuse without `--yes` in agent mode (an LLM must not silently auto-approve). |
-| `fruxon agents memory list/subjects/get/forget-subject <agent>` | Inspect and prune what an agent remembers. `list` filters server-side by `--subject`/`--search`/`--scope`; `forget-subject` is a GDPR-style delete (confirms; refuses without `--yes` in agent mode). |
+| `fruxon agents memory list/subjects/get/forget-subject <agent>` | Inspect and prune what an agent remembers. `list` filters server-side by `--subject`/`--query`/`--scope`; `forget-subject` is a GDPR-style delete (confirms; refuses without `--yes` in agent mode). |
 | `fruxon agents topics list/search/get/messages/sessions <agent>` + `fruxon agents inbox <agent>` | Read the conversation spine — the agent's topics (threads), one topic's transcript, its episodes, and its inbox (what it's focused on). `list`/`search` filter server-side by `--state`/`--participant`/`--query`. Read-only. Each message carries `author` — a human colleague's turn is stored as `ASSISTANT` on purpose, so `role` alone cannot tell their reply from the agent's; `HUMAN_OPERATOR` can. A message the runtime *withheld* is in no transcript at all — see `fruxon messages list`. `sessions` explains a fresh, blind session: a topic outlives its sessions, and `endCause` on the previous one (`CONSOLE_ALREADY_RESOLVED` — a human closed it in the provider's console) is why the next started with no history. |
 | `fruxon escalations list/history/unhandled/policy/ack` | What happened when an agent handed a conversation to a person. `list` is the queue (live takeovers + degraded escalations nobody was reachable for); `unhandled` is the append-only ledger under it. **`history` is the record of closed console-routed takeovers** — those leave the queue, so `list --status ALL` answers `[]` about a conversation a human worked for half an hour. Read `humanObservedAt` before believing a `RESOLVED`: null means nobody was ever seen picking it up. `policy <agent>` resolves who the *next* escalation would reach — an empty ladder under `NATIVE_HANDOFF` is correct, the console supplies the human. |
 | `fruxon messages list` | The channel ledger — including inbound an agent was never shown. A **withheld** message (a human owns the chat in the source console, or admission refused the sender) never becomes a conversation turn, so it is in no transcript and the thread reads as a customer being ignored. `--delivery WITHHELD_PENDING` lists the ones nothing has ever acted on; nothing drains them. |
@@ -138,6 +138,7 @@ Integrations + tools:
 | `fruxon keys list/mint/revoke/delete/history/scopes` | Audit and revoke scoped tokens. Minting opens the dashboard so the secret never enters the CLI process. |
 | `fruxon llm-providers list/get/models` | Browse LLM providers and models supported at the tenant level. |
 | `fruxon assets create/list/get/wait/operations/delete` | Manage knowledge-base (RAG) assets a step can query — upload local files, wait for async ingestion, inspect operations, and use the ids for `assetConfig.assetIds`. `delete` confirms + refuses without `--yes` in agent mode. |
+| `fruxon knowledge-bases consolidate/consolidation` | Find the near-duplicate articles a per-conversation merge left in an editable knowledge base and, with `--apply`, have the base's consolidator agent fold each cluster into one (union of tags, labels and sources; the rest archived with a `merged_into` label). Report-only by default; waits for the report unless `--no-wait`. |
 | `fruxon assets search/documents/chunks` | Reproduce and inspect a retrieval. `search` runs the same query an agent's `search_assets` does (`--mode HYBRID/VECTOR/FULL_TEXT`, `--top-k`, fusion weights) — note `score` is on a different scale per mode, and in hybrid the top hit is always 1.0. `documents` lists what the index contains (a `chunkCount` of 0 means that file yielded no indexable text); `chunks` reads one document's chunks in order. The `documentId` these print is the **index's** id, which is what `chunks` takes — on a knowledge base's backing asset it is not the editable document's id, and it changes whenever a document's body is re-indexed. The `fileName` (`<knowledge document id>.md`) is the document a `knowledge_base` tool would edit. |
 | `fruxon metrics list` | Browse the evaluation-metric catalog — the ids a step's LLM-judge config (`judge.metrics[]`) binds, with a default weight each. |
 | `fruxon triggers list/get/create/update/delete/fire/bind/unbind` | Manage triggers — the schedule/event sources that fire agents. `create`/`update` take `--file` (+`--schema`); `create` also takes `--application`, the Application that will own the trigger and must own everything it fires. `bind`/`unbind` wire which agents fire; `fire` runs it now. `fire`/`delete`/`unbind` confirm + refuse without `--yes` in agent mode. The control plane for autonomy. `get` returns the full stored `workShape` and every `scheduleTimes` slot, so `get -o json | jq .workShape` produces a body `update --file` can post straight back — a PATCH replaces the whole shape, so edit what you read. |
@@ -153,11 +154,11 @@ Integrations + tools:
 | `fruxon triggers set-stages <id> --file` | Replace an automation's stages without rewriting the rest of its work shape (a PATCH replaces the whole shape, so this reads it, splices, and posts). Takes a bare stages array or any document carrying one. Pre-flights the two refusals the server only reports after the write: live items at a stage your list drops, and a `door` that will re-expand `source` on save. `--dry-run` prints the merged shape and the warnings. |
 | `fruxon triggers revisions list/get/restore` | A trigger's audit history — every mutation writes a snapshot, and `changeReason` separates a config edit from a binding reconcile. `get -o json | jq .workShape` is the shape as it stood, which is how you undo an edit by hand. `restore` replays one and is **not** a universal undo: it runs the same validation a save does, so a snapshot that drops a stage still holding live items is refused. |
 | `fruxon secrets list/get/grants` | Discover tenant secrets a step can reference — the ids for `allowedSecretIds` and the `{{secret.KEY}}` names, with publish-state and per-agent grants. Metadata only; values are never returned. |
-| `fruxon participants list/get/create/update/delete/enable/disable` | Manage agent-network participants (people / groups / agents the network routes to). `list` takes `--search` (matches names **and channel addresses and account ids**, so a phone number or handle resolves to an id, and searches both directory tiers by default), `--kind`, `--tier`, `--agent`, `--environment-id`, and pages up to `--limit` / `--all`. `create`/`update` take `--file` (+`--schema`); `enable`/`disable` toggle routing; `delete` confirms + refuses without `--yes` in agent mode. |
+| `fruxon participants list/get/create/update/delete/enable/disable` | Manage agent-network participants (people / groups / agents the network routes to). `list` takes `--query` (matches names **and channel addresses and account ids**, so a phone number or handle resolves to an id, and searches both directory tiers by default), `--kind`, `--tier`, `--agent`, `--environment-id`, and pages up to `--limit` / `--all`. `create`/`update` take `--file` (+`--schema`); `enable`/`disable` toggle routing; `delete` confirms + refuses without `--yes` in agent mode. |
 | `fruxon applications roles <id>` | The Application's roster roles — who holds each, who defers to it, and how many holders are `consultable`. The answer to what a `--role` contact binding leaves open: the server takes any role string, so a role with references and no holders refuses at delivery time. `--unheld-only` lists just those. Trust the consultable count — every role path, delivery and consult alike, resolves through the consult-allowed member edges, so a holder without one is tagged but unreachable. |
 | `fruxon applications list/get` | Inspect Applications — the container that owns agents, workflows and people. Every agent belongs to exactly one, and `agents create` needs its id, so this is where you find it. Creating and re-homing an Application itself stays in the dashboard. |
 | `fruxon applications entry-points list/get/connect/attach/detach/move/update` | How inbound actually reaches an agent: an Application's claim on an external address. `list` with no Application answers "is this address already taken?". `connect` mints a new doorway (and prints the webhook URL **once**); `attach` adopts an existing one; `move` re-homes a claimed address; `detach` returns it to the Default Network. Writes — `detach`/`move` confirm first. |
-| `fruxon environments list/get/create/update/archive` | Manage end-customer environments — the slugs connector bindings and `execute(environmentSlug=…)` attribute runs to (per-customer cost tracking, quotas, analytics). `list --search` filters; `archive` confirms + refuses without `--yes` in agent mode. |
+| `fruxon environments list/get/create/update/archive` | Manage end-customer environments — the slugs connector bindings and `execute(environmentSlug=…)` attribute runs to (per-customer cost tracking, quotas, analytics). `list --query` filters; `archive` confirms + refuses without `--yes` in agent mode. |
 | `fruxon pipelines list/get` | Read collection pipelines — one Agent or Workflow run per item of a source. An agent's `pipelines.bindings` allowlist names them **by id** and `run_pipeline` refuses any id it does not name, so this is where those ids come from (`get` also lists the reusable `sourceId`s `allowedSourceIds` takes). Read-only. |
 | `fruxon capabilities list/get/create/update/delete` | Manage the consult-routing vocabulary (capabilities = name/area/description) that roster bindings and pins reference. `create`/`update` take `--file` (+`--schema`); `delete` --yes-gated in agent mode. |
 | `fruxon participants bind/unbind/roster` + `fruxon agents roster` | Wire a participant onto an agent's consult roster and set its policy (roles / urgency / response policy); `agents roster` reads who advises an agent. `unbind` --yes-gated. |

{fruxon-0.13.2 → fruxon-0.13.4}/README.md

@@ -63,7 +63,7 @@ Execution:
 | `fruxon agents executions trace <agent> <record-id>` | Step-by-step trace of one execution — LLM/tool calls, durations. `--show-io` also prints each tool step's parameters and result (the payload lives at `steps[].result`, a sibling of `toolTrace` — whose `resultDelivery` carries sizes only). |
 | `fruxon agents executions result <agent> <record-id>` | The final output one execution produced. |
 | `fruxon agents approvals list/get/respond/cancel <agent>` | Operate a step's human-in-the-loop gate — see what a run is blocked on and answer it. `respond`/`cancel` confirm first and refuse without `--yes` in agent mode (an LLM must not silently auto-approve). |
-| `fruxon agents memory list/subjects/get/forget-subject <agent>` | Inspect and prune what an agent remembers. `list` filters server-side by `--subject`/`--search`/`--scope`; `forget-subject` is a GDPR-style delete (confirms; refuses without `--yes` in agent mode). |
+| `fruxon agents memory list/subjects/get/forget-subject <agent>` | Inspect and prune what an agent remembers. `list` filters server-side by `--subject`/`--query`/`--scope`; `forget-subject` is a GDPR-style delete (confirms; refuses without `--yes` in agent mode). |
 | `fruxon agents topics list/search/get/messages/sessions <agent>` + `fruxon agents inbox <agent>` | Read the conversation spine — the agent's topics (threads), one topic's transcript, its episodes, and its inbox (what it's focused on). `list`/`search` filter server-side by `--state`/`--participant`/`--query`. Read-only. Each message carries `author` — a human colleague's turn is stored as `ASSISTANT` on purpose, so `role` alone cannot tell their reply from the agent's; `HUMAN_OPERATOR` can. A message the runtime *withheld* is in no transcript at all — see `fruxon messages list`. `sessions` explains a fresh, blind session: a topic outlives its sessions, and `endCause` on the previous one (`CONSOLE_ALREADY_RESOLVED` — a human closed it in the provider's console) is why the next started with no history. |
 | `fruxon escalations list/history/unhandled/policy/ack` | What happened when an agent handed a conversation to a person. `list` is the queue (live takeovers + degraded escalations nobody was reachable for); `unhandled` is the append-only ledger under it. **`history` is the record of closed console-routed takeovers** — those leave the queue, so `list --status ALL` answers `[]` about a conversation a human worked for half an hour. Read `humanObservedAt` before believing a `RESOLVED`: null means nobody was ever seen picking it up. `policy <agent>` resolves who the *next* escalation would reach — an empty ladder under `NATIVE_HANDOFF` is correct, the console supplies the human. |
 | `fruxon messages list` | The channel ledger — including inbound an agent was never shown. A **withheld** message (a human owns the chat in the source console, or admission refused the sender) never becomes a conversation turn, so it is in no transcript and the thread reads as a customer being ignored. `--delivery WITHHELD_PENDING` lists the ones nothing has ever acted on; nothing drains them. |
@@ -105,6 +105,7 @@ Integrations + tools:
 | `fruxon keys list/mint/revoke/delete/history/scopes` | Audit and revoke scoped tokens. Minting opens the dashboard so the secret never enters the CLI process. |
 | `fruxon llm-providers list/get/models` | Browse LLM providers and models supported at the tenant level. |
 | `fruxon assets create/list/get/wait/operations/delete` | Manage knowledge-base (RAG) assets a step can query — upload local files, wait for async ingestion, inspect operations, and use the ids for `assetConfig.assetIds`. `delete` confirms + refuses without `--yes` in agent mode. |
+| `fruxon knowledge-bases consolidate/consolidation` | Find the near-duplicate articles a per-conversation merge left in an editable knowledge base and, with `--apply`, have the base's consolidator agent fold each cluster into one (union of tags, labels and sources; the rest archived with a `merged_into` label). Report-only by default; waits for the report unless `--no-wait`. |
 | `fruxon assets search/documents/chunks` | Reproduce and inspect a retrieval. `search` runs the same query an agent's `search_assets` does (`--mode HYBRID/VECTOR/FULL_TEXT`, `--top-k`, fusion weights) — note `score` is on a different scale per mode, and in hybrid the top hit is always 1.0. `documents` lists what the index contains (a `chunkCount` of 0 means that file yielded no indexable text); `chunks` reads one document's chunks in order. The `documentId` these print is the **index's** id, which is what `chunks` takes — on a knowledge base's backing asset it is not the editable document's id, and it changes whenever a document's body is re-indexed. The `fileName` (`<knowledge document id>.md`) is the document a `knowledge_base` tool would edit. |
 | `fruxon metrics list` | Browse the evaluation-metric catalog — the ids a step's LLM-judge config (`judge.metrics[]`) binds, with a default weight each. |
 | `fruxon triggers list/get/create/update/delete/fire/bind/unbind` | Manage triggers — the schedule/event sources that fire agents. `create`/`update` take `--file` (+`--schema`); `create` also takes `--application`, the Application that will own the trigger and must own everything it fires. `bind`/`unbind` wire which agents fire; `fire` runs it now. `fire`/`delete`/`unbind` confirm + refuse without `--yes` in agent mode. The control plane for autonomy. `get` returns the full stored `workShape` and every `scheduleTimes` slot, so `get -o json | jq .workShape` produces a body `update --file` can post straight back — a PATCH replaces the whole shape, so edit what you read. |
@@ -120,11 +121,11 @@ Integrations + tools:
 | `fruxon triggers set-stages <id> --file` | Replace an automation's stages without rewriting the rest of its work shape (a PATCH replaces the whole shape, so this reads it, splices, and posts). Takes a bare stages array or any document carrying one. Pre-flights the two refusals the server only reports after the write: live items at a stage your list drops, and a `door` that will re-expand `source` on save. `--dry-run` prints the merged shape and the warnings. |
 | `fruxon triggers revisions list/get/restore` | A trigger's audit history — every mutation writes a snapshot, and `changeReason` separates a config edit from a binding reconcile. `get -o json | jq .workShape` is the shape as it stood, which is how you undo an edit by hand. `restore` replays one and is **not** a universal undo: it runs the same validation a save does, so a snapshot that drops a stage still holding live items is refused. |
 | `fruxon secrets list/get/grants` | Discover tenant secrets a step can reference — the ids for `allowedSecretIds` and the `{{secret.KEY}}` names, with publish-state and per-agent grants. Metadata only; values are never returned. |
-| `fruxon participants list/get/create/update/delete/enable/disable` | Manage agent-network participants (people / groups / agents the network routes to). `list` takes `--search` (matches names **and channel addresses and account ids**, so a phone number or handle resolves to an id, and searches both directory tiers by default), `--kind`, `--tier`, `--agent`, `--environment-id`, and pages up to `--limit` / `--all`. `create`/`update` take `--file` (+`--schema`); `enable`/`disable` toggle routing; `delete` confirms + refuses without `--yes` in agent mode. |
+| `fruxon participants list/get/create/update/delete/enable/disable` | Manage agent-network participants (people / groups / agents the network routes to). `list` takes `--query` (matches names **and channel addresses and account ids**, so a phone number or handle resolves to an id, and searches both directory tiers by default), `--kind`, `--tier`, `--agent`, `--environment-id`, and pages up to `--limit` / `--all`. `create`/`update` take `--file` (+`--schema`); `enable`/`disable` toggle routing; `delete` confirms + refuses without `--yes` in agent mode. |
 | `fruxon applications roles <id>` | The Application's roster roles — who holds each, who defers to it, and how many holders are `consultable`. The answer to what a `--role` contact binding leaves open: the server takes any role string, so a role with references and no holders refuses at delivery time. `--unheld-only` lists just those. Trust the consultable count — every role path, delivery and consult alike, resolves through the consult-allowed member edges, so a holder without one is tagged but unreachable. |
 | `fruxon applications list/get` | Inspect Applications — the container that owns agents, workflows and people. Every agent belongs to exactly one, and `agents create` needs its id, so this is where you find it. Creating and re-homing an Application itself stays in the dashboard. |
 | `fruxon applications entry-points list/get/connect/attach/detach/move/update` | How inbound actually reaches an agent: an Application's claim on an external address. `list` with no Application answers "is this address already taken?". `connect` mints a new doorway (and prints the webhook URL **once**); `attach` adopts an existing one; `move` re-homes a claimed address; `detach` returns it to the Default Network. Writes — `detach`/`move` confirm first. |
-| `fruxon environments list/get/create/update/archive` | Manage end-customer environments — the slugs connector bindings and `execute(environmentSlug=…)` attribute runs to (per-customer cost tracking, quotas, analytics). `list --search` filters; `archive` confirms + refuses without `--yes` in agent mode. |
+| `fruxon environments list/get/create/update/archive` | Manage end-customer environments — the slugs connector bindings and `execute(environmentSlug=…)` attribute runs to (per-customer cost tracking, quotas, analytics). `list --query` filters; `archive` confirms + refuses without `--yes` in agent mode. |
 | `fruxon pipelines list/get` | Read collection pipelines — one Agent or Workflow run per item of a source. An agent's `pipelines.bindings` allowlist names them **by id** and `run_pipeline` refuses any id it does not name, so this is where those ids come from (`get` also lists the reusable `sourceId`s `allowedSourceIds` takes). Read-only. |
 | `fruxon capabilities list/get/create/update/delete` | Manage the consult-routing vocabulary (capabilities = name/area/description) that roster bindings and pins reference. `create`/`update` take `--file` (+`--schema`); `delete` --yes-gated in agent mode. |
 | `fruxon participants bind/unbind/roster` + `fruxon agents roster` | Wire a participant onto an agent's consult roster and set its policy (roles / urgency / response policy); `agents roster` reads who advises an agent. `unbind` --yes-gated. |

{fruxon-0.13.2 → fruxon-0.13.4}/src/fruxon/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '0.13.2'
-__version_tuple__ = version_tuple = (0, 13, 2)
+__version__ = version = '0.13.4'
+__version_tuple__ = version_tuple = (0, 13, 4)
 
 __commit_id__ = commit_id = None

{fruxon-0.13.2 → fruxon-0.13.4}/src/fruxon/cli/__init__.py

@@ -247,6 +247,15 @@ class _FruxonTyperGroup(TyperGroup):
         except BaseException as exc:
             from fruxon.cli import _crash
 
+            # Click implements help and version as exceptions. A human's bare
+            # ``no_args_is_help`` group is another successful discovery path,
+            # despite Click retaining its historical exit code 2. Agent mode
+            # deliberately turns that same no-subcommand condition into a
+            # structured usage error below, so keep it on the failure path.
+            if _crash.is_success_exit(exc) or (_crash.is_no_args_help(exc) and not is_agent_mode()):
+                succeeded = True
+                raise
+
             duration_ms = int((_time.monotonic() - started) * 1000)
             command_name = self._command_path(ctx, entry_args)
             unexpected = _crash.is_unexpected(exc)
@@ -599,6 +608,7 @@ from fruxon.cli import examples as _examples  # noqa: E402, F401
 from fruxon.cli import guides as _guides  # noqa: E402, F401
 from fruxon.cli import integrations as _integrations  # noqa: E402, F401
 from fruxon.cli import keys as _keys  # noqa: E402, F401
+from fruxon.cli import knowledge_bases as _knowledge_bases  # noqa: E402, F401
 from fruxon.cli import llm_providers as _llm_providers  # noqa: E402, F401
 from fruxon.cli import messages as _messages  # noqa: E402, F401
 from fruxon.cli import metrics as _metrics  # noqa: E402, F401

{fruxon-0.13.2 → fruxon-0.13.4}/src/fruxon/cli/_crash.py

@@ -68,6 +68,21 @@ def is_usage_error(exc: BaseException) -> bool:
     return _is_click_exception(exc, class_name="UsageError")
 
 
+def is_success_exit(exc: BaseException) -> bool:
+    """Whether Click/Typer stopped successfully after help or version.
+
+    ``--help`` and ``--version`` use a zero-code ``Exit`` instead of returning
+    normally. Match both Click namespaces because current Typer vendors its
+    own copy while older releases use the top-level package.
+    """
+    return _is_click_exception(exc, class_name="Exit") and getattr(exc, "exit_code", 1) == 0
+
+
+def is_no_args_help(exc: BaseException) -> bool:
+    """Whether a ``no_args_is_help`` command group rendered its help."""
+    return _is_click_exception(exc, class_name="NoArgsIsHelpError")
+
+
 def _is_click_exception(exc: BaseException, *, class_name: str = "ClickException") -> bool:
     """Match Click's public exceptions and Typer's vendored equivalents."""
     import click

{fruxon-0.13.2 → fruxon-0.13.4}/src/fruxon/cli/agents.py

@@ -70,9 +70,9 @@ def agents_list(
             help="Include disabled agents (default: only enabled ones).",
         ),
     ] = False,
-    search: Annotated[
+    query: Annotated[
         str | None,
-        typer.Option("--search", help="Filter by free-text search (id, name, description)."),
+        typer.Option("--query", "-q", help="Filter by free-text query (id, name, description)."),
     ] = None,
     application: Annotated[
         str | None,
@@ -85,14 +85,14 @@ def agents_list(
     one-ID-per-line output (good for shell loops); ``--output json`` for
     machine consumption with the full agent payload we expose.
 
-    ``--search`` narrows server-side to a case-insensitive substring match on
+    ``--query`` narrows server-side to a case-insensitive substring match on
     the agent id, display name, and description. ``--application`` narrows to
     one ownership boundary (``fruxon applications list`` for the ids).
 
     Examples:
         fruxon agents list
         fruxon agents list --include-disabled
-        fruxon agents list --search invoice
+        fruxon agents list --query invoice
         fruxon agents list --application 6f1c…
         fruxon agents list --output json
         fruxon agents list --output id | xargs -n1 fruxon agents get
@@ -112,9 +112,9 @@ def agents_list(
     try:
         if stderr.is_terminal and output != "id":
             with stderr.status("[bold]Fetching agents…[/bold]"):
-                agents = client.list_agents(search=search, application=application)
+                agents = client.list_agents(query=query, application=application)
         else:
-            agents = client.list_agents(search=search, application=application)
+            agents = client.list_agents(query=query, application=application)
     except FruxonError as e:
         fail_from_api_error(e, hint=_hint_for_list_error(e))
 
@@ -138,11 +138,11 @@ def agents_list(
                 return
             if output == "id":
                 return
-            if search:
+            if query:
                 # A filter quirk, not an empty workspace — point at the filter, not onboarding.
                 say_info(
-                    f"No agents match [bold]{search}[/bold].",
-                    hint="Broaden the [bold]--search[/bold] term, or drop it to list every agent.",
+                    f"No agents match [bold]{query}[/bold].",
+                    hint="Broaden the [bold]--query[/bold] term, or drop it to list every agent.",
                 )
                 return
             say_info(

{fruxon-0.13.2 → fruxon-0.13.4}/src/fruxon/cli/agents_executions.py

@@ -81,6 +81,7 @@ _VALID_TRIGGER_TYPE = frozenset(
         "PARTICIPANT_REQUEST",
         "RELEVANCE_CHECK",
         "DOCUMENT_ENRICHMENT",
+        "KNOWLEDGE_CONSOLIDATION",
         "COLLECTION_ITEM",
         "TEST",
         "TOPIC_TURN",
@@ -150,7 +151,7 @@ def executions_list(
             "--participant",
             help=(
                 "Only runs served for this participant (Guid). Repeatable. "
-                "Resolve a phone/handle to an id with `fruxon participants list --search`."
+                "Resolve a phone/handle to an id with `fruxon participants list --query`."
             ),
         ),
     ] = None,

{fruxon-0.13.2 → fruxon-0.13.4}/src/fruxon/cli/agents_memory.py

@@ -7,7 +7,7 @@ read + GDPR surface over them: query "what does my agent remember about
 X", and forget everything about a subject.
 
 Designed for an LLM driver: ``list`` narrows **server-side** by
-``--subject`` / ``--search`` / ``--scope`` (so the agent asks precisely
+``--subject`` / ``--query`` / ``--scope`` (so the agent asks precisely
 instead of dumping everything), and ``forget-subject`` — irreversible —
 confirms first and refuses without ``--yes`` under agent mode.
 
@@ -53,7 +53,7 @@ def memory_list(
         str | None,
         typer.Option("--subject", help="Only memories about this subject (person / end-user key)."),
     ] = None,
-    search: Annotated[str | None, typer.Option("--search", help="Full-text filter over title + content.")] = None,
+    query: Annotated[str | None, typer.Option("--query", "-q", help="Full-text filter over title + content.")] = None,
     scope: Annotated[
         str | None,
         typer.Option("--scope", help="AGENT (cross-everyone facts) or SUBJECT (per-person facts)."),
@@ -72,14 +72,14 @@ def memory_list(
         ),
     ] = None,
 ):
-    """List what an agent remembers — narrow with --subject / --search / --scope.
+    """List what an agent remembers — narrow with --subject / --query / --scope.
 
     The filters run server-side, so "what does my agent remember about
     user_42" is `--subject user_42`, not a client-side scan.
 
     Examples:
         fruxon agents memory list my-agent --subject user_42
-        fruxon agents memory list my-agent --search "dark mode"
+        fruxon agents memory list my-agent --query "dark mode"
         fruxon agents memory list my-agent --scope AGENT --output id
     """
     output = resolve_output_format(output, human_default="table", agent_default="json")
@@ -95,9 +95,9 @@ def memory_list(
     try:
         if stderr.is_terminal and output != "id":
             with stderr.status(f"[bold]Fetching memories for [cyan]{agent}[/cyan]…[/bold]"):
-                memories = client.list_memories(agent, subject=subject, search=search, scope=scope_norm)
+                memories = client.list_memories(agent, subject=subject, query=query, scope=scope_norm)
         else:
-            memories = client.list_memories(agent, subject=subject, search=search, scope=scope_norm)
+            memories = client.list_memories(agent, subject=subject, query=query, scope=scope_norm)
     except FruxonError as e:
         fail_from_api_error(e, hint=_hint_for_get_error(e, agent, client))
 

{fruxon-0.13.2 → fruxon-0.13.4}/src/fruxon/cli/assets.py

@@ -1046,9 +1046,9 @@ def _render_explain_hit(
 @assets_app.command("documents")
 def assets_documents(
     asset: Annotated[str, typer.Argument(help="Asset identifier.")],
-    search: Annotated[
+    query: Annotated[
         str | None,
-        typer.Option("--search", "-q", help="Filter by file name, server-side."),
+        typer.Option("--query", "-q", help="Filter by file name, server-side."),
     ] = None,
     limit: Annotated[
         int,
@@ -1074,7 +1074,7 @@ def assets_documents(
 
     Examples:
         fruxon assets documents 2a03ed53…
-        fruxon assets documents 2a03ed53… --search handbook -o id
+        fruxon assets documents 2a03ed53… --query handbook -o id
     """
     output = resolve_output_format(output, human_default="table", agent_default="json")
     if output not in {"table", "json", "id"}:
@@ -1089,7 +1089,7 @@ def assets_documents(
     effective_limit = None if all_pages else limit
     client = build_client(workspace, base_url)
     try:
-        documents = client.list_asset_documents(asset, search=search, limit=effective_limit)
+        documents = client.list_asset_documents(asset, query=query, limit=effective_limit)
     except FruxonError as e:
         fail_from_api_error(e, hint=_hint_for_error(e))
 
@@ -1103,10 +1103,10 @@ def assets_documents(
 
     if not documents:
         say_info(
-            "No documents matched." if search else "This asset has no indexed documents.",
+            "No documents matched." if query else "This asset has no indexed documents.",
             hint=(
-                "Drop --search to see everything."
-                if search
+                "Drop --query to see everything."
+                if query
                 else f"If it was created recently, check [bold]fruxon assets operations {asset}[/bold]."
             ),
         )

{fruxon-0.13.2 → fruxon-0.13.4}/src/fruxon/cli/environments.py

@@ -46,9 +46,9 @@ app.add_typer(environments_app, name="environments")
 
 @environments_app.command("list")
 def environments_list(
-    search: Annotated[
+    query: Annotated[
         str | None,
-        typer.Option("--search", help="Case-insensitive substring filter on name, slug, and external id."),
+        typer.Option("--query", "-q", help="Case-insensitive substring filter on name, slug, and external id."),
     ] = None,
     group: Annotated[
         str | None,
@@ -76,7 +76,7 @@ def environments_list(
 
     Examples:
         fruxon environments list
-        fruxon environments list --search acme
+        fruxon environments list --query acme
         fruxon environments list --group "Emek Group"
         fruxon environments list -o json | jq '.[] | select(.isSystem|not) | .slug'
     """
@@ -92,9 +92,9 @@ def environments_list(
     try:
         if stderr.is_terminal and output != "id":
             with stderr.status("[bold]Fetching environments…[/bold]"):
-                environments = client.list_environments(search=search, group=group)
+                environments = client.list_environments(query=query, group=group)
         else:
-            environments = client.list_environments(search=search, group=group)
+            environments = client.list_environments(query=query, group=group)
     except FruxonError as e:
         fail_from_api_error(e, hint=_hint_for_error(e))
 
@@ -104,7 +104,7 @@ def environments_list(
             return
         if output == "id":
             return
-        filtered = bool(search or group)
+        filtered = bool(query or group)
         say_info(
             "No environments match." if filtered else "No environments in this workspace yet.",
             hint=None if filtered else "Create one with [bold]fruxon environments create <name>[/bold].",

{fruxon-0.13.2 → fruxon-0.13.4}/src/fruxon/cli/examples.py

@@ -175,7 +175,7 @@ _EXAMPLES: dict[str, list[tuple[str, str]]] = {
     ],
     "memory": [
         ("fruxon agents memory list my-agent --subject user_42", "What the agent remembers about one person"),
-        ("fruxon agents memory list my-agent --search 'dark mode'", "Full-text over its memories"),
+        ("fruxon agents memory list my-agent --query 'dark mode'", "Full-text over its memories"),
         ("fruxon agents memory subjects my-agent", "Which subjects it has memories about (+ counts)"),
         ("fruxon agents memory forget-subject my-agent user_42 --yes", "GDPR-forget everything about a subject"),
     ],
@@ -259,7 +259,7 @@ _EXAMPLES: dict[str, list[tuple[str, str]]] = {
     ],
     "environments": [
         ("fruxon environments list", "Browse end-customer environments (slugs runs attribute to)"),
-        ("fruxon environments list --search acme", "Filter by name / slug / external id"),
+        ("fruxon environments list --query acme", "Filter by name / slug / external id"),
         ('fruxon environments create "Acme Corp"', "Add one — the slug is generated from the name"),
         (
             'fruxon environments update 6f1c… --agent-context "VIP customer — prioritize."',

{fruxon-0.13.2 → fruxon-0.13.4}/src/fruxon/cli/integrations.py

@@ -57,7 +57,7 @@ integrations_app.add_typer(mcp_app, name="mcp")
 
 @integrations_app.command("list")
 def integrations_list(
-    search: Annotated[str | None, typer.Option("--search", help="Filter by free-text search.")] = None,
+    query: Annotated[str | None, typer.Option("--query", "-q", help="Filter by free-text query.")] = None,
     type_: Annotated[
         list[str] | None,
         typer.Option("--type", help="Filter by integration type. Repeatable."),
@@ -110,7 +110,7 @@ def integrations_list(
         if stderr.is_terminal and output != "id":
             with stderr.status("[bold]Fetching integrations…[/bold]"):
                 integrations = client.list_integrations(
-                    search=search,
+                    query=query,
                     types=type_,
                     tags=tag,
                     has_configs=has_configs,
@@ -119,7 +119,7 @@ def integrations_list(
                 )
         else:
             integrations = client.list_integrations(
-                search=search,
+                query=query,
                 types=type_,
                 tags=tag,
                 has_configs=has_configs,
@@ -137,7 +137,7 @@ def integrations_list(
             return
         say_info(
             "No integrations match."
-            if (search or type_ or tag or has_configs or has_triggers or has_channels)
+            if (query or type_ or tag or has_configs or has_triggers or has_channels)
             else "No integrations in this workspace yet.",
             hint="Create one with [bold]fruxon integrations create --file <int.json>[/bold].",
         )