fix(package): describe Gemini support as legacy CLI logs, not active

[andrei-hasna]

What

The published description field named "Gemini" alongside Claude,
Codex, and Codewith as an equally-current coding session source:

Search and sync AI coding sessions (Claude, Codex, Codewith, Gemini)
— unified SQLite index with full-text search

Why

The only Gemini integration is GeminiParser
(src/lib/ingest/gemini.ts). Its own docstring:

Best-effort parser for the Gemini CLI. Gemini records prompts in
...

and it reads from GEMINI_PATH (default ~/.gemini) — confirmed by
docs/configuration.md. Google retired the Gemini CLI on 2026-06-18
in favor of Antigravity CLI. This repo has zero Antigravity
mentions (grep -rln antigravity across the tree returns nothing),
so the description implied active parity with Claude/Codex/Codewith
for a coding agent that no longer serves requests.

Fix

package.json description now reads:

Search and sync AI coding sessions (Claude, Codex, Codewith, plus
legacy Gemini CLI logs) — unified SQLite index with full-text search

The parser is untouched and still works on whatever ~/.gemini data
exists locally; the change is only that the description no longer
implies Gemini is a live, actively-produced session source on the
same footing as the other three.

Scope

package.json description only, per the driving task.
hasna.contract.json carries the identical wording in a separate
service-contract description (used for deployment contracts, not the
npm registry listing) — left unchanged here and flagged in the task
rather than folded into this PR, since it is a different artifact
with its own review path.

Not done here

• No Antigravity parser was added. If this package should ingest
  Antigravity session data, that is separate scoped work.
• Not published to npm. This PR only changes what ships on the next
  publish; the registry description stays as-is until someone
  publishes a new version.

Ref: todos task 41e23961 (agent-chief-marketing / Maecenas).

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[andrei-hasna]

[REVIEW] GO — #54 @ 6a68a52 — lens: correctness+security+gates, reviewer unresolved-account002 (1 of 1)

Reviewed exact candidate:

• Base: origin/main at 739f4d39c76c24cd39223c8ad4525d163100f01d
• Head: 6a68a52aa1a74405222aec3bbdc715be6e939e8c
• Read git log --oneline origin/main..HEAD, git diff origin/main...HEAD --stat, and the full diff of package.json.
• Read the complete surrounding package.json plus the Gemini ingest implementation and registration in src/lib/ingest/gemini.ts and src/lib/ingest/index.ts, the source enum in src/types/index.ts, relevant Gemini parser/watch/CLI tests, and the corresponding README/configuration source descriptions.

Commands and measured results (unpiped):

• bun install — exit 0; setup only, 117 packages installed (not counted as a repository gate).
• bun run typecheck — exit 0; pass (the TypeScript gate emits no itemized pass/fail count).
• bun run test — exit 0; 378 pass, 0 fail, 1784 expectations across 44 files.
• git diff --check origin/main...HEAD — exit 0.

Blocking P0/P1 findings: none.

The changed package description accurately narrows Gemini support to legacy Gemini CLI logs. The implementation registers a best-effort parser for ~/.gemini/tmp/**/logs.json, and the change does not alter runtime behavior, trust boundaries, data handling, or security controls.

Non-blocking follow-ups: none.