feat(cursor): split legacy bridge from cliproxy provider

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`.