@kvell007/embed-labs-cli 0.1.0-alpha.9 → 0.1.0-alpha.91

package/README.md

@@ -22,8 +22,8 @@ names.
 - Auth token login, logout, and status commands.
 - Account registration, API key issue/list, token usage metering, and billing
   statement preview commands.
-- Server-side application source generation through Cloud API agents, followed by
-  task artifacts and downloads.
+- Board knowledge/method discovery through Cloud API, plus local-first
+  toolchain installation, validation, compile, and hardware handoff.
 - Debug tool, device, serial, SSH, and flash commands routed through the local
   bridge.
 - Project, task, artifact, and cloud status commands routed through the cloud
@@ -41,12 +41,49 @@ public SDK until a versioned API contract is approved.
 Current experimental npm install:
 
 ```bash
-npm install -g @kvell007/embed-labs-cli@alpha
+npm install -g embedlabs@latest
 embedlabs --help
 embedlabs help getting-started
+embedlabs local toolchain list
+embedlabs plugin update check
 embedlabs plugin install all
 ```
 
+Clean reinstall:
+
+```bash
+npm uninstall -g embedlabs
+npm install -g embedlabs@latest
+embedlabs plugin install all --force
+```
+
+Trae users can install only the Trae MCP integration:
+
+```bash
+embedlabs auth login --token <your_token>
+embedlabs plugin install trae
+```
+
+The Trae installer writes Trae's `mcp.json`, configures
+`embedlabs mcp start`, copies the Embed Labs icon, and creates the local
+Gallery metadata Trae uses for MCP icons. Restart Trae after installation.
+
+For IDEs that support MCP but do not have an automatic installer yet, generate
+the correct manual MCP config:
+
+```bash
+embedlabs mcp config
+embedlabs mcp config --client cursor
+embedlabs mcp config --client trae
+```
+
+If an early test build was installed under legacy alias names, remove those
+aliases once with:
+
+```bash
+npm uninstall -g embedlabs-cli embedboard embedboard-cli
+```
+
 Future organization-scope install after final release approval:
 
 ```bash
@@ -81,32 +118,60 @@ embedlabs doctor
 embedlabs auth login --token <token>
 ```
 
+If a cloud or plugin command reaches a protected API before a token is
+configured, the CLI returns `auth_token_missing` with the registration URL and
+these setup options:
+
+```bash
+open https://api.embedboard.com/dashboard
+embedlabs auth login --token <your_token>
+# or for automation:
+export EMBED_API_TOKEN=<your_token>
+embedlabs auth status
+```
+
+If `.embed-labs/auth.json` was copied from another computer, protected Cloud
+requests fail before network I/O with `tool_integrity_check_failed` and the
+message `工具完整性校验失败，请在当前电脑重新执行 embedlabs auth login --token <key>`.
+
 For the current public API plus local TaishanPi verification path, see
 `docs/runbooks/PUBLIC_CLI_USER_VERIFICATION.md`.
 
-For the cloud build path:
+For board knowledge and local toolchain work:
 
 ```bash
-embed build template list
-embed build template show <template_id>
-embed build workspace provision --account <account_id> --project <project_id> --template <template_id>
-embed build workspace source put <workspace_id> --file ./main.c:src/main.c
-embed build application generate --workspace <workspace_id> --prompt "Create a minimal Linux app"
-embed cloud task artifacts <task_id>
-embed artifact download <artifact_id> --output ./artifact.bin
+embed board registry list
+embed board methods taishanpi-1m-rk3566
+embed board knowledge search taishanpi-1m-rk3566 --query "UART pinout"
+embed local toolchain list
+embed local toolchain latest --board taishanpi-1m-rk3566
+embed local toolchain validate --board taishanpi-1m-rk3566 --mode minimal
+embed local compile taishanpi --source ./main.c --output ./.embed-labs/build/main
 ```
 
+Server-side user workspaces and server Docker builds are disabled in the
+local-first product mode. The server remains responsible for accounts, API
+keys, model routing, billing, plugin releases, SDK/download metadata, and small
+image/DTB/logo package generation.
+
 For local hardware access:
 
 ```bash
 embed bridge start
 embed device list
 embed tool call wifi.scan --input-json '{"host":"198.19.77.2","user":"root"}'
+embed tool call rp2350.monitor.capabilities --json
+embed tool call rp2350.monitor.gpio.read --input-json '{"pins":[16,17],"pull":"none"}' --approve
+embed tool call rp2350.monitor.spi.transfer --input-json '{"hex":"a55a3cc3"}' --approve
+embed tool call rp2350.monitor.uart.write --input-json '{"baud":115200,"text":"hello","line_ending":"lf"}' --approve
+embed tool call rp2350.monitor.i2c.transfer --input-json '{"address":"0x50","write":"00","read_len":4}' --approve
+embed tool call rp2350.monitor.wifi.manage --input-json '{"action":"scan"}' --approve
+embed tool call rp2350.monitor.probe.debug --input-json '{"action":"status"}' --approve
 embed tool call chip.temperature --input-json '{"host":"198.19.77.2","user":"root"}'
 embed flash plan --board <rp2350|taishanpi> --artifact ./artifact.bin
 ```
 
-For cloud API workflows, point the CLI at a running cloud API service:
+For local Cloud API development, override the production default:
 
 ```bash
 EMBED_CLOUD_API_URL=http://127.0.0.1:18100 embed cloud status
@@ -159,14 +224,25 @@ embed billing snapshot create --account <account_id> [--from <iso>] [--to <iso>]
 embed billing snapshot list --account <account_id> [--json]
 embed billing snapshot show <billing_snapshot_id> [--json]
 
+embed board registry list [--json]
+embed board methods <template_id> [--json]
+embed board knowledge <template_id> [--json]
+embed board knowledge search <template_id> --query <text> [--json]
 embed build template list [--json]
 embed build template show <template_id> [--json]
-embed build workspace provision --account <account_id> --project <project_id> [--template <template_id>] [--copy-mode auto|copy|symlink|skeleton] [--require-seed] [--dry-run] [--json]
-embed build workspace list --account <account_id> [--json]
-embed build workspace show <workspace_id> [--json]
-embed build workspace source put <workspace_id> [--account <account_id>] --file <local_path>:<source_path> [--file <local_path>:<source_path>] [--json]
-embed build application stub --workspace <workspace_id> [--account <account_id>] [--json]
-embed build application generate --workspace <workspace_id> --prompt <request> [--account <account_id>] [--target <source_path>] [--provider stub|openai|cc|claude-code] [--model <model>] [--json]
+embed local toolchain list [--board <board_id>] [--json]
+embed local toolchain installed [--board <board_id>] [--json]
+embed local toolchain latest [--board <board_id>] [--json]
+embed local toolchain current [--json]
+embed local toolchain install [--board <board_id>] [--mode minimal|runtime|compile|qt|firmware|full|images] [--json]
+embed local toolchain validate [--board <board_id>] [--mode minimal|runtime|compile|qt|firmware|full|images] [--json]
+embed local compile taishanpi --source <main.c|main.cpp> --output <artifact> [--json]
+embed local build qt-smoke --build-dir <build_dir> [--source <qt-cmake-dir>] [--target-name <executable>] [--json]
+
+The `qt-smoke` subcommand name is kept for compatibility. When `--source` and
+`--target-name` are supplied, it builds the supplied TaishanPi Qt/CMake
+application, including official board-pack examples such as
+`board-packs/taishanpi/examples/modbus-loop-demo/taishanpi`.
 
 embed bridge start [--host 127.0.0.1] [--port 18083]
 embed bridge status [--json]
@@ -182,6 +258,14 @@ embed tool call chip.cpu.frequency --input-json '{"host":"198.19.77.2","user":"r
 embed tool call chip.temperature --input-json '{"host":"198.19.77.2","user":"root"}' [--json]
 embed tool call qml.runtime.status --input-json '{"host":"198.19.77.2","user":"root","port":18130}' [--json]
 embed tool call qml.runtime.start --input-json '{"host":"198.19.77.2","user":"root","port":18130}' [--json]
+embed tool call rp2350.monitor.capabilities [--json]
+embed tool call rp2350.monitor.gpio.read --input-json '{"pins":[16,17]}' --approve [--json]
+embed tool call rp2350.monitor.spi.transfer --input-json '{"hex":"a55a3cc3"}' --approve [--json]
+embed tool call rp2350.monitor.uart.write --input-json '{"baud":115200,"text":"hello","line_ending":"lf"}' --approve [--json]
+embed tool call rp2350.monitor.i2c.transfer --input-json '{"address":"0x50","write":"00","read_len":4}' --approve [--json]
+embed tool call rp2350.monitor.wifi.manage --input-json '{"action":"scan"}' --approve [--json]
+embed tool call rp2350.monitor.probe.debug --input-json '{"action":"status"}' --approve [--json]
+embed tool call rp2350.monitor.operation --input-json '{"action":"logic.stop","params":{}}' --approve [--json]
 
 embed serial list [--json]
 embed serial capture --path <port> [--baud 115200] [--duration 5] [--json]
@@ -248,7 +332,7 @@ preview records; they are not invoices and do not collect payment.
 - `EMBED_BRIDGE_URL`: local bridge URL used by bridge-backed commands. Default:
   `http://127.0.0.1:18083`.
 - `EMBED_CLOUD_API_URL`: cloud API URL used by cloud-backed commands. Default:
-  `http://127.0.0.1:18100`.
+  `https://api.embedboard.com`.
 - `EMBED_API_TOKEN`: auth token source for non-interactive sessions.
 - `EMBED_AUTH_PROFILE`: profile name used with `EMBED_API_TOKEN`.
 - `EMBED_AUTH_FILE`: token file path for `embed auth login`. Default:
@@ -274,10 +358,10 @@ Current local workflows are intentionally guarded:
   evidence without opening probes or starting debug sessions.
 - RP2350 UF2 flashing requires a mounted UF2 volume, a `.uf2` artifact, a ready
   flash plan, and explicit `--approve`.
-- TaishanPi flash planning can validate expected image files and local tool
-  availability, but real destructive TaishanPi flashing is guarded and not
-  enabled. `embed flash run --board taishanpi --approve` remains blocked until
-  the exact hardware profile and Board Pack command templates are accepted.
+- TaishanPi initialization image flashing resolves the installed local SDK
+  image set by default. `embed flash run --board taishanpi --approve` writes
+  through Local Bridge only after the ready plan validates `rkdeveloptool`,
+  `parameter.txt`, and all required images.
 
 These commands should be treated as current local evidence and planning tools,
 not broad hardware support claims.