AGENTS.md · diff
git:20260412.97c1189 to git:20260815.d6fd4c6
9 added, 122 removed. Audit A to A.
# Agent Instructions
- This project uses **bd** (beads) for issue tracking. Run `bd onboard` to get started.
-
- ## Quick Reference
-
- ```bash
- bd ready # Find available work
- bd show <id> # View issue details
- bd update <id> --status in_progress # Claim work
- bd close <id> # Complete work
- bd sync # Sync with git
- ```
+ Project context and conventions live in [CLAUDE.md](CLAUDE.md), including the
+ registration checklist every new skill must satisfy.
## Landing the Plane (Session Completion)
**When ending a work session**, you MUST complete ALL steps below. Work is NOT complete until `git push` succeeds.
**MANDATORY WORKFLOW:**
- 1. **File issues for remaining work** - Create issues for anything that needs follow-up
+ 1. **File issues for remaining work** - Open GitHub issues for anything that needs follow-up
2. **Run quality gates** (if code changed) - Tests, linters, builds
3. **Update issue status** - Close finished work, update in-progress items
4. **PUSH TO REMOTE** - This is MANDATORY:
```bash
git pull --rebase
- bd sync
git push
git status # MUST show "up to date with origin"
```
5. **Clean up** - Clear stashes, prune remote branches
6. **Verify** - All changes committed AND pushed
7. **Hand off** - Provide context for next session
**CRITICAL RULES:**
- Work is NOT complete until `git push` succeeds
- NEVER stop before pushing - that leaves work stranded locally
- NEVER say "ready to push when you are" - YOU must push
- If push fails, resolve and retry until it succeeds
-
- <!-- BEGIN BEADS INTEGRATION v:1 profile:full hash:d4f96305 -->
- ## Issue Tracking with bd (beads)
-
- **IMPORTANT**: This project uses **bd (beads)** for ALL issue tracking. Do NOT use markdown TODOs, task lists, or other tracking methods.
-
- ### Why bd?
-
- - Dependency-aware: Track blockers and relationships between issues
- - Git-friendly: Dolt-powered version control with native sync
- - Agent-optimized: JSON output, ready work detection, discovered-from links
- - Prevents duplicate tracking systems and confusion
-
- ### Quick Start
-
- **Check for ready work:**
-
- ```bash
- bd ready --json
- ```
-
- **Create new issues:**
-
- ```bash
- bd create "Issue title" --description="Detailed context" -t bug|feature|task -p 0-4 --json
- bd create "Issue title" --description="What this issue is about" -p 1 --deps discovered-from:bd-123 --json
- ```
-
- **Claim and update:**
-
- ```bash
- bd update <id> --claim --json
- bd update bd-42 --priority 1 --json
- ```
+ ## Quality Gates
- **Complete work:**
+ Run all four before pushing:
```bash
- bd close bd-42 --reason "Completed" --json
+ ./scripts/validate-frontmatter.sh
+ node scripts/run-evals.js --min-rank1 75 --collision-threshold 0.75
+ bats tests/
+ ./scripts/check-codex-parity.sh
```
-
- ### Issue Types
-
- - `bug` - Something broken
- - `feature` - New functionality
- - `task` - Work item (tests, docs, refactoring)
- - `epic` - Large feature with subtasks
- - `chore` - Maintenance (dependencies, tooling)
-
- ### Priorities
-
- - `0` - Critical (security, data loss, broken builds)
- - `1` - High (major features, important bugs)
- - `2` - Medium (default, nice-to-have)
- - `3` - Low (polish, optimization)
- - `4` - Backlog (future ideas)
-
- ### Workflow for AI Agents
-
- 1. **Check ready work**: `bd ready` shows unblocked issues
- 2. **Claim your task atomically**: `bd update <id> --claim`
- 3. **Work on it**: Implement, test, document
- 4. **Discover new work?** Create linked issue:
- - `bd create "Found bug" --description="Details about what was found" -p 1 --deps discovered-from:<parent-id>`
- 5. **Complete**: `bd close <id> --reason "Done"`
-
- ### Auto-Sync
-
- bd automatically syncs via Dolt:
-
- - Each write auto-commits to Dolt history
- - Use `bd dolt push`/`bd dolt pull` for remote sync
- - No manual export/import needed!
-
- ### Important Rules
-
- - ✅ Use bd for ALL task tracking
- - ✅ Always use `--json` flag for programmatic use
- - ✅ Link discovered work with `discovered-from` dependencies
- - ✅ Check `bd ready` before asking "what should I work on?"
- - ❌ Do NOT create markdown TODO lists
- - ❌ Do NOT use external issue trackers
- - ❌ Do NOT duplicate tracking systems
-
- For more details, see README.md and docs/QUICKSTART.md.
-
- ## Landing the Plane (Session Completion)
-
- **When ending a work session**, you MUST complete ALL steps below. Work is NOT complete until `git push` succeeds.
-
- **MANDATORY WORKFLOW:**
-
- 1. **File issues for remaining work** - Create issues for anything that needs follow-up
- 2. **Run quality gates** (if code changed) - Tests, linters, builds
- 3. **Update issue status** - Close finished work, update in-progress items
- 4. **PUSH TO REMOTE** - This is MANDATORY:
- ```bash
- git pull --rebase
- bd dolt push
- git push
- git status # MUST show "up to date with origin"
- ```
- 5. **Clean up** - Clear stashes, prune remote branches
- 6. **Verify** - All changes committed AND pushed
- 7. **Hand off** - Provide context for next session
-
- **CRITICAL RULES:**
- - Work is NOT complete until `git push` succeeds
- - NEVER stop before pushing - that leaves work stranded locally
- - NEVER say "ready to push when you are" - YOU must push
- - If push fails, resolve and retry until it succeeds
-
- <!-- END BEADS INTEGRATION -->