update name

Author: AnonJon

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,6 +1,6 @@
 ---
 name: Bug report
-about: Report a bug in kdocter
+about: Report a bug in kroot
 title: "[bug] "
 labels: bug
 assignees: ""
@@ -18,7 +18,7 @@ A clear and concise description of what happened.
 ## Command run
 
 ```bash
-kdocter diagnose cluster
+kroot diagnose cluster
 ```
 
 ## Expected behavior

.github/pull_request_template.md

@@ -25,7 +25,7 @@ cargo test --workspace
 If relevant, include sample CLI commands and output:
 
 ```bash
-cargo run -p kdocter -- diagnose cluster
+cargo run -p kroot -- diagnose cluster
 ```
 
 ## Checklist

.github/workflows/release.yml

@@ -19,15 +19,15 @@ jobs:
           - os: ubuntu-latest
             target: x86_64-unknown-linux-gnu
             archive_ext: tar.gz
-            binary_name: kdocter
+            binary_name: kroot
           - os: macos-latest
             target: aarch64-apple-darwin
             archive_ext: tar.gz
-            binary_name: kdocter
+            binary_name: kroot
           - os: windows-latest
             target: x86_64-pc-windows-msvc
             archive_ext: zip
-            binary_name: kdocter.exe
+            binary_name: kroot.exe
 
     steps:
       - name: Checkout
@@ -39,30 +39,30 @@ jobs:
           targets: ${{ matrix.target }}
 
       - name: Build release binary
-        run: cargo build -p kdocter --release --target ${{ matrix.target }}
+        run: cargo build -p kroot --release --target ${{ matrix.target }}
 
       - name: Package archive (unix)
         if: runner.os != 'Windows'
         run: |
           mkdir -p dist
           cp target/${{ matrix.target }}/release/${{ matrix.binary_name }} dist/
-          tar -C dist -czf kdocter-${{ github.ref_name }}-${{ matrix.target }}.tar.gz ${{ matrix.binary_name }}
+          tar -C dist -czf kroot-${{ github.ref_name }}-${{ matrix.target }}.tar.gz ${{ matrix.binary_name }}
 
       - name: Package archive (windows)
         if: runner.os == 'Windows'
         shell: pwsh
         run: |
           New-Item -ItemType Directory -Path dist -Force | Out-Null
           Copy-Item "target/${{ matrix.target }}/release/${{ matrix.binary_name }}" "dist/${{ matrix.binary_name }}"
-          Compress-Archive -Path "dist/${{ matrix.binary_name }}" -DestinationPath "kdocter-${{ github.ref_name }}-${{ matrix.target }}.zip"
+          Compress-Archive -Path "dist/${{ matrix.binary_name }}" -DestinationPath "kroot-${{ github.ref_name }}-${{ matrix.target }}.zip"
 
       - name: Upload archive artifact
         uses: actions/upload-artifact@v4
         with:
-          name: kdocter-${{ matrix.target }}
+          name: kroot-${{ matrix.target }}
           path: |
-            kdocter-${{ github.ref_name }}-${{ matrix.target }}.tar.gz
-            kdocter-${{ github.ref_name }}-${{ matrix.target }}.zip
+            kroot-${{ github.ref_name }}-${{ matrix.target }}.tar.gz
+            kroot-${{ github.ref_name }}-${{ matrix.target }}.zip
 
   publish:
     name: Publish GitHub Release

AGENTS.md

@@ -1,6 +1,6 @@
-# kdocter
+# kroot
 
-kdocter is a CLI tool for performing root cause analysis (RCA)
+kroot is a CLI tool for performing root cause analysis (RCA)
 on Kubernetes clusters.
 
 The tool diagnoses failures like:

CHANGELOG.md

@@ -8,9 +8,9 @@ All notable changes to this project will be documented in this file.
 
 ### Added
 
-- Initial `kdocter` CLI:
-  - `kdocter diagnose cluster`
-  - `kdocter diagnose pod <name>`
+- Initial `kroot` CLI:
+  - `kroot diagnose cluster`
+  - `kroot diagnose pod <name>`
 - Namespace controls: `-n/--namespace`, `-A/--all-namespaces`
 - Output formats: `text`, `json`, `sarif`
 - Offline analysis via `--context-file`

CONTRIBUTING.md

@@ -1,12 +1,12 @@
-# Contributing to kdocter
+# Contributing to kroot
 
-Thanks for contributing to kdocter.
+Thanks for contributing to kroot.
 
 ## Development setup
 
 ```bash
-git clone https://github.com/AnonJon/kdocter
-cd kdocter
+git clone https://github.com/AnonJon/kroot
+cd kroot
 cargo build --workspace
 ```
 

Cargo.lock

@@ -1,46 +1,46 @@
-![CI](https://github.com/AnonJon/kdocter/actions/workflows/ci.yml/badge.svg)
-![Release](https://img.shields.io/github/v/release/AnonJon/kdocter)
+![CI](https://github.com/AnonJon/kroot/actions/workflows/ci.yml/badge.svg)
+![Release](https://img.shields.io/github/v/release/AnonJon/kroot)
 ![License](https://img.shields.io/badge/license-MIT-blue)
 ![Rust](https://img.shields.io/badge/rust-stable-orange)
 ![Kubernetes](https://img.shields.io/badge/kubernetes-compatible-blue)
 
-# kdocter
+# kroot
 
 Root cause analysis for Kubernetes incidents.
 
-`kdocter` is a Rust CLI that analyzes Kubernetes resources,
+`kroot` is a Rust CLI that analyzes Kubernetes resources,
 builds dependency graphs, and explains _why failures occur_.
 
-Instead of only detecting symptoms, `kdocter` builds a dependency graph
+Instead of only detecting symptoms, `kroot` builds a dependency graph
 and traces resource relationships to explain root causes.
 
 ## TL;DR
 
 ```bash
-kdocter diagnose cluster -A
+kroot diagnose cluster -A
 ```
 
 Find root causes for Kubernetes failures using dependency-aware analysis.
 
-## How kdocter Works
+## How kroot Works
 
-`kdocter` analyzes a cluster in three stages:
+`kroot` analyzes a cluster in three stages:
 
 1. Collect Kubernetes resources (pods, services, secrets, and related objects).
 2. Build a dependency graph between resources.
 3. Run analyzers that detect failure patterns and trace root causes.
 
-This allows `kdocter` to report not just failing resources, but the dependency chains that explain the failure.
+This allows `kroot` to report not just failing resources, but the dependency chains that explain the failure.
 
 ## Contents
 
 - [TL;DR](#tldr)
-- [How kdocter Works](#how-kdocter-works)
-- [Why kdocter](#why-kdocter)
+- [How kroot Works](#how-kroot-works)
+- [Why kroot](#why-kroot)
 - [Features](#features)
 - [Installation](#installation)
 - [Quick Start](#quick-start)
-- [When to Use kdocter](#when-to-use-kdocter)
+- [When to Use kroot](#when-to-use-kroot)
 - [Example Output](#example-output)
 - [Command Reference](#command-reference)
 - [Output Formats](#output-formats)
@@ -58,10 +58,10 @@ This allows `kdocter` to report not just failing resources, but the dependency c
 - [Contributing](#contributing)
 - [License](#license)
 
-## Why kdocter
+## Why kroot
 
 Most Kubernetes tooling tells you _what failed_.
-`kdocter` is designed to explain _why it failed_ by correlating resources and their relationships.
+`kroot` is designed to explain _why it failed_ by correlating resources and their relationships.
 
 Example chain:
 
@@ -87,8 +87,8 @@ Example chain:
 ### Build and run locally
 
 ```bash
-git clone https://github.com/AnonJon/kdocter
-cd kdocter
+git clone https://github.com/AnonJon/kroot
+cd kroot
 cargo build --workspace
 ```
 
@@ -101,32 +101,32 @@ cargo install --path cli
 ### Install from source repository (single command)
 
 ```bash
-cargo install --git https://github.com/AnonJon/kdocter --bin kdocter
+cargo install --git https://github.com/AnonJon/kroot --bin kroot
 ```
 
 Then run:
 
 ```bash
-kdocter --help
+kroot --help
 ```
 
 ## Quick Start
 
 Diagnose current namespace from your active kubeconfig context:
 
 ```bash
-cargo run -p kdocter -- diagnose cluster
+cargo run -p kroot -- diagnose cluster
 ```
 
 Diagnose a specific pod:
 
 ```bash
-cargo run -p kdocter -- diagnose pod payments-api -n prod
+cargo run -p kroot -- diagnose pod payments-api -n prod
 ```
 
-## When to Use kdocter
+## When to Use kroot
 
-`kdocter` is useful when:
+`kroot` is useful when:
 
 - a pod is failing but the root cause is unclear
 - service traffic suddenly stops working
@@ -135,14 +135,14 @@ cargo run -p kdocter -- diagnose pod payments-api -n prod
 
 Typical workflow:
 
-1. Run `kdocter diagnose cluster`.
+1. Run `kroot diagnose cluster`.
 2. Inspect dependency traces.
 3. Identify the upstream failing resource.
 
 ## Example Output
 
 ```text
-$ kdocter diagnose cluster -n prod
+$ kroot diagnose cluster -n prod
 
 Diagnosis Report
 ----------------
@@ -168,13 +168,13 @@ Dependency Traces:
 ### Diagnose cluster
 
 ```bash
-kdocter diagnose cluster [-n <namespace> | -A] [--output text|json|sarif] [--context-file <path>]
+kroot diagnose cluster [-n <namespace> | -A] [--output text|json|sarif] [--context-file <path>]
 ```
 
 ### Diagnose pod
 
 ```bash
-kdocter diagnose pod <name> [-n <namespace>] [--output text|json|sarif] [--context-file <path>]
+kroot diagnose pod <name> [-n <namespace>] [--output text|json|sarif] [--context-file <path>]
 ```
 
 ### Notes
@@ -199,7 +199,7 @@ Human-readable diagnosis report with:
 Machine-readable output for scripting:
 
 ```bash
-kdocter diagnose cluster --output json -n prod
+kroot diagnose cluster --output json -n prod
 ```
 
 High-level JSON shape:
@@ -213,15 +213,15 @@ High-level JSON shape:
 SARIF output is useful for CI systems and security/dev tooling pipelines:
 
 ```bash
-kdocter diagnose cluster --output sarif -A > kdocter.sarif.json
+kroot diagnose cluster --output sarif -A > kroot.sarif.json
 ```
 
 ## Release Binaries and Package Managers
 
 Release binaries are published on tagged releases (`v*`) through:
 
 - [`.github/workflows/release.yml`](./.github/workflows/release.yml)
-- [Latest release](https://github.com/AnonJon/kdocter/releases/latest)
+- [Latest release](https://github.com/AnonJon/kroot/releases/latest)
 
 Available now:
 
@@ -237,7 +237,7 @@ Planned install paths:
 Run analysis against a previously captured context:
 
 ```bash
-kdocter diagnose cluster --context-file ./context.json
+kroot diagnose cluster --context-file ./context.json
 ```
 
 Example context fixture:
@@ -283,15 +283,15 @@ kubectl get events -n prod
 
 This surfaces symptoms, but usually not the full dependency cause chain.
 
-`kdocter` correlates dependencies directly:
+`kroot` correlates dependencies directly:
 
 `Pod/prod/payments-api -> Secret/prod/db-password -> Secret missing`
 
 That gives a direct root-cause path instead of disconnected clues.
 
 ## Project Status
 
-`kdocter` is early-stage but functional for real diagnostics.
+`kroot` is early-stage but functional for real diagnostics.
 
 First public release: `v0.1.0` (March 8, 2026).
 
@@ -307,19 +307,19 @@ Expect active iteration as graph coverage and reasoning depth expand.
 
 ## Similar Tools
 
-`kdocter` focuses on dependency-aware root cause analysis.
+`kroot` focuses on dependency-aware root cause analysis.
 
 Related tools:
 
 - `popeye` (cluster linting)
 - `kube-score` (manifest/static analysis)
 - `kubectl` (manual troubleshooting)
 
-`kdocter` complements these by correlating runtime relationships between resources.
+`kroot` complements these by correlating runtime relationships between resources.
 
 ## Kubernetes Permissions (RBAC)
 
-`kdocter` collects and correlates multiple resource types. Your identity should allow at least:
+`kroot` collects and correlates multiple resource types. Your identity should allow at least:
 
 - `get/list` on `pods`
 - `get/list` on `services`
@@ -362,7 +362,7 @@ DependencyGraph
 
 Workspace crates:
 
-- `cli`: binary crate (`kdocter`)
+- `cli`: binary crate (`kroot`)
 - `crates/cluster`: Kubernetes collectors and context loading
 - `crates/types`: normalized domain models
 - `crates/graph`: dependency graph builder/model (`petgraph`)

README.md

@@ -1,5 +1,5 @@
 [package]
-name = "kdocter"
+name = "kroot"
 version = "0.1.0"
 edition = "2024"
 

cli/Cargo.toml

@@ -5,7 +5,7 @@ use serde::Serialize;
 use std::path::PathBuf;
 
 #[derive(Parser, Debug)]
-#[command(name = "kdocter", about = "Kubernetes root cause analysis CLI")]
+#[command(name = "kroot", about = "Kubernetes root cause analysis CLI")]
 struct Cli {
     #[command(subcommand)]
     command: Commands,
@@ -331,8 +331,8 @@ fn build_sarif_log(diagnoses: &[types::Diagnosis]) -> SarifLog {
         runs: vec![SarifRun {
             tool: SarifTool {
                 driver: SarifDriver {
-                    name: "kdocter".to_string(),
-                    information_uri: "https://github.com/AnonJon/kdocter".to_string(),
+                    name: "kroot".to_string(),
+                    information_uri: "https://github.com/AnonJon/kroot".to_string(),
                     rules: rules.into_values().collect(),
                 },
             },