refactor(HAI-116): rename kb to hai across all packages, CLI, and docs

- Rename npm packages from @kb/* to @hai/* and update all workspace references
- Rename CLI binary from kb to hai and config directory from .kb to .hai
- Update dashboard UI branding, titles, and references from kb to hai
- Update all test files, CI workflows, and documentation to reflect new naming
- Run comprehensive grep verification to ensure no stale kb references remain
This commit is contained in:
Dustin Byrne
2026-03-26 22:25:30 -04:00
parent 1c5eb494db
commit c802108a02
84 changed files with 792 additions and 1363 deletions

View File

@@ -1,14 +1,14 @@
---
name: hai-board
description: Start and manage the hai dashboard web UI and AI engine. Use when asked to start the board, run the dashboard, enable the AI engine, or configure hai settings.
name: kb-board
description: Start and manage the kb dashboard web UI and AI engine. Use when asked to start the board, run the dashboard, enable the AI engine, or configure kb settings.
---
# hai board
# kb board
## Start the dashboard
```bash
hai dashboard
kb dashboard
```
Opens the kanban board at http://localhost:4040 and starts the AI engine.
@@ -30,7 +30,7 @@ Run in two terminals:
```bash
# Terminal 1: start the server + engine
hai dashboard
kb dashboard
# Terminal 2: watch-rebuild the React dashboard UI
pnpm dev:ui
@@ -38,7 +38,7 @@ pnpm dev:ui
## Configuration
Settings are in `.hai/config.json`:
Settings are in `.kb/config.json`:
```json
{
@@ -61,13 +61,13 @@ Settings are in `.hai/config.json`:
## Task storage
Tasks live in `.hai/tasks/`:
Tasks live in `.kb/tasks/`:
```
.hai/
.kb/
├── config.json
└── tasks/
└── HAI-001/
└── KB-001/
├── task.json # Metadata, steps, log
└── PROMPT.md # Task specification
```

View File

@@ -1,11 +1,11 @@
---
name: hai-task
description: Create, manage, and track tasks on the hai board. Use when asked to create a task, file a bug, report an issue, check task status, update progress, or interact with the hai task board in any way.
name: kb-task
description: Create, manage, and track tasks on the kb board. Use when asked to create a task, file a bug, report an issue, check task status, update progress, or interact with the kb task board in any way.
---
# hai task
# kb task
hai is an AI-orchestrated task board. Tasks flow through columns:
kb is an AI-orchestrated task board. Tasks flow through columns:
**triage → todo → in-progress → in-review → done**
## Commands
@@ -13,9 +13,9 @@ hai is an AI-orchestrated task board. Tasks flow through columns:
### Create a task
```bash
hai task create "description of what needs to be done"
hai task create "button is misaligned" --attach screenshot.png
hai task create "server crash" --attach error.log --attach trace.txt
kb task create "description of what needs to be done"
kb task create "button is misaligned" --attach screenshot.png
kb task create "server crash" --attach error.log --attach trace.txt
```
Creates a task in **triage**. The AI triage agent will specify it into a full
@@ -25,7 +25,7 @@ move it to **todo**.
Options:
- `--attach <file>` — attach files (images, logs, configs). Repeatable.
Images are sent to the triage agent for visual context.
Files are stored in `.hai/tasks/HAI-XXX/attachments/`.
Files are stored in `.kb/tasks/KB-XXX/attachments/`.
Tips:
- Be descriptive — the triage agent uses this to write the spec
@@ -37,7 +37,7 @@ Tips:
### List tasks
```bash
hai task list
kb task list
```
Shows all tasks grouped by column with IDs and descriptions.
@@ -45,7 +45,7 @@ Shows all tasks grouped by column with IDs and descriptions.
### Show task details
```bash
hai task show HAI-001
kb task show KB-001
```
Shows full task info: steps, progress, log entries, dependencies.
@@ -53,7 +53,7 @@ Shows full task info: steps, progress, log entries, dependencies.
### Move a task
```bash
hai task move HAI-001 <column>
kb task move KB-001 <column>
```
Columns: `triage`, `todo`, `in-progress`, `in-review`, `done`
@@ -68,7 +68,7 @@ Transitions are validated:
### Update step status
```bash
hai task update HAI-001 <step-number> <status>
kb task update KB-001 <step-number> <status>
```
Status: `pending`, `in-progress`, `done`, `skipped`
@@ -78,7 +78,7 @@ Steps are 0-indexed and auto-parsed from the PROMPT.md headings.
### Log an entry
```bash
hai task log HAI-001 "what happened"
kb task log KB-001 "what happened"
```
Adds a timestamped log entry visible on the task card.
@@ -86,7 +86,7 @@ Adds a timestamped log entry visible on the task card.
### Merge a completed task
```bash
hai task merge HAI-001
kb task merge KB-001
```
Squash-merges the task's branch into main with an AI-written commit message.
@@ -95,12 +95,12 @@ Cleans up the worktree and branch after merge.
## Workflow
1. **Create**`hai task create "description"` → goes to triage
1. **Create**`kb task create "description"` → goes to triage
2. **Triage** — AI agent reads the codebase, writes a PROMPT.md spec, moves to todo
3. **Schedule** — Scheduler moves to in-progress when deps are met and concurrency allows
4. **Execute** — AI agent works the task in a git worktree, reports progress via tools
5. **Review** — Cross-model reviewer checks plan/code at step boundaries
6. **Merge**`hai task merge HAI-001` squash-merges to main
6. **Merge**`kb task merge KB-001` squash-merges to main
## Filing good tasks
@@ -108,14 +108,14 @@ A task can be anything from a rough idea to a detailed spec:
```bash
# Rough — triage agent will flesh it out
hai task create "the login page is slow"
kb task create "the login page is slow"
# Specific — triage agent will structure it
hai task create "Add rate limiting to POST /api/tasks. Use a token bucket algorithm with 100 req/min per IP. Return 429 with Retry-After header when exceeded."
kb task create "Add rate limiting to POST /api/tasks. Use a token bucket algorithm with 100 req/min per IP. Return 429 with Retry-After header when exceeded."
# Bug report with screenshot
hai task create "button is misaligned on mobile" --attach screenshot.png
kb task create "button is misaligned on mobile" --attach screenshot.png
# Bug report with logs
hai task create "server crashes on startup" --attach crash.log
kb task create "server crashes on startup" --attach crash.log
```