@quantiya/codevibe-core 2.0.23 → 2.0.24

package/dist/orchestration-shell/context-compaction.d.ts

@@ -239,6 +239,8 @@ export declare function renderRehydratedSessionContext(deps: {
     clearance: ContextItemSensitivity;
     /** Stage-2 R1 H1 — the dispatch scope (see `rehydrateSessionContext`). */
     scope?: DispatchScope;
+    /** Classifier control state comes from the current request, not prior decisions. */
+    purpose?: 'classification';
 }): Promise<string>;
 /**
  * §6 Eviction/GC — TTL-only retention sweep of the per-session log dirs

package/dist/orchestration-shell/index.d.ts

@@ -924,21 +924,6 @@ export declare function serializeShellSubmissions(handler: (text: string, images
  * slash route then reports "unavailable").
  */
 export declare function buildContinuationActionDeps(args: RunOrchestrationShellArgs, store: OrchestrationStore): Partial<ContinuationCliDeps>;
-/**
- * WEB-BROWSING deterministic fast-path detector (docs/WEB-BROWSING-DESIGN.md).
- * Returns the http(s) URL(s) to read when the prompt is unambiguously a "read
- * this URL" request, else null. Tight by design:
- *   - SUPPRESSED while a clarification is pending (don't hijack a pending
- *     start_task whose answer happens to be a URL) — the classifier handles it.
- *     This is correct for EVERY pending clarification: a `browse` decision never
- *     emits a clarifying_question (the parser invariant forbids advisory_summary/
- *     clarifying_question on browse), so a pending clarification is ALWAYS from a
- *     non-browse route — there is no "pending browse clarification" to preserve.
- *   - fires ONLY when the prompt is URL-leading OR a read-intent verb governs the
- *     URL clause (so "fix the CORS bug, API at https://…" stays start_task).
- * The URL regex is copied from `protectUrls` (unexported in local-advisory.ts).
- */
-export declare function detectBrowseFastPath(text: string, pending: PendingClarification | null): string[] | null;
 /**
  * Tokenize a command line string respecting single/double quotes and backslash escapes.
  * Returns tokens array or error if unclosed quote / trailing escape.

package/dist/planner/local-gemma.d.ts

@@ -2,7 +2,9 @@ import type { PlannerAdapter } from './adapter';
 import type { LocalGemmaAdvisoryRunner } from './local-advisory';
 import type { PlannerDecision, PlannerInput, PlannerProbeResult } from './types';
 export interface LocalGemmaPlannerRunner {
-    classify(promptText: string): Promise<string>;
+    classify(promptText: string, options?: {
+        jsonSchema?: object;
+    }): Promise<string>;
     generateAdvisory?: LocalGemmaAdvisoryRunner['generateAdvisory'];
     probe?(): Promise<PlannerProbeResult>;
     /**
@@ -24,16 +26,42 @@ export interface LocalGemmaPlannerRunner {
  * local Gemma model RESPONDED but its output could not be parsed into a valid
  * route (out-of-domain prose, truncated JSON, unsupported action/keys, etc.).
  *
- * This is deliberately DISTINCT from an infrastructure failure (Ollama
- * unreachable / timeout / budget / tier-gate — those reject out of the runner,
- * never reach the parser). The orchestration shell catches THIS class and
- * degrades to a safe "general question / not a build request" advisory route
- * instead of surfacing a `planner-error`; a genuine infra failure still surfaces
- * "Planner unavailable" because retrying would not help.
+ * Distinct from infrastructure failure: the shell reports invalid routing data
+ * without inventing a successful classification or starting a task.
  */
 export declare class PlannerOutputUnparseableError extends Error {
     constructor(message: string);
 }
+export declare const LOCAL_GEMMA_DECISION_JSON_SCHEMA: {
+    type: string;
+    properties: {
+        rationale: {
+            type: string;
+        };
+        clarifying_question: {
+            type: string;
+        };
+        advisory_summary: {
+            type: string;
+        };
+        browseUrls: {
+            type: string;
+            items: {
+                type: string;
+                pattern: string;
+            };
+        };
+        browseQuery: {
+            type: string;
+        };
+        action: {
+            type: string;
+            enum: ("start_task" | "summarize_current_status" | "advisory_response" | "ask_user" | "refuse" | "team_decompose" | "familiarize" | "brainstorm" | "browse")[];
+        };
+    };
+    required: string[];
+    additionalProperties: boolean;
+};
 /**
  * Text-only route classifier prompt. It intentionally excludes repository
  * paths, summaries, source snippets, file bodies, and the raw structural digest.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@quantiya/codevibe-core",
-  "version": "2.0.23",
+  "version": "2.0.24",
   "description": "Core library for CodeVibe plugins - shared keychain, crypto, AppSync, and auth functionality",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/dist/orchestration-shell/direct-file-delete.d.ts

@@ -1,22 +0,0 @@
-export interface DirectFileDeleteRequest {
-    paths: string[];
-}
-export interface DirectFileDeleteResult {
-    deleted: string[];
-}
-/**
- * Recognize only a closed, deterministic delete request. Anything ambiguous
- * remains on the ordinary planner/implementor path.
- *
- * Supported examples:
- *   Delete only a.txt.
- *   Please delete only `a file.txt` and `b.txt`.
- *   Delete only a.txt. Do not create, modify, or delete any other file.
- */
-export declare function parseDirectFileDeleteRequest(text: string): DirectFileDeleteRequest | null;
-/**
- * Delete only the explicitly named regular files. All targets are validated
- * before the first mutation; each unlink is bound to the captured parent and
- * file incarnation and directory-fsynced by the anchored helper.
- */
-export declare function executeDirectFileDelete(cwd: string, request: DirectFileDeleteRequest): Promise<DirectFileDeleteResult>;