fix: cli command reference

Author: rellfy

src/console_and_cli.md

@@ -24,26 +24,29 @@ asterai auth status             # Show current auth status
 ### Component Commands
 
 ```bash
-asterai component init <name>   # Create a new component project
-asterai component push          # Push component to the registry (from project dir)
-asterai component pull <name>   # Pull a component from the registry
-asterai component list          # List your components
-asterai component pkg           # Package the component's WIT into a WASM package
+asterai component init [name] [-l <language>]    # Scaffold a new component project
+asterai component build                          # Build the component (from project dir)
+asterai component pkg                            # Package the component's WIT into a WASM package
+asterai component push                           # Push component to the registry (from project dir)
+asterai component pull <name>                    # Pull a component from the registry
+asterai component list                           # List your components
+asterai component delete <namespace:name>        # Delete a component and all its versions
 ```
 
 ### Environment Commands
 
 ```bash
-asterai env init <name>                           # Create a new environment
-asterai env run <name>                            # Run environment locally
-asterai env call <name> <component> <fn> [args]   # Call a function
-asterai env push <name>                           # Push environment to registry
-asterai env pull <name>                           # Pull environment from registry
-asterai env list                                  # List your environments
-asterai env inspect <name>                        # Show environment details
-asterai env add <name> --component <spec>         # Add a component
-asterai env remove <name> --component <spec>      # Remove a component
+asterai env init <name> [-e]                     # Create a new environment (-e to edit)
+asterai env edit <name>                          # Open environment in editor ($EDITOR or vi)
+asterai env call <name> <component> <fn> [args]  # Call a function
+asterai env push <name>                          # Push environment to registry
+asterai env pull <name>                          # Pull environment from registry
+asterai env list                                 # List your environments
+asterai env inspect <name>                       # Show environment details
+asterai env add-component <env> <component>      # Add a component
+asterai env remove-component <env> <component>   # Remove a component
 asterai env set-var <name> --var NAME=VALUE       # Set environment variable
+asterai env delete <namespace:name>              # Delete an environment (-r for registry)
 ```
 
 ## ☁️ Cloud Console

src/environments.md

@@ -28,8 +28,8 @@ asterai env init my-env
 This creates an empty environment. Add components to it:
 
 ```bash
-asterai env add my-env --component your-username:hello-world@0.1.0
-asterai env add my-env --component other-user:useful-tool@1.2.0
+asterai env add-component my-env your-username:hello-world@0.1.0
+asterai env add-component my-env other-user:useful-tool@1.2.0
 ```
 
 ## ⚙️ Configuration
@@ -99,8 +99,8 @@ processing component:
 
 ```bash
 asterai env init data-pipeline
-asterai env add data-pipeline --component your-username:web-scraper@1.0.0
-asterai env add data-pipeline --component your-username:data-processor@1.0.0
+asterai env add-component data-pipeline your-username:web-scraper@1.0.0
+asterai env add-component data-pipeline your-username:data-processor@1.0.0
 ```
 
 The data processor can import and call functions from the web scraper,
@@ -124,7 +124,7 @@ This shows:
 ```bash
 asterai env list                    # List all your environments
 asterai env pull my-env             # Pull an environment from the registry
-asterai env remove my-env --component your-username:hello-world@0.1.0  # Remove a component
+asterai env remove-component my-env your-username:hello-world@0.1.0  # Remove a component
 ```
 
 ## 👉 Next Steps

src/hello_world.md

@@ -41,7 +41,7 @@ asterai auth status
 ### 3. Create a new component
 
 ```bash
-asterai component init hello-world typescript
+asterai component init hello-world
 cd hello-world
 ```
 
@@ -119,28 +119,20 @@ Create a new environment and add your component to it:
 
 ```bash
 asterai env init my-env
-asterai env add my-env --component your-username:hello-world@0.1.0
+asterai env add-component my-env your-username:hello-world@0.1.0
 ```
 
-### 9. Run locally
+### 9. Call your function
 
-Run the environment locally:
-
-```bash
-asterai env run my-env
-```
-
-### 10. Call your function
-
-In another terminal, call your component's function:
+Call your component's function:
 
 ```bash
 asterai env call my-env your-username:hello-world hello-world.greet '"World"'
 ```
 
 You should see: `hello World!` 🎉
 
-### 11. Push to the cloud (optional)
+### 10. Push to the cloud (optional)
 
 To run your environment in the cloud, push it to the registry:
 

src/registry.md

@@ -32,7 +32,7 @@ Use them for proprietary tools or internal integrations.
 Publish a component with the CLI:
 
 ```bash
-asterai publish
+asterai component push
 ```
 
 The component version is defined in your `component.wit` file.