chore: set parallel agent dispatch and tracer ownership

This commit is contained in:
zenchantlive 2026-02-11 17:44:41 -08:00
parent 292a72f861
commit 7537ec27b0
5 changed files with 142 additions and 7 deletions

View file

@ -0,0 +1,32 @@
# Agent A Dispatch: Registry/API
## Branch + Worktree
- Branch: `feat/registry-api`
- Worktree: `C:\Users\Zenchant\codex\beadboard\.worktrees\agent-a`
## Beads
- `bb-6aj.1` (in_progress, assignee `agent-a`)
- `bb-6aj.2` (open, assignee `agent-a`) after `bb-6aj.1` closes
## Scope
- Implement registry persistence at `%USERPROFILE%\.beadboard\projects.json`
- Implement projects API route for add/remove/list
- Windows-safe normalization only
## File Ownership
- `src/lib/registry.ts`
- `src/app/api/projects/route.ts`
- `tests/lib/registry.test.ts`
- `tests/api/projects-route.test.ts`
## Hard Constraints
- Never write directly to `.beads/issues.jsonl`
- No Unix-only assumptions
- Validate and normalize project paths consistently
## Verification
```powershell
npm run typecheck
npm run test
```

View file

@ -0,0 +1,40 @@
# Agent B Dispatch: Tracer Bullet 1 Kanban
## Branch + Worktree
- Branch: `feat/kanban-baseline`
- Worktree: `C:\Users\Zenchant\codex\beadboard\.worktrees\agent-b`
## Beads
- `bb-trz.1` (in_progress, assignee `agent-b`)
- `bb-trz.2` (in_progress, assignee `agent-b`)
- `bb-trz.3` (in_progress, assignee `agent-b`)
- `bb-trz.4` (in_progress, assignee `agent-b`)
## Scope
- Deliver tracer bullet 1 baseline:
- status columns (`open`, `in_progress`, `blocked`, `deferred`, `closed`)
- bead cards (priority/type/labels/assignee/dependency count)
- detail panel
- search/filter/stats controls
- Use real read path (`.beads/issues.jsonl`) from server layer, not demo-only data
## File Ownership
- `src/app/page.tsx`
- `src/components/kanban/*`
- `src/components/shared/*`
- `src/lib/kanban.ts`
- `src/lib/read-issues.ts`
- `tests/lib/kanban.test.ts`
## Hard Constraints
- Read boundary only for this phase
- No write path to JSONL
- Keep Windows-safe path handling in read layer
## Verification
```powershell
npm run typecheck
npm run test
npm run dev
```

View file

@ -0,0 +1,31 @@
# Agent C Dispatch: Scanner
## Branch + Worktree
- Branch: `feat/scanner`
- Worktree: `C:\Users\Zenchant\codex\beadboard\.worktrees\agent-c`
## Beads
- `bb-6aj.3` (open, assignee `agent-c`) start only after `bb-6aj.1` closure
- `bb-6aj.3.1` optional follow-up
## Scope
- Scanner rooted to `%USERPROFILE%` by default
- Bounded recursion and ignore patterns
- Full-drive (`C:\`, `D:\`) scan must be explicit opt-in only
## File Ownership
- `src/lib/scanner.ts`
- `src/app/api/scan/route.ts` (if needed)
- `tests/lib/scanner.test.ts`
## Hard Constraints
- No default full-drive crawl
- No Unix-only shell assumptions
- Keep path normalization consistent
## Verification
```powershell
npm run typecheck
npm run test
```

View file

@ -0,0 +1,32 @@
# Parallel Launch Order
## 1) Start Agent A + Agent B in Parallel
Terminal A:
```powershell
cd C:\Users\Zenchant\codex\beadboard\.worktrees\agent-a
```
Use prompt: `docs/dispatch/agent-a-registry-api.md`
Terminal B:
```powershell
cd C:\Users\Zenchant\codex\beadboard\.worktrees\agent-b
```
Use prompt: `docs/dispatch/agent-b-kanban.md`
## 2) Start Agent C After Registry Persistence Completes
Terminal C:
```powershell
cd C:\Users\Zenchant\codex\beadboard\.worktrees\agent-c
```
Use prompt: `docs/dispatch/agent-c-scanner.md`
## 3) Integration Gate
From root `C:\Users\Zenchant\codex\beadboard`:
```powershell
npm run typecheck
npm run test
```