Guided Carvel (ytt) install mission in KubeStellar Console

We built a guided install mission for Carvel (ytt) inside [KubeStellar Console](https://console.kubestellar.io?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=carvel), a standalone Kubernetes dashboard (unrelated to legacy kubestellar/kubestellar, kubeflex, or OCM — zero shared code).

> **[Open the Carvel (ytt) install mission](https://console.kubestellar.io/missions/install-carvel?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=carvel)**

### What the mission does

The mission runs against your live cluster via kubeconfig. Each step:

1. **Pre-flight** — checks prerequisites (ytt, kbld, kapp, imgpkg CLI tools)
2. **Commands** — shows the exact install commands with flags explained. Copy-paste or run directly from the console
3. **Validation** — after each step, queries the cluster to verify success (pod phase, CRD registration, service endpoints)
4. **Troubleshooting** — on failure, reads pod logs, events, and resource status from your cluster and suggests fixes
5. **Rollback** — each step includes the corresponding uninstall commands to undo

Works as read-only documentation too — no cluster connection required to browse.

### Architecture

```mermaid
graph LR
A["KubeStellar Console"] --> B["30+ Dashboards
150+ Monitoring Cards"]
A --> M["Marketplace
(console-marketplace)"]
A --> D["AI Mission Explorer"]
D --> E["console-kb"]
E --> F["186 Install Missions
67 Solution Missions"]
A --> C["AI Recommendations"]
A --> H["kc-agent → Codex, Copilot,
Claude CLI, Kube API, MCP"]
click A href "https://console.kubestellar.io?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=carvel" _blank
click M href "https://github.com/kubestellar/console-marketplace?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=carvel" _blank
click E href "https://github.com/kubestellar/console-kb/blob/master/fixes/cncf-install/install-carvel.json?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=carvel" _blank
click F href "https://console.kubestellar.io/missions/install-carvel?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=carvel" _blank
click H href "https://github.com/kubestellar/console/tree/main/cmd/kc-agent?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=carvel" _blank
```

- **console-kb** — YAML-based knowledge base defining each mission's steps, commands, and validation checks ([Carvel (ytt) installer definition](https://github.com/kubestellar/console-kb/blob/master/fixes/cncf-install/install-carvel.json?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=carvel))
- **console-marketplace** — community-contributed monitoring cards per CNCF project ([github.com/kubestellar/console-marketplace](https://github.com/kubestellar/console-marketplace?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=carvel))
- **kc-agent** — bridges coding agents (Codex, Copilot, Claude CLI) to Kube API and MCP servers (kubestellar-ops, kubestellar-deploy) for automated cluster operations

### Install

Local (connects to your current kubeconfig context):
```bash
curl -sSL https://raw.githubusercontent.com/kubestellar/console/main/start.sh | bash
```

With GitHub OAuth:
```bash
export GITHUB_CLIENT_ID=
export GITHUB_CLIENT_SECRET=
curl -sSL https://raw.githubusercontent.com/kubestellar/console/main/start.sh | bash
```

Deploy into a cluster:
```bash
curl -sSL https://raw.githubusercontent.com/kubestellar/console/main/deploy.sh | bash
```

---

Mission definitions are open source — PRs to improve the Carvel (ytt) mission welcome at [install-carvel.json](https://github.com/kubestellar/console-kb/blob/master/fixes/cncf-install/install-carvel.json?utm_source=github&utm_medium=issue&utm_campaign=cncf_outreach&utm_term=carvel). Feel free to close if not relevant.

The proposed work is described as an external KubeStellar Console mission rather than a change to ytt. Review the linked console-kb fixes/cncf-install/install-carvel.json and the console repositories first, then confirm whether any actionable change belongs in this repository; the issue provides no ytt file, test, or acceptance criteria.

Written by the indexing model from the issue text.