Rename the repo to better match the actual product scope

The public repository has grown beyond an eval-only story: it now covers
replay, regression testing, trace packaging, failure analysis, and
dataset slicing for LLM agents. The old name still undersold that broader
reliability workflow, so this change renames the repo surface to
AgentReliabilityKit and aligns the visible docs, assets, and automation
paths with the new positioning.

Constraint: Keep the existing tool names and artifact contracts stable while clarifying the monorepo brand
Rejected: Keep the AgentEvalKit name and only tweak the description | still too narrow for the shipped functionality
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Keep future top-level naming and copy aligned with the full reliability loop, not just evaluation in isolation
Tested: AgentCI / TracePack / PackSlice test suites; root automation demo script; GitHub repo rename and issue closure verification
Not-tested: FailMap suite on this final rename-only pass

Author: weiyi

.github/FUNDING.yml

@@ -8,4 +8,4 @@ liberapay: ""
 issuehunt: ""
 otechie: ""
 custom:
-  - https://github.com/Jasvina/AgentEvalKit
+  - https://github.com/Jasvina/AgentReliabilityKit

.github/ISSUE_TEMPLATE/config.yml

@@ -1,11 +1,11 @@
 blank_issues_enabled: false
 contact_links:
   - name: Roadmap and project direction
-    url: https://github.com/Jasvina/AgentEvalKit/blob/main/ROADMAP.md
+    url: https://github.com/Jasvina/AgentReliabilityKit/blob/main/ROADMAP.md
     about: Read the public roadmap before proposing broad new directions.
   - name: Discussions
-    url: https://github.com/Jasvina/AgentEvalKit/discussions
+    url: https://github.com/Jasvina/AgentReliabilityKit/discussions
     about: Use Discussions for open-ended questions, ideas, and design conversations.
   - name: Security reporting
-    url: https://github.com/Jasvina/AgentEvalKit/blob/main/SECURITY.md
+    url: https://github.com/Jasvina/AgentReliabilityKit/blob/main/SECURITY.md
     about: Please report undisclosed security issues privately.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -27,6 +27,6 @@ Describe the smallest useful feature that would address it.
 
 What file, output, or CLI shape would this add or change?
 
-## Why this belongs in AgentEvalKit
+## Why this belongs in AgentReliabilityKit
 
 Explain why this strengthens the eval / regression / failure-analysis story rather than adding a generic demo.

.github/workflows/ci.yml

@@ -128,14 +128,14 @@ jobs:
         with:
           python-version: "3.11"
       - name: Run monorepo automation demo
-        run: ./scripts/run_automation_demo.sh /tmp/agentevalkit-automation-demo
+        run: ./scripts/run_automation_demo.sh /tmp/agentreliabilitykit-automation-demo
       - name: Validate automation outputs
         run: |
           python - <<'PY'
           import json
           from pathlib import Path
 
-          out = Path("/tmp/agentevalkit-automation-demo")
+          out = Path("/tmp/agentreliabilitykit-automation-demo")
           assert (out / "manifest.json").exists()
           assert (out / "agentci-summary.json").exists()
           assert (out / "agentci-regression.json").exists()
@@ -144,7 +144,7 @@ jobs:
           assert (out / "packslice" / "summary.json").exists()
 
           demo_manifest = json.loads((out / "manifest.json").read_text())
-          assert demo_manifest["format"] == "agentevalkit-demo-v1"
+          assert demo_manifest["format"] == "agentreliabilitykit-demo-v1"
           assert demo_manifest["summary"]["agentci"]["regression_passed"] is True
 
           agentci_summary = json.loads((out / "agentci-summary.json").read_text())
@@ -167,5 +167,5 @@ jobs:
       - name: Upload automation demo artifacts
         uses: actions/upload-artifact@v4
         with:
-          name: agentevalkit-automation-demo
-          path: /tmp/agentevalkit-automation-demo
+          name: agentreliabilitykit-automation-demo
+          path: /tmp/agentreliabilitykit-automation-demo

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-All notable changes to `AgentEvalKit` will be documented in this file.
+All notable changes to `AgentReliabilityKit` will be documented in this file.
 
 The project currently tracks a single public line of development on `main`, with GitHub releases used to mark meaningful public milestones in the repo's evolution.
 
@@ -10,7 +10,7 @@ Initial public toolkit release for the repo in its current form.
 
 ### Added
 
-- clarified monorepo positioning as `AgentEvalKit`
+- clarified monorepo positioning as `AgentReliabilityKit`
 - root automation demo with machine-readable `manifest.json`
 - GitHub-facing repository docs and community health files
 - issue templates, PR template, roadmap, labels, Discussions, funding metadata, and code ownership metadata

CODE_OF_CONDUCT.md

@@ -2,7 +2,7 @@
 
 ## Our Commitment
 
-We want `AgentEvalKit` to be a useful, welcoming open-source project for people working on agent evals, infrastructure, reliability, and research tooling.
+We want `AgentReliabilityKit` to be a useful, welcoming open-source project for people working on agent evals, infrastructure, reliability, and research tooling.
 
 Contributors, maintainers, and community members are expected to keep interactions respectful, constructive, and focused on improving the work.
 

CONTRIBUTING.md

@@ -1,6 +1,6 @@
-# Contributing to AgentEvalKit
+# Contributing to AgentReliabilityKit
 
-Thanks for checking out `AgentEvalKit`.
+Thanks for checking out `AgentReliabilityKit`.
 
 This monorepo is intentionally narrow: each project should solve a concrete gap in agent reproducibility, regression testing, failure analysis, or benchmark preparation. Contributions are most useful when they strengthen that end-to-end story instead of adding unrelated demos.
 
@@ -65,7 +65,7 @@ For monorepo automation checks, the root demo script is often the fastest way to
 
 ```bash
 chmod +x scripts/run_automation_demo.sh
-./scripts/run_automation_demo.sh /tmp/agentevalkit-demo
+./scripts/run_automation_demo.sh /tmp/agentreliabilitykit-demo
 ```
 
 That demo now writes a root `manifest.json` alongside the per-tool artifacts, which is the best single file to inspect when you want to confirm the end-to-end handoff shape.
@@ -117,7 +117,7 @@ cd projects/packslice && python -m unittest discover -s tests -v
 End-to-end validation:
 
 ```bash
-./scripts/run_automation_demo.sh /tmp/agentevalkit-demo
+./scripts/run_automation_demo.sh /tmp/agentreliabilitykit-demo
 ```
 
 If you change CLI output that is documented in the README, examples, or CI workflow, update those references in the same pull request.
@@ -164,6 +164,6 @@ If you want to propose a new project for the monorepo, start by describing:
 - the missing workflow in today's agent tooling
 - why the problem is not already well served by existing OSS
 - the minimal artifact contract and CLI that would make it useful
-- how it would connect to the rest of `AgentEvalKit`
+- how it would connect to the rest of `AgentReliabilityKit`
 
 The best proposals usually start small: one tight workflow, one useful artifact, one clear CLI, and one obvious connection to the rest of the toolchain.

README.md

@@ -1,12 +1,12 @@
-# AgentEvalKit
+# AgentReliabilityKit
 
-[![CI](https://github.com/Jasvina/AgentEvalKit/actions/workflows/ci.yml/badge.svg)](https://github.com/Jasvina/AgentEvalKit/actions/workflows/ci.yml)
-[![License](https://img.shields.io/github/license/Jasvina/AgentEvalKit)](LICENSE)
-[![Monorepo](https://img.shields.io/badge/layout-agent%20tooling%20monorepo-0a7bbb)](https://github.com/Jasvina/AgentEvalKit)
+[![CI](https://github.com/Jasvina/AgentReliabilityKit/actions/workflows/ci.yml/badge.svg)](https://github.com/Jasvina/AgentReliabilityKit/actions/workflows/ci.yml)
+[![License](https://img.shields.io/github/license/Jasvina/AgentReliabilityKit)](LICENSE)
+[![Monorepo](https://img.shields.io/badge/layout-agent%20tooling%20monorepo-0a7bbb)](https://github.com/Jasvina/AgentReliabilityKit)
 
 Open-source tooling for agent evals, regression testing, trace packaging, failure clustering, and dataset slicing.
 
-`AgentEvalKit` is a focused monorepo for a specific gap in the LLM agent stack: teams can build agents, but still struggle to replay failures, turn real traces into reusable eval assets, cluster recurring failure modes, and produce stable train/eval/test slices from the same evidence.
+`AgentReliabilityKit` is a focused monorepo for a specific gap in the LLM agent stack: teams can build agents, but still struggle to replay failures, turn real traces into reusable eval assets, cluster recurring failure modes, and produce stable train/eval/test slices from the same evidence.
 
 ## Why this exists
 
@@ -20,7 +20,7 @@ This repo is built around that loop:
 4. cluster repeated failures across runs or releases
 5. slice the same artifact into reproducible datasets
 
-That makes `AgentEvalKit` closer to an eval-and-reliability toolkit than a general agent framework.
+That makes `AgentReliabilityKit` closer to an eval-and-reliability toolkit than a general agent framework.
 
 ## What you get
 
@@ -33,7 +33,7 @@ That makes `AgentEvalKit` closer to an eval-and-reliability toolkit than a gener
 ## Toolchain at a glance
 
 <p align="center">
-  <img src="docs/assets/agentevalkit-overview.svg" alt="AgentEvalKit architecture overview" width="100%" />
+  <img src="docs/assets/agentreliabilitykit-overview.svg" alt="AgentReliabilityKit architecture overview" width="100%" />
 </p>
 
 ```text
@@ -46,13 +46,13 @@ PackSlice -> split packs into balanced train/eval/test datasets
 ## What the demo produces
 
 <p align="center">
-  <img src="docs/assets/agentevalkit-demo-terminal.svg" alt="AgentEvalKit terminal-style demo output" width="100%" />
+  <img src="docs/assets/agentreliabilitykit-demo-terminal.svg" alt="AgentReliabilityKit terminal-style demo output" width="100%" />
 </p>
 
 Run the end-to-end repo demo with:
 
 ```bash
-./scripts/run_automation_demo.sh /tmp/agentevalkit-demo
+./scripts/run_automation_demo.sh /tmp/agentreliabilitykit-demo
 ```
 
 The output is intentionally machine-readable. A successful run gives you a root `manifest.json` plus per-tool artifacts:
@@ -183,7 +183,7 @@ The most useful agent infra repos are usually:
 3. demoable in a few minutes
 4. useful to both researchers and production teams
 
-`AgentEvalKit` is built around that rule.
+`AgentReliabilityKit` is built around that rule.
 
 ## Monorepo structure
 
@@ -207,7 +207,7 @@ projects/
 - public roadmap: `ROADMAP.md`
 - changelog: `CHANGELOG.md`
 - discussions: GitHub Discussions
-- social preview source: `docs/assets/agentevalkit-social-preview.svg`
+- social preview source: `docs/assets/agentreliabilitykit-social-preview.svg`
 
 ## Roadmap
 

ROADMAP.md

@@ -1,6 +1,6 @@
 # Roadmap
 
-`AgentEvalKit` is a toolkit for the agent reliability loop:
+`AgentReliabilityKit` is a toolkit for the agent reliability loop:
 
 1. capture real runs
 2. replay and diff them

SECURITY.md

@@ -2,7 +2,7 @@
 
 ## Scope
 
-`AgentEvalKit` is a public toolkit for agent eval, regression testing, trace packaging, failure clustering, and dataset slicing. Security reports are especially helpful when they involve:
+`AgentReliabilityKit` is a public toolkit for agent eval, regression testing, trace packaging, failure clustering, and dataset slicing. Security reports are especially helpful when they involve:
 
 - secret leakage or incomplete redaction in `TracePack`
 - unsafe artifact handling in `AgentCI`, `FailMap`, or `PackSlice`