@thinkingai/ae-cli 6.1.29 → 6.1.30

package/dist/{things-22KQWC23.js → things-DDQ52Z3Q.js}

@@ -1,17 +1,17 @@
 import { createRequire as __createRequire } from 'node:module'; const require = __createRequire(import.meta.url);
 import {
   resolveMemoryApiBaseUrl
-} from "./chunk-QZUVLFNR.js";
-import "./chunk-N6XBLRB7.js";
-import "./chunk-RJHGDWSC.js";
+} from "./chunk-AWVZTN2B.js";
+import "./chunk-VDICGXCY.js";
+import "./chunk-JSBLCLFE.js";
 import {
   CapabilityGatewayError,
   buildCapabilityGatewayUrl,
   callCapabilityApi
-} from "./chunk-3SDHJOCR.js";
+} from "./chunk-HRUOV6EQ.js";
 import "./chunk-Y74WTIKJ.js";
-import "./chunk-H3K5UGYC.js";
-import "./chunk-JNVVJ273.js";
+import "./chunk-SOSFRU3O.js";
+import "./chunk-4PSTYEG5.js";
 import {
   PermissionError
 } from "./chunk-Z3Q2AEIN.js";

package/dist/{update-XX4ILU7X.js → update-CTLNTX35.js}

@@ -5,7 +5,7 @@ import {
 import {
   printError,
   printOutput
-} from "./chunk-QZLRHGVH.js";
+} from "./chunk-YULUBP3R.js";
 import {
   buildVersionInstallPlan,
   exactVersion,
@@ -17,13 +17,13 @@ import {
   installVersion,
   recordVersionSyncResult,
   rememberBusinessConfig
-} from "./chunk-2UW3Y463.js";
+} from "./chunk-CG773QXN.js";
 import {
   peekCliToken
-} from "./chunk-H3K5UGYC.js";
+} from "./chunk-SOSFRU3O.js";
 import {
   getActiveHost
-} from "./chunk-JNVVJ273.js";
+} from "./chunk-4PSTYEG5.js";
 import "./chunk-Z3Q2AEIN.js";
 
 // src/commands/update.ts

package/dist/{workspace-LYDAP647.js → workspace-2CKQX2XL.js}

@@ -13,15 +13,15 @@ import {
   workspaceResourcePath,
   workspaceTargetFlags,
   workspaceTargetPath
-} from "./chunk-7JAVT5TK.js";
+} from "./chunk-E25OSZLJ.js";
 import "./chunk-RK6GLDGI.js";
 import {
   getAgentBuffer
-} from "./chunk-N6XBLRB7.js";
-import "./chunk-RJHGDWSC.js";
+} from "./chunk-VDICGXCY.js";
+import "./chunk-JSBLCLFE.js";
 import "./chunk-Y74WTIKJ.js";
-import "./chunk-H3K5UGYC.js";
-import "./chunk-JNVVJ273.js";
+import "./chunk-SOSFRU3O.js";
+import "./chunk-4PSTYEG5.js";
 import {
   CliValidationError
 } from "./chunk-Z3Q2AEIN.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thinkingai/ae-cli",
-  "version": "6.1.29",
+  "version": "6.1.30",
   "description": "CLI tool for ThinkingAI (AE) analytics platform",
   "type": "module",
   "bin": {

package/skills/ae-kb/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ae-kb
-version: 1.0.8
+version: 1.0.9
 description: 'AE knowledge base CLI manual for creating, importing read-only compiled snapshots, querying, LLM-powered ask, listing accessible knowledge bases and their sources, deterministic index/grep/read retrieval, checking status, ZIP source upload and directory management, raw child-file reading, revision-checked child updates and deletion, compiling, schema generation, URL sources, source deletion, ordinary text source creation, full reads and revision-checked editing, file/ZIP source draft replacement and restoration, and knowledge base deletion. Use when the user asks to manage AE (Agentic Engine) knowledge bases, import a compiled Markdown ZIP snapshot, upload documents or URLs to a knowledge base, query knowledge, ask knowledge bases with an LLM, list accessible knowledge bases or source metadata, inspect knowledge base indexes, search knowledge base pages, read a specific knowledge base page, check knowledge base status, generate schemas, compile knowledge, remove sources, create or edit text sources, or delete a knowledge base. To choose which knowledge base is worth searching, use the ae-kb-discovery skill first; this skill runs the retrieval once a target is chosen. Must use ae-cli kb commands and must not guess knowledge base names, scopes, page paths, source IDs, source display names, JSON payload shapes, or URL formats.'
 ---
 
@@ -29,7 +29,7 @@ Read [Publication and read contexts](references/publication.md) for company appr
 - Read operations can run directly after required inputs are known. Write operations require explicit user intent. Only `high-risk-write` commands require the CLI confirmation prompt; use `--yes` after explicit authorization.
 - Prefer `--dry-run` before destructive or broad writes when the user has not already validated the target.
 - Do not invent knowledge base names, scopes, source IDs, source display names, or JSON payloads. Ask the user or query known context when values are missing.
-- When building a `--sources` ref (or `+read --source`), copy the exact `scope` and `name` from `+list` output — run `ae-cli kb +list` first when the scope of a named knowledge base is unknown.
+- When building a `--sources` ref (or `+read --source`), copy the exact `scope` and display `name` from trusted active-source context or `+list` output. Run `ae-cli kb +list` when neither supplies the exact scope and name; never use a slug as the display name.
 - JSON flags must be valid JSON strings, usually wrapped in single quotes in shell commands.
 - Successful commands return JSON by default. Use `--format table` only when a table is easier for a human to scan. Envelope may include optional `_notice.host_compat`.
 - `--host <url>` overrides the active AE host. It is available on every command and may be placed after the subcommand, e.g. `ae-cli kb +<command> --host <url>`.
@@ -348,7 +348,9 @@ Use the deterministic retrieval primitives when an agent needs to explore knowle
 
 **Before running a real query, read [`references/query-workflow.md`](references/query-workflow.md)** — it selects the next useful retrieval step without crawling. It covers candidate indexing, copied-path grep, direct bounded reads of linked short pages, same-page read windows, linked-page re-grep when needed, optional outline-derived ranges, and coverage assessment. This section below is the per-command reference the workflow draws on.
 
-Start with `+list` or `+index` to discover accessible knowledge bases. Use `+index` when you also need navigation maps:
+Start with the trusted active sources described by `ae-kb-discovery`. Explicit references go straight to scoped retrieval without `+list`; relevant preferred candidates go first, with `+list` only if unrelated or insufficient. When no trusted active sources exist, use `+list` to discover accessible knowledge bases. Use `+index` when you also need navigation maps:
+
+When discovery is needed:
 
 ```bash
 ae-cli kb +list

package/skills/ae-kb/references/query-workflow.md

@@ -11,11 +11,12 @@ Everything below is server-side LLM-free.
 
 ## The loop
 
-This picks up **after** `ae-kb-discovery` has listed accessible knowledge bases
-and ranked candidates. Start here with a chosen candidate; scope every `+index`
-/ `+grep` / `+read` call to it with `--sources` / `--source`. If the candidate
-turns out not to cover the question, go back to `ae-kb-discovery` for the next
-candidate rather than searching everything blindly.
+This picks up **after** `ae-kb-discovery` has chosen a candidate from trusted active sources or `+list`.
+An explicit reference skips `+list` and stays within the referenced list, even when page evidence is insufficient.
+Preferred candidates are searched only when relevant; clearly unrelated candidates or evidence gaps can lead to `+list`.
+After `+list`, retrieve from at most three distinct newly discovered knowledge bases; count every new source in a multi-source `+ask` separately. Explicit references and preferred candidates do not consume that budget.
+Start here with a chosen candidate; scope every `+index` / `+grep` / `+read` call to it with `--sources` / `--source`. If the candidate turns out not to cover the question, go back to `ae-kb-discovery` for the next allowed candidate rather than searching everything blindly.
+When using `+ask` with explicit references or preferred candidates, always pass `--sources` containing only the relevant authorized sources from that active list; never omit it or include unrelated sources. For an explicit reference, insufficient evidence does not authorize expansion to another knowledge base.
 
 **Known-page fast path:** within the same host, identity, KB and published revision,
 reuse navigation and read evidence already obtained in this task. Copy exact

package/skills/ae-kb-discovery/SKILL.md

@@ -1,5 +1,6 @@
 ---
 name: ae-kb-discovery
+version: 1.0.0
 description: >
   Discover which AE (Agentic Engine) knowledge bases accessible to the current user are worth searching, and decide whether to search at all, through read-only operations. Use when the user explicitly asks to search knowledge bases, internal documentation, or company materials. Also use when a task requires internal facts or business context, or when ae-analysis sees an enabled KB auto-discovery company switch before choosing its query route. Use internal context to explain data analysis results, anomalies, or trends and form evidence-backed conclusions. Do not use if the user explicitly asks not to access knowledge bases. This skill covers discovery and candidate selection; run the actual `+index` / `+grep` / `+read` / `+ask` retrieval with the `ae-kb` skill.
 ---
@@ -32,9 +33,17 @@ Do not use this skill when:
 
 ## Discovery Workflow
 
-### 1. Get the List of Accessible Knowledge Bases
+### 1. Use Trusted Active Sources Before Discovery
 
-First, get the lightweight list of knowledge bases accessible to the current user:
+If the current turn's trusted system context supplies **explicitly referenced** knowledge bases with exact `scope` and display `name`, use only relevant references from that list. Hand them directly to `ae-kb` for scoped `+index` / `+grep` / `+read` retrieval; do not call `+list` or search an unreferenced knowledge base. If retrieved pages leave a gap, report it. A knowledge base named only in user text is not a trusted active reference.
+
+If trusted context instead supplies **preferred candidates**, compare their names, descriptions and bindings with the question. Search only relevant candidates first. If all are clearly unrelated, or their retrieved pages leave a gap, call `+list` for other accessible sources. Metadata never counts as answer evidence. Preferred candidates are not a search limit and do not consume the newly discovered source budget below.
+
+When no trusted active sources are supplied, discover accessible knowledge bases with `+list` as usual. Copy exact `scope` and display `name` from trusted context or `+list`; never derive a CLI `--sources` name from a slug alone.
+
+### 2. Get the List of Accessible Knowledge Bases When Needed
+
+When discovery is needed, get the lightweight list of knowledge bases accessible to the current user:
 
 ```bash
 ae-cli kb +list
@@ -44,7 +53,7 @@ Use the exact `scope` and knowledge base name returned by the command, together
 
 If `+list` is unavailable or fails, do not guess which knowledge bases exist. If the user explicitly requested a knowledge base search, explain that discovery cannot currently be completed. Otherwise, return to the original task and reassess the capabilities currently available.
 
-### 2. Rank Candidate Knowledge Bases
+### 3. Rank Candidate Knowledge Bases
 
 Rank candidates in this order:
 
@@ -54,9 +63,9 @@ Rank candidates in this order:
 
 Compare `targetId` with the corresponding current ID or code first. Use `targetName` only as a secondary signal when an ID or code is unavailable; do not replace a conflicting ID match with a name match. A candidate with no bindings or no current-context match remains eligible for semantic ranking. A binding to another project or space lowers implicit priority but does not exclude the candidate, and an explicit user choice still takes precedence.
 
-Select one preferred knowledge base by default. When several candidates are highly relevant, retain no more than three and try them one at a time in priority order. Do not read the indexes of all candidates in advance. A binding, name, description, tag, or language match only indicates that a knowledge base is worth searching; it does not prove a content match, grant access, or count as knowledge base evidence.
+Select one candidate to search at a time. After `+list`, retrieve from at most three distinct newly discovered knowledge bases in this task; stop when page evidence is sufficient. Every new source used by `+index`, `+grep`, `+read` or `+ask` counts once, including each source in a multi-source `+ask`. Explicit references and preferred candidates do not count toward this budget. Do not read the indexes of all candidates in advance. A binding, name, description, tag, or language match only indicates that a knowledge base is worth searching; it does not prove a content match, grant access, or count as knowledge base evidence.
 
-### 3. Hand Off to Retrieval
+### 4. Hand Off to Retrieval
 
 Once a preferred knowledge base is selected, hand off to the `ae-kb` skill and follow its `references/query-workflow.md` for the entire retrieval procedure — including when `+ask` is appropriate.
 
@@ -98,7 +107,7 @@ When using internal context to explain data analysis results, anomalies, or tren
 When knowledge base evidence provides only partial coverage, is entirely absent, or retrieval fails:
 
 1. Stop repeating searches against the same candidate knowledge base.
-2. If ranked candidates remain, switch to the next candidate. Search no more than three knowledge bases in one task.
+2. If ranked candidates remain, switch to the next candidate. After `+list`, retrieve from no more than three distinct newly discovered knowledge bases; explicit references and preferred candidates do not consume that budget.
 3. When all candidates provide no coverage, return to the user's original request instead of remaining in the knowledge base retrieval subtask.
 4. Reassess the capabilities currently available and choose the next path that best serves the original task. Do not hard-code a fixed fallback.
 5. Retain verified background evidence when useful, but never attribute conclusions drawn from other sources to a knowledge base.