@hraness/kb 0.18.0 → 0.19.0

package/README.md

@@ -14,34 +14,67 @@ system.
 Bun 1.3.14 or newer is required.
 
 ```sh
-bun add --global @hraness/kb@0.18.0
+bun add --global @hraness/kb@0.19.0
+kb --help
 ```
 
-## Why kb
-
-- **Inspect what agents recover.** Markdown and Git stay authoritative,
-  retrieval signals stay distinct, and indexes, embeddings, and graph views
-  remain replaceable.
-- **Keep the application independent.** Application code imports neither the
-  vault nor a hosted knowledge service. Capture and semantic adapters declare
-  their network, browser, native-tool, and model-download effects.
-
-## Create one durable note
+## Keep one decision available to the next session
 
-From a directory without an existing `kb/` path, this local task creates a
-vault, writes one typed note, and finds it without a network request or
-embedding model:
+Suppose a parser must stop retrying after three attempts. Record that constraint
+in a note, then link the plan that will implement it:
 
-```sh
+```shell
 kb init kb
 kb note create notes/parser-contract \
-  --title "Parser contract" --type concept --tag architecture --root kb
-kb search "parser contract" --root kb --mode exact
+  --title "Parser contract" --type concept --tag architecture \
+  --body "Parser retries stop after three attempts." --root kb
+kb note create plans/parser-v2 \
+  --title "Parser v2" --type plan \
+  --body "The plan implements [[notes/parser-contract|the parser contract]]." \
+  --root kb
+```
+
+The first `kb note create` command stores ordinary Markdown at
+`kb/notes/parser-contract.md` and assigns its stable `document_id`. Add the
+exact code boundary to that note's frontmatter so path lookup can recover it:
+
+```yaml
+repository_scopes:
+  - packages/parser
 ```
 
-The note is stored at `kb/notes/parser-contract.md`. Exact search reads the
-current Markdown and returns that record. Commit the vault when it should
-travel with the repository.
+Commit the vault with the repository. The Markdown and its Git history are the
+durable record.
+
+## Recover the stopped session
+
+In a later session, start from the code path and inspect each independent
+signal:
+
+```shell
+kb context packages/parser/src/index.ts --root kb --repo .
+kb search "why parser retries stop" --root kb --mode exact \
+  --history --repo .
+kb backlinks notes/parser-contract --root kb
+kb history notes/parser-contract --root kb --repo .
+```
+
+| Signal | What it recovers |
+| --- | --- |
+| Markdown | The current parser constraint in the file you can review and edit. |
+| Backlinks | The plan that explicitly links to the constraint. |
+| Exact search | The current note matched from its words, without a network request or embedding model. |
+| Repository context | Inherited `AGENTS.md` guides and records scoped to `packages/parser`. |
+| Git history | The commits and bounded co-change evidence associated with the note. |
+
+Together, those views recover the persisted decision, related plan, applicable
+rules, and provenance needed to resume the work. They do not reconstruct
+private chat or prove that the note is still correct. Open the returned
+Markdown and guides before acting on them.
+
+The boundaries stay visible: Markdown and Git are authoritative, backlinks and
+indexes are replaceable views, and Git work is opt-in. Application code imports
+neither the vault nor a hosted knowledge service.
 
 <!-- hraness:kb-landing:end -->
 
@@ -51,22 +84,6 @@ travel with the repository.
 [KB source on GitHub](https://github.com/hraness/kb) ·
 [KB overview](https://hraness.com/kb)
 
-## Use
-
-```sh
-kb init kb
-kb clip https://example.com/article --output articles
-kb pdf ./report.pdf --output articles
-kb percolate notes/topic --root .
-kb context packages/parser/src/index.ts --root kb --repo .
-kb list --where type=plan --scope packages/parser --root .
-kb links notes/topic --root . --direction both
-kb search "parser-v2" --root . --mode exact
-kb portfolio search "parser-v2" --registry kb-portfolio.json \
-  --workspace .. --shared
-kb history search packages/parser --root . --repo .. --json
-```
-
 ## A knowledge base for your coding agents
 
 > Give coding agents durable, searchable memory beside the repository with plain Markdown, Git history, and replaceable local search.
@@ -171,6 +188,14 @@ Retrieval is bounded. The high-level `kb search` and `KnowledgeBaseSession.searc
 
 Each note owns its outbound typed relationships in frontmatter. KB derives backlinks, inverse edges, and bounded traversal at read time, so parallel agents do not contend on one generated fact file. `kb percolate <note>` reports recurring concepts and missing-link candidates with inspectable support but writes nothing. An agent reads the cited notes before creating a reusable concept or relationship. Semantic similarity never creates an edge automatically.
 
+Percolation Result V2 presents a missing relationship as an unordered pair of
+notes with a required predicate. It does not choose the source, direction, or a
+`related-to` fallback. Recommended authored predicates include `synthesizes`,
+`evidenced-by`, `informed-by`, `supersedes`, and `contradicts`; they are an
+advisory vocabulary, so a vault can use another canonical predicate when its
+prose and evidence define the claim. KB never infers reciprocal, inverse,
+transitive, or similarity-derived relationships.
+
 Git provenance is opt-in. A search without `--history` performs no Git indexing. `--history` requests best-effort provenance, while `--require-history` rejects unavailable history or incomplete provenance for the selected notes. If one commit exceeds the 2,000-path detail limit, KB retains its identity and vault-local note associations, marks its co-change detail incomplete, and continues through later commits. Best-effort search reports that requested lane as partial.
 
 Local attachment checks cover Markdown and Obsidian references to images, PDFs, and editable tldraw sources. They reject missing or escaping files while leaving external URLs alone. A source-inbox view separately lists recent captures that have no inbound disposition from maintained knowledge. It is an advisory, not an automatic backlink requirement: a saved source may intentionally remain a leaf.
@@ -187,69 +212,45 @@ The same mixed-cache, single-run test recorded p95 latencies of 44.345 milliseco
 
 Search finds candidates. Similarity does not establish that a passage is current, correct, or supported by its sources. The Markdown, cited captures, explicit relationships, and requested Git history supply the material a reader must inspect.
 
+### Customize through an approved proposal
+
+The Agent Skill routes setup and evolution requests before it prepares a
+runtime. It inspects the proposed location without mutation, interviews the
+user about the memory questions the KB should answer, and presents exact read
+and write targets. Only the approved targets may be scaffolded. A changed path,
+repository, account, integration, or companion skill requires renewed
+approval.
+
+The standard router may be enough. A recurring ritual can instead receive a
+companion skill with explicit inputs, authority, durable outputs, idempotence,
+failure behavior, and verification. These skills are inert instructions. They
+do not create a plugin runtime, execute vault metadata, inherit ambient account
+access, or couple application code to the KB. An exact repeat is a no-op;
+divergence, path escape, symbolic links, partial writes, and unapproved
+external surfaces stop the workflow.
+
+The repository's fake-capability suite exercises those transitions. It is a
+tested contract example, not proof that every agent or host integration
+complies.
+
+This workflow builds on Frank Chen's public notes about [designing a personal
+knowledge base with an
+agent](https://gist.github.com/fxchen/773397095d7a6bffda621e4237da0da9)
+and [extending it with
+skills](https://gist.github.com/fxchen/09cb410b22c9c5256d80243ee925b57e).
+
+KB ships no `kb_role` metadata, lifecycle resolver or API, lifecycle CLI,
+compatibility diagnostic, or metadata migration. A frozen Phase 0 value gate
+must show that those surfaces improve deterministic agent decisions before they
+are introduced. Current and historical plan routing remains derived from
+existing type, path, and status conventions.
+
 ### Adopt the smallest useful split
 
 Start with a short inherited `AGENTS.md` path for rules whose omission would make an edit wrong. A small knowledge base may need only Markdown, Git, an index page, and ordinary file search. Add source capture when evidence keeps disappearing. Add repository scopes when agents need to recover current memory from code paths. Add metadata or hybrid search when file search stops answering the repository's questions. Add links and graph views only when the relationships themselves help people make decisions.
 
 Treat the knowledge base as repository-adjacent durable memory. Authored Markdown and Git are the record; catalogs, indexes, embeddings, and graph views are replaceable ways to find and inspect it. Checks can validate structure, captures can preserve a selected surface, and similarity can suggest candidates. None of those mechanisms proves that a source is trustworthy or an explanation is still true. People and agents must revise the knowledge as the repository changes.
 
-## Upgrade to v0.18.0
-
-Version 0.18.0 adds a review-only adoption seam for exact dependency closures
-from an Oh working authority. Trusted host code creates a
-`createOhAdoptionPreparerV1` facade with the expected binding and head,
-destination, rights clearance, review route, and conflict policy. The narrow
-`prepare` call accepts only a capsule plus transformation and redaction
-disclosures, returns deeply immutable deterministic Markdown and manifest
-bytes with status `prepared`, and has no vault, Git, Oh-store, or promotion
-capability. KB pins `@hraness/oh` v0.2.0 and delegates closure integrity to its
-official store verifier.
-
-## Upgrade to v0.17.3
-
-Version 0.17.3 restructures the README around an inspectable first task,
-explicit operating boundaries, and a shorter path from installation to useful
-output. Runtime APIs and package behavior are unchanged.
-
-## Upgrade to v0.17.2
-
-Version 0.17.2 improves package discovery through focused npm keywords, a more
-specific README opening, and direct links between npm, GitHub, and the project
-overview. Runtime APIs and package behavior are unchanged.
-
-## Upgrade to v0.17.1
-
-Version 0.17.1 adds the public `@hraness/kb` npm installation path without
-changing the runtime API introduced in 0.17.0. Bun `1.3.14` or newer is now an
-explicit package requirement. Consumers should review the package's declared
-dual-use capture boundary and the lifecycle scripts used by optional browser
-and native search adapters before enabling those scripts.
-
-## Upgrade to v0.17.0
-
-Version 0.17 adds selected portfolio federation, stable note identities,
-qualified external relations, search rules, capture inspection, and untrusted
-context packing. Consumers with typed fixtures or custom capture writers should
-make these migrations before upgrading:
-
-- Capture writers now emit manifest schema v4 and must provide the stored
-  document `path`, exact UTF-8 `bytes`, and lowercase SHA-256 digest. The reader
-  can inspect schema v1-v3, but verification reports their document integrity as
-  unavailable instead of success.
-- `DecisionContextOutput.search` has been removed. Consume the bounded untrusted
-  `context` projection and its `truncated` flag instead of transporting the raw
-  search result into an agent prompt.
-- `VaultAnalysis` fixtures must include `externalAuthoredRelations`, even when
-  the value is an empty array. This keeps qualified authored edges distinct
-  from locally resolved graph edges.
-- `createNote` and `kb note create` now assign `document_id` to new ordinary
-  notes. Preserve that ID across renames and update snapshots that intentionally
-  assert the generated frontmatter.
-
-Existing Markdown is not rewritten automatically. Add IDs to maintained legacy
-notes only through reviewed edits, and keep every QMD, graph, portfolio, and
-audit projection disposable.
-
 ## Installation reference
 
 [Bun](https://bun.sh/docs/installation) is the required runtime.
@@ -259,9 +260,9 @@ audit projection disposable.
 Copy this prompt into Codex, Claude Code, or another coding agent:
 
 ```text
-Install the `kb` Agent Skill from `hraness/kb#v0.18.0` with the standard skills
+Install the `kb` Agent Skill from `hraness/kb#v0.19.0` with the standard skills
 CLI. Use the skill's runtime instructions to install the exact
-`@hraness/kb@0.18.0` registry release only when the command is missing. Verify it
+`@hraness/kb@0.19.0` registry release only when the command is missing. Verify it
 with `kb doctor` and `kb --help`, but do not initialize or modify a vault until
 I ask.
 ```
@@ -269,25 +270,25 @@ I ask.
 Install the single public skill with either runner:
 
 ```sh
-npx skills add hraness/kb#v0.18.0
-bunx skills add hraness/kb#v0.18.0
+npx skills add hraness/kb#v0.19.0
+bunx skills add hraness/kb#v0.19.0
 ```
 
 Both commands discover the same `kb` skill and install it into the selected
 agent runner. Skill installation is inert: it does not initialize a vault,
 refresh a catalog, or edit Markdown. When invoked, the skill uses an existing
 `kb` command or, when the command is missing, checks for Bun and installs the
-CLI from the immutable `@hraness/kb@0.18.0` npm version.
+CLI from the immutable `@hraness/kb@0.19.0` npm version.
 
 The public skills CLI reads `skills/kb/` from the repository. The immutable
-`0.18.0` npm package includes the same tree under
+`0.19.0` npm package includes the same tree under
 `node_modules/@hraness/kb/skills/kb/`, and the package check verifies that the
 installed skill is byte-identical to the repository source.
 
 Install the two global commands with Bun:
 
 ```sh
-bun add --global @hraness/kb@0.18.0
+bun add --global @hraness/kb@0.19.0
 kb --help
 kb-evaluation-builder --help
 ```
@@ -295,7 +296,7 @@ kb-evaluation-builder --help
 The same registry package can be installed with npm:
 
 ```sh
-npm install --global --ignore-scripts @hraness/kb@0.18.0
+npm install --global --ignore-scripts @hraness/kb@0.19.0
 kb --help
 ```
 
@@ -308,7 +309,7 @@ reviewed and enabled; run `kb doctor` to inspect the resulting capabilities.
 For programmatic use, add the exact npm version to a Bun project:
 
 ```sh
-bun add --exact @hraness/kb@0.18.0
+bun add --exact @hraness/kb@0.19.0
 ```
 
 The resulting dependency should remain exact:
@@ -316,12 +317,12 @@ The resulting dependency should remain exact:
 ```json
 {
   "dependencies": {
-    "@hraness/kb": "0.18.0"
+    "@hraness/kb": "0.19.0"
   }
 }
 ```
 
-Version 0.18.0 retains three public GitHub dependencies: `@hraness/oh` at
+Version 0.19.0 retains three public GitHub dependencies: `@hraness/oh` at
 immutable release `v0.2.0` for closure verification,
 `@steipete/sweet-cookie` at Hraness release `v0.4.2` for the cookie-scope safety
 fork, and `@tobilu/qmd` at commit
@@ -507,7 +508,12 @@ Predicates use lower-kebab-case. Local targets use exact vault-root IDs without
 `.md`; cross-vault targets use canonical stable `kb://` URIs. `kb graph`, `kb backlinks`, `kb relation list`, and `kb links` derive
 inverse edges and bounded paths without injecting reciprocal or inferred facts into notes.
 `kb percolate` proposes reusable concepts and missing connections with explicit
-support; an agent reviews the cited prose before authoring anything.
+support; an agent reviews the cited prose before authoring anything. In its V2
+result, a missing relationship is an unordered endpoint pair with a required
+predicate, never an executable directed assertion or an automatic
+`related-to`. Common reviewed claims use `synthesizes`, `evidenced-by`,
+`informed-by`, `supersedes`, or `contradicts`; other canonical custom predicates
+remain valid when their meaning is supported.
 
 Within a portfolio, a note can target a stable cross-vault identity such as
 `kb://hraness/sleepyland/sound-wellness-expansion`. The target vault must be
@@ -580,20 +586,98 @@ diffs, and the explicit local job ledger are available from
 The repository ships one reusable `kb` Agent Skill under `skills/kb/`. Its
 intent router loads focused references only when a task needs them: querying
 repository context and agent memory, capturing URLs or PDFs, writing durable
-plans, promoting concepts and typed relationships, or refreshing and checking
-a vault. The package smoke test keeps future tagged packages byte-identical to
+plans, promoting concepts and typed relationships, refreshing and checking a
+vault, or designing a setup through an interview and approved proposal. An
+approved setup may scaffold a bounded companion skill for a distinct recurring
+ritual. The package smoke test keeps future tagged packages byte-identical to
 that source tree.
 
 ```sh
-npx skills add hraness/kb#v0.18.0
+npx skills add hraness/kb#v0.19.0
 # or
-bunx skills add hraness/kb#v0.18.0
+bunx skills add hraness/kb#v0.19.0
 ```
 
 The skill invokes the installed `kb` command without depending on a repository
-checkout. Its runtime setup installs the pinned CLI only when the command is
-missing, and it never initializes or mutates a vault as an installation side
-effect. The repository's phase-orchestration skill remains available to local
-repository agents but is marked internal, so public skill discovery omits it.
+checkout. It routes setup and evolution before runtime preparation. For
+execution workflows, runtime setup installs the pinned CLI only when the
+command is missing, and it never initializes or mutates a vault as an
+installation side effect. The repository's phase-orchestration skill remains
+available to local repository agents but is marked internal, so public skill
+discovery omits it.
 
 See [Design](docs/design.md), [Portfolio federation](docs/portfolio.md), [Agent workflow](docs/agent-workflow.md), [PDF capture](docs/pdf.md), and [Contributing](CONTRIBUTING.md) for the durable contracts and development gate. hraness/kb is available under the [MIT License](LICENSE).
+
+## Release notes
+
+### Upgrade to v0.19.0
+
+Version 0.19.0 adds interview-first setup and evolution guidance, a bounded
+filesystem-only companion-skill scaffold contract, and Percolation Result V2.
+V2 requires an explicit predicate and leaves relationship ownership and
+direction to review. The release does not add lifecycle metadata, a resolver,
+a lifecycle CLI, inferred edges, or automatic account and network actions.
+
+### Upgrade to v0.18.1
+
+Version 0.18.1 restructures the public README and hosted projection around one
+durable note, the exact recovery workflow, inspectable retrieval signals, and
+explicit authority boundaries. Runtime APIs and package behavior are
+unchanged.
+
+### Upgrade to v0.18.0
+
+Version 0.18.0 adds a review-only adoption seam for exact dependency closures
+from an Oh working authority. Trusted host code creates a
+`createOhAdoptionPreparerV1` facade with the expected binding and head,
+destination, rights clearance, review route, and conflict policy. The narrow
+`prepare` call accepts only a capsule plus transformation and redaction
+disclosures, returns deeply immutable deterministic Markdown and manifest
+bytes with status `prepared`, and has no vault, Git, Oh-store, or promotion
+capability. KB pins `@hraness/oh` v0.2.0 and delegates closure integrity to its
+official store verifier.
+
+### Upgrade to v0.17.3
+
+Version 0.17.3 restructures the README around an inspectable first task,
+explicit operating boundaries, and a shorter path from installation to useful
+output. Runtime APIs and package behavior are unchanged.
+
+### Upgrade to v0.17.2
+
+Version 0.17.2 improves package discovery through focused npm keywords, a more
+specific README opening, and direct links between npm, GitHub, and the project
+overview. Runtime APIs and package behavior are unchanged.
+
+### Upgrade to v0.17.1
+
+Version 0.17.1 adds the public `@hraness/kb` npm installation path without
+changing the runtime API introduced in 0.17.0. Bun `1.3.14` or newer is now an
+explicit package requirement. Consumers should review the package's declared
+dual-use capture boundary and the lifecycle scripts used by optional browser
+and native search adapters before enabling those scripts.
+
+### Upgrade to v0.17.0
+
+Version 0.17 adds selected portfolio federation, stable note identities,
+qualified external relations, search rules, capture inspection, and untrusted
+context packing. Consumers with typed fixtures or custom capture writers should
+make these migrations before upgrading:
+
+- Capture writers now emit manifest schema v4 and must provide the stored
+  document `path`, exact UTF-8 `bytes`, and lowercase SHA-256 digest. The reader
+  can inspect schema v1-v3, but verification reports their document integrity as
+  unavailable instead of success.
+- `DecisionContextOutput.search` has been removed. Consume the bounded untrusted
+  `context` projection and its `truncated` flag instead of transporting the raw
+  search result into an agent prompt.
+- `VaultAnalysis` fixtures must include `externalAuthoredRelations`, even when
+  the value is an empty array. This keeps qualified authored edges distinct
+  from locally resolved graph edges.
+- `createNote` and `kb note create` now assign `document_id` to new ordinary
+  notes. Preserve that ID across renames and update snapshots that intentionally
+  assert the generated frontmatter.
+
+Existing Markdown is not rewritten automatically. Add IDs to maintained legacy
+notes only through reviewed edits, and keep every QMD, graph, portfolio, and
+audit projection disposable.

package/dist/authoring.js

@@ -13,9 +13,9 @@ import {
   normalizeRelationPredicate,
   noteRevision,
   removeNoteRelation
-} from "./index-01jj6rbv.js";
+} from "./index-gxr0fctd.js";
 import"./index-3rm7cz6h.js";
-import"./index-cxfrakt7.js";
+import"./index-ekpwvbra.js";
 export {
   removeNoteRelation,
   noteRevision,

package/dist/benchmark.js

@@ -4,13 +4,13 @@ import {
   createSyntheticRankFusionFixture,
   evaluateRanking,
   evaluateRetrievalBenchmark
-} from "./index-s2gw5aw9.js";
-import"./index-cv6fh7z5.js";
+} from "./index-qwgsmtsz.js";
+import"./index-gm9t95d9.js";
 import"./index-d13v9ckt.js";
 import"./index-48pz4jpc.js";
 import"./index-06c9ctr6.js";
 import"./index-5vwpzb5a.js";
-import"./index-cxfrakt7.js";
+import"./index-ekpwvbra.js";
 export {
   evaluateRetrievalBenchmark,
   evaluateRanking,

package/dist/cli.js

@@ -13,7 +13,7 @@ import {
   loadPortfolioRegistry,
   openKnowledgePortfolio,
   snapshotPortfolioRegistry
-} from "./index-jsmvyyvf.js";
+} from "./index-ey46z1zf.js";
 import {
   diffCaptureBundle
 } from "./index-j4zgmzjr.js";
@@ -34,11 +34,11 @@ import {
   MAX_PERCOLATION_NOTES,
   MAX_SCOPED_PERCOLATION_MENTION_PAIRS,
   percolateVault
-} from "./index-dyqwejk5.js";
+} from "./index-nd6nynv2.js";
 import {
   knowledgeBaseEvaluationRetrieverIds,
   openKnowledgeBaseEvaluation
-} from "./index-n5dd7r0v.js";
+} from "./index-xw9ac71d.js";
 import {
   DEFAULT_SEARCH_RESULTS,
   MAX_SEARCH_CANDIDATES,
@@ -46,7 +46,7 @@ import {
   MAX_SEARCH_RELATED_SEEDS,
   MAX_SEARCH_RESULTS,
   openKnowledgeBase
-} from "./index-zzhgcwyt.js";
+} from "./index-vxmf14m1.js";
 import {
   MAX_SEARCH_RULE_CONFIG_BYTES,
   parseSearchRules
@@ -59,7 +59,7 @@ import {
   refreshVault,
   scanVault,
   sha256EmbeddingModelFile
-} from "./index-zxdy5pby.js";
+} from "./index-5m2ydj5q.js";
 import"./index-4j3tt0c3.js";
 import"./index-1gwbassd.js";
 import {
@@ -79,11 +79,11 @@ import {
   addNoteRelation,
   createNote,
   removeNoteRelation
-} from "./index-01jj6rbv.js";
+} from "./index-gxr0fctd.js";
 import"./index-3rm7cz6h.js";
 import {
   validateSearchQuery
-} from "./index-cv6fh7z5.js";
+} from "./index-gm9t95d9.js";
 import {
   navigateLinks
 } from "./index-d13v9ckt.js";
@@ -111,7 +111,7 @@ import {
   lookupNote,
   parseVaultKey,
   renderCatalog
-} from "./index-cxfrakt7.js";
+} from "./index-ekpwvbra.js";
 import {
   main
 } from "./index-0kavxzqj.js";
@@ -2885,7 +2885,7 @@ function renderPercolation(result, note) {
     if (candidate.kind === "missing-concept") {
       lines.push(`  concept  #${safe(candidate.tag)} \u2192 ${safe(candidate.suggestedId)}  (${candidate.support} supporting notes)` + (candidate.collidesWith === null ? "" : `; natural ID is occupied by ${safe(candidate.collidesWith)}`));
     } else if (candidate.kind === "missing-relation") {
-      lines.push(`  relation  ${safe(candidate.source)} ${safe(candidate.suggestedPredicate)} ${safe(candidate.target)}  (${candidate.support} shared signals)`);
+      lines.push(`  relation pair  {${safe(candidate.source)}, ${safe(candidate.target)}}  (predicate required; ${candidate.support} shared signals)`);
     } else if (candidate.kind === "unlinked-mention") {
       lines.push(`  mention  ${safe(candidate.source)} \u2192 ${safe(candidate.target)}  (${candidate.support})`);
     } else {
@@ -2927,12 +2927,16 @@ async function runPercolate(command, output, dependencies) {
     minSupport: command.minSupport,
     limit: command.limit
   });
-  output.stdout(command.json ? terminalSafeJson({
+  const jsonOutput = {
     root: snapshot.root,
     note: command.note ?? null,
     minSupport: command.minSupport,
-    ...result
-  }) : sanitizeTerminalText(renderPercolation(result, command.note)));
+    limit: command.limit,
+    schemaVersion: result.schemaVersion,
+    candidates: result.candidates,
+    truncated: result.truncated
+  };
+  output.stdout(command.json ? terminalSafeJson(jsonOutput) : sanitizeTerminalText(renderPercolation(result, command.note)));
   return 0;
 }
 async function runList(command, output, dependencies) {

package/dist/evaluation-builder.js

@@ -4,15 +4,15 @@ import {
   knowledgeBaseEvaluationRetrieverIds,
   openKnowledgeBaseEvaluation,
   verifyFrozenEvaluationSnapshot
-} from "./index-n5dd7r0v.js";
-import"./index-zzhgcwyt.js";
+} from "./index-xw9ac71d.js";
+import"./index-vxmf14m1.js";
 import"./index-adx6khj5.js";
 import {
   indexSemanticVault,
   recommendedEmbeddingModel,
   recommendedEmbeddingModelSha256,
   scanVault
-} from "./index-zxdy5pby.js";
+} from "./index-5m2ydj5q.js";
 import"./index-4j3tt0c3.js";
 import {
   runGitCommand
@@ -22,12 +22,12 @@ import {
   MAX_EVALUATION_EVIDENCE_BYTES,
   MAX_EVALUATION_RESULTS_PER_QUERY
 } from "./index-b88v3vtm.js";
-import"./index-cv6fh7z5.js";
+import"./index-gm9t95d9.js";
 import"./index-d13v9ckt.js";
 import"./index-48pz4jpc.js";
 import"./index-06c9ctr6.js";
 import"./index-5vwpzb5a.js";
-import"./index-cxfrakt7.js";
+import"./index-ekpwvbra.js";
 import"./index-1xxnjn0d.js";
 
 // src/evaluation-builder.ts

package/dist/evaluation-kb.js

@@ -4,19 +4,19 @@ import {
   knowledgeBaseEvaluationRetrieverIds,
   openKnowledgeBaseEvaluation,
   verifyFrozenEvaluationSnapshot
-} from "./index-n5dd7r0v.js";
-import"./index-zzhgcwyt.js";
+} from "./index-xw9ac71d.js";
+import"./index-vxmf14m1.js";
 import"./index-adx6khj5.js";
-import"./index-zxdy5pby.js";
+import"./index-5m2ydj5q.js";
 import"./index-4j3tt0c3.js";
 import"./index-1gwbassd.js";
 import"./index-b88v3vtm.js";
-import"./index-cv6fh7z5.js";
+import"./index-gm9t95d9.js";
 import"./index-d13v9ckt.js";
 import"./index-48pz4jpc.js";
 import"./index-06c9ctr6.js";
 import"./index-5vwpzb5a.js";
-import"./index-cxfrakt7.js";
+import"./index-ekpwvbra.js";
 import"./index-1xxnjn0d.js";
 export {
   verifyFrozenEvaluationSnapshot,

package/dist/graph.js

@@ -9,6 +9,7 @@ import {
   catalogEnd,
   catalogStart,
   isCanonicalNoteId,
+  isCanonicalRelationPredicate,
   lookupNote,
   metadataValueFromUnknown,
   normalizeVaultPath,
@@ -17,7 +18,7 @@ import {
   replaceCatalog,
   searchableMarkdown,
   wikiLinks
-} from "./index-cxfrakt7.js";
+} from "./index-ekpwvbra.js";
 export {
   wikiLinks,
   searchableMarkdown,
@@ -27,6 +28,7 @@ export {
   normalizeVaultPath,
   metadataValueFromUnknown,
   lookupNote,
+  isCanonicalRelationPredicate,
   isCanonicalNoteId,
   catalogStart,
   catalogEnd,

package/dist/{index-zxdy5pby.js → index-5m2ydj5q.js}

@@ -2,7 +2,7 @@
 import {
   fuseRankedCandidates,
   validateSearchQuery
-} from "./index-cv6fh7z5.js";
+} from "./index-gm9t95d9.js";
 import {
   MAX_ANALYZED_NOTES,
   analyzeVault,
@@ -12,7 +12,7 @@ import {
   parseNote,
   renderCatalog,
   replaceCatalog
-} from "./index-cxfrakt7.js";
+} from "./index-ekpwvbra.js";
 
 // src/semantic.ts
 import { createHash as createHash2 } from "crypto";