@alphafox/cli 0.3.11 → 0.3.13

package/skills/alphafox-shared/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: alphafox-shared
 description: Shared AlphaFox CLI rules for Agents — auth, profiles, envelopes, risk gates, and public operationIds only.
-version: 0.3.11
+version: 0.3.13
 ---
 
 # AlphaFox shared Agent contract
@@ -14,7 +14,7 @@ Co-versioned with `@alphafox/cli`. Query compatibility with `alphafox version --
 
 Prefer the wizard (CLI + Agent Skills) or the Agent install guide. Do not treat
 `npm install -g @alphafox/cli` as enough for Agents — Skills must be registered
-with `alphafox skills sync`.
+with `alphafox skills sync` (canonical store plus `~/.claude/skills` links).
 
 ```bash
 npx @alphafox/cli@latest install
@@ -24,6 +24,15 @@ npx @alphafox/cli version --format json --no-input
 npx @alphafox/cli doctor --format json --no-input
 ```
 
+Uninstall is **not** `alphafox uninstall`. After an explicit user request:
+
+```bash
+curl -fsSL https://raw.githubusercontent.com/alphafoxai/alphafox-cli/main/scripts/uninstall.cjs | node -- --dry-run
+curl -fsSL https://raw.githubusercontent.com/alphafoxai/alphafox-cli/main/scripts/uninstall.cjs | node -- --yes
+```
+
+After install, `auth status --verify` shows `session: active`, and the AI tool has restarted, follow skill `alphafox` **After install** (Lite square 带单员 + classic strategies). Do not skip that welcome.
+
 The CLI checks npm at most once every 24 hours and only prints a notice on
 **stderr**. It never auto-upgrades. If you see
 `[alphafox] update available` (or `updateAvailable: true`), ask the user:

package/skills/auth/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: alphafox-auth
 description: Login, status, logout, whoami, and environment isolation for AlphaFox CLI.
-version: 0.3.11
+version: 0.3.13
 ---
 
 # Auth Skill

package/skills/cache/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: alphafox-cache
 description: Inspect and clean local Engine backtest caches (downloaded OHLCV tape and wasm runtime). Use when the user asks to 清理缓存, free disk, or after a large historical backtest.
-version: 0.3.11
+version: 0.3.13
 ---
 
 # Cache

package/skills/engine-backtest/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: alphafox-engine-backtest
 description: Local Engine WASM backtest (alphafox engine-backtest run|sweep) vs catalog experiment CRUD.
-version: 0.3.11
+version: 0.3.13
 ---
 
 # Engine Backtest

package/skills/exchange/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: alphafox-exchange
 description: Exchange connectors list and connection management via Public API.
-version: 0.3.11
+version: 0.3.13
 ---
 
 # Exchange connectors

package/skills/market/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: alphafox-market
 description: Market data and ticker resolution for US equity perps, RWAs, and crypto on the same perp catalog. Use when the user names 美股, NVDA, AAPL, BTC, or any 标的. Keep the operator's asset class via symbolMetadata — do not rewrite NVDA into a crypto coin.
-version: 0.3.11
+version: 0.3.13
 ---
 
 # Market

package/skills/notification/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: alphafox-notification
 description: Notification channels and subscriptions.
-version: 0.3.11
+version: 0.3.13
 ---
 
 # Notification

package/skills/strategy/SKILL.md

@@ -1,18 +1,22 @@
 ---
 name: alphafox-strategy
-description: Strategy definitions — list types (grid, dca, copy, …) and validate config. Creating a running strategy is creating a trader; use alphafox-trading for that.
-version: 0.3.11
+description: Strategy definitions — list types, read a definition's contract, and validate config. Creating a running strategy is creating a trader; use alphafox-trading for that. Local Engine backtest is alphafox-engine-backtest.
+version: 0.3.13
 ---
 
 # Strategy definitions
 
 Always `--format json --no-input`. Read scopes `trading:read`; validate is `trading:write`.
 
-A **definition** is a strategy type (grid, dca, copy, …). A **trader** is one running instance of a definition. Instantiating a definition is `alphafox-trading`, not this skill.
+A **definition** is a strategy type. A **trader** is one running instance. Instantiating is `alphafox-trading`. Local wasm backtest is `alphafox-engine-backtest`. This skill only discovers types and checks config.
 
-Whenever the human names a ticker (US stock, coin, or contract), resolve it with `alphafox resolve-symbols` (`skills/market`) before writing symbols into a config you later validate or hand to create. 美股 are equity perps in `binance_perp_usdt` (`NVDA/USDT:USDT`, `assetClass=equity_perp`) — do not swap them for a crypto coin.
+Human-named tickers go through `alphafox resolve-symbols` (`skills/market`) before they enter a config you later validate or hand to create. 美股 are equity perps in `binance_perp_usdt` (`NVDA/USDT:USDT`, `assetClass=equity_perp`).
 
-## Read
+Do not enumerate engine strategy IDs in this file. Pick the definition from `list` / `byId.get`. Do not add a wizard command. Do not invent a second catalog.
+
+## Discover
+
+`trading.strategy_definitions.list` returns **active** rows only. Hidden types (including Hyperliquid / rebate copy) are absent from list; `byId.get` and `validate_config` still work when the operator named that id. Creation of those copy variants is `alphafox-trading` (`trading.hl_copy_traders.create` / `trading.rebate_copy_traders.create`).
 
 ```bash
 alphafox schema trading.strategy_definitions.list --format json --no-input
@@ -20,18 +24,51 @@ alphafox api GET /api/v1/trading/strategy-definitions --format json --no-input
 alphafox trading strategy_definitions byId get --definitionId <id> --format json --no-input
 ```
 
-Use the list to pick the definition the operator named. Copy / rebate-copy / DCA / grid are rows in this catalog, not a separate product.
+Match the name the operator used against list `id` / `name` / `display`. If they already gave an id that list omitted, `byId.get` that id. Copy / DCA / grid are catalog rows, not separate products.
+
+`byId.get` is the operator model. Read, in order:
+
+1. `id`, `category` (`COPY` / `DCA` / `GRID` / `TREND` / `OTHERS`), `status`
+2. English `description` (mechanism). Prefer it over marketing `display.description`
+3. `capabilities` and `commonModules` (event-driven vs polling, signal sources, manual sync)
+4. `strategyConfigSchema` required fields and each field's `display` — including decision-logic enums inside this definition
+5. `capabilities.actionDefinitions` (what a manual action changes)
+
+Explain the type from those fields. Missing a layer → say unknown; do not fill from memory. Decision logic (`simple-long`, grid `mode` `neutral`/`long`/`short`) is an internal parameter, not a new definition id.
+
+## Configure with the human
+
+The human answers knobs. You write JSON.
+
+1. Confirm the definition from `byId.get` in the operator's language (what it is, what drives it, how positions change).
+2. From `strategyConfigSchema` plus common required fields, ask **only** values the human must choose: symbols (resolve first), direction / mode, size, signal source, leverage. Do not walk every optional key.
+3. Write `strategy-config.json` as:
+
+```json
+{
+  "configSchemaVersion": 4,
+  "config": {
+    "common": {},
+    "strategy": {}
+  }
+}
+```
+
+`configSchemaVersion` comes from the definition (`configSchemaVersion` on `byId.get` / list). Omit it only when the schema says it is optional; when present it must match the definition. `common` is shared risk / SLTP / execution / market. `strategy` is this type's parameters and decision logic. Do not use top-level `settings`, `policyId`, or `policyParams`.
+
+4. Keys and enums come from the definition schema, not from this skill. Do not ship a default `grid.json` / `dca.json`.
 
 ## Validate config
 
-Read `request.body` first. Do not invent definition or config fields.
+Read `alphafox schema trading.strategy_definitions.byId.validate_config` first. Catalog `request.body` may look like a free `JsonObject`; still send the envelope above. The server checks the definition schema.
 
 ```bash
-alphafox schema trading.strategy_definitions.byId.validate_config --format json --no-input
 alphafox trading strategy_definitions byId validate_config --definitionId <id> --config @./strategy-config.json --format json --no-input
 ```
 
-After the config validates, create the running instance with `alphafox-trading`.
+`body_schema` / `body_schema_missing` (exit `64`): re-read the operation schema. Server field-path errors: fix that path. Do not retry with a different envelope.
+
+After it validates: create with `alphafox-trading`, or backtest with `alphafox-engine-backtest`. Do not create or backtest from this skill.
 
 ## operationIds
 

package/skills/trading/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: alphafox-trading
 description: Running strategies (traders) — create, list, start, and stop. A trader is a live or paper strategy instance (grid, dca, copy, …), not a person.
-version: 0.3.11
+version: 0.3.13
 ---
 
 # Running strategies (traders)