chore: merge dev into openai provider routing

docs/cursor-integration.md

@@ -1,17 +1,20 @@
 # Cursor IDE Integration
 
-This guide covers the current CCS-owned Cursor runtime, including auth import, local daemon lifecycle, live probe checks, and dashboard controls.
+This guide covers the deprecated CCS-owned Cursor IDE bridge, including auth import, local daemon lifecycle, live probe checks, and dashboard controls.
+
+`ccs cursor` now belongs to the CLIProxy-backed Cursor provider path.
+Use `ccs legacy cursor` for the deprecated local bridge documented here.
 
 ## What It Provides
 
 - OpenAI-compatible local endpoint powered by Cursor credentials.
 - Anthropic-compatible local endpoint at `/v1/messages` for Claude-native clients.
 - Cursor model list and chat completions via the local CCS daemon.
-- Dedicated dashboard page: `ccs config` -> `Cursor IDE`.
+- Dedicated dashboard page: `ccs config` -> `Deprecated` -> `Cursor IDE (Legacy)`.
 
 ## What This Runtime Actually Does
 
-`ccs cursor` does not launch Cursor IDE itself.
+`ccs legacy cursor` does not launch Cursor IDE itself.
 
 The current workflow is:
 1. import Cursor credentials from local SQLite or manual input
@@ -32,7 +35,7 @@ Treat this as a CCS-managed Cursor bridge, not a generic CLIProxy-backed provide
 ### 1) Enable integration
 
 ```bash
-ccs cursor enable
+ccs legacy cursor enable
 ```
 
 ### 2) Import credentials
@@ -40,25 +43,25 @@ ccs cursor enable
 Auto-detect from Cursor local SQLite state:
 
 ```bash
-ccs cursor auth
+ccs legacy cursor auth
 ```
 
 Manual fallback:
 
 ```bash
-ccs cursor auth --manual --token <token> --machine-id <machine-id>
+ccs legacy cursor auth --manual --token <token> --machine-id <machine-id>
 ```
 
 ### 3) Start daemon
 
 ```bash
-ccs cursor start
+ccs legacy cursor start
 ```
 
 ### 4) Run a live probe
 
 ```bash
-ccs cursor probe
+ccs legacy cursor probe
 ```
 
 Use this to verify that the current build can complete one real authenticated request through the local daemon.
@@ -66,26 +69,37 @@ Use this to verify that the current build can complete one real authenticated re
 ### 5) Run Cursor-backed Claude
 
 ```bash
-ccs cursor "explain this repo"
+ccs legacy cursor "explain this repo"
 ```
 
 ### 6) Verify status
 
 ```bash
-ccs cursor status
+ccs legacy cursor status
 ```
 
-Use `ccs cursor` with bare or normal Claude args to run through the local Cursor proxy.
+Use `ccs legacy cursor` with bare or normal Claude args to run through the local Cursor proxy.
 The admin namespace remains available for setup and inspection:
 
 ```bash
-ccs cursor help
+ccs legacy cursor help
 ```
 
 ### 7) Stop daemon
 
 ```bash
-ccs cursor stop
+ccs legacy cursor stop
+```
+
+## Supported Cursor Provider Path
+
+For the supported CLIProxy-backed Cursor provider, use:
+
+```bash
+ccs cursor --auth
+ccs cursor --accounts
+ccs cursor --config
+ccs cursor "task"
 ```
 
 ## Runtime Defaults
@@ -96,7 +110,7 @@ ccs cursor stop
 - Model list resolution: authenticated live fetch when available, with cached/default fallback.
 - Request model validation: if a requested model is not present in the available Cursor model catalog, daemon falls back to the resolved default model.
 - Daemon API surface: `POST /v1/chat/completions`, `POST /v1/messages`, and `GET /v1/models`.
-- Live verification: `ccs cursor probe` or `POST /api/cursor/probe`
+- Live verification: `ccs legacy cursor probe` or `POST /api/cursor/probe`
 
 These values are managed in unified config and can be updated from CLI or dashboard.
 
@@ -108,7 +122,7 @@ Open dashboard:
 ccs config
 ```
 
-Then navigate to `Cursor IDE` in the sidebar.
+Then navigate to `Cursor IDE (Legacy)` in the `Deprecated` section.
 
 Available controls:
 
@@ -131,9 +145,9 @@ When raw settings include a local `ANTHROPIC_BASE_URL` port override, CCS synchr
 
 ### `Not authenticated` or `expired` in `ccs cursor status`
 
-- Re-run `ccs cursor auth` (or manual auth command).
+- Re-run `ccs legacy cursor auth` (or manual auth command).
 
-### `ccs cursor probe` fails even though status is green
+### `ccs legacy cursor probe` fails even though status is green
 
 - `status` proves local config/auth/daemon readiness only.
 - `probe` proves the live runtime path.
@@ -148,4 +162,4 @@ When raw settings include a local `ANTHROPIC_BASE_URL` port override, CCS synchr
 ### Daemon fails to start
 
 - Check if port `20129` is in use.
-- Change port in dashboard config tab, then retry `ccs cursor start`.
+- Change port in dashboard config tab, then retry `ccs legacy cursor start`.

docs/openai-compatible-providers.md

@@ -109,6 +109,11 @@ Supported request-time selectors:
 - plain model ids
   Example: `deepseek-chat`
 
+Plain model ids use exact string equality against the configured profile model
+slots (`model`, `opusModel`, `sonnetModel`, `haikuModel`). CCS does not apply
+fuzzy matching or prefix matching here. If no exact match is found, the request
+stays on the active profile with the requested model id unchanged.
+
 Routing behavior:
 
 1. `profile:model` wins immediately.
@@ -146,6 +151,11 @@ Current scenario detection:
 
 Routing decisions are logged through CCS structured logs.
 
+`longContextThreshold` uses an intentionally approximate token estimate based on
+message characters, tool payload size, and a `chars / 4` heuristic. Tune the
+threshold conservatively if your routing decision needs a sharper cutoff near
+the boundary.
+
 ## How Profile Detection Works
 
 CCS keeps these profiles in the normal API/settings-profile flow.
@@ -308,3 +318,15 @@ The shipped coverage includes:
 - integration tests for daemon lifecycle and `/health` / `/v1/models`
 - e2e tests for `ccs proxy` lifecycle
 - e2e tests for `ccs <profile>` auto-routing through a mock upstream
+
+Focused verification command:
+
+```bash
+bun test tests/e2e/proxy-command.e2e.test.ts tests/integration/proxy/request-routing.test.ts --coverage
+```
+
+Pre-merge gate:
+
+```bash
+bun run validate
+```

docs/system-architecture/index.md

@@ -1,6 +1,6 @@
 # CCS System Architecture
 
-Last Updated: 2026-04-07
+Last Updated: 2026-04-14
 
 High-level architecture overview for the CCS (Claude Code Switch) system.
 
@@ -19,6 +19,7 @@ Dashboard localization (i18n) architecture and contributor workflow are document
 
 CCS v7.34 adds Image Analysis Hook for vision model proxying through CLIProxy with automatic injection for all profile types.
 CCS v7.67 adds a native structured logging lane for CCS-owned runtime events, backed by `src/services/logging/`, bounded JSONL files under `~/.ccs/logs/`, and a dedicated dashboard `/logs` route.
+CCS PR review now uses PR-Agent in GitHub Actions, with reviews running on the self-hosted `cliproxy` runner, existing `AI_REVIEW_*` workflow variables and secrets preserved as the runtime contract, and repo-level guidance stored in `.pr_agent.toml`.
 
 ```
 +===========================================================================+
@@ -415,6 +416,30 @@ See [Provider Flows](./provider-flows.md) → Authentication Flow section.
         +---> First run creates: ~/.ccs/
 ```
 
+### PR Review Lane
+
+Automated pull request review stays in `.github/workflows/ai-review.yml`, but the workflow now runs PR-Agent instead of the old Claude action. Reviews run on the existing self-hosted `cliproxy` runner, while the workflow preserves the existing `AI_REVIEW_BASE_URL`, `AI_REVIEW_MODEL`, and `AI_REVIEW_API_KEY` contract by mapping those values into PR-Agent env keys such as `OPENAI.*`, `config.*`, and `github_action_config.*`. Repo-specific reviewer guidance lives in `.pr_agent.toml`.
+
+```
+GitHub Actions `ai-review.yml`
+      |
+      v
+Self-hosted `cliproxy` runner
+      |
+      v
+PR-Agent action
+      |
+      v
+CLIProxy
+      |
+      v
+Configured model from `.pr_agent.toml`
+```
+
+- `ai-review.yml` owns automation wiring such as runner selection, PR-Agent action usage, and runtime values mapped from `AI_REVIEW_*` into `OPENAI.*`, `config.*`, and `github_action_config.*`.
+- `.pr_agent.toml` in the repo root owns review instructions for this repository.
+- Contributors should treat PR-Agent comments and trusted `/review` reruns as the primary AI review path for PRs targeting CCS.
+
 ### Runtime Dependencies
 
 ```