savant-code 0.0.19 → 0.0.20

package/dev/nova/specs/launch-strategy-research-prompt.md

@@ -1,88 +0,0 @@
-# Gemini Deep Research Prompt — Launch Strategy for Savant Code
-
-## Context
-
-I'm launching an open-source, free-tier AI coding agent CLI called "Savant Code" (Apache-2.0 licensed). It's a
-TypeScript monorepo with an ECHO Protocol governance system that enforces code quality through a 9-agent roster. Key
-differentiator: the agent self-audits through a perfection loop before shipping code. It runs via BYOK (Bring Your Own
-Key) or local Ollama models. The ad infrastructure is wired but not yet active.
-
-I need comprehensive market research on the best launch strategy.
-
----
-
-## Research Questions
-
-### 1. Launch Channels & Distribution
-
-- What are the most effective launch channels for open-source developer tools in 2025-2026?
-- Product Hunt vs Hacker News (Show HN) vs Reddit (r/programming, r/LocalLLaMA, r/MachineLearning) — which drives the
-  most sustained traction for CLI dev tools?
-- What developer newsletters or blogs (e.g., Console, TLDR, ByteByteGo, Hacker Newsletter) accept submissions from
-  open-source projects?
-- How do successful coding agents (Cline, Aider, OpenHands, Continue, Cursor) distribute their tools? What channels did
-  they use at launch?
-- Is Twitter/X still effective for developer tool launches, or has it shifted to other platforms (Bluesky, Mastodon, dev.to)?
-- What role do GitHub stars play in discovery? How do projects accelerate star growth?
-
-### 2. Competitor Launch Strategies
-
-- How did Codebuff launch? What channels did they use? What was their initial traction?
-- How did Cline (formerly Claude Dev) grow from zero to its current user base?
-- What did OpenHands (formerly OpenDevin) do to gain 50K+ GitHub stars?
-- How did Goose (Block) leverage being a corporate-backed open-source project?
-- What pricing models are coding agents using? (Freemium, usage-based, seat-based, BYOK)
-- What's the typical conversion rate from free-tier users to paid users in developer tools?
-
-### 3. Pricing & Monetization
-
-- What's the standard ad CPM for CLI text ads in developer tools? Is $20-45 CPM realistic?
-- How do developer tools structure their free tier vs paid tier? What's the typical feature split?
-- What's the break-even point for a free-tier coding agent (users needed to cover inference costs)?
-- Are there examples of developer tools successfully using ad-supported models? What ad networks work for CLI/terminal products?
-- How do tools handle the "data for compute" model? Which providers accept developer workflow data as payment for inference?
-
-### 4. Pre-Launch Preparation
-
-- What should a launch-ready open-source project have before going public? (README, docs, landing page, contributing
-  guide, license, etc.)
-- How important is a landing page vs just a GitHub repo? What should the landing page include?
-- What documentation structure works best for developer tools? (README + docs site, or just comprehensive README?)
-- Should I create a Discord/Slack community before launch or after?
-- What's the ideal time between "first public commit" and "official launch announcement"?
-
-### 5. Launch Timing & Sequencing
-
-- Is there a best day of week / time of year to launch a developer tool?
-- Should I do a soft launch (quiet GitHub push) before the official launch?
-- How do I sequence the launch across multiple channels? (e.g., Hacker News first, then Product Hunt, then Reddit?)
-- What's the typical "launch week" playbook for an open-source dev tool?
-- How do I maintain momentum after the initial launch spike? What's the 30/60/90 day strategy?
-
-### 6. Community & Growth
-
-- What's the most effective way to build an early adopter community for a coding agent?
-- How do I get beta testers before launch? Where do developer early adopters hang out?
-- What role do influencers/developers with large followings play in dev tool launches? How do I get their attention?
-- Should I offer exclusive access or features to early adopters?
-- How do successful open-source projects handle feature requests and community contributions without losing direction?
-
-### 7. Risk & Differentiation
-
-- What are the biggest risks when launching a coding agent in a crowded market (2025-2026)?
-- How do I differentiate from Cursor, GitHub Copilot, Cline, and other established players?
-- What messaging resonates with developers who are frustrated with existing coding agents?
-- How do I position "quality over speed" as a competitive advantage?
-- What should I avoid doing at launch? Common mistakes that kill developer tool launches?
-
----
-
-## Output Format
-
-For each question, provide:
-
-1. **Direct answer** with specific data/examples where available
-2. **Source** (article, case study, or data point)
-3. **Actionable recommendation** for Savant Code specifically
-
-Prioritize insights from 2024-2026. Focus on what actually worked, not theoretical best practices.

package/dev/releases/README.md

@@ -1,50 +0,0 @@
-<!-- markdownlint-disable MD041 -->
-
-# dev/releases/ -- Ephemeral Release-Notes Staging
-
-> **Status:** Ephemeral. Gitignored (except this README) per **FID-2026-0718-025**.
-
-This directory is an **ephemeral staging area** for the Orchestrator's release-notes drafts, NOT a canonical
-release-history store.
-
-## Conventions
-
-| Artifact                          | Canonical Source-of-Truth           |
-| --------------------------------- | ----------------------------------- |
-| In-repo history                   | `CHANGELOG.md` (auto-archive)       |
-| External releases                 | GitHub Releases (web UI / `gh` CLI) |
-| Ephemeral drafts                  | THIS directory (gitignored)         |
-
-## Why Ephemeral
-
-Three reasons (per FID-2026-0718-025 + Thinker-with-files-gemini review):
-
-1. **Single Source of Truth** -- `CHANGELOG.md` Line 1 declares itself the canonical in-repo history via ECHO FID
-   Auto-Archive rule.
-2. **GitHub Releases is canonical external source** -- in-repo `.md` files would risk drift if GitHub content diverges.
-3. **`dev/*` permanent siblings** (`fids/`, `nova/`, `session-summaries/`) hold original process context not found
-   elsewhere; release notes are entirely derivative of CHANGELOG + GitHub Releases.
-
-## Workflow
-
-1. Draft `dev/releases/v<X>.<Y>.<Z>.md` here (gitignored, free to evolve without commits).
-2. Publish to GitHub Releases via `gh release create v<X>.<Y>.<Z> --notes-file dev/releases/v<X>.<Y>.<Z>.md` OR via the
-   GitHub web UI release-creation form.
-3. Optionally commit a frozen copy as canonical repo-state reference (rare exception, like the v0.0.2.md commit backing
-   the pre-rebrand safety checkpoint).
-4. Old drafts are removed on next release cycle.
-
-## Current Staged Drafts
-
-(None at the moment. Add drafts as `dev/releases/v<X>.<Y>.<Z>.md`.)
-
-## See Also
-
-- `../../CHANGELOG.md` -- canonical in-repo history
-- GitHub Releases -- canonical external source
-- `../fids/archive/FID-2026-0718-025-dev-releases-ephemeral-staging.md` -- the FID that established this convention
-
----
-
-<sub>Part of the [savant-code/savant-code monorepo](https://github.com/savant0x/savant-code), governed by the [ECHO
-Protocol v0.2.0](../../ECHO.md).</sub>

package/dev/session-summaries/2026-07-16-1255.md

@@ -1,128 +0,0 @@
-# Session 2026-07-16-1255: Resumption — OpenRouter Direct Provider
-
-## Initial State Assessment
-
-- **Protocol:** ECHO v0.1.2 (updated from v0.1.1 since last session), `strict_mode: true` (all 15 laws active).
-- **Language:** TypeScript monorepo (Bun runtime).
-- **New in ECHO v0.1.2:**
-  - **FID Perfection Loop Trigger** (line 232): operator phrase "run the perfection loop" forces RED→GREEN→AUDIT on FIDs
-    with missed-question surfacing.
-  - **FID Perfection Loop Completion Requirement** (line 285): every open FID must have complete Perfection Loop before
-    implementation; incomplete FIDs not eligible.
-- **Prior session (2026-07-16-1221):** ECHO boot, providers/persona/dev orientation, env hygiene fix (FID-005),
-  OpenRouter swap (FID-006).
-
-## State Verification (Law 1 — Read 0-EOF; ECHO Audit)
-
-Re-read `ECHO.md` (447 lines, v0.1.2), `protocol.config.yaml`, verified all claimed FID-005 and FID-006 changes are
-present in source:
-
-| Change | Location | Verified |
-|--------|----------|----------|
-| `load-dev-env.ts` upward-walking resolver | `cli/src/pre-init/load-dev-env.ts` | ✅ exists |
-| `.env.local` at repo root | `C:\Users\spenc\dev\savant-code\.env.local` | ✅ exists, 75 lines |
-| Preload wired as first `index.tsx` import | `cli/src/index.tsx:6` | ✅ confirmed |
-| `INFERENCE_BASE_URL` env getter | `sdk/src/env.ts:62` | ✅ confirmed |
-| `INFERENCE_API_KEY` env getter | `sdk/src/env.ts:69` | ✅ confirmed |
-| SDK exports | `sdk/src/index.ts:99-102` | ✅ confirmed |
-| `resolveOpenRouterApiKey` (`OR_MASTER_KEY`) | `sdk/src/impl/openrouter-key-resolver.ts:16` | ✅ exists |
-| `model-provider.ts` uses env-driven URL/key | `sdk/src/impl/model-provider.ts:256-259` | ✅ confirmed |
-| Dev-mode auth bypass | `cli/src/utils/auth.ts:119-130` | ✅ confirmed |
-| `getUserInfoFromApiKey` no-backend stub | `sdk/src/impl/database.ts:105-118` | ✅ confirmed |
-
-`.env.local` already configured for direct-OpenRouter:
-
-- `INFERENCE_BASE_URL=https://openrouter.ai/api/v1`
-- `OR_MASTER_KEY=<SECRET_1cb09941>`
-- `DIRECT_PROVIDER=openrouter`
-
-## Open Work
-
-| ID | Status | Topic |
-|----|--------|-------|
-| FID-2026-0714-001 | archived | `BACKGROUND` process_type (still relevant — check if resolved) |
-| FID-2026-0714-002 | archived | 740 `any` sites |
-| FID-2026-0714-003 | archived | 562 `console.*` in prod |
-| FID-2026-0714-004 | archived | Lost `Chunk` type safety |
-| FID-2026-0714-005 | archived | Env hygiene (FIXED — verified) |
-| FID-2026-0714-006 | archived | OpenRouter swap (FIXED — verified) |
-
-## Compliance Gaps Identified (ECHO Law 10, FID Auto-Archive)
-
-1. **CHANGELOG.md does not exist.** FID-005 and FID-006 were archived without CHANGELOG entries (FID Auto-Archive step 2
-   requires this).
-2. **No session summary exists for the FID-006 implementation work** (which happened between prior session and this
-   resumption). The FID itself contains the only record.
-3. **LEARNINGS.md has no entry for the FID-005/FID-006 discoveries** (e.g., `--cwd` disables dotenv, OR_MASTER_KEY
-   pattern, env-vs-backend chokepoint insight).
-
-These are all retroactive documentation gaps from the inter-session work. Per ECHO, I should address them when natural,
-not block current work on them.
-
-## Planned Work (this session)
-
-1. **Verify direct-OpenRouter boot works end-to-end** — run `bun dev` with the current `.env.local` and confirm:
-   - `Using environment: dev` printed
-   - Dev-mode auth bypass triggers (no `POST /api/auth/cli/code` failure)
-   - Login flow proceeds (or presents the bypass stub state)
-2. **Audit FID-006 claims against actual code**:
-   - Typecheck the SDK package (`bunx tsc --noEmit -p sdk/tsconfig.json`)
-   - Lint touched files (`bunx eslint` on sdk/src/impl/{model-provider.ts, openrouter-key-resolver.ts, database.ts}`)
-   - Confirm call-graph reachability per FID-006 AUDIT spec
-3. **If dev boot succeeds**, demonstrate a real inference call to OpenRouter (if `OR_MASTER_KEY` is actually a master
-   key) or identify what blocks it.
-
-## Final Outcome (this session)
-
-The actual root cause of the boot failure was **not** the auth gate (the dev-mode bypass added
-in FID-006 works correctly — verified directly: `getAuthTokenDetails()` returns
-`dev-local-bypass-token` when `INFERENCE_BASE_URL` is set). It was a **separate runtime
-crash in the TUI**: `cli/src/chat.tsx` referenced `loadCodebuffModelPreference` and
-`saveCodebuffModelPreference` inside a `useCallback` dep array without importing them.
-React's `useCallback` dep-array identifier resolution is lazy, so `tsc` did not catch it
-and the user saw a red `ReferenceError` overlay painting the entire TUI.
-
-### New work produced
-
-- **FID-2026-0716-001 (high → closed)**: missing import in `cli/src/chat.tsx`. Added both
-  identifiers to the existing `./utils/settings` import block at lines 72-77 (alphabetical).
-  AUDIT: `bun dev` TUI renders cleanly with SavantFree landing visible; tsc reports only 2
-  pre-existing model-picker.tsx errors (unrelated, separate FID). Archived to
-  `dev/fids/archive/`. CHANGELOG entry appended.
-- **FID-2026-0716-002 (low → active, flag-only)**: `model-picker.tsx` references
-  `key.input` and `key.alt` not on OpenTUI's `KeyEvent` typings. 2 tsc errors persist
-  (pre-existing baseline). Per ECHO Additional Rule, flagged but not blocking.
-- **CHANGELOG.md**: created with retroactive entries for FID-001 (this session),
-  FID-006 (OpenRouter swap, mid-session), FID-005 (env hygiene, prior session).
-- **LEARNINGS.md**: appended Session 2026-07-16-1255 learnings covering --cwd dotenv
-  disable, OR_MASTER_KEY pattern, React useCallback dep-array lazy-resolution, agent
-  behavior notes (reproduce-don't-infer, ECHO Additional Rule value, Start-Process bun
-  workaround).
-
-### Verified state at end of session
-
-- ECHO.md read 0-EOF (v0.1.2, 447 lines) — confirmed.
-- `protocol.config.yaml` strict_mode: true, language: typescript.
-- `bun dev` boots: env validation passes (`Using environment: dev`), auth bypass fires
-  (`dev-local-bypass-token`), TUI renders normally (SavantFree landing text, project dir,
-  input placeholder, `< DEFAULT` mode banner visible in captured log).
-- `bunx tsc --noEmit -p sdk/tsconfig.json`: exit 0 (FID-006 wire-up clean).
-- Active FIDs: FID-2026-0716-002 (model-picker typings, flag-only).
-- Archived FIDs: 006 + 005 (prior session) + 0716-001 (this session).
-
-## Next Action (for follow-up session)
-
-1. **Real OpenRouter smoke test**: confirm the `OR_MASTER_KEY` in `.env.local` actually
-   exchanges for a valid key and that an inference call reaches OpenRouter
-   (`minimax/minimax-m3` is the default SavantFree model — verify it is enabled for the key).
-2. **FID-2026-0716-002 fix**: cast `key` to `KeyEvent & { input?: string; alt?: boolean }`
-   in `model-picker.tsx:132-133` so tsc baseline drops to 0 errors.
-3. **Open FIDs ranked**: FID-002 (740 `any`), FID-003 (562 console), FID-004 (Chunk type
-   safety), FID-001 background terminal — all archived but the **technical debt** is not
-   actually addressed; only the bookkeeping (FID document) was closed. They are likely
-   candidates for a follow-up Perfection Loop run if the user requests it.
-
-## Asked questions / decisions (this session)
-
-- User chose: **Fix the import via FID + perfection loop** for the chat.tsx bug.
-- User chose: **Backfill now** for CHANGELOG/LEARNINGS retroactive gaps.

package/dev/session-summaries/2026-07-17-1000.md

@@ -1,64 +0,0 @@
-# Session 2026-07-17-1000: UI Redesign, Sidebar Data Wiring, Model Persistence, ASCII Header
-
-## Initial State Assessment
-
-- **Protocol:** ECHO v0.1.2, `strict_mode: true`.
-- **Language:** TypeScript monorepo (Bun runtime).
-- **Prior session (2026-07-16-1255):** OpenRouter direct provider swap, env hygiene fixes, dev-mode auth bypass verified
-  working.
-
-## Completed Work
-
-### FID-ui-redesign-neon-slate (G1-G16)
-
-| Gate | Description |
-|------|-------------|
-| G1-G16 | Neon Slate theme applied across TUI: color palette overhaul, sidebar styling, input bar border, directory line repositioning |
-
-### FID-sidebar-data-wiring (G1-G8)
-
-| Gate | Description |
-|------|-------------|
-| G1-G8 | Right sidebar wired with live data: session info, model selection, token counts, active tool indicators |
-
-### FID-model-persistence (G1-G6)
-
-| Gate | Description |
-|------|-------------|
-| G1-G6 | Unified model pipeline via `useSavantModelStore.switchModel()` — single source of truth replacing 4 fragmented stores |
-
-## Key Changes
-
-- **Neon Slate theme:** New color palette across entire TUI
-- **Right sidebar:** Live data display (session info, model, tokens, tools)
-- **Model pipeline:** `useSavantModelStore.switchModel()` as unified entry point (was 4 separate stores)
-- **ASCII art header:** With border framing and version tracking
-- **Input bar border:** Visual refinement on chat input
-- **Directory line:** Repositioned in layout
-
-## Issues Resolved
-
-| Issue | Resolution |
-|-------|------------|
-| Model drift (4 stores → 1) | Consolidated into `useSavantModelStore` with `switchModel()` |
-| OpenTUI text rendering | Required numeric width (not string) for layout calculations |
-| `useLogo` fallback | Added fallback path when logo asset unavailable |
-| `import.meta.dir` path resolution | Fixed for correct runtime path in Bun context |
-
-## Typecheck
-
-- **CLI:** passes (TS5101 deprecation warnings only)
-- **SDK:** passes (TS5101 deprecation warnings only)
-- **Database:** passes (TS5101 deprecation warnings only)
-
-## Files Changed
-
-- `cli/src/chat.tsx` — sidebar wiring, model store integration
-- `cli/src/components/` — new/updated UI components for Neon Slate theme
-- `sdk/src/` — model persistence pipeline
-
-## Next Action (for follow-up session)
-
-1. Address remaining FID-2026-0716-002 (model-picker typings, 2 tsc errors)
-2. Consider Perfection Loop on archived technical debt FIDs if requested
-3. OpenRouter smoke test (confirm OR_MASTER_KEY validity)

package/dev/session-summaries/2026-07-19-eslint-zero-tolerance-cleanup.md

@@ -1,145 +0,0 @@
-# Session Summary: 2026-07-19 ESLint Zero-Tolerance Cleanup (packages/)
-
-**Session ID:** 2026-07-19-eslint-zero-tolerance-cleanup
-**Duration:** 2026-07-19 (after FID-028 + OpenRouter branding)
-**Status:** completed (in-progress — CLI remaining)
-
----
-
-## Initial State
-
-### Environment
-
-- **OS:** Windows 11 (win32)
-- **Language/Runtime:** TypeScript 5.x, Bun 1.3.14
-- **Branch:** main
-- **Last Commit:** FID-026 Phase B close-out (rebrand: codebuff → savant-code)
-
-### Dependencies
-
-- ESLint flat config (`eslint.config.js`) with `typescript-eslint` v7+
-- `eslint-plugin-import` for import ordering rules
-
----
-
-## Planned Work
-
-1. [x] Fix all ESLint issues in `packages/` (45 issues)
-2. [x] Fix remaining `sdk/` issues (~31 post-FID-029 initial cleanup)
-3. [x] Fix remaining `agents/` issues
-4. [ ] Fix `cli/` issues (136 remaining — deferred to next session)
-
----
-
-## Work Completed
-
-### Task 1: Fix `sdk/src` ESLint issues (~31 issues)
-
-- **Status:** completed
-- **Changes Made:**
-  - `impl/model-provider.ts`, `impl/llm.ts` — replaced `any` with proper interfaces (`ProviderParsedResponse`, typed
-    error structures)
-  - `__tests__/*.test.ts` — replaced `as any` and `: any` with concrete types (mock<[], void>, etc.), added proper test
-    interfaces
-- **Verification:** `eslint sdk/src/ --max-warnings 0` — 0 issues ✅
-
-### Task 2: Fix `packages/` ESLint issues (45 issues)
-
-- **Status:** completed
-- **Changes Made:**
-  - 30 `no-explicit-any` errors fixed: replaced `mock<any, any[]>` with `mock<[], void>`, `: any` with
-    `Partial<Parameters<>>`, `Record<string, any>` with concrete types, `as any` casts with proper type annotations
-  - 6 `no-unused-vars` warnings fixed: prefixed `parentResult` → `_parentResult`, `toolResults` → `_toolResults`,
-    `result` → `_result`, `step` → `_step`
-  - 6 `import/order` warnings fixed: moved `StreamChunk` type imports before `function-params` imports, fixed malformed
-    import merge in `read-docs-tool.test.ts`
-  - 2 `no-console` warnings fixed: removed debug `console.log` calls
-  - Fixed TypeScript compilation errors from overly restrictive `Record<string, ...>` types by using
-    `Partial<Parameters<>>` and `{ n?: number }` patterns
-- **Verification:** `eslint packages/ --max-warnings 0` — 0 issues ✅
-
-### Task 3: Fix `agents/` ESLint issues
-
-- **Status:** completed
-- **Changes Made:**
-  - Replaced `any` with concrete types across editor, base2, and type definition files
-  - Fixed `import/order` warnings
-  - Removed `no-console` violations in test runner files
-- **Verification:** `eslint agents/ --max-warnings 0` — 0 issues ✅
-
-### Task 4: Fix `cli/` ESLint issues (136 remaining)
-
-- **Status:** in-progress (deferred)
-- **Remaining:** 44 errors, 92 warnings in cli/src/
-- **Note:** 11 warnings are auto-fixable with `--fix`
-
----
-
-## Issues Discovered
-
-### Issue 1: CRLF/LF line ending mismatches break str_replace
-
-- **Severity:** medium
-- **Status:** acknowledged
-- **Detail:** The `str_replace` tool consistently failed on files with CRLF line endings (Windows default). Python
-  scripts were needed as a workaround. Files stored with LF endings worked fine.
-
-### Issue 2: Overly restrictive Record types cause TypeScript compilation errors
-
-- **Severity:** medium
-- **Status:** resolved
-- **Detail:** Replacing `: any` with `Record<string, string | number | boolean | null | undefined>` was too restrictive
-  for objects containing functions and nested types. Fixed by using `Partial<Parameters<typeof fn>[0]>` pattern instead.
-
----
-
-## Validation Results
-
-- [x] `eslint packages/ --max-warnings 0`: PASS (0 errors, 0 warnings)
-- [x] `eslint sdk/src/ --max-warnings 0`: PASS (0 errors, 0 warnings)
-- [x] `eslint agents/ --max-warnings 0`: PASS (0 errors, 0 warnings)
-- [ ] `eslint cli/src/ --max-warnings 0`: FAIL (44 errors, 92 warnings — deferred)
-
----
-
-## Final State
-
-### Code Changes
-
-- **Files Modified:** ~35 files across sdk/, packages/, agents/, cli/
-- **Changes:** ESLint compliance fixes — no functional or runtime changes
-
-### Git Status
-
-- **Branch:** main
-- **Uncommitted Changes:** yes
-
----
-
-## Lessons Learned
-
-- `Partial<Parameters<typeof fn>[0]>` is a clean replacement for `: any` in test helper variables when the exact type is
-  complex and dynamically extended in `beforeEach`
-- `Record<string, primitiveUnion>` is too restrictive for test objects that contain functions, nested objects, and
-  AbortSignal instances — use function-parameter-based types instead
-- `mock<[], void>` is the correct type for `mock(() => {})` in bun:test — avoids `mock<any, any[]>`
-- CRLF/LF line endings cause fragile str_replace tool behavior on Windows; Python scripts with explicit `newline=''` are
-  more reliable for bulk replacements
-
----
-
-## Next Session
-
-### Priority Tasks
-
-1. [ ] Fix `cli/src/` ESLint issues (136 remaining): 44 `no-explicit-any` errors + 92 warnings (mostly `import/order`,
-   `no-unused-vars`, `no-console`)
-2. [ ] Run full x4 typecheck gate (sdk + common + agent-runtime + cli)
-3. [ ] Close FID-029 with all workspaces at 0
-
-### Notes for Next Agent
-
-- The pattern proven in common/, packages/, sdk/, and agents/ works: replace `: any` with `Partial<Parameters<>>`,
-  `mock<any, any[]>` with `mock<[], void>`, and `Record<string, any>` with concrete AgentTemplate/ToolMessage/etc. types
-- `cli/src/` is the largest workspace with ~136 remaining issues
-- FID-2026-0719-029 tracks the overall zero-tolerance push gate

package/dev/session-summaries/2026-07-19-fid-026-debugging-and-rename.md

@@ -1,79 +0,0 @@
-# Session Summary — 2026-07-19: FID-026 Debugging + IS_SAVANT_FREE Rename
-
-**Duration:** 2026-07-19 (afternoon session)
-**Context:** Post-FID-026 Phase B rebrand. CLI launched showing "Out of credits" despite OpenRouter routing being configured.
-
----
-
-## Issues Diagnosed
-
-### 1. "Out of Credits" Banner in Direct-Provider Mode (Root Cause)
-
-**Symptom:** CLI showed "Out of credits. Please add credits at https://savant-code.com/usage" despite
-`DIRECT_PROVIDER=openrouter` and `OPENROUTER_API_KEY` being set.
-
-**Root cause:** `useUsageMonitor` and `OutOfCreditsBanner` never checked `isDirectProviderMode()`. They only checked
-`IS_SAVANT_FREE` (free mode flag). When running in premium mode with direct-provider routing, the usage query fired against
-the backend URL (which defaulted to `https://savant-code.com`) instead of being skipped. The rebrand's env var rename
-(`NEXT_PUBLIC_CODEBUFF_APP_URL` → `NEXT_PUBLIC_FREEBUFF_APP_URL`) exposed this gap — the user may have had the old env
-var set before the rebrand.
-
-**Fix:** Added `isDirectProviderMode()` bypass to 4 files:
-
-- `use-usage-monitor.ts` — `enabled: !IS_SAVANT_FREE && !isDirectProviderMode()`
-- `out-of-credits-banner.tsx` — early return
-- `subscription-limit-banner.tsx` — early return
-- `usage-banner.tsx` — early return
-
-### 2. `IS_FREEBUFF` → `IS_SAVANT_FREE` Rename
-
-**Scope:** 132 instances across 46 files, all in `cli/src/`.
-
-**Method:** Single `sed` replacement across all `.ts`/`.tsx` files. Updated declaration in `constants.ts` with
-clarifying comment documenting the `SAVANT_FREE_MODE` env var mapping.
-
-**Quality gate:** CLI typecheck passes at 0 errors. x4 typecheck gate all green.
-
-### 3. Free Mode Disabled (Temporary)
-
-Hardcoded `IS_SAVANT_FREE = false` with TODO comment. The full SavantFree system (session gate, model store, UI
-components, free model selector) is preserved intact — only the flag is bypassed. Restore with one line change when
-ready.
-
----
-
-## Key Learnings
-
-1. **Direct-provider mode was incomplete.** The connection status check skipped backend pings, but
-   usage/subscription/credits banners all independently queried the backend. Each banner was gated only on
-   `IS_SAVANT_FREE`, not `isDirectProviderMode()`. When adding new backend-dependent UI, always add the direct-provider
-   bypass.
-
-2. **Env var renames have cascading effects.** `NEXT_PUBLIC_CODEBUFF_APP_URL` → `NEXT_PUBLIC_FREEBUFF_APP_URL` broke any
-   pre-existing user env configs. The fallback (`https://savant-code.com`) meant API calls went to the wrong host
-   silently.
-
-3. **`IS_SAVANT_FREE` was the last unbranded constant.** The rebrand renamed file paths, component names, types, and env
-   vars — but the feature flag constant was left for last. 132 instances is a lot, but a single `sed` replacement
-   handled it cleanly because the name was unique and used consistently.
-
-4. **Doc counts must be source-verified.** Nova caught undercounts in the preserved-item tables. Source-verified
-   repo-wide counts: `codebuff_tool_call` = 97, `codebuff_cli` = 2,
-   `codebuff_terminal_command` = 1, `SAVANT_FREE_MODE` = 108,
-   `CODEBUFF_CLI_*` = 51, savant settings keys = 23. Active-source-only counts
-   are lower (e.g., 72 / 103 / 24 / 25). Repo-wide counts include the audit
-   documents themselves; active-source counts exclude docs/tests/CHANGELOG and
-   are the operational baseline. `codebuff-client.ts` was verified removed from disk via `test -f`; no code action
-   required.
-
----
-
-## Files Changed (This Session)
-
-| Change | Files | Instances |
-|--------|-------|-----------|
-| Direct-provider bypass | 4 | 4 early-return/enabled changes |
-| `IS_FREEBUFF` → `IS_SAVANT_FREE` | 46 | 132 replacements |
-| Comment update | 1 | Declaration doc in constants.ts |
-
-**Cumulative FID-026:** 232 files, 2,132 insertions, 927 deletions.

package/dev/session-summaries/2026-07-19-fid-026-phase-b-rebrand.md

@@ -1,76 +0,0 @@
-# Session 2026-07-19: FID-026 Phase B — TypeScript Rebrand
-
-## Summary
-
-Executed FID-026 Phase B (steps 1–6): complete rebrand of all TypeScript workspaces
-from `@codebuff/*` → `@savant-code/*`. Reduced 171 type errors to 0 through surgical
-`str_replace` edits across ~50 files — no scripts or sed used.
-
-**Final state:** 199 files changed, 1,984 insertions, 800 deletions. x4 typecheck gate
-clean (sdk + common + agent-runtime + cli). FID archived to `dev/fids/archive/`,
-CHANGELOG entry written.
-
-## Key Changes
-
-### Component renames (SavantFree$1 mangled identifiers → proper names)
-
-- `SavantFreeModelSelector`, `SavantFreeLandingScreen`, `SavantFreeReferralBanner`,
-  `SavantFreeActiveSessionSummary`, `SavantFreeSupersededScreen`
-
-### Type renames
-
-- CLI types: `SavantFreeSession`, `SavantFreeSessionStatus`, `SavantFreeSessionStore`,
-  `SavantFreeModelStore`, `SavantFreeSessionProgress`, `SavantFreeInstanceOwner`,
-  `SavantFreeStreakLine`, `SavantFreeGateErrorCode`, `SavantFreeReferralFocusTarget`
-- Common types: `SavantSessionState`, `SavantModel`, `SavantAccessTier`,
-  `SavantReferralInfo`, `SavantBlockReason`, `SavantIpPrivacySignal`,
-  `SavantRateLimitsByModel`, `SavantStreakResponse`
-
-### Env/client renames
-
-- `resetCodebuffClient` → `resetSavantCodeClient` (5 files)
-- `getCodebuffClient` → `getSavantCodeClient` (2 files)
-- `CODEBUFF_API_KEY` → `SAVANT_CODE_API_KEY` (2 files)
-- `NEXT_PUBLIC_CODEBUFF_APP_URL` → `NEXT_PUBLIC_FREEBUFF_APP_URL` (4 files + fallback)
-- `CODEBUFF_IS_BINARY` → `SAVANT_CODE_IS_BINARY` (5 files + CliEnv type)
-
-### Cleanup
-
-- Removed stale `codebuff-client.ts` (0 importers)
-- Renamed `LOGO_CODEBUFF` → `LOGO_SAVANT_CODE`
-
-### Intentionally preserved
-
-- Wire protocol: `codebuff_tool_call`, `codebuff_cli`, `codebuff_terminal_command`,
-  `codebuff_end_step`, `cli.update_codebuff_failed`
-- Config paths: `manicode` config dir, `.manicodeignore`
-
-## Quality Gates
-
-- ✅ cli typecheck: 0 errors (down from 171 → 0)
-- ✅ common typecheck: 0 errors
-- ✅ x4 gate (sdk + common + agent-runtime + cli): all 0 errors
-- ✅ Repo-wide grep: 0 stray `@codebuff/`, `codebuff`, or `manicode` in source
-
-## Key Learnings
-
-- **Never use sed for rebrands at scale.** `SavantFree$1` was a prior sed artifact.
-  All fixes done via `str_replace` with exact context strings — no regex, no cascading
-  corruption.
-- **Mangled identifiers cascade badly.** A single prior-broken `Freebuff$1` → `SavantFree$1`
-  mangling contaminated 27 files with a name that mapped to 8 different types.
-  Context-specific per-file replacements were the only safe approach.
-- **Wire protocol references must stay.** The `codebuff_tool_call` XML tag, Gravity ads
-  surface identifiers, and analytics event string values cannot be renamed without
-  breaking server/LLM/ads compatibility.
-- **Config dir paths are user-facing.** Changing `~/.config/manicode/` would orphan
-  all existing user installations. Left as-is with explicit documentation.
-
-## Environment
-
-- **Date:** 2026-07-19
-- **OS:** Windows 11 + Git Bash (MSYS)
-- **Bun:** 1.3.14
-- **TypeScript:** 5.5.4, `strict: true`
-- **ECHO Protocol:** v0.2.0
-- **Branch:** `main`