@inkeep/open-knowledge 0.59.0-beta.1 → 0.59.0-beta.11

package/dist/constants-SPXFIIpr.mjs

@@ -0,0 +1,2 @@
+import"./src-BxdlvOrw.mjs";var e=`0.59.0-beta.11`;const t=`config.yml`,n=e;export{n,t};
+//# sourceMappingURL=constants-SPXFIIpr.mjs.map

package/dist/index.d.mts

@@ -13473,6 +13473,15 @@ declare const LAUNCH_CONFIG_NAME = "open-knowledge-ui";
  * empty config dirs for editors they haven't installed; the consent flow
  * bypasses the check because the user explicitly toggled the editor
  * checkbox in the dialog.
+ *
+ * The bypass does NOT extend to editors whose config dir doubles as their
+ * detection probe — see `writeWouldFabricateDetection`. Those resolve to
+ * `skipped-missing`, which BOTH consumers of this outcome handle:
+ * the first-launch consent flow ignores it (only `failed` surfaces an error),
+ * and Settings → AI tools maps it to an explicit "not found on this machine"
+ * message in `integrations-settings.ts`'s `setEditor`. Settings is the
+ * reachable path — its rows keep a live checkbox regardless of detection,
+ * whereas the consent dialog only ever offers detected editors.
  */
 declare function writeEditorMcpConfig(target: EditorMcpTarget, cwd: string, installOptions: McpInstallOptions, home?: string, configPathOverride?: string): EditorMcpResult;
 interface UserMcpConfigsOptions {
@@ -13505,6 +13514,11 @@ interface UserMcpConfigsOptions {
  * Bypasses `isEditorTargetAvailable` via `skipAvailabilityCheck: true` — the
  * user explicitly toggled the editor checkbox; their click IS the consent,
  * so skip-on-missing would silently drop their selection.
+ *
+ * Consent is consent to WIRE a tool, never to invent one: the bypass stops at
+ * editors whose config dir is also their detection probe, where writing would
+ * make OK detect a tool it only detects because it wrote there. Those come
+ * back `skipped-missing` instead.
  */
 declare function writeUserMcpConfigs(opts: UserMcpConfigsOptions): Promise<EditorMcpResult[]>;
 /**
@@ -14103,33 +14117,6 @@ interface IntegrationWriteOutcome {
 }
 //#endregion
 //#region src/integrations/resolve-project-root.d.ts
-/**
- * Resolve a CLI project root via ancestor-walk for `.ok/config.yml` first,
- * git-root promotion second. Mirrors desktop `discoverProject` from
- * `packages/desktop/src/main/folder-admission.ts` with a flat record shape and
- * synchronous execution suited to CLI ergonomics — `ok init` calls this
- * before any filesystem side effect. It is init-only by design: git-root
- * promotion and the home-dir stop are scaffolding concerns. Lifecycle
- * commands anchor to an EXISTING project via the CLI preAction hook's
- * `resolveProjectAnchor` (`findEnclosingProjectRoot` semantics) instead.
- *
- * Walk-up rules:
- *   - Realpath cwd, stop at home, filesystem root, or 30 levels.
- *   - First `.ok/config.yml` hit wins; cursor != cwd ⇒ ancestorPromoted.
- *   - No ancestor: try `git rev-parse --show-toplevel`; promote only when the
- *     resolved root is a strict descendant of homeDir (carve-out for
- *     hypothetical `~/.git/`).
- *   - Otherwise: projectRoot = cwd, no promotion (today's CLI behavior).
- *
- * `defaultContentDir` is always `'.'` — content scope equals the resolved
- * `projectRoot`. On git-root promotion the user can still narrow scope via
- * `config.yml`'s `content.dir`, but the default aligns "opened folder" and
- * "content dir" so the two never diverge silently.
- *
- * Pure of stdout — the caller decides whether to print `[ok] Opened existing
- * project at …` or a git-root disclosure line based on the returned record
- * plus its own `existsSync(<projectRoot>/.ok)` probe.
- */
 interface ResolveProjectRootResult {
   /** Where `.ok/` lives or will live. Equals `realpath(cwd)` when no
    * promotion happened; otherwise the ancestor that owned `.ok/config.yml`