@gmickel/gno 2.7.0 → 2.8.0

package/README.md

@@ -139,7 +139,7 @@ See the [guide](docs/COMPILED-CONTEXT.md).
 
 <!-- public-truth:current-version -->
 
-> Current source version: **v2.7.0**. See [CHANGELOG.md](./CHANGELOG.md).
+> Current source version: **v2.8.0**. See [CHANGELOG.md](./CHANGELOG.md).
 
 <!-- /public-truth -->
 
@@ -184,9 +184,8 @@ See the [guide](docs/COMPILED-CONTEXT.md).
   explicit read-only retrieval smoke from Connectors.
 - **One resident gateway**: `gno serve` and `gno daemon` now host stateful
   Streamable HTTP MCP at `/mcp` from the same long-lived runtime as their
-  watcher, jobs, stores, and models. The packed npm smoke proves two-client
-  parity, warm reuse, redacted lifecycle status, fail-closed security, restart,
-  and shutdown.
+  watcher, jobs, stores, and models. Several MCP clients can share one
+  resident process and get the same results as stdio MCP.
 - **Knowledge Delta**: `gno changes`, `gno diff`, and `gno impact` expose
   bounded metadata-only history, structural change summaries, and explainable
   dependency paths across CLI, REST, MCP, and SDK.
@@ -215,17 +214,14 @@ See the [guide](docs/COMPILED-CONTEXT.md).
   `local_only`, `lan`, or `remote` boundary that follows mixed and derived
   evidence through resident serving, inference, publishing, exports, Capsules,
   and traces. Authentication never overrides policy.
-- **Source availability (`any` | `local`)**: opt-in `local` refuses
-  cloud-placeholder materialization on the macOS File Provider layouts covered
-  by physical evidence (Google Drive, iCloud Drive, and OneDrive for both
-  validated immediate SharePoint library roots). Hierarchical directory
-  classification + guarded content recheck; skips are not conversion errors;
-  unproven prefixes preserve indexed descendants. Distinct from egress.
-  Unsupported platforms fail closed; no claim of zero provider activity or
-  universal provider support. On the controlled 5,000-file all-local corpus,
-  production `any` regressed -1.1280% and hierarchical `local` added 1.1841%
-  median traversal overhead (2 warmups, 9 samples per lane; same corpus and
-  interleaved pre-implementation/current production walkers).
+- **Source availability (`any` | `local`)**: opt-in `local` indexes only files
+  already on disk and never makes a cloud provider download one. Supported on
+  macOS with Google Drive (My Drive and Shared drives), iCloud Drive, and
+  OneDrive SharePoint library roots.
+  Cloud-only files are skipped and reported, not treated as conversion errors,
+  and documents under a cloud-only folder stay indexed. Other platforms fail
+  with an error. On a 5,000-file all-local collection, `local` scans about 1%
+  slower than `any`.
 - **Read-only integrity audits**: `gno audit` and MCP `gno_audit` inspect local
   links, declared provenance, and source/index freshness offline. Stable,
   bounded findings distinguish complete, partial, unavailable, and changing
@@ -240,7 +236,7 @@ See the [guide](docs/COMPILED-CONTEXT.md).
 <!-- public-truth:default-embed-model -->
 - **Default Embed Model**: all four built-in presets use `Qwen3-Embedding-0.6B-GGUF`; see the dated, fixture-scoped evidence below
 <!-- /public-truth -->
-- **Regression Fixes**: tightened phrase/negation/hyphen/underscore BM25 behavior, cleaned non-TTY hyperlink output, improved `gno doctor` chunking and embedding fingerprint visibility, and fixed the embedding autoresearch harness
+- **Regression Fixes**: tightened phrase/negation/hyphen/underscore BM25 behavior, cleaned non-TTY hyperlink output, and improved `gno doctor` chunking and embedding fingerprint visibility
 
 ### Upgrading Existing Collections
 
@@ -1318,10 +1314,10 @@ Current product stance:
 
 Why Qwen is the current default:
 
-- matches or exceeds `bge-m3` on the tiny canonical benchmark
-- significantly beats `bge-m3` on the real GNO `src/serve` code slice
-- also beats `bge-m3` on a pinned public-OSS code slice
-- also beats `bge-m3` on the multilingual prose/docs benchmark lane
+- ties `bge-m3` on the small [canonical code benchmark](./evals/fixtures/code-embedding-benchmark/canonical.md) (vector nDCG@10 `0.95` each)
+- beats `bge-m3` on [GNO's own web server code](./evals/fixtures/code-embedding-benchmark/repo-serve.md) (`0.8102` vs `0.1003`)
+- beats `bge-m3` on [pinned open-source code slices](./evals/fixtures/code-embedding-benchmark/oss-slices.md) (`1.0` vs `0.6116`)
+- beats `bge-m3` on the multilingual prose/docs benchmark below
 
 Current trade-off:
 
@@ -1340,7 +1336,7 @@ bun run bench:general-embeddings --candidate qwen3-embedding-0.6b --write
 
 <!-- public-truth:general-embedding-benchmark -->
 
-The immutable April 2026 FastAPI-docs run used 15 documents in five corpus
+The April 2026 FastAPI-docs run used 15 documents in five corpus
 languages (`en`, `de`, `fr`, `es`, `zh`) and 13 queries:
 
 - [bge-m3 incumbent](./evals/fixtures/general-embedding-benchmark/2026-04-06-bge-m3-incumbent.md): vector nDCG@10 `0.3503`, hybrid nDCG@10 `0.642`
@@ -1362,23 +1358,23 @@ languages.
 
 <!-- public-truth:cjk-lexical-benchmark -->
 
-Lexical fallback has separate evidence. The immutable
+Lexical fallback has separate evidence. The
 [July 22, 2026 CJK result](./evals/fixtures/cjk-lexical-benchmark/2026-07-22.md)
 uses 21 synthetic documents and 25 same-language queries across Chinese,
-Japanese, and Korean. Production BM25 lexical results and frozen floors:
+Japanese, and Korean. Production BM25 lexical results and the promotion floors:
 
 - Chinese: baseline Recall@10 `0.2222`, nDCG@10 `0.1481`, zero-result `0.7778`; promotion Recall@10 `0.4722`, nDCG@10 `0.3981`, maximum zero-result `0.5278`
 - Japanese: baseline Recall@10 `0.125`, nDCG@10 `0.125`, zero-result `0.875`; promotion Recall@10 `0.375`, nDCG@10 `0.375`, maximum zero-result `0.625`
 - Korean: baseline Recall@10 `0.5`, nDCG@10 `0.5`, zero-result `0.5`; promotion Recall@10 `0.75`, nDCG@10 `0.75`, maximum zero-result `0.25`
 
-The
+The "promotion" values are the floors a CJK-aware lexical analyzer must reach
+before GNO ships one.
 [promotion-gates.md](./evals/fixtures/cjk-lexical-benchmark/promotion-gates.md)
-also bind MRR, non-regression, and cost requirements. This lexical result does
-not reduce or replace the semantic evidence above. All positive qrels use
-relevance `3`, so
-nDCG measures placement but not distinctions among positive gain grades.
-Production tokenization is unchanged; improvements remain gated work for
-`fn-109`.
+lists them along with MRR, non-regression, and cost requirements. No analyzer
+has met them, so production BM25 tokenization is unchanged. These lexical
+numbers do not measure semantic retrieval. All positive qrels use relevance
+`3`, so nDCG measures placement but not distinctions among positive gain
+grades.
 
 <!-- /public-truth -->
 

package/assets/skill/SKILL.md

@@ -352,6 +352,12 @@ offline audits inspect parsed local links, explicitly declared capture/logical-
 record provenance, and observable source/index freshness. They never repair,
 rewrite, persist findings, judge factual truth, or replace retrieval.
 
+`--max-findings` accepts `all` (MCP `maxFindings: "all"`) to export every
+finding. Link findings carry `referenceKind`, `resolutionStatus`, and
+`resolvedScope` in their evidence detail; ambiguous vault links list the tied
+`candidates`. Report `truncation.snapshotTruncated` as "totals cover the
+bounded snapshot, not the whole index".
+
 Treat exit `4` as a complete report with findings. Exit `5` or report status
 `partial`/`changed_during_audit` means evidence is unavailable, inconclusive,
 cancelled, truncated, or repeatedly changed—never healthy. Preserve stable
@@ -389,7 +395,7 @@ remaining steps apply under the default `full` profile.
    - MCP text is the compact `gno-context-agent-v1` evidence projection. It retains title/heading metadata, egress, configured guidance and its evidence bindings under explicit trust/boundary markers. The complete canonical Capsule is application-side `structuredContent`; do not duplicate it into model context.
 3. Use `gno_ask` only for explicit local verified synthesis. Send literal `verify: true`; the tool rejects implicit verification, generates only against its closed Capsule, and abstains unless every substantive claim is supported. Preserve exact spans, gaps, semantic capability state, and abstention. This does not guarantee corpus completeness or source truth.
 4. Use `gno_query` for interactive lookup or manual retrieval control. It returns snippets plus `uri`, `docid`, often `line`, and sometimes `context`. Treat `context` as user-configured guidance for interpreting that exact result; cite source content at the returned URI/lines, not the guidance itself. Bounded graph expansion is on by default; set `graph: false` or `noGraph: true` only for an explicit BM25/vector-only path.
-5. Use graph/link expansion for relationship context: `gno_graph_query` for typed relationship traversal, `gno_graph_neighbors` for nearby documents, `gno_graph_path` for "how are X and Y connected?", `gno_links`/`gno_backlinks` for one-document link expansion, and `gno_similar` for semantic neighbors. Prefer explicit or typed edges over inferred, ambiguous, or similarity edges when confidence matters.
+5. Use graph/link expansion for relationship context: `gno_graph_query` for typed relationship traversal, `gno_graph_neighbors` for nearby documents, `gno_graph_path` for "how are X and Y connected?", `gno_links`/`gno_backlinks` for one-document link expansion, and `gno_similar` for semantic neighbors. Prefer explicit or typed edges over inferred, ambiguous, or similarity edges when confidence matters. Plain `[[Note]]` links resolve across collections of the same vault (link workspace), so backlinks and impact can name other collections; pass `collection`/`collections` to keep results inside the user's scope. Never tell users to rewrite links into `[[collection:Note]]` to make them resolve.
 6. Use `gno_query_diagnose` when a known target document should have appeared but did not; it reports BM25/vector/fusion/graph/rerank stage presence and filter state.
 7. Use `gno_get` with `fromLine`/`lineCount` for targeted reads, or `gno_multi_get` to batch top refs.
 8. Use `gno_section` only when you need a durable section locator or must re-resolve one after edits. Prefer search → `gno_get` for ordinary retrieval. `action=create` needs `ref` plus exactly one of `anchor`|`line`; `action=resolve` needs `ref` plus `target`. Cite or open content only for `exact`/`recovered` results, then follow the tool's ready-to-use `gno_get` guidance (`fromLine = lineStart`; `lineCount = lineEnd - lineStart + 1`). Never navigate or cite `ambiguous`/`stale`/`missing`.
@@ -418,6 +424,7 @@ changed source:
 gno changes --since 2026-07-20T00:00:00Z --json
 gno diff gno://notes/plan.md --json
 gno impact gno://notes/plan.md --max-depth 3 --json
+gno impact gno://notes/plan.md --collection notes --json   # stay in scope
 ```
 
 Treat cursors and change IDs as opaque. Journal results are bounded,

package/assets/skill/cli-reference.md

@@ -594,7 +594,8 @@ gno impact gno://notes/plan.md --max-depth 3 --json
 `changes` accepts an ISO time or opaque cursor and optional collection/limit.
 `diff` reports structural headings, links, and typed-relationship changes for
 one retained change. `impact` follows inbound evidence edges with explicit
-depth/node/edge/frontier/visited bounds. Expired journal history is reported,
+depth/node/edge/frontier/visited bounds; repeat `-c, --collection <name>` to
+keep the traversal (and every path step) inside those collections. Expired journal history is reported,
 not reconstructed.
 
 ## Private Retrieval Traces
@@ -679,6 +680,12 @@ gno backlinks <ref> [options]
 `--relation <type>` to query semantic typed edges instead of positional
 wiki/markdown links. Do not combine `--type` with `--edge-type`.
 
+Plain `[[Note]]` and `[[Folder/Note]]` links resolve across all collections
+that share one vault (the nearest `.obsidian` folder, or `workspaceRoot` in
+the config): exact path, then same folder, then shallowest file; ties stay
+unresolved and are listed by `gno audit links`. JSON names the other
+collection (`resolvedCollection` for links, `sourceCollection` for backlinks).
+
 ### gno graph query
 
 Bounded typed-edge traversal from a document.

package/assets/skill/examples.md

@@ -314,7 +314,8 @@ gno similar gno://notes/auth.md --cross-collection
 # In your documents:
 
 See [[API Design]] for details.
-Check [[work:Project Plan]] for cross-collection link.
+Check [[Projects/Plan]] for a path link (resolves across collections of one vault).
+Check [[work:Project Plan]] to name the target collection explicitly.
 Read [[Security#OAuth]] for specific section.
 ```
 

package/assets/skill/mcp-reference.md

@@ -144,7 +144,9 @@ lives in `structuredContent`; its text projection is deliberately compact and
 should not be expanded back into duplicate model context.
 
 Use `gno_changes`, `gno_diff`, and `gno_impact` for retained metadata history
-and bounded dependency questions. Use `gno_trace_list` and `gno_trace_show` for
+and bounded dependency questions. `gno_impact` takes optional `collections`
+to keep the traversal in scope; links in a vault can resolve across
+collections, so unscoped graph tools cover every collection. Use `gno_trace_list` and `gno_trace_show` for
 private local diagnostics. Invoke `gno_trace_label` only when the user
 explicitly provides a relevant, irrelevant, or missing-expected judgment.
 Trace export/replay/delete/purge and saved-Capsule watch lifecycle remain

package/browser-extension/artifacts/gno-browser-clipper-v2.8.0.zip.sha256

@@ -0,0 +1 @@
+2066003653182eb93964c5c058c86f691abf536f5093d1d0e8db2f382aedce19  gno-browser-clipper-v2.8.0.zip

package/browser-extension/dist/manifest.json

@@ -21,5 +21,5 @@
   "content_security_policy": {
     "extension_pages": "script-src 'self'; object-src 'none'; connect-src http://127.0.0.1:*"
   },
-  "version": "2.7.0"
+  "version": "2.8.0"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gmickel/gno",
-  "version": "2.7.0",
+  "version": "2.8.0",
   "description": "Local semantic search for your documents. Index Markdown, PDF, and Office files with hybrid BM25 + vector search.",
   "keywords": [
     "embeddings",
@@ -89,6 +89,7 @@
     "smoke:serve-shutdown": "bun scripts/serve-shutdown-smoke.ts",
     "test:watcher:filesystem": "bun test test/serve/watch-service-filesystem.test.ts test/serve/resident-runtime.test.ts",
     "bench:watcher-reconciliation": "bun scripts/watcher-reconciliation-benchmark.ts",
+    "bench:session-import": "bun scripts/session-import-benchmark.ts",
     "smoke:watcher-reconciliation": "bun scripts/watcher-reconciliation-smoke.ts",
     "bench:code-embeddings": "bun scripts/code-embedding-benchmark.ts",
     "bench:code-embeddings:write": "bun scripts/code-embedding-benchmark.ts --write",

package/spec/cli.md

@@ -263,6 +263,8 @@ gno status [--json|--md]
     {
       "name": "work",
       "path": "/path",
+      "workspaceRoot": "/vault",
+      "workspaceSource": "detected",
       "documentCount": 100,
       "chunkCount": 500,
       "embeddedCount": 500
@@ -624,9 +626,11 @@ refuses descent into dataless or availability-unknown directories
 (`DATALESS_DIRECTORY` skip, or the fail-closed codes above) and preserves
 previously indexed descendants under those unproven prefixes rather than
 marking them inactive. Eligible files have no availability `errorCode`.
-Evidence-qualified scope: Google Drive, iCloud Drive, and OneDrive only for the
-tested OS/provider configuration; OneDrive only for both validated immediate
-SharePoint library roots. No Windows/Linux guarantee; metadata/provider
+Evidence-qualified scope: Google Drive (`My Drive` and immediate Shared drives
+under `Shared drives/<drive>`; the `Shared drives` folder itself is
+unsupported), iCloud Drive, and OneDrive only for the tested OS/provider
+configuration; OneDrive only for the two validated immediate SharePoint library
+roots. No Windows/Linux guarantee; metadata/provider
 bookkeeping may occur; GNO does not pin/evict/download as product behavior.
 Source availability is distinct from `egressPolicy` (where derived content may
 travel).
@@ -886,6 +890,15 @@ projection.
 content-free decision, lineage, partial disclosure, audit metadata, and
 remediation contract.
 
+`workspaceSource` is `detected` (nearest `.obsidian/` ancestor-or-self of the
+collection root), `configured` (`workspaceRoot` setting), `disabled`
+(`workspaceRoot: false`), `unavailable` (the root or an ancestor could not be
+inspected; links stay collection-scoped) or `none`. `workspaceRoot` is the
+effective workspace root, present only for `detected`/`configured`, and is a
+same-host-only field like `path`. Terminal output adds a `Link workspace:` line
+per workspace collection. `gno collection list` reports the same per
+collection as `effectiveWorkspaceRoot` and `workspaceSource`.
+
 ### gno audit
 
 Read-only, offline knowledge-integrity audits. This command is distinct from
@@ -901,8 +914,17 @@ gno audit [links|provenance|freshness|all] [--collection <name>...] \
   [--json] [--output <path>]
 ```
 
-The default category is `all`; `--max-findings` defaults to 100 and is bounded
-to 1–1000. Truncation limits returned findings but preserves exact totals.
+The default category is `all`; `--max-findings` defaults to 100 and accepts an
+integer from 1 to 100000 or `all`. `all` returns every finding of the bounded
+audit snapshot, and per-rule caps follow the same value. Any other value
+(zero, negative, non-integer, above 100000) is a validation error (exit 1)
+that states the accepted range. Truncation limits returned findings but
+preserves exact totals. The report's `truncation` block reports three separate
+conditions: `findingsTruncated` (the finding cap cut the list),
+`snapshotTruncated` (the bounded snapshot of 50,000 documents/links was cut, so
+totals cover the snapshot only and are not complete-index totals), and
+`evidenceTruncated` (evidence items, tied-candidate lists, or evidence detail
+text were shortened).
 `--output` writes only the requested report artifact with local file
 permissions. Human output renders the same report represented by
 `audit-report.schema.json`.
@@ -924,6 +946,20 @@ healthy.
 - `4` — complete report with findings
 - `5` — partial, inconclusive, unavailable, or changed-during-audit evidence
 
+Link findings resolve with the workspace-aware resolver (see
+docs/ARCHITECTURE.md "Resolution"). Their evidence `detail` JSON carries
+separate `referenceKind` (`wiki-name`, `wiki-path`, `explicit-collection`,
+`markdown`), `resolutionStatus` (`unresolved`, `ambiguous`) and
+`resolvedScope` (`same-collection`, `cross-collection`, `explicit-collection`,
+or null when unresolved). Ambiguous workspace links add `candidateCount` and
+`candidates` (tied candidate URIs in canonical path order); in a
+collection-scoped audit, candidates outside the requested collections are
+counted in `candidatesWithheld` and never named, and a list longer than the
+detail bound sets `candidatesTruncated` (and `truncation.evidenceTruncated`).
+Orphans stay "no incoming or outgoing resolved links", with connectivity drawn
+from the whole index even when the audited documents are scoped; a tied link
+connects nothing.
+
 The JSON contract is versioned as `gno://schemas/audit-report@1.0`. Finding IDs
 are stable SHA-256 identities derived from rule, normalized subject/location,
 and load-bearing evidence. Wall-clock timing and traversal order do not affect
@@ -4179,13 +4215,19 @@ Find active documents that depend on one document through inbound typed,
 wiki-link, or Markdown-link edges.
 
 ```bash
-gno impact <doc> [--max-depth <n>] [--max-nodes <n>] [--max-edges <n>] [--frontier-limit <n>] [--visited-limit <n>] [--json]
+gno impact <doc> [-c, --collection <name>...] [--max-depth <n>] [--max-nodes <n>] [--max-edges <n>] [--frontier-limit <n>] [--visited-limit <n>] [--json]
 ```
 
 The traversal is cycle-safe and enforces depth, node, edge, frontier, and
 visited-row caps. Every impacted document includes one deterministic
 dependency-to-root evidence path. JSON output uses `impact.schema.json`.
 
+`--collection` (repeatable) limits the traversal to those collections: only
+their documents are visited, returned, or used as a path step, so a document
+outside the scope never bridges two in-scope documents. Omitted means every
+indexed collection. An unknown collection, or a `<doc>` outside the requested
+collections, is a validation error (exit 1).
+
 **Exit Codes:**
 
 - 0: Success

package/spec/db/schema.sql

@@ -172,7 +172,6 @@ CREATE TABLE IF NOT EXISTS documents (
 );
 
 CREATE INDEX IF NOT EXISTS idx_documents_collection ON documents(collection);
-CREATE INDEX IF NOT EXISTS idx_documents_active ON documents(active);
 CREATE INDEX IF NOT EXISTS idx_documents_mirror_hash ON documents(mirror_hash);
 CREATE INDEX IF NOT EXISTS idx_documents_docid ON documents(docid);
 CREATE INDEX IF NOT EXISTS idx_documents_uri ON documents(uri);

package/spec/mcp.md

@@ -351,7 +351,8 @@ Collection names are case-insensitive on input and normalized to lowercase in re
 `gno_audit` is a read-only, offline tool that returns the same
 `gno://schemas/audit-report@1.0` report as `gno audit`. Its closed input accepts
 `category` (`links`, `provenance`, `freshness`, or `all`), collection/path/tag
-filters, and `maxFindings` (1–1000). `maxAgeDays`, `orphanRoots`, and
+filters, and `maxFindings` (an integer from 1 to 100000, or `"all"` for every
+finding of the bounded snapshot; default 100). `maxAgeDays`, `orphanRoots`, and
 `orphanIgnorePrefixes` are optional explicit policy inputs. Request
 cancellation returns a partial report rather than a false clean result. The
 tool is annotated with
@@ -1841,8 +1842,15 @@ pending), `sourceUnavailable`, `staleParser` and last import time, and the
 switches, pending and running work, last run, last success, next due time,
 recovery action). The result contains no host paths.
 
+Each call (and each `gno_sessions_import` call) first re-reads the server's
+config file and adopts it when it changed, so source changes made by another
+process show without a restart. An unchanged file is a no-op; a source-only
+change keeps open HTTP sessions.
+
 **Errors:** `SESSIONS_NOT_CONFIGURED` when the server's config has no
-`sessions` block.
+`sessions` block; `SESSIONS_RUNTIME_FAILURE` when the config file cannot be
+read (never answered from the stale config); `SESSIONS_BINDING_MISMATCH` when
+the file is now bound to a different index (not adopted).
 
 ### gno_sessions_import
 
@@ -2371,7 +2379,14 @@ structure is derived from `structureDelta.truncated`.
 
 ### gno_impact
 
-Read-only inbound dependency traversal for `ref`. Inputs `maxDepth`,
+Read-only inbound dependency traversal for `ref`. Optional `collections`
+(array of collection names) limits the traversal as `gno impact --collection`
+does; omitted means every collection. Over Streamable HTTP, egress policy is
+checked on `collections` (every collection when omitted, because the result
+can reach any collection a link resolves into) and on the collection of `ref`;
+a docid `ref` is checked against every collection. The same rule applies to
+`gno_backlinks` and `gno_graph*` refs, and `gno_similar` with
+`crossCollection: true` is checked against every collection. Inputs `maxDepth`,
 `maxNodes`, `maxEdges`, `frontierLimit`, and `visitedLimit` use the same bounds
 as CLI/REST/SDK. Structured content is `impact.schema.json`; each impacted
 document includes a deterministic evidence path over typed or backlink

package/spec/output-schemas/audit-report.schema.json

@@ -260,13 +260,27 @@
     "truncation": {
       "type": "object",
       "additionalProperties": false,
-      "required": ["findingsTruncated", "maxFindings"],
+      "required": [
+        "findingsTruncated",
+        "maxFindings",
+        "snapshotTruncated",
+        "evidenceTruncated"
+      ],
       "properties": {
         "findingsTruncated": { "type": "boolean" },
         "maxFindings": {
-          "type": "integer",
-          "minimum": 1,
-          "maximum": 1000
+          "oneOf": [
+            { "type": "integer", "minimum": 1, "maximum": 100000 },
+            { "const": "all" }
+          ]
+        },
+        "snapshotTruncated": {
+          "type": "boolean",
+          "description": "The bounded audit snapshot was cut; finding totals cover the snapshot only, not the whole index"
+        },
+        "evidenceTruncated": {
+          "type": "boolean",
+          "description": "Evidence items, candidate lists, or evidence detail text were shortened"
         }
       }
     },

package/spec/output-schemas/backlinks.schema.json

@@ -28,6 +28,10 @@
                 "type": "string",
                 "description": "Source document title"
               },
+              "sourceCollection": {
+                "type": "string",
+                "description": "Collection of the linking document (may differ from the target's in a link workspace)"
+              },
               "linkText": {
                 "type": "string",
                 "description": "Link display text"

package/spec/output-schemas/collection-list.schema.json

@@ -6,7 +6,7 @@
   "type": "array",
   "items": {
     "type": "object",
-    "required": ["name", "path", "pattern", "include", "exclude"],
+    "required": ["name", "pattern", "include", "exclude"],
     "properties": {
       "name": {
         "type": "string",
@@ -15,7 +15,7 @@
       },
       "path": {
         "type": "string",
-        "description": "Absolute path to collection root directory"
+        "description": "Absolute path to collection root directory. Same-host callers only: omitted for a remote REST caller."
       },
       "pattern": {
         "type": "string",
@@ -39,6 +39,19 @@
       "languageHint": {
         "type": "string",
         "description": "BCP-47 language hint for the collection"
+      },
+      "workspaceRoot": {
+        "description": "Configured link workspace: an absolute path joins the collection to that workspace root; false keeps links inside the collection. Absent means auto-detect. Same-host callers only: omitted for a remote REST caller.",
+        "oneOf": [{ "type": "string" }, { "const": false }]
+      },
+      "effectiveWorkspaceRoot": {
+        "type": "string",
+        "description": "CLI list only: effective link workspace root (nearest .obsidian folder, or the configured root). Absent when links stay inside the collection."
+      },
+      "workspaceSource": {
+        "type": "string",
+        "enum": ["none", "detected", "configured", "disabled", "unavailable"],
+        "description": "CLI list only: how the link workspace was set"
       }
     }
   }

package/spec/output-schemas/graph.schema.json

@@ -92,6 +92,8 @@
                 "enum": [
                   "exact-title",
                   "exact-path",
+                  "exact-name",
+                  "tie-break",
                   "path-fallback",
                   "ambiguous-fallback",
                   "similarity"

package/spec/output-schemas/links-list.schema.json

@@ -78,6 +78,10 @@
                 "type": "string",
                 "description": "URI of resolved target document"
               },
+              "resolvedCollection": {
+                "type": "string",
+                "description": "Collection of the resolved target (may differ from the source's in a link workspace)"
+              },
               "resolvedTitle": {
                 "type": "string",
                 "description": "Title of resolved target document"

package/spec/output-schemas/status.schema.json

@@ -90,24 +90,18 @@
     },
     "configPath": {
       "type": "string",
-      "description": "Path to config file"
+      "description": "Path to config file. Same-host callers only: omitted for a remote REST or HTTP MCP caller."
     },
     "dbPath": {
       "type": "string",
-      "description": "Path to SQLite database"
+      "description": "Path to SQLite database. Same-host callers only: omitted for a remote REST or HTTP MCP caller."
     },
     "collections": {
       "type": "array",
       "description": "Collection statistics",
       "items": {
         "type": "object",
-        "required": [
-          "name",
-          "path",
-          "documentCount",
-          "chunkCount",
-          "embeddedCount"
-        ],
+        "required": ["name", "documentCount", "chunkCount", "embeddedCount"],
         "properties": {
           "name": {
             "type": "string",
@@ -115,7 +109,22 @@
           },
           "path": {
             "type": "string",
-            "description": "Collection root path"
+            "description": "Collection root path. Same-host callers only: omitted for a remote REST or HTTP MCP caller."
+          },
+          "workspaceRoot": {
+            "type": "string",
+            "description": "Effective link workspace root: plain wiki links resolve across every collection under it. Present only when the collection is in a workspace. Same-host callers only: omitted for a remote REST or HTTP MCP caller."
+          },
+          "workspaceSource": {
+            "type": "string",
+            "enum": [
+              "none",
+              "detected",
+              "configured",
+              "disabled",
+              "unavailable"
+            ],
+            "description": "How the link workspace was set: detected (nearest .obsidian folder), configured (workspaceRoot setting), disabled (workspaceRoot: false), unavailable (root could not be inspected; links stay collection-scoped), none (no workspace)"
           },
           "documentCount": {
             "type": "integer",
@@ -595,13 +604,14 @@
           "type": "array",
           "items": {
             "type": "object",
-            "required": ["label", "path", "reason"],
+            "required": ["label", "reason"],
             "properties": {
               "label": {
                 "type": "string"
               },
               "path": {
-                "type": "string"
+                "type": "string",
+                "description": "Suggested folder path. Same-host callers only: omitted for a remote REST or HTTP MCP caller."
               },
               "reason": {
                 "type": "string"
@@ -883,10 +893,11 @@
         },
         "cache": {
           "type": "object",
-          "required": ["path", "totalSizeBytes", "totalSizeLabel"],
+          "required": ["totalSizeBytes", "totalSizeLabel"],
           "properties": {
             "path": {
-              "type": "string"
+              "type": "string",
+              "description": "Model cache directory. Same-host callers only: omitted for a remote REST or HTTP MCP caller."
             },
             "totalSizeBytes": {
               "type": "integer",
@@ -941,7 +952,6 @@
                   "role",
                   "uri",
                   "cached",
-                  "path",
                   "sizeBytes",
                   "statusLabel"
                 ],
@@ -957,7 +967,8 @@
                     "type": "boolean"
                   },
                   "path": {
-                    "type": ["string", "null"]
+                    "type": ["string", "null"],
+                    "description": "Cached model file, or null when not cached. Same-host callers only: omitted for a remote REST or HTTP MCP caller."
                   },
                   "sizeBytes": {
                     "type": ["integer", "null"],