Dicklesworthstone
af045d8375
Keep completed removal evidence when later validation fails. Make prune audit and non-Windows removal-parent sync unconditional instead of inheriting default-off capture fsync. Preserve capture policy. Add real filesystem partial-failure/retry regression and document remaining unlink-to-result crash window. RCH ovh-a job30023605353973786: STAGE=source-identity EXIT=0; STAGE=source-freshness EXIT=0; STAGE=clippy EXIT=0; STAGE=lib-tests EXIT=0 (18); STAGE=test-cli_mirror_prune EXIT=0 (6); STAGE=goldens EXIT=0 (68).92 selected tests passed on final Rust bytes. STAGE=fmt EXIT=1; STAGE=ubs EXIT=1 (1 critical,740 warnings, one file). Strict gate RED; no push/closure. Full source/CLI hash and command receipt on bead2l1b0.39. Power-loss exactly-once recovery remains unproven.
Beads - AI-Native Issue Tracking
Welcome to Beads! This repository uses Beads for issue tracking - a modern, AI-native tool designed to live directly in your codebase alongside your code.
What is Beads?
Beads is issue tracking that lives in your repo, making it perfect for AI coding agents and developers who want their issues close to their code. No web UI required - everything works through the CLI and integrates seamlessly with git.
Learn more: github.com/steveyegge/beads
Quick Start
Essential Commands
# Create new issues
bd create "Add user authentication"
# View all issues
bd list
# View issue details
bd show <issue-id>
# Update issue status
bd update <issue-id> --status in_progress
bd update <issue-id> --status done
# Sync with git remote
bd sync
Working with Issues
Issues in Beads are:
- Git-native: Stored in
.beads/issues.jsonland synced like code - AI-friendly: CLI-first design works perfectly with AI coding agents
- Branch-aware: Issues can follow your branch workflow
- Always in sync: Auto-syncs with your commits
Why Beads?
✨ AI-Native Design
- Built specifically for AI-assisted development workflows
- CLI-first interface works seamlessly with AI coding agents
- No context switching to web UIs
🚀 Developer Focused
- Issues live in your repo, right next to your code
- Works offline, syncs when you push
- Fast, lightweight, and stays out of your way
🔧 Git Integration
- Automatic sync with git commits
- Branch-aware issue tracking
- Intelligent JSONL merge resolution
Get Started with Beads
Try Beads in your own projects:
# Install Beads
curl -sSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bash
# Initialize in your repo
bd init
# Create your first issue
bd create "Try out Beads"
Learn More
- Documentation: github.com/steveyegge/beads/docs
- Quick Start Guide: Run
bd quickstart - Examples: github.com/steveyegge/beads/examples
Repo-Specific Agent Defaults
This repository has legacy historical issue IDs mixed with current
coding_agent_session_search-* IDs. To keep agent workflows stable:
- Start triage with
bv --robot-triageorbv --robot-next. - Use
br ready --jsonto confirm actionable work. - Prefer explicit stale-safe flags on
brcommands in multi-agent sessions.
Workspace config (.beads/config.yaml) sets:
issue_prefix: coding_agent_session_searchallow_legacy_ids: trueno-auto-import: true
Runtime note: even with no-auto-import: true, some br invocations can still
hit prefix-mismatch checks in this mixed-ID workspace. Use explicit flags for
reliable operation:
br ready --json --no-auto-import --allow-stalebr show <id> --json --no-auto-import --allow-stalebr list --status=open --json --no-auto-import --allow-stale
This preserves access to legacy records while avoiding auto-import validation paths that can fail in shared sessions.
Beads: Issue tracking that moves at the speed of thought ⚡