chore: ensure max 100 cols

Author: rellfy

src/components.md

@@ -2,11 +2,16 @@
 title: 🧩 Components
 ---
 
-Components are the building blocks of asterai. A component is a portable, sandboxed program that can be published to the registry and run anywhere.
+Components are the building blocks of asterai.
+A component is a portable, sandboxed program that can be published to
+the registry and run anywhere.
 
 ## What is a Component?
 
-A component is compiled code with a typed interface. You write it in a supported language (TypeScript, Python, Rust, Go, etc.), define its interface, and asterai compiles it to a portable format that runs in any asterai environment.
+A component is compiled code with a typed interface.
+You write it in a supported language (TypeScript, Python, Rust, Go,
+etc.), define its interface, and asterai compiles it to a portable
+format that runs in any asterai environment.
 
 Components can:
 - 📤 Export functions for other components or AI agents to call
@@ -15,7 +20,10 @@ Components can:
 
 ## Component Interface
 
-Every component has an interface defined in [WIT (WebAssembly Interface Types)](https://component-model.bytecodealliance.org/design/wit.html). This defines what functions your component exports and what types it uses.
+Every component has an interface defined in
+[WIT (WebAssembly Interface Types)](https://component-model.bytecodealliance.org/design/wit.html).
+This defines what functions your component exports and what types it
+uses.
 
 Example interface for a burger ordering tool:
 
@@ -39,15 +47,20 @@ world component {
 
 The interface declares:
 - **Package**: Your namespace, component name, and version
-- **Imports**: Capabilities your component needs (here, the asterai host API)
+- **Imports**: Capabilities your component needs
+  (here, the asterai host API)
 - **Exports**: Functions your component provides
 - **Types**: Data structures used by your functions
 
 ### 🔗 Composability: Interfaces vs World Exports
 
-If you want other components to be able to call your component's functions, you **must** put those functions inside a named interface. Functions exported directly at the world level (bare exports) can only be called by the host runtime, not by other components.
+If you want other components to be able to call your component's
+functions, you **must** put those functions inside a named interface.
+Functions exported directly at the world level (bare exports) can only
+be called by the host runtime, not by other components.
 
-What this means is that these functions can only be called externally, e.g. from other environments via the asterai API.
+What this means is that these functions can only be called externally,
+e.g. from other environments via the asterai API.
 
 ❌ **Not composable** — only the host can call `order-burger`:
 
@@ -69,7 +82,8 @@ world component {
 }
 ```
 
-✅ **Composable** — other components can import and call `your-username:burger-shop/api`:
+✅ **Composable** — other components can import and call
+`your-username:burger-shop/api`:
 
 ```wit
 package your-username:burger-shop@0.1.0;
@@ -99,11 +113,14 @@ With the second form, another component can import your interface:
 import your-username:burger-shop/api@0.1.0;
 ```
 
-See the [Component Model composition docs](https://component-model.bytecodealliance.org/composing-and-distributing/composing.html#what-is-composition) for more details.
+See the
+[Component Model composition docs](https://component-model.bytecodealliance.org/composing-and-distributing/composing.html#what-is-composition)
+for more details.
 
 ## Component Implementation
 
-The implementation is your actual code. Here's the TypeScript implementation for the interface above:
+The implementation is your actual code.
+Here's the TypeScript implementation for the interface above:
 
 ```ts
 import * as asterai from "asterai:host/api@0.1.0";
@@ -140,10 +157,16 @@ pub fn order_burger(order: Order) -> OrderResult {
 
 ## 🏷️ Versioning
 
-Components use semantic versioning. Each published version is immutable—you can't overwrite an existing version. This ensures reproducible builds and reliable dependencies.
+Components use semantic versioning.
+Each published version is immutable—you can't overwrite an existing
+version.
+This ensures reproducible builds and reliable dependencies.
 
 ## 👉 Next Steps
 
-- [Hello World guide](/hello_world): Create and deploy your first component
-- [CLI reference](/console_and_cli): Learn the asterai CLI commands
-- [Registry](/registry): Publish and discover components
+- [Hello World guide](/hello_world):
+  Create and deploy your first component
+- [CLI reference](/console_and_cli):
+  Learn the asterai CLI commands
+- [Registry](/registry):
+  Publish and discover components

src/console_and_cli.md

@@ -4,7 +4,8 @@ title: ⌨️ CLI & Console
 
 ## CLI
 
-The asterai CLI is the primary tool for building, publishing, and running components and environments.
+The asterai CLI is the primary tool for building, publishing, and
+running components and environments.
 
 ### Installation
 
@@ -47,7 +48,8 @@ asterai env set-var <name> --var NAME=VALUE       # Set environment variable
 
 ## ☁️ Cloud Console
 
-The [cloud console](https://asterai.io/dashboard) provides a web interface for managing your asterai resources:
+The [cloud console](https://asterai.io/dashboard) provides a web
+interface for managing your asterai resources:
 
 - 📦 **Environments**: Create, configure, and monitor environments
 - 🧩 **Components**: View your published components and their versions
@@ -56,5 +58,7 @@ The [cloud console](https://asterai.io/dashboard) provides a web interface for m
 
 ## 👉 Next Steps
 
-- [Hello World guide](/hello_world): Build and run your first component
-- [Components](/components): Learn how components work
+- [Hello World guide](/hello_world):
+  Build and run your first component
+- [Components](/components):
+  Learn how components work

src/environments.md

@@ -2,7 +2,9 @@
 title: 📦 Environments
 ---
 
-Environments are deployable bundles that combine components with configuration. They are the unit of deployment in asterai.
+Environments are deployable bundles that combine components with
+configuration.
+They are the unit of deployment in asterai.
 
 ## What is an Environment?
 
@@ -12,7 +14,8 @@ An environment is a runtime context that:
 - ☁️ Can run locally or in the cloud
 - 🔒 Provides isolation between deployments
 
-Think of components as reusable building blocks, and environments as the assembled application that runs them.
+Think of components as reusable building blocks, and environments as
+the assembled application that runs them.
 
 ## 🛠️ Creating an Environment
 
@@ -52,7 +55,9 @@ const apiKey = asterai.getEnv("API_KEY");
 
 ### Secrets
 
-For sensitive values like API keys, use the cloud console to set secrets. Secrets are encrypted at rest and only decrypted at runtime.
+For sensitive values like API keys, use the cloud console to set
+secrets.
+Secrets are encrypted at rest and only decrypted at runtime.
 
 ## ▶️ Running Environments
 
@@ -64,7 +69,9 @@ Run an environment on your machine for development and testing:
 asterai env run my-env
 ```
 
-This starts a local runtime that loads your components and configuration. You can then call functions:
+This starts a local runtime that loads your components and
+configuration.
+You can then call functions:
 
 ```bash
 asterai env call my-env your-username:hello-world greeting.get-greeting '"World"'
@@ -78,21 +85,26 @@ Push your environment to run it on asterai's infrastructure:
 asterai env push my-env
 ```
 
-Once pushed, your environment is available via the asterai API. No infrastructure management required.
+Once pushed, your environment is available via the asterai API.
+No infrastructure management required.
 
 ## 🔗 Composing Components
 
-Environments can contain multiple components that work together. Each component can import and call functions from other components in the same environment.
+Environments can contain multiple components that work together.
+Each component can import and call functions from other components in
+the same environment.
 
-Example: An environment with a web scraper component and a data processing component:
+Example: An environment with a web scraper component and a data
+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
 ```
 
-The data processor can import and call functions from the web scraper, creating a pipeline.
+The data processor can import and call functions from the web scraper,
+creating a pipeline.
 
 ## Inspecting Environments
 
@@ -117,6 +129,9 @@ asterai env remove my-env --component your-username:hello-world@0.1.0  # Remove
 
 ## 👉 Next Steps
 
-- [Hello World guide](/hello_world): Create your first component and environment
-- [Components](/components): Learn how to build components
-- [CLI reference](/console_and_cli): Full CLI command reference
+- [Hello World guide](/hello_world):
+  Create your first component and environment
+- [Components](/components):
+  Learn how to build components
+- [CLI reference](/console_and_cli):
+  Full CLI command reference

src/hello_world.md

@@ -2,7 +2,8 @@
 title: 🚀 Hello World
 ---
 
-This guide walks you through creating your first asterai component and running it in an environment.
+This guide walks you through creating your first asterai component and
+running it in an environment.
 
 ## 📋 Prerequisites
 
@@ -11,7 +12,8 @@ This guide walks you through creating your first asterai component and running i
 
 ## Overview
 
-You'll create a simple component that returns a greeting, then run it locally in an environment.
+You'll create a simple component that returns a greeting, then run it
+locally in an environment.
 
 ## Steps
 
@@ -23,7 +25,8 @@ npm install -g @asterai/cli
 
 ### 2. Authenticate
 
-Generate an API key from [your dashboard](https://asterai.io/dashboard/account):
+Generate an API key from
+[your dashboard](https://asterai.io/dashboard/account):
 
 ```bash
 asterai auth login <your_api_key>
@@ -45,7 +48,8 @@ npm install
 
 ### 4. Define the interface
 
-Edit `plugin.wit` to define your component's interface. Replace `your-username` with your asterai username:
+Edit `plugin.wit` to define your component's interface.
+Replace `your-username` with your asterai username:
 
 ```wit
 package your-username:hello-world@0.1.0;
@@ -59,7 +63,8 @@ world component {
 }
 ```
 
-This declares a component that exports one function: `get-greeting`, which takes a name and returns a greeting string.
+This declares a component that exports one function: `get-greeting`,
+which takes a name and returns a greeting string.
 
 ### 5. Implement the component
 
@@ -124,15 +129,20 @@ To run your environment in the cloud, push it to the registry:
 asterai env push my-env
 ```
 
-Your environment is now available to run on asterai's cloud infrastructure.
+Your environment is now available to run on asterai's cloud
+infrastructure.
 
 ## 🎯 What's Next?
 
-You've created a component and run it in an environment. From here you can:
+You've created a component and run it in an environment.
+From here you can:
 
 - ➕ Add more functions to your component
 - 📥 Import other components from the registry
-- 🔧 Add configuration (environment variables, secrets) to your environment
+- 🔧 Add configuration (environment variables, secrets) to your
+  environment
 - 🔗 Compose multiple components in a single environment
 
-See the [Components](/components) page for more on building components, or [Registry](/registry) for publishing and discovering components.
+See the [Components](/components) page for more on building
+components, or [Registry](/registry) for publishing and discovering
+components.

src/introduction.md

@@ -2,51 +2,80 @@
 title: 👋 Introduction
 ---
 
-Asterai is the tool marketplace for AI agents. Discover, share, and deploy tools written in any programming language, with instant cloud execution.
+Asterai is the tool marketplace for AI agents.
+Discover, share, and deploy tools written in any programming language,
+with instant cloud execution.
 
 ## What is asterai?
 
-Asterai is a registry and runtime for portable, sandboxed tools. Write a tool once in your preferred language, publish it to the registry, and run it anywhere—locally or in the cloud.
+Asterai is a registry and runtime for portable, sandboxed tools.
+Write a tool once in your preferred language, publish it to the registry,
+and run it anywhere—locally or in the cloud.
 
-Under the hood, asterai uses [WebAssembly](/webassembly) for portability and security. But you don't need to know anything about WebAssembly to use asterai. Just write code in a supported language (TypeScript, Python, Rust, Go, and more), and asterai handles the rest.
+Under the hood, asterai uses [WebAssembly](/webassembly) for portability
+and security.
+But you don't need to know anything about WebAssembly to use asterai.
+Just write code in a supported language (TypeScript, Python, Rust, Go,
+and more), and asterai handles the rest.
 
 ## Key Concepts
 
-1. 🧩 **Component**: A portable tool or library. Components are published to the registry and can be composed together. Write them in any supported language.
+1. 🧩 **Component**: A portable tool or library.
+   Components are published to the registry and can be composed together.
+   Write them in any supported language.
 
-2. 📦 **Environment**: A deployable bundle of one or more components with configuration (environment variables, secrets). Environments can run locally or in the cloud.
+2. 📦 **Environment**: A deployable bundle of one or more components
+   with configuration (environment variables, secrets).
+   Environments can run locally or in the cloud.
 
-3. 🔍 **Registry**: Where components are published and discovered. Each user has a namespace for their components.
+3. 🔍 **Registry**: Where components are published and discovered.
+   Each user has a namespace for their components.
 
-4. ⌨️ **CLI**: The open-source command-line tool for building, publishing, and running components locally.
+4. ⌨️ **CLI**: The open-source command-line tool for building,
+   publishing, and running components locally.
 
-5. ☁️ **Cloud**: Run environments on asterai's infrastructure with a simple API call—no DevOps required.
+5. ☁️ **Cloud**: Run environments on asterai's infrastructure with a
+   simple API call—no DevOps required.
 
 ## Why asterai?
 
 🌐 **Language interoperability**
-Write tools in any language. Components written in different languages work together seamlessly through typed interfaces.
+Write tools in any language.
+Components written in different languages work together seamlessly
+through typed interfaces.
 
 🔒 **Sandboxed execution**
-AI agents can run untrusted code safely. Each component runs in an isolated sandbox with explicit permissions.
+AI agents can run untrusted code safely.
+Each component runs in an isolated sandbox with explicit permissions.
 
 📤 **True portability**
-Deploy anywhere. No dependency hell. Same behavior locally and in the cloud.
+Deploy anywhere. No dependency hell.
+Same behavior locally and in the cloud.
 
 ⚡ **Instant deployment**
-Tools just work. No containers, no infrastructure configuration. Publish and run.
+Tools just work. No containers, no infrastructure configuration.
+Publish and run.
 
 ## Example Use Cases
 
 ### 🤖 Tools for AI Agents
-Build reliable tools that your AI agents can call: API integrations, data processing, web scraping, file operations. Components provide type-safe interfaces that LLMs can understand and use correctly.
+Build reliable tools that your AI agents can call: API integrations,
+data processing, web scraping, file operations.
+Components provide type-safe interfaces that LLMs can understand and
+use correctly.
 
 ### 🗣️ Polyglot Libraries
-Use the right language for each job. A Rust component for performance-critical math, a Python component for ML inference, a TypeScript component for API calls—all composable in a single environment.
+Use the right language for each job.
+A Rust component for performance-critical math, a Python component for
+ML inference, a TypeScript component for API calls—all composable in a
+single environment.
 
 ### ⚙️ Serverless Functions
-Deploy functions to the cloud without managing infrastructure. Pay only for what you use, with global edge execution for low latency.
+Deploy functions to the cloud without managing infrastructure.
+Pay only for what you use, with global edge execution for low latency.
 
 ## 🚀 Getting Started
 
-The fastest way to get started is the [Hello World guide](/hello_world), which walks you through creating and deploying your first component.
+The fastest way to get started is the
+[Hello World guide](/hello_world), which walks you through creating and
+deploying your first component.