@solarains/va-cli 0.1.1 → 0.1.2

package/README.md

@@ -1,132 +1,18 @@
-# va-cli
+# @solarains/va-cli
 
-Bootstrap CLI for the new VAOne product.
+VisionAlpha CLI.
 
-This project intentionally starts as a runnable but business-light CLI shell. It
-defines the command tree, local config and state layout, token-storage
-abstraction, diagnostics path, and placeholder commands that later child
-changes will extend for browser auth, installation binding, and usage queries.
-
-Parent architecture references:
-
-- `openspec/changes/define-skills-mvp-architecture/proposal.md`
-- `openspec/changes/define-skills-mvp-architecture/design.md`
-- `openspec/changes/define-skills-mvp-architecture/specs/skills-system-architecture/spec.md`
-- `openspec/changes/define-skills-mvp-architecture/master-task-list.md`
-- `openspec/changes/bootstrap-va-cli/design.md`
-- `openspec/changes/add-cli-browser-auth-flow/proposal.md`
-- `openspec/changes/add-cli-browser-auth-flow/design.md`
-
-Current command surface:
-
-- `vaone init`
-- `vaone auth login`
-- `vaone auth logout`
-- `vaone usage`
-- `vaone doctor`
-
-Current auth foundation:
-
-- `vaone auth login` now generates PKCE verifier/challenge pairs for a public CLI client
-- the CLI creates or resumes a durable installation identity with ed25519 key material
-- primary completion uses a localhost loopback callback
-- fallback completion prints the browser URL and terminal QR code, then polls the same auth session
-- token persistence stores account id, installation id, session id, access token, and refresh token metadata
-- refresh continuation signs `refreshToken + installationId + signedAt` with the local installation private key
-- revoked installations and invalid installation-proof refresh attempts now resolve to explicit re-login guidance instead of generic refresh failure
-
-Current source layout:
-
-- `src/cli/` startup, command tree, help rendering
-- `src/commands/` grouped command handlers
-- `src/config/` runtime configuration and endpoint loading
-- `src/features/init/` agent target detection, managed pack generation, init orchestration
-- `src/state/` local path layout and file-backed storage adapters
-- `src/shared/` logging and output helpers
-
-## `vaone init`
-
-`vaone init` is the supported onboarding path for agent-ready setup. It now:
-
-- detects Codex, Claude Code, and OpenClaw install surfaces
-- supports `project` and `user` scope installation
-- installs thin VAOne-managed agent packs that call back into `vaone`
-- chains into `vaone auth login` by default unless `--skip-login` is set
-- runs CLI-native readiness checks before exit
-
-Supported flags:
-
-- `--agents codex,claude,openclaw`
-- `--scope project|user`
-- `--skip-login`
-- `--force`
-- `--yes`
-
-Target-specific install behavior:
-
-- Codex: installs `vaone/SKILL.md` under `.codex/skills` or `~/.codex/skills`
-- Claude Code: installs managed files under `.claude/commands`, `.claude/agents`, and `.claude/VAONE.md`
-- OpenClaw: installs `vaone/SKILL.md` under `skills` or `~/.openclaw/skills`
-
-Current MVP limits:
-
-- Claude Code support is limited to managed command and agent guide files; deeper adapter behavior can be expanded later
-- OpenClaw marketplace plugin packaging is still deferred; this change only installs local skill assets
-- Agents may need a full restart or a new session before they discover newly installed files
-
-## Local development
-
-```bash
-pnpm install
-pnpm cli -- --help
-```
-
-## Validation
+## Install
 
 ```bash
-pnpm typecheck
-pnpm lint
-pnpm test
-pnpm build
-node dist/main.js --help
+npm install -g @solarains/va-cli
 ```
 
-## npm release packaging
-
-`va-cli` now assembles a dedicated publish root under `dist/publish/` and
-publishes from that directory instead of from the repository root.
-
-Useful commands:
+## Usage
 
 ```bash
-pnpm build:publish
-pnpm pack:publish
-pnpm verify:publish
+vaone --help
+vaone init
 ```
 
-Release flow:
-
-```bash
-pnpm release:prepare
-pnpm verify:publish
-npm publish dist/publish --access public
-```
-
-`pnpm release:prepare` increments the patch version in the root
-`package.json`, then rebuilds `dist/publish/` with the updated version.
-
-Before the first real npm publish, add the intended license text at
-`va-cli/LICENSE`. The packaging flow copies that file into `dist/publish/` when
-present.
-
-## Git Workflow
-
-- 提交信息使用 Conventional Commits，建议以中文描述主要变更，例如 `feat(cli): 增加日报查询命令`
-- 本仓库启用 Husky：
-  - `pre-commit` 会执行 `pnpm lint-staged` 和 `pnpm typecheck`
-  - `commit-msg` 会执行 `pnpm commitlint --edit`
-- PR 需要填写摘要、背景、验证方式，以及配置 / 认证 / 本地状态影响
-- CLI 相关 PR 请附关键命令示例输出
-- 提交前最少通过：
-  - `pnpm lint`
-  - `pnpm typecheck`
+Use `vaone ...` to access the CLI command surface.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@solarains/va-cli",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Bootstrap CLI for the VAOne product.",
   "bin": {
     "vaone": "dist/main.js"