Cleanup: Runtime artifacts, hard-coded paths, PR 14 bug fixes

This commit is contained in:
zenchantlive 2026-03-05 15:57:33 -08:00
parent 98886d1901
commit 1c4b5ab401
27 changed files with 1629 additions and 204 deletions

View file

@ -16,14 +16,14 @@
**Files:**
- Modify: `beadboard/.beads/issues.jsonl` via `bd` commands only
- Read: `/mnt/c/Users/Zenchant/codex/beadboard/AGENTS.md`
- Read: `/mnt/c/Users/Zenchant/codex/beadboard/NEXT_SESSION_PROMPT.md`
- Read: `beadboard/AGENTS.md`
- Read: `beadboard/NEXT_SESSION_PROMPT.md`
**Step 1: Claim/track implementation bead(s)**
Run:
```bash
cd /mnt/c/Users/Zenchant/codex/beadboard
cd beadboard
bd create --title="Global installer runtime manager implementation" --description="Implement npm-global-first runtime manager with migration from repo-path shims" --type=task --priority=1 --label="installation,cli,runtime"
bd update <new-bead-id> --status in_progress --assignee <agent-bead-id>
```

View file

@ -1,6 +1,6 @@
# Next Session Prompt: Dolt/Beads Database Recovery and Source-of-Truth Reconciliation
You are continuing work in `/mnt/c/Users/Zenchant/codex/beadboard`.
You are continuing work in `beadboard`.
## Problem snapshot (as of 2026-02-28)
Bead state appears empty in `bd ready`, but `.beads/issues.jsonl` contains historical data.

View file

@ -1,6 +1,6 @@
# Next Session Prompt: Holistic UX Critique for Professional Multi-Agent Operations
You are continuing work in `/mnt/c/Users/Zenchant/codex/beadboard`.
You are continuing work in `beadboard`.
## Understanding Brief
BeadBoard is intended to be a **professional multi-agent communication + work management system** where:

View file

@ -123,7 +123,7 @@ Wildcards:
"id": "proto_20260214_001",
"version": "v1",
"event_type": "HANDOFF",
"project_root": "C:/Users/Zenchant/codex/beadboard",
"project_root": "/path/to/project",
"bead_id": "bb-u6f.6.3",
"from_agent": "amber-otter",
"to_agent": "cobalt-harbor",