@quantiya/codevibe-core 2.0.49 → 2.0.51

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -61,6 +61,22 @@ export declare function markKeytarUsed(): void;
61
61
  * pinned down here rather than only through a (non-deterministic) init path.
62
62
  */
63
63
  export declare function fileStoreHasCredentials(): boolean;
64
+ /**
65
+ * Did keytar fail to load because its NATIVE BINARY is missing? That is the exact
66
+ * 2026-09-23 failure: an installer skipped keytar's install script, so the package
67
+ * was present with no build/Release/keytar.node and require() threw
68
+ * "Cannot find module '../build/Release/keytar.node'". It is an installation
69
+ * defect, not a keyring or sign-in problem, and rebuilding the module repairs it.
70
+ * Deliberately narrow — any other load error keeps its existing message.
71
+ */
72
+ export declare function isKeytarBinaryMissing(loadError: string | null): boolean;
73
+ /**
74
+ * The message for a keytar whose native binary is missing. `codevibe update`
75
+ * repairs the Claude Code plugin; the explicit rebuild works for every install
76
+ * layout (plugin cache and global npm install), fetching keytar's prebuilt
77
+ * binary as a normal install does.
78
+ */
79
+ export declare function keytarBinaryMissingMessage(loadError: string, installRoot: string | null, migratedToKeyring?: boolean): string;
64
80
  /** True if the file backend was auto-selected (no OS keyring service present). */
65
81
  export declare function wasAutoFileFallback(): boolean;
66
82
  /**
@@ -195,3 +195,10 @@ export declare function attachmentsToBase64(attachments: ImageAttachment[], opts
195
195
  images: string[];
196
196
  failed: ImageAttachment[];
197
197
  };
198
+ /**
199
+ * Detects whether a clarifying question emitted on an image attachment turn is a blind deflection
200
+ * caused by a text-only classifier's inability to see/inspect images (e.g. asking the user to
201
+ * describe the screenshot or what to do with it, or generic rephrase requests), rather than a genuine
202
+ * domain clarification (e.g. "which specific region?").
203
+ */
204
+ export declare function isBlindImageClarification(prompt: string, clarifyingQuestion?: string): boolean;
@@ -62,7 +62,7 @@ export declare class CliEntitlementError extends Error {
62
62
  constructor(message: string, cause?: unknown);
63
63
  }
64
64
  /** Both Companion and Orchestration require a verified signed-in account. */
65
- export declare function requireCliAuthentication(client: Pick<AppSyncClient, 'authenticateWithStoredTokens' | 'getLastAuthFailureKind'>): Promise<void>;
65
+ export declare function requireCliAuthentication(client: Pick<AppSyncClient, 'authenticateWithStoredTokens' | 'getLastAuthFailureKind'> & Partial<Pick<AppSyncClient, 'getLastAuthFailureDetail'>>): Promise<void>;
66
66
  export interface ParsedCliArgs {
67
67
  agent?: 'CLAUDE' | 'CODEX' | 'ANTIGRAVITY';
68
68
  help: boolean;