@5ive-tech/cli 1.0.6 → 1.0.8

package/README.md

@@ -1,4 +1,4 @@
-# Five CLI
+# 5IVE CLI
 
 CLI for building, testing, deploying, and executing 5ive DSL programs.
 
@@ -6,7 +6,7 @@ CLI for building, testing, deploying, and executing 5ive DSL programs.
 
 ```bash
 npm install -g @5ive-tech/cli
-five --version
+5ive --version
 ```
 
 Or run without global install:
@@ -20,14 +20,14 @@ npx @5ive-tech/cli --help
 ### 1) Initialize a project
 
 ```bash
-five init my-program
+5ive init my-program
 cd my-program
 ```
 
 ### 2) Compile to a `.five` artifact (recommended)
 
 ```bash
-five compile src/main.v -o build/main.five
+5ive compile src/main.v -o build/main.five
 ```
 
 The `.five` artifact contains bytecode and ABI and is the best default for deployment and SDK integration.
@@ -35,29 +35,29 @@ The `.five` artifact contains bytecode and ABI and is the best default for deplo
 ### 3) Run locally
 
 ```bash
-five execute build/main.five --local -f 0
+5ive execute build/main.five --local -f 0
 ```
 
 ### 4) Configure on-chain target
 
 ```bash
-five config init
-five config set --target devnet
-five config set --keypair ~/.config/solana/id.json
-five config set --program-id <FIVE_VM_PROGRAM_ID> --target devnet
+5ive config init
+5ive config set --target devnet
+5ive config set --keypair ~/.config/solana/id.json
+5ive config set --program-id <FIVE_VM_PROGRAM_ID> --target devnet
 ```
 
 ### 5) Deploy and execute on-chain
 
 ```bash
-five deploy build/main.five --target devnet
-five execute build/main.five --target devnet -f 0
+5ive deploy build/main.five --target devnet
+5ive execute build/main.five --target devnet -f 0
 ```
 
 If you already have a deployed script account:
 
 ```bash
-five execute --script-account <SCRIPT_ACCOUNT_PUBKEY> --target devnet -f 0
+5ive execute --script-account <SCRIPT_ACCOUNT_PUBKEY> --target devnet -f 0
 ```
 
 ## Program ID Resolution
@@ -66,7 +66,7 @@ For on-chain commands (`deploy`, `execute`, `deploy-and-execute`, `namespace`),
 
 1. `--program-id` flag
 2. `five.toml` `[deploy].program_id`
-3. `five config` stored value for current target
+3. `5ive config` stored value for current target
 4. `FIVE_PROGRAM_ID` environment variable
 
 If none are set, on-chain commands fail fast with a program ID setup error.
@@ -76,139 +76,129 @@ If none are set, on-chain commands fail fast with a program ID setup error.
 ### Project build flow
 
 ```bash
-five build
-five deploy build/main.five --project .
-five execute build/main.five --project . -f 0
+5ive build
+5ive deploy build/main.five --project .
+5ive execute build/main.five --project . -f 0
 ```
 
-`five build` / `--project` use `five.toml` and the generated manifest to resolve artifacts.
+`5ive build` / `--project` use `five.toml` and the generated manifest to resolve artifacts.
 
-### One-command deploy+execute (great for smoke tests)
+### One-command deploy+execute (smoke tests)
 
 ```bash
-five deploy-and-execute build/main.five --target devnet -f 0
+5ive deploy-and-execute build/main.five --target devnet -f 0
 ```
 
 ### Run tests
 
 ```bash
-five test --sdk-runner
-five test tests/ --on-chain --target devnet
+5ive test --sdk-runner
+5ive test tests/ --on-chain --target devnet
 ```
 
 ### Namespace operations
 
 ```bash
-five namespace register @your-domain
-five namespace bind @your-domain/program --script <SCRIPT_ACCOUNT_PUBKEY>
-five namespace resolve @your-domain/program
+5ive namespace register @your-domain
+5ive namespace bind @your-domain/program --script <SCRIPT_ACCOUNT_PUBKEY>
+5ive namespace resolve @your-domain/program
 ```
 
-## Advanced CLI Workflows (Optional)
+## Advanced Workflows (Optional)
 
-Most teams can stay on the quick-start path. Use these features when you need deeper control.
-
-### 1) Compile diagnostics and machine-readable metrics
+### Compile diagnostics and machine-readable metrics
 
 ```bash
-five compile src/main.v \
+5ive compile src/main.v \
   --analyze \
   --metrics-output build/compile-metrics.json \
   --metrics-format json \
   --error-format json
 ```
 
-### 2) Project-aware execution from `five.toml` context
+### Project-aware execution from `five.toml` context
 
 ```bash
-five execute --project . -f 0
-five execute --project . -f 0 --params params.json --target devnet
+5ive execute --project . -f 0
+5ive execute --project . -f 0 --params params.json --target devnet
 ```
 
-### 3) Deploy large artifacts with chunk/optimization controls
+### Deploy large artifacts with chunk/optimization controls
 
 ```bash
-five deploy build/main.five --target devnet --optimized --progress
-five deploy build/main.five --target devnet --force-chunked --chunk-size 900
-five deploy build/main.five --target devnet --dry-run --format json
+5ive deploy build/main.five --target devnet --optimized --progress
+5ive deploy build/main.five --target devnet --force-chunked --chunk-size 900
+5ive deploy build/main.five --target devnet --dry-run --format json
 ```
 
-### 4) Deploy-and-execute for fast integration checks
+### Deploy-and-execute for fast integration checks
 
 ```bash
-five deploy-and-execute build/main.five --target devnet -f 0 -p "[100]"
-five deploy-and-execute src/main.v --target local --debug --cleanup
+5ive deploy-and-execute build/main.five --target devnet -f 0 -p "[100]"
+5ive deploy-and-execute src/main.v --target local --debug --cleanup
 ```
 
-### 5) Advanced test modes
+### Advanced test modes
 
 ```bash
-five test --sdk-runner --format json
-five test test-scripts/ --on-chain --target devnet --batch --analyze-costs
-five test --watch --parallel 4
+5ive test --sdk-runner --format json
+5ive test test-scripts/ --on-chain --target devnet --batch --analyze-costs
+5ive test --watch --parallel 4
 ```
 
-### 6) Namespace manager and lockfile modes
+### Namespace manager and lockfile modes
 
 ```bash
 # On-chain manager flow
-five namespace register @acme --manager <MANAGER_SCRIPT_ACCOUNT>
-five namespace bind @acme/payments --script <SCRIPT_ACCOUNT_PUBKEY> --manager <MANAGER_SCRIPT_ACCOUNT>
+5ive namespace register @acme --manager <MANAGER_SCRIPT_ACCOUNT>
+5ive namespace bind @acme/payments --script <SCRIPT_ACCOUNT_PUBKEY> --manager <MANAGER_SCRIPT_ACCOUNT>
 
 # Local lockfile-only flow (no manager RPC)
-five namespace resolve @acme/payments --local
+5ive namespace resolve @acme/payments --local
 ```
 
-### 7) Config layering and explicit RPC overrides
+### Config layering and explicit RPC overrides
 
 ```bash
-five config set --rpc-url https://api.devnet.solana.com --target devnet
-five config set --show-config true
-five deploy build/main.five --target devnet --network https://your-rpc.example.com
+5ive config set --rpc-url https://api.devnet.solana.com --target devnet
+5ive config set --show-config true
+5ive deploy build/main.five --target devnet --network https://your-rpc.example.com
 ```
 
 ## Artifact and SDK Interop
 
-`@5ive-tech/cli` and `@5ive-tech/sdk` work best with `.five` artifacts:
-
-- Compile with CLI to `.five`
-- Load and interact in SDK via ABI-aware helpers
-- Use the same artifact in frontend flows on [5ive.tech](https://5ive.tech)
-
-You can still use `.bin` where needed, but `.five` is the preferred default.
+`@5ive-tech/cli` and `@5ive-tech/sdk` work best with `.five` artifacts.
 
 ## Common Commands
 
 ```bash
-five help <command>
-five help compile
-five help deploy
-five help execute
-five help config
+5ive help <command>
+5ive help compile
+5ive help deploy
+5ive help execute
+5ive help config
 ```
 
 ## Troubleshooting
 
 ### `Program ID required` or `owner/program mismatch`
 
-Set or override the VM program ID:
-
 ```bash
-five config set --program-id <FIVE_VM_PROGRAM_ID> --target devnet
+5ive config set --program-id <FIVE_VM_PROGRAM_ID> --target devnet
 # or
-five deploy build/main.five --program-id <FIVE_VM_PROGRAM_ID> --target devnet
+5ive deploy build/main.five --program-id <FIVE_VM_PROGRAM_ID> --target devnet
 ```
 
 ### `Keypair file not found`
 
 ```bash
-five config set --keypair ~/.config/solana/id.json
+5ive config set --keypair ~/.config/solana/id.json
 ```
 
-### Command-specific help from global help flow
+### Command-specific help
 
 ```bash
-five compile --help
-five execute --help
-five config --help
+5ive compile --help
+5ive execute --help
+5ive config --help
 ```

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "@5ive-tech/cli",
-  "version": "1.0.6",
+  "version": "1.0.8",
   "description": "High-performance CLI for Five VM development with WebAssembly integration",
   "type": "module",
   "main": "dist/index.js",
   "bin": {
-    "five": "dist/index.js",
-    "five-cli": "dist/index.js"
+    "5ive": "dist/index.js",
+    "five": "dist/index.js"
   },
   "engines": {
     "node": ">=18.0.0"
@@ -33,8 +33,7 @@
     "lint": "eslint src/**/*.ts",
     "format": "prettier --write src/**/*.ts",
     "dev": "npm run build:js:dev",
-    "prepublishOnly": "npm run build",
-    "postinstall": "npm run verify:wasm || npm run sync:wasm"
+    "prepublishOnly": "npm run build"
   },
   "files": [
     "dist/",
@@ -79,7 +78,7 @@
     "ora": "^8.0.1",
     "semver": "^7.6.0",
     "ws": "^8.16.0",
-    "@5ive-tech/sdk": "^1.1.3"
+    "@5ive-tech/sdk": "^1.1.4"
   },
   "devDependencies": {
     "@types/fs-extra": "^11.0.4",