unique-sdk 2026.30.0.dev2__tar.gz → 2026.30.0.dev4__tar.gz

{unique_sdk-2026.30.0.dev2 → unique_sdk-2026.30.0.dev4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: unique-sdk
-Version: 2026.30.0.dev2
+Version: 2026.30.0.dev4
 Summary: 
 Author: Martin Fadler, Konstantin Krauss, Andreas Hauri
 Author-email: Martin Fadler <martin.fadler@unique.ch>, Konstantin Krauss <konstantin@unique.ch>, Andreas Hauri <andreas@unique.ch>

{unique_sdk-2026.30.0.dev2 → unique_sdk-2026.30.0.dev4}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "unique_sdk"
-version = "2026.30.0.dev2"
+version = "2026.30.0.dev4"
 description = ""
 readme = "README.md"
 license = { text = "MIT" }

{unique_sdk-2026.30.0.dev2 → unique_sdk-2026.30.0.dev4}/unique_sdk/cli/commands/search.py

@@ -261,9 +261,16 @@ def cmd_search(
             "searchString": query,
             "searchType": "COMBINED",
             "limit": limit,
+            # An unscoped search must send an explicit ``scopeIds: null``,
+            # never omit the key. An absent key reaches node-ingestion as
+            # ``undefined`` and is destructure-defaulted to ``[]``, which
+            # getScopes treats as "restrict to zero scopes" — an entire-KB
+            # search then returns nothing on companies without file-based
+            # access. A JSON ``null`` bypasses both the default and the
+            # truthy check, matching what unique_toolkit's
+            # search_content_chunks sends. See UN-22753.
+            "scopeIds": scope_ids or None,
         }
-        if scope_ids:
-            search_params["scopeIds"] = scope_ids
         if metadata_filter:
             search_params["metaDataFilter"] = metadata_filter
 

{unique_sdk-2026.30.0.dev2 → unique_sdk-2026.30.0.dev4}/unique_sdk/cli/skills/unique-cli-search/SKILL.md

@@ -7,10 +7,7 @@ description: >-
   platform. Use whenever the user asks to find, search, or query documents
   or content on Unique, including filtering by folder or metadata.
   Also covers `unique-cli read <cont_id>` for reading the full indexed text
-  of a document when its content ID is already known, and
-  `unique-cli uploaded-search "<query>"` for searching documents uploaded for
-  the current task/row, which are NOT in the knowledge-base scope and never
-  appear in `unique-cli search`.
+  of a document when its content ID is already known.
   NOTE: This search uses combined vector + full-text indexing. Excel
   (.xlsx/.xls), CSV (.csv), and image files are NOT full-text indexed,
   so they will not appear in search results. To locate these file types,
@@ -95,43 +92,10 @@ unique-cli search "audit" -m department=Legal -m year=2025
 unique-cli search "regulatory" -f /Legal -m year=2025 -l 50
 ```
 
-## Searching Uploaded Documents (`uploaded-search`)
-
-Documents **uploaded for the current task** (e.g. an Agentic Table row's
-attached files) are **not** part of the knowledge-base folder scope. They will
-**never** appear in `unique-cli search` results, no matter the folder or
-metadata filters — uploaded files are scoped to the chat, not to a KB folder.
-Use `uploaded-search` to retrieve them:
-
-```bash
-# Search the documents uploaded for this row/task
-unique-cli uploaded-search "target asset classes and investment strategy"
-
-# Limit results
-unique-cli uploaded-search "fee structure" --limit 50
-```
-
-When to use which:
-
-| You want to search… | Command |
-|---------------------|---------|
-| The knowledge base (folders the task scope grants) | `unique-cli search "<query>"` |
-| Documents uploaded for **this** row/task | `unique-cli uploaded-search "<query>"` |
-
-`uploaded-search` returns the same `<sourceN>...</sourceN>` blocks as `search`
-and shares the **same per-turn citation manifest**, so `[sourceN]` numbering is
-continuous across both commands within a turn — cite an uploaded-document fact
-exactly the same way (`[sourceN]`). If no documents were uploaded for the task,
-the command reports that and you should fall back to `unique-cli search`.
-
-> **Note:** there is no `--folder`/`--metadata` for `uploaded-search` — the set
-> of uploaded documents is fixed by what was attached to the task.
-
 ## Command Reference
 
 ```
 unique-cli search <query> [--folder <path|scope_id>] [--metadata <key=value>]... [--limit <N>]
-unique-cli uploaded-search <query> [--limit <N>]
 ```
 
 | Option | Short | Default | Description |

unique_sdk-2026.30.0.dev4/unique_sdk/cli/skills/unique-cli-uploaded-search/SKILL.md

@@ -0,0 +1,113 @@
+---
+name: unique-cli-uploaded-search
+description: >-
+  Search the documents uploaded for the CURRENT task/row (e.g. an Agentic
+  Table row's attached files) via the `unique-cli uploaded-search "<query>"`
+  command, with the same per-turn citation tracking as `unique-cli search`
+  so cited facts render as `<sup>N</sup>` footnotes and clickable reference
+  chips on the Unique platform. ALWAYS use this skill when the user refers to
+  documents they uploaded/attached to this task, or when you need facts from
+  the task's own attached files. These uploaded files are scoped to the chat,
+  NOT to a knowledge-base folder, so they will NEVER appear in
+  `unique-cli search` results no matter the folder or metadata filters. Use
+  `unique-cli search` for the knowledge base and this command for the task's
+  uploaded documents; the two are complementary and citation numbering is
+  shared across them within a turn.
+---
+
+# Unique CLI -- Uploaded Document Search
+
+Documents **uploaded for the current task** (for example an Agentic Table
+row's attached files) are **not** part of the knowledge-base folder scope.
+They are scoped to the chat, so they will **never** appear in
+`unique-cli search` results — no folder or metadata filter can surface them.
+Use `unique-cli uploaded-search` to retrieve them.
+
+## Basic Usage
+
+```bash
+# Search the documents uploaded for this row/task
+unique-cli uploaded-search "target asset classes and investment strategy"
+
+# Limit results
+unique-cli uploaded-search "fee structure" --limit 50
+```
+
+There is **no** `--folder`/`--metadata` for `uploaded-search` — the set of
+uploaded documents is fixed by what was attached to the task.
+
+If no documents were uploaded for this task, the command reports that and you
+should fall back to `unique-cli search` for the knowledge base.
+
+## When to use which command
+
+| You want to search… | Command |
+|---------------------|---------|
+| The knowledge base (folders the task scope grants) | `unique-cli search "<query>"` |
+| Documents uploaded for **this** row/task | `unique-cli uploaded-search "<query>"` |
+
+## Output Format
+
+Each result is rendered as a `<sourceN>...</sourceN>` block, identical to
+`unique-cli search`. `N` is **1-based** and **shared with `unique-cli search`
+within the same turn** — both commands append to the same per-turn citation
+manifest, so numbering stays continuous across them (a `search` call that
+emitted `<source1>`–`<source3>` is followed by an `uploaded-search` call whose
+first result is `<source4>`).
+
+```
+Found 1 result(s):
+
+<source1>
+<|document|>investment-mandate.pdf</|document|>
+<|page|>2</|page|>
+<|info|>cont_abc123</|info|>
+...the mandate targets EMEA equities with a 5% cap per issuer...
+</source1>
+```
+
+## Citation Rules
+
+Cite a fact from `uploaded-search` results with `[sourceN]`, **exactly** as you
+would for `unique-cli search` — the two share the same namespace and manifest.
+The Unique platform converts each `[sourceN]` marker in your final answer into a
+`<sup>N</sup>` footnote and a clickable reference chip.
+
+```
+The uploaded mandate caps single-issuer exposure at 5% [source1].
+```
+
+**Rules** (enforced by the platform's reference post-processor):
+
+1. **`[sourceN]` is for KB and uploaded-document results.** Web results from
+   `unique-cli web-search` use `[websourceN]` — never mix the two namespaces.
+2. Only cite numbers you saw in the **current** turn's `search` /
+   `uploaded-search` output. Numbers from previous turns are stale and will be
+   silently dropped.
+3. Write `source` in singular form with the number in digits: `[source1]`,
+   `[source2]` — not `[Source 1]` or `[source one]`.
+4. Prefer citing each fact with a single, most-relevant source.
+5. Do not invent source numbers for remembered or inferred facts.
+
+## Command Reference
+
+```
+unique-cli uploaded-search <query> [--limit <N>]
+```
+
+| Option | Short | Default | Description |
+|--------|-------|---------|-------------|
+| `--limit` | `-l` | 200 | Max results |
+
+## Prerequisites
+
+Requires these environment variables:
+
+```bash
+UNIQUE_USER_ID    # User ID (required)
+UNIQUE_COMPANY_ID # Company ID (required)
+UNIQUE_API_KEY    # API key — optional on localhost / secured cluster
+UNIQUE_APP_ID     # App ID — optional on localhost / secured cluster
+```
+
+Install: `pip install unique-sdk`

{unique_sdk-2026.30.0.dev2 → unique_sdk-2026.30.0.dev4}/unique_sdk/cli/state.py

@@ -263,6 +263,14 @@ class ShellState:
         """Return True if *content_id* is in the current workspace scope.
 
         Precedence (UN-21780):
+        0. Per-row uploaded documents (``.unique-uploaded.json``) surfaced by
+           ``unique-cli uploaded-search`` are task inputs that live *outside* the
+           KB scope boundary by design, so neither the metadata filter nor the
+           static ``scopeIds`` path below would admit them. Exempt them for
+           non-destructive access so the agent can ``read``/``ls``/``cite`` a doc
+           it just found via uploaded-search — mirroring the chat-file exemption.
+           Mutating ops (``rm``/``mv``) pass ``allow_chat_files=False`` and stay
+           denied, so an uploaded input can't be deleted or renamed this way.
         1. A per-message UniqueQL ``metaDataFilter`` (e.g. an Agentic Table
            column's ``scope_rules``) is the authority for this turn and
            *replaces* the static ``scopeIds`` for content access. Files the
@@ -275,6 +283,8 @@ class ShellState:
            ``is_folder_target_within_workspace``).
         3. With neither configured, everything is in scope.
         """
+        if allow_chat_files and content_id in self.uploaded_search_content_ids:
+            return True
         if self.workspace_metadata_filter is not None:
             if allow_chat_files and content_id in self._chat_file_content_ids():
                 return True