@quantiya/codevibe-core 2.0.6 → 2.0.7

package/dist/reviewer/providers/gemini.d.ts

@@ -1,109 +0,0 @@
-import { type ReviewerEvaluateOptions, type ReviewerProvider, type ReviewerSpec } from '../provider.js';
-import { type SubprocessOutcome } from '../subprocess.js';
-import type { ReviewerVerdict } from '../types.js';
-import { type VerdictClassifier } from '../verdict-classifier.js';
-import type { BuiltCommand } from './claude.js';
-/** Construction options. */
-export interface GeminiReviewerProviderOptions {
-    /** Override the `gemini` executable path. Production callers pass nothing
-     *  (PATH lookup); integration tests can stub Gemini with a shell-script
-     *  fixture. */
-    executable?: string;
-}
-/**
- * JSON envelope shape emitted by `gemini --output-format json`. We only care
- * about `response`; the other fields (`session_id`, `stats`) are consumed by
- * the JSON deserializer but not surfaced on `ReviewerVerdict` directly.
- *
- * Tolerates missing or extra top-level keys for cross-version compatibility.
- */
-export interface GeminiEnvelope {
-    response: string;
-    /** Gemini 0.38.2 emits this; older versions may not. */
-    session_id?: string;
-    stats?: GeminiStats;
-}
-export interface GeminiStats {
-    /** Map of model name → per-model stats. Token usage MUST be summed across
-     *  every entry (R2 "telemetry timebomb" lesson — picking an arbitrary one
-     *  via `Object.values()[0]` would under-report when Gemini reports
-     *  auxiliary models). */
-    models?: Record<string, GeminiModelStats>;
-}
-export interface GeminiModelStats {
-    tokens?: {
-        /** Prompt + response tokens combined. Populated by Gemini's
-         *  `stats.models.<name>.tokens.total`; used for cost telemetry. */
-        total?: number;
-    };
-}
-/**
- * Real Gemini CLI reviewer provider. Wraps the `gemini` binary.
- */
-export declare class GeminiReviewerProvider implements ReviewerProvider {
-    private readonly executable;
-    constructor(opts?: GeminiReviewerProviderOptions);
-    evaluate(spec: ReviewerSpec, gateId: string, opts?: ReviewerEvaluateOptions): Promise<ReviewerVerdict>;
-}
-/**
- * Construct the Gemini CLI invocation. Split out from `evaluate` so unit
- * tests can assert on the built arg list + env without actually spawning a
- * process.
- *
- * Locked flag set:
- * - `-p ''` — non-interactive mode, empty inline prompt so the full prompt
- *   is read from stdin (consistent with Claude path).
- * - `--approval-mode plan` — read-only sandbox.
- * - `--output-format json` — structured reply envelope that survives
- *   user-hook stdout pollution.
- * - `--model <hint>` — optional; omitted when `spec.model_hint` is `null`.
- *
- * `spec.tool_allowlist` is **intentionally unused** for Gemini. Plan mode
- * is the design-locked sandbox; mapping the Claude-style allowlist to
- * Gemini's (deprecated) `--allowed-tools` flag would hit the known
- * non-interactive bugs flagged in the module docs.
- *
- * # QUORUM_REVIEWER_SUBPROCESS env var
- *
- * Set unconditionally to `'1'` in the child's environment. The user's
- * Gemini plugin checks this at the top of `hooks/common.sh` and
- * short-circuits every hook — without this gate, reviewer spawns would
- * each create a new backend session and mark the user's primary Gemini
- * session INACTIVE (empirically observed 2026-04-21 during Phase 2c.2
- * local testing).
- */
-export declare function buildCommand(executable: string, spec: ReviewerSpec, sandboxed?: boolean): BuiltCommand;
-/**
- * Map the raw subprocess outcome into a `ReviewerVerdict` or throw a
- * structured `ReviewerErrorClass`. See `claude.ts::buildVerdict` for the
- * shared safety rule (non-zero exit overrides any parseable stdout).
- */
-export declare function buildVerdict(spec: ReviewerSpec, gateId: string, outcome: SubprocessOutcome, classifyVerdict?: VerdictClassifier): Promise<ReviewerVerdict>;
-/**
- * Parse the FIRST complete JSON object in `stdout`, discarding any trailing
- * bytes. User-level hooks (e.g., CodeVibe's own Gemini plugin hooks
- * installed in `~/.gemini/settings.json`) append log lines to stdout AFTER
- * the model's reply envelope. This walks the text byte-by-byte tracking
- * brace depth + string escapes to find where the first JSON object ends,
- * then `JSON.parse` that slice — the equivalent of Rust's
- * `serde_json::Deserializer::into_iter().next()` for our purposes.
- *
- * Returns `null` if stdout contains no valid JSON value at all, the
- * extracted slice fails strict JSON parsing, OR the parsed value isn't a
- * shape-conformant `GeminiEnvelope` (i.e. missing or non-string
- * `response`). The caller routes any of these to ParseFailure with raw
- * stdout — matching Rust's serde-deserialization-failure path.
- *
- * # Why runtime shape validation
- *
- * Rust's `serde_json::Deserializer` rejects `{}` or `{"response":123}`
- * during deserialization because `GeminiEnvelope { response: String, ... }`
- * makes the field required at the type-system layer. TypeScript's
- * `JSON.parse(slice) as GeminiEnvelope` is a compile-time-only assertion
- * with no runtime check, so we reproduce serde's behavior with an
- * explicit `validateGeminiEnvelope` step. Without this, a syntactically-
- * valid-but-shape-bad envelope would land an `undefined.replace()`
- * TypeError up the call stack instead of a structured ParseFailure
- * (R1 finding on Phase 2f.1.b round 1).
- */
-export declare function parseFirstJsonEnvelope(stdout: string): GeminiEnvelope | null;