feat: Update version to v0.4.2 and add comet init command documentation

Author: speier

Makefile

@@ -1,4 +1,4 @@
-VERSION=v0.4.1
+VERSION=v0.4.2
 
 tag:
 	@git tag -a ${VERSION} -m "version ${VERSION}" && git push origin ${VERSION}

README.md

@@ -131,6 +131,20 @@ comet version
 comet plan <stack> [component]
 ```
 
+### `comet init`
+
+**Description:** Initialize backends and providers without running plan/apply operations.
+
+**Usage:**
+```
+comet init <stack> [component]
+```
+
+Useful for:
+- Preparing infrastructure for read-only operations (like `comet output`)
+- Troubleshooting provider/backend initialization issues
+- CI/CD validation pipelines
+
 ### `comet output`
 
 **Description:** Show output values from components.

docs/best-practices.md

@@ -352,13 +352,20 @@ wait
 ```bash
 # Solution: Re-initialize Terraform
 rm -rf .terraform
-comet apply <stack> <component>
+comet init <stack> <component>
+```
+
+**Issue:** "Required plugins are not installed"
+```bash
+# Solution: Initialize providers and backends
+comet init <stack> <component>
 ```
 
 **Issue:** Cross-stack reference returns null
 ```bash
 # Solution: Ensure referenced stack is applied first
 comet apply infra vpc
+comet init app webapp   # Initialize to query outputs
 comet apply app webapp  # Now vpc outputs are available
 ```
 

website/docs/advanced/best-practices.md

@@ -378,13 +378,20 @@ jobs:
 **Backend configuration changed:**
 ```bash
 rm -rf .terraform
-comet apply <stack> <component>
+comet init <stack> <component>
+```
+
+**Required plugins are not installed:**
+```bash
+# Initialize providers and backends
+comet init <stack> <component>
 ```
 
 **Cross-stack reference returns null:**
 ```bash
 # Ensure referenced stack is applied first
 comet apply infrastructure vpc
+comet init application webapp   # Initialize to query outputs
 comet apply application webapp
 ```
 

website/docs/guides/cli-reference.md

@@ -93,6 +93,44 @@ comet plan production vpc
 **Output:**
 Shows Terraform plan output with additions, changes, and deletions.
 
+## comet init
+
+Initialize backends and providers without running plan or apply operations. This is useful for setting up the environment before querying outputs or troubleshooting initialization issues.
+
+### Initialize All Components
+
+```bash
+comet init <stack>
+```
+
+**Example:**
+```bash
+comet init dev
+```
+
+### Initialize a Specific Component
+
+```bash
+comet init <stack> <component>
+```
+
+**Example:**
+```bash
+comet init dev vpc
+```
+
+**What it does:**
+- Generates backend configuration files (`backend.tf.json`)
+- Generates provider configuration files (`providers_gen.tf`)
+- Downloads required provider plugins
+- Configures remote state backend
+- Does NOT run plan, apply, or make infrastructure changes
+
+**Use cases:**
+- Before running `comet output` on a fresh checkout
+- Troubleshooting provider/backend initialization issues
+- CI/CD validation pipelines that only need to query infrastructure
+
 ## comet apply
 
 Create or update infrastructure based on your configuration.
@@ -290,6 +328,17 @@ comet apply dev
 comet output dev
 ```
 
+### Read-Only Query (Fresh Checkout)
+
+```bash
+# 1. Initialize backends and providers
+comet init production
+
+# 2. Query infrastructure outputs
+comet output production vpc
+comet output production gke
+```
+
 ### Updating Infrastructure
 
 ```bash