30dfb247dc
## Problem When bd sync detected stale DB (>50% divergence), it would import JSONL to fix the DB, but then immediately export the DB back to JSONL. This caused the stale DB to overwrite the JSONL after a git pull, undoing cleanup work. Example scenario: 1. Clone has 688 stale issues in DB (628 closed) 2. git pull brings JSONL with 62 issues (cleanup applied) 3. bd sync detects 1009.7% divergence and imports JSONL (DB → 62 issues) ✓ 4. bd sync exports DB to JSONL (JSONL still 62 issues) ✓ 5. But this marks JSONL as "changed" and commits/pushes it ✗ ## Solution After ZFC (JSONL First Consistency) import, set skipExport flag to prevent the export step. JSONL is the source of truth after import - DB should sync to match, not export back. ## Changes - cmd/bd/sync.go: Add skipExport flag, set it after ZFC import - cmd/bd/sync.go: Wrap export logic in `if !skipExport` block - CHANGELOG.md: Update ZFC entry with accurate description - cmd/bd/sync_test.go: Add TestZFCSkipsExportAfterImport Fixes #bd-l0r 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
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
Beads: Issue tracking that moves at the speed of thought ⚡