gemiterm 2.0.0 → 2.1.1

package/openspec/changes/archive/2026-06-09-refactor-interactive-prompt-loop/specs/interactive-prompt-loop/spec.md

@@ -1,35 +0,0 @@
-## ADDED Requirements
-
-### Requirement: Interactive prompt loop SHALL support continuous chat sessions
-The interactive prompt loop utility SHALL provide a reusable mechanism for chat commands to engage in continuous back-and-forth conversations with the user until explicitly terminated.
-
-#### Scenario: User sends multiple messages in a session
-- **WHEN** user starts an interactive session and enters a message
-- **THEN** the system processes the message and displays the response
-- **AND** the system prompts for the next message
-
-#### Scenario: User can exit the session
-- **WHEN** user types "/exit" or "/quit"
-- **THEN** the system displays "Goodbye." and terminates the session
-
-#### Scenario: Empty input is handled gracefully
-- **WHEN** user presses Enter without typing anything
-- **THEN** the system re-prompts without sending an empty message
-
-#### Scenario: Errors during message processing do not terminate the session
-- **WHEN** user enters a message but processing throws an error
-- **THEN** the system displays the error message
-- **AND** the system re-prompts for the next message
-
-### Requirement: Interactive prompt loop SHALL support command-specific message handling
-The utility SHALL accept a callback function that handles each message, allowing different commands to process messages differently.
-
-#### Scenario: New chat command creates new conversation
-- **WHEN** the new command uses the interactive loop with a message handler
-- **AND** user enters a message
-- **THEN** the system starts a new conversation and displays the response
-
-#### Scenario: Continue command sends to existing conversation
-- **WHEN** the continue command uses the interactive loop with a message handler
-- **AND** user enters a message
-- **THEN** the system sends the message to the existing conversation ID

package/openspec/changes/archive/2026-06-09-refactor-interactive-prompt-loop/tasks.md

@@ -1,28 +0,0 @@
-## 1. Create shared interactive prompt utility
-
-- [x] 1.1 Create `src/cli/utils/interactive-prompt.ts` module
-- [x] 1.2 Define `MessageHandler` callback interface for command-specific message processing
-- [x] 1.3 Implement `runInteractiveLoop` function that handles prompt loop mechanics
-- [x] 1.4 Ensure loop continues until /exit or /quit command
-- [x] 1.5 Handle empty input gracefully without sending
-
-## 2. Refactor new-command.ts
-
-- [x] 2.1 Import the new `runInteractiveLoop` utility
-- [x] 2.2 Replace `startInteractive` method with call to `runInteractiveLoop`
-- [x] 2.3 Pass message handler callback that creates new chat conversations
-- [x] 2.4 Remove duplicated `startInteractive` method
-- [x] 2.5 Verify interactive mode loops correctly (not just one message)
-
-## 3. Refactor continue-command.ts
-
-- [x] 3.1 Import the new `runInteractiveLoop` utility
-- [x] 3.2 Replace `startInteractive` method with call to `runInteractiveLoop`
-- [x] 3.3 Pass message handler callback that sends to existing conversation
-- [x] 3.4 Remove duplicated `startInteractive` method
-
-## 4. Verify
-
-- [x] 4.1 Run `bun run test` to ensure all tests pass
-- [x] 4.2 Manually test `new` command interactive mode loops correctly
-- [x] 4.3 Manually test `continue` command interactive mode works correctly

package/openspec/changes/archive/2026-06-09-replace-gemini-api-placeholder-with-gemini-reverse/.openspec.yaml

@@ -1,2 +0,0 @@
-schema: spec-driven
-created: 2026-06-09

package/openspec/changes/archive/2026-06-09-replace-gemini-api-placeholder-with-gemini-reverse/design.md

@@ -1,323 +0,0 @@
-## Context
-
-`src/services/gemini-client-wrapper.ts` is a 304-line placeholder that talks
-to `gemini.google.com` over `fetch()` with hand-typed `URLSearchParams` bodies
-and guessed endpoint paths. The class implements two interfaces:
-
-- `IGeminiClientService` (`src/core/command-handlers.ts:92`) — `deleteChat`,
-  `sendMessage`, `startNewChat`, `profileHasConversation`, `forProfile`.
-- `IGeminiClientQueryService` (`src/core/query-handlers.ts:56`) — `listChats`,
-  `fetchChat`, `listModels`.
-
-`GeminiClientService` is currently constructed in one place
-(`src/cli/index.ts:98,110`) and consumed in three (`src/cli/index.ts:116-153`,
-`src/services/profile-auth-manager.ts:22-54`, plus all command/query handlers
-that depend on the interfaces — never on the class directly).
-
-The proposed replacement is the npm package
-[`gemini-reverse`](https://www.npmjs.com/package/gemini-reverse) by
-[rynn-k](https://github.com/rynn-k/Gemini-Reverse). It exposes:
-
-- `class GeminiClient` with constructor
-  `({ secure_1psid, secure_1psidts?, proxy?, cookies? })` and async
-  `init({ timeout?, autoClose?, closeDelay?, autoRefresh?, refreshInterval?,
-  verbose?, watchdogTimeout? })`.
-- `client.listChats(): ChatInfo[]` (fields: `cid`, `title`, `is_pinned`,
-  `timestamp`).
-- `client.readChat(cid: string, limit?: number): Promise<ChatHistory | null>` —
-  `ChatHistory.turns: { role, text, parts? }[]`.
-- `client.startChat(opts?): ChatSession` — session with
-  `sendMessage({ prompt, … }): Promise<ModelOutput>`,
-  `readHistory(limit?): Promise<ChatHistory | null>`, `cid`, `rcid`.
-- `client.generateContent({ prompt, … }): Promise<ModelOutput>` for
-  single-shot.
-- `client.deleteChat(cid: string): Promise<void>`.
-- `client.listModels(): AvailableModel[]` (fields: `model_id`, `model_name`,
-  `display_name`, `description`, `capacity`, `is_available`, …).
-- Error classes: `GeminiError` (base), `AuthError`, `APIError`, `TimeoutError`,
-  `UsageLimitExceeded`, `TemporarilyBlocked`, `ModelInvalid`.
-
-`src/core/errors.ts` defines `GemitermError` (base), `AuthenticationError`,
-`CookieExpiredError`, `GeminiAPIError`, `ConversationNotFoundError`,
-`ConversationPendingError`. Callers expect these types in `try/catch` blocks
-(e.g. `command-handlers.ts:120`, `query-handlers.ts:138`).
-
-## Goals / Non-Goals
-
-**Goals:**
-
-- Replace the placeholder `fetch()`-based HTTP client with a real Gemini web
-  protocol client that talks to the live service.
-- Keep the public class signature of `GeminiClientService` and the two
-  interfaces it implements bit-identical, so all 11 CLI commands, the
-  `ProfileAuthManager`, and the command/query handlers need zero edits.
-- Translate `gemini-reverse` exceptions into our `GemitermError` subclasses so
-  the existing error-handling in command handlers keeps working.
-- Preserve the per-profile session model: each profile gets its own
-  `GeminiClient` (and therefore its own auto-refresh watchdog) bound to the
-  cookies loaded by `CookieStorageService`.
-- Add a unit test file that mocks `gemini-reverse` and verifies the mapping
-  and error translation in isolation, so we don't need a real Google account
-  in CI.
-- Stay at the 432/432 test baseline (and add new tests on top of it).
-
-**Non-Goals:**
-
-- Surfacing `gemini-reverse` features the wrapper doesn't currently expose
-  (Gems, file uploads, deep research, streaming, image/video output, candidate
-  selection). These are deferred to a follow-up change.
-- Changing the cookie storage file format or the v1.4.1 → v2.0.0 migration
-  story.
-- Touching any of the four regression-gate files flagged in `AGENTS.md`
-  (`playwright-cli-driver.ts`, `cookie-monitor.ts`, `auth-service.ts`,
-  `cookie-storage-service.ts`).
-- Resolving the existing `bun run build` breakage (that's the
-  `cross-platform-build-and-ci` change).
-- Re-shaping `IGeminiClientService` or `IGeminiClientQueryService` — those
-  are part of the `conversations` / `multi-profile-conversations` /
-  `commands` capability contracts and are explicitly preserved.
-
-## Decisions
-
-### Decision 1: `gemini-reverse` over hand-rolled or other libraries
-
-We pick `gemini-reverse@^0.x` (pin the exact range in `tasks.md` based on
-current npm at implementation time) because:
-
-- It is the only widely-used library that wraps the live Gemini web protocol
-  (same upstream as our `playwright-cli`-driven auth).
-- It handles cookie auto-refresh in the background (the upstream `1PSIDTS`
-  cookie rotates on a timer; hand-rolling this is a known footgun).
-- It is pure JavaScript with no native bindings, so Bun resolves it cleanly.
-
-**Alternatives considered:**
-
-- *Port Python `gemiterm` v1.4.1's `gemini_webapi` usage.* Rejected: that
-  project is the Python equivalent, not a Node package.
-- *Re-implement the HTTP client in TypeScript.* Rejected: the upstream
-  protocol changes and the auth flow is non-trivial; this is the path that
-  produced the placeholder we're replacing.
-- *Use Google's official `generativelanguage` SDK.* Rejected: that's a
-  different product (AI Studio API key model) — `gemiterm` is explicitly a
-  CLI for the consumer web app, not the AI Studio API.
-
-### Decision 2: Compose `GeminiClient` per-instance, not per-CLI
-
-The current placeholder holds cookies on a `GeminiClientConfig` and uses
-`fetch()` directly. The new wrapper holds a `GeminiClient` instance from
-`gemini-reverse` as a private field, and calls `listChats()` / `readChat()` /
-`startChat()` / `deleteChat()` / `listModels()` on it.
-
-`forProfile(name)` constructs a brand-new `GeminiClientService` with a
-brand-new `GeminiClient` bound to the profile's cookies. This is what
-`gemini-reverse` is designed for (one client = one logged-in account) and
-naturally scopes the upstream auto-refresh watchdog to that profile.
-
-**Why not a single shared `GeminiClient` and pass cookies per call?** The
-upstream API bakes cookies into the client at construction time and runs the
-refresh watchdog against that single account. A shared client would mean the
-"current" profile is implicit state, and `forProfile()` could race the
-watchdog. Per-instance is the upstream-idiomatic and race-free model.
-
-### Decision 3: Translation layer is a private helper, not a public module
-
-Mapping `gemini-reverse` types into our domain types (`ChatInfo`, `Message`,
-model display names) and translating exceptions into `GemitermError`
-subclasses lives as **private methods** on `GeminiClientService`, not as
-exported functions in a new module. Reasons:
-
-- Only `GeminiClientService` needs them.
-- Keeping the translation local makes the wrapper's contract surface minimal
-  — `core/types.ts` stays the only public domain-types module, and
-  `core/errors.ts` stays the only public error module.
-- It avoids leaking the `gemini-reverse` import path into more than one file
-  (which simplifies future swaps if we ever need to replace this library
-  again).
-
-The private helpers we will introduce:
-
-- `toDomainChatInfo(raw: geminiReverse.ChatInfo, profileName?: string):
-  ChatInfo` — maps `cid → id`, `is_pinned → isPinned`, preserves `timestamp`
-  and `title`, adds `profile` when `profileName` is set (matches existing
-  placeholder behavior on `gemini-client-wrapper.ts:144`).
-- `toDomainMessages(history: geminiReverse.ChatHistory, conversationId:
-  string): Message[]` — flattens `turns[].text ?? turns[].parts[].text` and
-  normalizes `role` to `"user" | "model"`.
-- `toDomainModelName(model: geminiReverse.AvailableModel): string` — returns
-  `display_name || model_name || model_id`.
-- `translateError(e: unknown): GemitermError` — see Decision 5.
-
-### Decision 4: `init()` is exposed on the wrapper, not lazy
-
-The placeholder's constructor sets `this.authenticated = !!config.secure1psid`
-and never makes a network call. `gemini-reverse`'s `GeminiClient.init()` is
-async and does perform I/O (probe models, set up refresh watchdog). To keep
-the wrapper's construction synchronous (the factory in `src/cli/index.ts:98,110`
-calls `new GeminiClientService(…)` without `await`), we add an explicit async
-`init(): Promise<void>` on the wrapper that:
-
-1. Awaits `this.client.init({ timeout: 300_000, autoClose: false,
-   autoRefresh: true, refreshInterval: 540_000 })`.
-2. Is called once at CLI startup (in `src/cli/index.ts` after the factory
-   is constructed and before the first user command) — the call site edit
-   is a 2-line addition.
-3. Is idempotent (`this.initialized` guard) so re-entry from test setup is
-   safe.
-4. `forProfile()` returns a wrapper whose `init()` is also lazily awaited
-   before its first call (or eagerly awaited in the same place; decided in
-   the implementation based on call-site symmetry).
-
-The factory in `src/cli/index.ts` constructs the wrapper with
-`secure1psid: ""` (a placeholder until a profile is selected). For that
-factory instance, `init()` is called with empty cookies and we treat that as
-"deferred" — `init()` is still awaited, but the underlying `GeminiClient` is
-not used for I/O until a profile is selected (the per-profile wrappers
-constructed via `forProfile()` do the real I/O).
-
-**Why not lazy `init()` on first call?** Two reasons: (a) the existing
-`ProfileAuthManager` and command handlers can call methods concurrently
-during a multi-profile operation, and lazy init is racy without a mutex; (b)
-explicit init at startup makes the `await` visible in `src/cli/index.ts` and
-keeps the lifecycle linear.
-
-### Decision 5: Error translation mapping
-
-Add a private `translateError(e: unknown): GemitermError` to the wrapper
-(per Decision 3). Mapping:
-
-| `gemini-reverse` class  | Translated to                        | Message                                              |
-|-------------------------|--------------------------------------|------------------------------------------------------|
-| `AuthError`             | `AuthenticationError`                | `"Session expired or invalid. Please run 'gemiterm login' again."` (matches the existing message at `gemini-client-wrapper.ts:83`) |
-| `TimeoutError`          | `GeminiAPIError`                     | `"Request to Gemini timed out"`                      |
-| `UsageLimitExceeded`    | `GeminiAPIError`                     | `"Gemini usage limit reached; try again later or switch model"` |
-| `TemporarilyBlocked`    | `GeminiAPIError`                     | `"Temporarily blocked by Gemini; try a proxy or wait"` |
-| `ModelInvalid`          | `GeminiAPIError`                     | `"Model is invalid or unavailable"`                  |
-| `APIError`              | `GeminiAPIError`                     | `e.message` (with `cause = e`)                       |
-| any other `GeminiError` | `GeminiAPIError`                     | `e.message` (with `cause = e`)                       |
-| anything else           | `GeminiAPIError`                     | `"Unexpected error: " + String(e)`                   |
-
-The `cause` field on `GeminiAPIError` is supported by `Error` since ES2022
-and is the right channel for the underlying error so the existing
-`logger.debug(\`${operation} failed: ${error}\`)` calls in
-command/query handlers still see the original message via
-`error.cause?.message`.
-
-We do **not** re-export `gemini-reverse` error classes from `core/errors.ts`.
-That would leak the library's type surface into our public module, which
-violates the "translate, don't re-export" principle and increases the blast
-radius of any future library swap.
-
-### Decision 6: `sendMessage` and `startNewChat` return types stay text-only
-
-`IGeminiClientService.sendMessage(cid, msg): Promise<string>` and
-`startNewChat(msg): Promise<{ response: string; conversationId: string }>`
-return plain text today. `gemini-reverse` returns a rich `ModelOutput` with
-candidates, images, videos, thoughts, deep-research plans, and an `rcid` we
-can use as the conversation ID.
-
-We keep the wrappers text-only for this change and pull
-`output.text.toString()`. Surfacing candidates / media / `rcid` is a
-follow-up change (and a new capability spec) — it requires deciding how
-`gemiterm chat --json` should serialize them, which is out of scope here.
-
-For `startNewChat`, the `conversationId` we return comes from the
-`ChatSession.cid` after `client.startChat().sendMessage(...)` returns
-(equivalently `output.rcid` is also a valid candidate — we pick `cid` to
-match the existing `cid` field on `ChatInfo` from `listChats`).
-
-### Decision 7: Test strategy — module mock, not real network
-
-Add `tests/services/gemini-client-wrapper.test.ts` that:
-
-- Uses `bun:test`'s `mock.module("gemini-reverse", …)` to install a fake
-  `GeminiClient` class whose constructor records its arguments and whose
-  methods return fixtures.
-- Spies on the fake's `listChats` / `readChat` / `startChat` / `deleteChat` /
-  `listModels` / `init` methods to assert that the wrapper calls them with
-  the right arguments and translates the return values into our domain
-  types.
-- Asserts the `AuthError → AuthenticationError` and the other error
-  translations by injecting the relevant `gemini-reverse` error class
-  instances and catching them.
-- Verifies `forProfile(name)` constructs a *new* `GeminiClient` bound to
-  that profile's cookies (asserted via a counter on the mock constructor).
-
-This mirrors the test style of
-`tests/services/cookie-storage-service.test.ts` and keeps the test
-self-contained (no network, no Playwright, no `playwright-cli`).
-
-The factory instance in `src/cli/index.ts:110` uses an empty
-`secure1psid: ""` and is used only as a `forProfile` factory; it is not
-exercised directly. We add a separate, small test for "empty-cookies client
-constructs but does not throw" to lock in the invariant.
-
-### Decision 8: Dependency version
-
-Pin `gemini-reverse` to `^0.5.0` (or whatever the latest stable is at
-implementation time — task 1 of `tasks.md` re-validates this against
-`npm view gemini-reverse version` and updates the `package.json` entry
-accordingly). The `^0.5.0` placeholder is to convey "use the latest 0.x" in
-the `tasks.md` pin — implementers should re-check the registry.
-
-## Risks / Trade-offs
-
-- **[Upstream library is unofficial / can break]** → Mitigation: we wrap it
-  in `GeminiClientService` and translate errors. If `gemini-reverse`
-  changes its public API, the blast radius is the wrapper file only. We
-  also pin to `^0.x` (not `^1.0.0` yet) to acknowledge pre-1.0 churn.
-- **[Cookie auto-refresh race with multi-profile use]** → Mitigation:
-  per-instance `GeminiClient` per profile (Decision 2). Each profile's
-  watchdog runs against its own session, no shared state.
-- **[Bun resolution of npm package]** → Mitigation: `gemini-reverse` is
-  pure JS (no native bindings, no `node-gyp`). Task 1 in `tasks.md` adds
-  a `bun test` smoke step that imports the package from a placeholder
-  `src/services/__smoke__/import-gemini-reverse.test.ts` to catch any
-  resolution issue early. The smoke test is removed after the real tests
-  are in place.
-- **[Loss of placeholder-specific `search` / `limit` / `offset` filtering
-  in `listChats`]** → Mitigation: `gemini-reverse`'s `listChats()` returns
-  a fully populated array. The wrapper applies the same post-filter (case-
-  insensitive `search` on `title`, then `offset` slice, then `limit` slice)
-  after mapping, preserving the existing behavior at
-  `gemini-client-wrapper.ts:148-160`.
-- **[Empty-cookies factory instance crashes `init()`]** → Mitigation:
-  `gemini-reverse`'s `init()` tolerates null/empty `secure_1psid` (it
-  defers actual I/O until a method is called). We add a smoke test
-  asserting the factory instance constructs and `init()` resolves without
-  throwing.
-- **[Per-call `GeminiClient` construction is heavier than per-call `fetch`]**
-  → Mitigation: this is a CLI invoked once per user command, not a
-  long-running daemon. Construction cost is negligible.
-- **[Test count churn]** → The new test file adds tests but should not
-  remove any of the 432 existing tests. `bun run test` after
-  implementation must show `≥ 432` tests passing (target: 432 + ~25 new
-  cases from the new file).
-
-## Migration Plan
-
-- **Deploy**: this is a `v2.0.0` change; deploy with the normal release
-  process (handled by the `cross-platform-build-and-ci` change once
-  that's implemented — out of scope here).
-- **Rollback**: revert the single commit that swaps the wrapper; the
-  previous `fetch()`-based implementation lives in `git` history. Cookie
-  files in `%APPDATA%\gemiterm\` / `~/.config/gemiterm/` are unchanged.
-- **User action**: none. No re-auth, no config migration, no new flags.
-- **Operational note**: the first call after upgrade will hit
-  `gemini-reverse`'s model probe and chat list, which performs a couple
-  of HTTPS requests at startup. Latency is comparable to the placeholder.
-
-## Open Questions
-
-- **Q1**: At implementation time, confirm the latest published
-  `gemini-reverse` version on npm and pin accordingly (placeholder:
-  `^0.5.0`).
-- **Q2**: Confirm Bun resolves `import { GeminiClient } from "gemini-reverse"`
-  cleanly (no `bun install` quirks). This is the first non-Bun-first-party
-  runtime dep we're pulling in.
-- **Q3**: Decide whether `init()` failure should be fatal at CLI startup
-  or deferred until first use. Default plan (per Decision 4): fatal
-  at startup, with the error mapped to `GeminiAPIError` and surfaced as
-  the standard CLI error.
-- **Q4**: Should we expose a `--no-auto-refresh` flag to disable
-  `gemini-reverse`'s cookie auto-refresh for debugging? Deferred to a
-  follow-up; not in this change.

package/openspec/changes/archive/2026-06-09-replace-gemini-api-placeholder-with-gemini-reverse/proposal.md

@@ -1,122 +0,0 @@
-## Why
-
-`src/services/gemini-client-wrapper.ts` is a hand-rolled placeholder that talks
-to `gemini.google.com` over `fetch()` with hard-coded URL paths
-(`/app/api/chat/history`, `/app/api/chat/<id>/send`, `/app/api/models`, …) and
-URL-encoded form bodies. Those endpoints and shapes are educated guesses — the
-real Gemini web app uses a different RPC and streaming protocol, so today the
-CLI is structurally a stub against a real (changing) Google surface. We need
-to swap the in-tree HTTP client for the community-maintained
-[`gemini-reverse`](https://www.npmjs.com/package/gemini-reverse) library
-(rynn-k/Gemini-Reverse), which already implements the live Gemini web protocol
-(including cookie auto-refresh, streaming, model discovery, and per-account
-sessions). This is a prerequisite for actually shipping v2.0.0 against the
-real Gemini web app.
-
-## What Changes
-
-- **Add `gemini-reverse` as a runtime dependency** in `package.json` and
-  document the minimum supported version pinned in `tasks.md`.
-- **Replace the body of `src/services/gemini-client-wrapper.ts`** so that
-  `GeminiClientService` composes a `GeminiClient` from `gemini-reverse`
-  instead of issuing `fetch()` calls. The public class signature and the two
-  interfaces it implements (`IGeminiClientService` in
-  `src/core/command-handlers.ts`, `IGeminiClientQueryService` in
-  `src/core/query-handlers.ts`) **do not change** — all call sites in
-  `src/cli/index.ts`, `src/services/profile-auth-manager.ts`, and the command
-  / query handlers keep working without edits.
-- **Map `gemini-reverse` types into our domain types** in
-  `src/services/gemini-client-wrapper.ts`:
-  - `ChatInfo` (ours) ← `ChatInfo` from `gemini-reverse` (`cid` → `id`,
-    `is_pinned` → `isPinned`, `timestamp` preserved, optional `profile` added
-    for the multi-profile case).
-  - `Message[]` (ours) ← `ChatHistory.turns` from `readChat(cid, limit)` (role
-    `"user"` vs `"model"`, content flattened from `text` / `parts[].text`,
-    `conversationId` injected).
-  - `string[]` of model display names (ours) ←
-    `AvailableModel[]` from `listModels()` (use `display_name` with `model_id`
-    as fallback).
-- **Map `gemini-reverse` errors into our error hierarchy** in
-  `src/core/errors.ts` (re-export shim or constructor translation in the
-  wrapper):
-  - `AuthError` → `AuthenticationError` (with the same "run `gemiterm login`"
-    message).
-  - `UsageLimitExceeded` / `TemporarilyBlocked` / `ModelInvalid` →
-    `GeminiAPIError` with a domain-specific message prefix.
-  - `TimeoutError` → `GeminiAPIError` ("Request to Gemini timed out").
-  - `APIError` / other `GeminiError` subclasses → `GeminiAPIError` with the
-    original `message` and `cause` set to the underlying error.
-- **Preserve multi-profile behavior**: `forProfile(name)` still returns a new
-  `GeminiClientService` instance bound to that profile's cookies loaded from
-  `CookieStorageService`. The underlying `GeminiClient` is constructed
-  per-profile, so the upstream cookie auto-refresh watchdog is scoped to that
-  profile's session.
-- **Preserve initialization sequencing**: the wrapper's `init()` is called
-  once after the `GeminiClient` is constructed and before any I/O. `init()`
-  configures `timeout`, `autoRefresh: true`, `refreshInterval: 540000` (9
-  minutes, matching upstream defaults), and `autoClose: false` so the process
-  stays warm during a CLI session.
-- **Add a unit test file `tests/services/gemini-client-wrapper.test.ts`** that
-  mocks the `gemini-reverse` `GeminiClient` class via a module mock and
-  verifies the mapping/translation for `listChats`, `fetchChat`, `sendMessage`,
-  `startNewChat`, `deleteChat`, `listModels`, `forProfile`, and the
-  `AuthError → AuthenticationError` translation. Reuse the existing
-  test-factory style from `tests/services/cookie-storage-service.test.ts`.
-
-No public CLI surface, command output, config file format, or persisted cookie
-file format changes. The v1.4.1 → v2.0.0 upgrade path stays intact.
-
-## Capabilities
-
-### New Capabilities
-
-None. This change is a drop-in implementation swap; no new user-visible
-capability is introduced. If we ever need to expose `gemini-reverse` features
-the wrapper doesn't currently surface (Gems, file uploads, deep research,
-streaming `--json`), those would be a separate change with their own
-`specs/<name>/spec.md`.
-
-### Modified Capabilities
-
-None. The requirements in `openspec/specs/conversations/spec.md`,
-`openspec/specs/multi-profile-conversations/spec.md`, `openspec/specs/commands/`
-(every command that talks to Gemini), and `openspec/specs/auth/spec.md` are
-unaffected — the `IGeminiClientService` / `IGeminiClientQueryService` contract
-and observable behavior of every command are preserved. This is an
-implementation-detail refactor only.
-
-## Impact
-
-- **Dependencies**: adds `gemini-reverse` to `dependencies` in
-  `package.json`. Confirms Bun runtime can resolve and load the package (it's
-  pure Node.js, no native bindings).
-- **Source files**:
-  - **Modified**: `src/services/gemini-client-wrapper.ts` (full rewrite of
-    internal implementation; public class signature unchanged).
-  - **Modified**: `src/core/errors.ts` — add `translateGeminiError(e: unknown):
-    GemitermError` helper (or extend the wrapper to perform the mapping
-    inline; decided in `design.md`).
-  - **New**: `tests/services/gemini-client-wrapper.test.ts`.
-- **Call sites (no edits expected, verified during implementation)**:
-  - `src/cli/index.ts` (3× `IGeminiClientService` / `IGeminiClientQueryService`
-    consumers and the factory `new GeminiClientService({ secure1psid: "" }, …)`).
-  - `src/services/profile-auth-manager.ts` (consumes `IGeminiClientService`).
-  - `src/core/command-handlers.ts`, `src/core/query-handlers.ts` (consume the
-    interfaces, not the class).
-- **Sensitive-area check**: `AGENTS.md` flags four files as regression-gate
-  files for auth flow; this change touches `src/services/gemini-client-wrapper.ts`
-  only, which is **not** one of those four. The four flagged files
-  (`playwright-cli-driver.ts`, `cookie-monitor.ts`, `auth-service.ts`,
-  `cookie-storage-service.ts`) are not modified by this change. The wrapper
-  consumes `CookieStorageService` via its existing constructor parameter, so
-  the auth pipeline keeps working.
-- **Tests**: target stays at the 432/432 baseline. The new test file is
-  expected to add coverage (post-implementation count > 432).
-- **Build**: `bun run build` (which currently fails for unrelated reasons
-  captured in the `cross-platform-build-and-ci` change) is unaffected by
-  this change.
-- **No new environment variables.** `gemini-reverse` honors
-  `GEMINI_COOKIE_PATH`; we do not set it, so the library uses its default
-  temp directory.
-- **No config-file or cookie-file format change.** v1.4.1 users upgrading
-  to v2.0.0 will not need to re-authenticate.

package/openspec/changes/archive/2026-06-09-replace-gemini-api-placeholder-with-gemini-reverse/specs/no-capability-changes/spec.md

@@ -1,29 +0,0 @@
-## ADDED Requirements
-
-### Requirement: This change introduces no new requirements
-This change is a pure implementation swap of the in-tree Gemini HTTP client
-(`src/services/gemini-client-wrapper.ts`) for the npm `gemini-reverse`
-library. The public contracts — `IGeminiClientService`,
-`IGeminiClientQueryService`, and the `GeminiClientService` class signature —
-are preserved bit-identical. No new user-visible capability is added, and no
-existing requirement in `openspec/specs/conversations/spec.md`,
-`openspec/specs/multi-profile-conversations/spec.md`, `openspec/specs/commands/`,
-or `openspec/specs/auth/spec.md` is modified. All other capabilities in
-`openspec/specs/` are likewise unaffected.
-
-#### Scenario: Public contract preserved
-- **WHEN** a caller imports `GeminiClientService`,
-  `IGeminiClientService`, or `IGeminiClientQueryService` and uses the
-  existing methods (`listChats`, `fetchChat`, `sendMessage`, `startNewChat`,
-  `deleteChat`, `listModels`, `forProfile`, `profileHasConversation`)
-- **THEN** signatures, return types, and thrown error types are identical to
-  the pre-change implementation; the 11 CLI commands, the
-  `ProfileAuthManager`, and all command/query handlers compile and run
-  without source edits
-
-#### Scenario: Per-profile sessions preserved
-- **WHEN** a caller invokes `geminiClient.forProfile("work")` and then
-  `listChats()` on the returned instance
-- **THEN** the `ChatInfo[]` results are scoped to the "work" profile's
-  Google account and carry `profile: "work"` on each entry, matching the
-  existing behavior of the placeholder