@autorag/librarian 2.10.3 → 2.10.4

package/README.md

@@ -140,8 +140,9 @@ does, and searches them right alongside your files:
   or connect your own provider key and pay the provider directly.
 
 > [!TIP]
-> **The app's source lives in [NomaDamas/AutoRAG-app](https://github.com/NomaDamas/AutoRAG-app)**
-> (Electron + React, AGPL-3.0). It depends on `@autorag/librarian` from this
+> **The Dazzi desktop app's source lives in [NomaDamas/AutoRAG-app](https://github.com/NomaDamas/AutoRAG-app)**
+> (Electron + React, [Fair Source](https://fair.io/) under `FSL-1.1-MIT`). It
+> depends on the open-source `@autorag/librarian` engine (Apache-2.0) from this
 > repository; build, run, and file app issues there.
 
 ### One engine, every surface
@@ -150,7 +151,7 @@ The app is one way in. The same librarian runs everywhere else:
 
 | Surface | Use it for | Start here |
 |---|---|---|
-| **Desktop app** | Browsing and asking in one window | [NomaDamas/AutoRAG-app](https://github.com/NomaDamas/AutoRAG-app) |
+| **Desktop app (Dazzi)** | Browsing and asking in one window | [NomaDamas/AutoRAG-app](https://github.com/NomaDamas/AutoRAG-app) (Fair Source, FSL-1.1-MIT) |
 | **Terminal UI** | Interactive, steerable search sessions | [`autorag tui`](#2-search-from-cli) |
 | **CLI** | Scripts, indexing, health checks | [CLI Command Reference](#cli-command-reference) |
 | **MCP server** | Feeding retrieval to Claude Code, Codex, and other agents | [AutoRAG Lite MCP Server](#autorag-lite-mcp-server) |
@@ -263,6 +264,25 @@ autorag refresh
 autorag status
 ```
 
+### Excluding files and folders
+
+Leave generated workspaces or archives out when initializing:
+
+```bash
+autorag init --search-paths "$HOME/Documents" \
+  --exclude "$HOME/Documents/Build output" \
+  --exclude "$HOME/Documents/Archive, old"
+```
+
+Repeat `--exclude` for each file or folder. Each argument is one complete path,
+including spaces and commas; relative paths resolve from the current directory.
+Excluding a folder also excludes its descendants. Paths are literal, not globs.
+
+For an existing configuration, edit its `excludePaths` array and run
+`autorag refresh` to update the indexes. File-name search applies exclusions to
+native fsearch and Everything results as well as the filesystem walk. See the
+[exclusion configuration examples](docs/minsync-setup.md#excluding-files-and-folders).
+
 ### Document languages and parsers
 
 One global `languages` setting describes the corpus. It is resolved from

package/dist/agent/agent.d.ts

@@ -247,7 +247,7 @@ export interface AutoRAGAgentOptions {
      * `searchPaths`). Enabled by default on Windows; ignored elsewhere.
      * `false` disables it. The remaining fields are test seams.
      */
-    everything?: Omit<EverythingClientOptions, "root" | "folders"> | false;
+    everything?: Omit<EverythingClientOptions, "root" | "folders" | "excludeFolders"> | false;
     /**
      * macOS/Linux-only instant file/folder name search through the user's
      * fsearch-cli (FSearch, GPL — spawned as a separate process, never

package/dist/agent/answer-guidelines.d.ts

@@ -17,3 +17,20 @@ export declare const ANSWER_IMAGE_DELTA_RULE = "An image already embedded in the
  * caller only ever sees numbered citations backed by recorded evidence.
  */
 export declare const ANSWER_CITATION_RULE = "**Citations**: cite supporting evidence inline with the evidence id shown next to each retrieved result, in square brackets (e.g. [e3], or [e3][e7] for two). Copy ids exactly; never invent one. For a local file you opened yourself with `bash`, cite `[file:<absolute path>]`. Cite the evidence that backs a sentence at the end of that sentence. Do not cite numbers, paths, or anything else.";
+/**
+ * Deliverable/artifact rule (issue #1832). The 5-bullet cap and direct-answer
+ * format remain the default unless the user explicitly asks otherwise; when the
+ * caller requests a deliverable (a reply email, letter, legal opinion, summary
+ * document, insertable case citation block, checklist, report, or workflow
+ * document), the agent produces the complete finished artifact as a file in a
+ * format aligned with the context and domain, and keeps the answer itself
+ * concise by stating the created file's location and briefly summarizing what
+ * was generated (citing only the underlying source evidence).
+ */
+export declare const ANSWER_DELIVERABLE_RULE = "**Deliverables and artifacts**: if the user asks you to draft, write, generate, or prepare a deliverable or artifact (a reply email, letter, legal opinion, summary document, standard-format case citation block, checklist, report, or workflow document \u2014 including requests phrased as \"how should I reply...\" to a specific message), produce the finished, ready-to-use artifact as a file (using `write`, `edit`, or `bash` in local sessions, without overwriting existing source files) in a file format, extension, and structure aligned with the context and domain (e.g. `.eml` or `.md`/`.txt` with headers for an email reply; `.md`, `.txt`, `.docx`, `.hwp`, or `.pdf` matching workspace conventions for a legal opinion, insertable case-citation block, or summary document; `.csv`, `.xlsx`, or `.json` for structured tabular data), containing the complete unabridged artifact (including required headers, precedent passages, pinpoint paragraphs, and standard-format citations) inside the file instead of merely describing how to produce it. Do NOT dump the full artifact text into your reply: unless the user explicitly requests otherwise, keep your reply concise within the at-most-5-bullet direct-answer format, clearly stating the created file's exact path/location and briefly summarizing what was generated with inline citations to the underlying source evidence (`[eN]` or `[file:<source path>]`); never cite the newly created deliverable file itself as `[file:...]`.";
+/**
+ * Verification-phase deliverable rule: create the context-aligned deliverable
+ * file (in local sessions) and report its location and concise summary if the
+ * fast-phase draft could not write the file yet or only gave advice about it.
+ */
+export declare const ANSWER_DELIVERABLE_DELTA_RULE = "If a deliverable or artifact was requested and the first answer could not write the file yet (the fast phase runs without tool calls) or only gave advice about it, create the complete context-aligned deliverable file now during verification and report the created file's location and a brief summary concisely.";

package/dist/cli/commands/types.d.ts

@@ -1,6 +1,8 @@
 export interface CommandContext {
     positionals: string[];
     flags: Record<string, string | boolean | undefined>;
+    /** All values of repeatable flags, in command-line order. */
+    repeatedFlags?: Readonly<Record<string, readonly string[]>>;
     json: boolean;
     debug: boolean;
     cwd: string;

package/dist/cli/index.d.ts

@@ -5,6 +5,7 @@ export type { CommandName };
 interface ParsedArgs {
     positionals: string[];
     flags: Record<string, string | boolean>;
+    repeatedFlags?: Readonly<Record<string, readonly string[]>>;
 }
 export declare function parseArgs(argv: readonly string[]): ParsedArgs | {
     error: string;