licell 1.0.6 → 1.0.8

package/README.en.md

@@ -9,7 +9,7 @@ It is not just a bag of cloud commands. It is organized around one primary deliv
 - one main entry: `deploy`
 - one project state file: `.licell/project.json`
 - one set of atomic resource commands: `fn` / `oss` / `dns` / `domain`
-- one agent-facing surface: `--help` / `--output json` / `mcp` / `skills`
+- one agent-facing surface: `catalog` / `--help` / `--output json` / `capability` / `skills`
 
 Default region is `cn-hangzhou`. For agent automation, use a dedicated test account or isolated region instead of sharing a production environment directly. For team sharing, use the team auth distribution workflow described below.
 
@@ -30,6 +30,8 @@ Licell currently covers:
 - custom domains, HTTPS, CDN, DNS
 - ACR / Docker image deployment
 - serverless database and cache helpers
+- ACK / ACS cluster and workload inventory
+- protocol-driven discovery and controlled raw API fallback across 16,242 Alibaba Cloud APIs
 - MCP / skills / JSON output / shared-doc generation for agent automation
 
 ---
@@ -85,10 +87,10 @@ That means command-surface changes can converge across help, MCP, skills, and do
 
 ## Installation
 
-### Recommended: install script
+### Recommended: global npm install
 
 ```bash
-curl -fsSL https://github.com/team-harness/licell/releases/latest/download/install.sh | bash
+npm install -g licell
 ```
 
 After installation, run:
@@ -119,7 +121,8 @@ For team usage, see the [Team Auth Distribution](#team-auth-distribution) sectio
 
 ### Other install sources and upgrades
 
-- npm global install and GitHub Release binaries are also supported
+- If you do not want a Node.js dependency, use the GitHub Release installer instead: `curl -fsSL https://github.com/team-harness/licell/releases/latest/download/install.sh | bash`
+- Choose either npm or the release installer; the first `licell` on PATH shadows the other copy
 - for upgrades, run `licell upgrade`
 - read the detailed upgrade rules below only when needed
 
@@ -247,6 +250,22 @@ Usage and security guidance:
 
 ## Agent Interfaces
 
+Start every natural-language Alibaba Cloud task with the curated command catalog:
+
+```bash
+licell catalog --output json
+```
+
+If no curated command covers the outcome, continue with `capability products/search/describe`, then follow `execution.preferred`. Raw writes require `--dry-run`, explicit `--yes`, and read-back verification through `nextActions[]`.
+
+For VPC inventory, agents can stay on the curated surface and inspect the network relationships directly:
+
+```bash
+licell vpc list --region cn-hangzhou --output json
+licell vpc info <vpc> --output json
+licell vpc topology <vpc> --output json
+```
+
 ### 1. Structured help
 
 Licell help is designed for both humans and agents.

package/README.md

@@ -87,10 +87,10 @@ Licell 最新架构里，命令不再只是“能执行”，还要“能自我
 
 ## 安装
 
-### 推荐：安装脚本
+### 推荐：npm 全局安装
 
 ```bash
-curl -fsSL https://github.com/team-harness/licell/releases/latest/download/install.sh | bash
+npm install -g licell
 ```
 
 安装完成后，可直接运行：
@@ -121,7 +121,8 @@ licell auth restore '<token>' '<passkey>' --yes
 
 ### 其他安装方式与升级
 
-- 也支持 npm 全局安装和 GitHub Release 二进制分发
+- 不希望依赖 Node.js 时，可改用 GitHub Release 安装脚本：`curl -fsSL https://github.com/team-harness/licell/releases/latest/download/install.sh | bash`
+- npm 与安装脚本二选一，不要同时安装；PATH 中第一条 `licell` 会遮蔽另一份
 - 升级时直接运行 `licell upgrade`
 - 如需了解升级来源或升级渠道，再看下面这份说明
 
@@ -130,6 +131,7 @@ licell auth restore '<token>' '<passkey>' --yes
 
 <!-- BEGIN GENERATED:README_UPGRADE_GUIDANCE -->
 - `licell upgrade` 会优先按“当前正在执行的安装来源”升级
+- 不要同时保留多个全局安装来源；PATH 中排在最前的 `licell` 会遮蔽其它已升级版本，可用 `licell upgrade --dry-run --output json` 查看冲突入口
 - 如果当前是 `npm` / `pnpm` / `yarn` / `bun` 全局安装，会调用对应包管理器执行全局升级
 - 如果当前是项目内依赖、`node_modules/.bin/licell` 或开发链接，默认不会自动做全局升级
 - 安装脚本和二进制都来自同一个 `releases/latest`，优先下载预构建单文件可执行；若当前平台暂无预构建资产，自动回退源码安装
@@ -521,9 +523,11 @@ licell e2e cleanup <runId>
 
 ### Agent Contract
 
-- 发现命令目录：`licell catalog --output json`。
-- 读取单命令契约：`licell <command> --help --output json`。
-- 真正执行命令：`licell <command> --output json`，并过滤 `@@LICELL_JSON@@` 前缀逐行解析。
+- 始终先发现领域命令：`licell catalog --output json`。
+- 命中领域命令：读取 `licell <command> --help --output json`，再执行该命令。
+- 未命中领域命令：依次执行 `capability products/search/describe --output json`，并读取 `execution.preferred`。
+- raw 写操作必须先 `--dry-run`，再显式 `--yes`，最后按 `nextActions[]` 回读验证。
+- 解析执行结果时，只消费带 `@@LICELL_JSON@@` 前缀的逐行 JSON record。
 - 对 `type=event` 的 record，优先读取稳定字段 `stage` / `action` / `status` / `source` / `terminal`。
 - 对 `type=error` 的 record，优先读取 `nextActions[]` 获取首选补救步骤。
 
@@ -533,6 +537,7 @@ licell e2e cleanup <runId>
 - `licell <command> --help --output json`：读取 `help.kind` / `help.schemaVersion`；当前为 `licell-help@1.0`。
 - `licell catalog --output json`：读取 `kind` / `schemaVersion`；当前为 `licell-agent-command-catalog@1.0`。
 - `licell catalog --output json` 还会显式声明 help schema 与 CLI record schema：`licell-help@1.0` / `licell-cli-record@1.0`。
+- 读取 `catalog.agentWorkflow` 获取“领域命令优先、raw capability 兜底”的自然语言路由契约；只有两层发现都失败，才可判定不支持。
 - Agent 优先读取 `nextActions[]` 作为稳定下一步入口；`recommendedFlow` / `decisionGuide` / `remediation[]` 作为补充语义层。
 - 命令自己的业务结果字段继续读取对应命令 help / catalog 里的 `result`；下面三组 contract 只描述公共 CLI record 包络。
 
@@ -751,6 +756,12 @@ licell e2e cleanup <runId>
 | `licell ecs rm <instanceId>` | 删除（释放）ECS 实例（delete 的别名） | `--region`, `--dry-run`, `--yes` |
 | `licell ecs start <instanceId>` | 启动 ECS 实例 | `--region`, `--dry-run` |
 | `licell ecs stop <instanceId>` | 停止 ECS 实例 | `--region`, `--dry-run`, `--yes` |
+| `licell k8s clusters` | 列出当前地域的 ACK / ACS Kubernetes 集群 | `--region`, `--name` |
+| `licell k8s logs <cluster> <target>` | 只读读取 ACK / ACS 集群内工作负载日志 | `--region`, `--namespace`, `--container` |
+| `licell k8s workloads <cluster>` | 只读查询 ACK / ACS 集群内已部署的工作负载和 Service | `--region`, `--private`, `--request-timeout` |
+| `licell vpc info <vpc>` | 按 VPC ID 或唯一名称查看网络详情 | `--region` |
+| `licell vpc list` | 列出当前地域的 VPC 网络 | `--region`, `--name`, `--limit` |
+| `licell vpc topology <vpc>` | 聚合查看 VPC、交换机、路由表、NAT 网关和 EIP 拓扑 | `--region` |
 
 #### Automation & Tooling