Add maybeAutoPush() in PersistentPostRun (after auto-commit and auto-backup)
that pushes to the Dolt remote when an origin is configured. Uses the same
pattern as maybeAutoBackup: debounce interval, change detection via commit
hash comparison, and non-fatal warnings on failure.
Config keys: dolt.auto-push (bool, auto-enabled when origin exists),
dolt.auto-push-interval (duration, default 5m).
This completes the Dolt replication story: users add a remote once and
data flows automatically.
Closes: bd-5x9
Executed-By: beads/polecats/quartz
Rig: beads
Role: polecats
Document the full dependency and gate systems which had no dedicated
guide. Prompted by community discussion #2164 asking how to keep
dependent work in sync when beads updates aren't tied to code merges.
- New docs/DEPENDENCIES.md: dependency types, ready work, visualization,
cross-repo deps, gate types (gh:pr, gh:run, timer, bead, human),
gate automation, and workflow recipes
- Add Gates section to CLI_REFERENCE.md (bd gate commands were missing)
- Cross-reference from QUICKSTART.md and DOLT.md
Adds `bd backup` command that exports all database tables to sorted JSONL
files in .beads/backup/ for off-machine recovery. Events are exported
incrementally using a high-water mark. Each table is written atomically
via temp file + rename.
Auto-backup runs in PersistentPostRun when backup.enabled is true,
throttled by backup.interval (default 15m). Optional git-push mode
auto-commits and pushes backup files.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Executed-By: beads/crew/emma
Rig: beads
Role: crew
Updates AGENT_INSTRUCTIONS.md and docs/CLAUDE.md to recommend make install over go build -o bd, preventing stale binary issues.
PR: https://github.com/steveyegge/beads/pull/2109
Author: l0g1x (Krystian Gebis)
Agent instructions and CLAUDE.md told agents to run
`go build -o bd ./cmd/bd` followed by `./bd`, creating stale local
binaries in every worktree. Change to `make install` which places the
binary in ~/.local/bin (the canonical location) and use `bd` from PATH
instead of `./bd`.
Standardize start-work semantics to `bd update <id> --claim` across docs,
examples, templates, and website static LLM artifacts. Replaces
`--status in_progress` with `--claim` where the meaning is start-work.
Also fixes stale comment in llms.txt ("Update status" → "Start work").
Co-Authored-By: Valeriy Pavlovich <iqdoctor@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add a new MCP `claim` tool as the atomic start-work operation (CLI equivalent: `bd update <id> --claim`). Keep `update` for semantic updates. Update MCP-facing docs/examples to use `claim` for start-work. Add focused tests for client/tool/server claim paths.
Co-Authored-By: Valeriy Pavlovich <iqdoctor@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* feat: support issue_id_mode=counter for sequential IDs (GH#2002)
When `issue_id_mode=counter` is set via `bd config set issue_id_mode counter`,
`bd create` now assigns monotonically increasing integer IDs instead of
hash-based IDs. The counter is stored in a new `issue_counter` table (one row
per prefix) and incremented atomically within the same transaction as the issue
insert.
- Add `issue_counter` table to schema (version bumped to 5)
- Add migration 006 to create `issue_counter` table on existing databases
- Add `GetNextIssueCounter()` to queries.go (standalone transaction, for
callers outside CreateIssue)
- Modify `generateIssueID()` to check `issue_id_mode` config and use counter
path when set to "counter"; hash mode remains the default when unset
- Explicit `--id` flag continues to take precedence over counter mode
- Tests: TestGetNextIssueCounter_Sequential, TestGetNextIssueCounter_MultiplePrefixes,
TestCreateIssue_CounterMode, TestCreateIssue_ExplicitIDOverridesCounter,
TestCreateIssue_HashModeDefault, TestMigrateIssueCounterTable
* docs: document issue_id_mode=counter feature (GH#2002)
Add documentation for the sequential counter ID mode across all relevant docs:
- docs/CONFIG.md: new issue_id_mode namespace entry and full example section
with tradeoff table, migration guidance, and per-prefix counter isolation
- .beads/BD_GUIDE.md: counter mode section with when-to-use, migration
considerations, and explicit --id override behavior
- docs/ADAPTIVE_IDS.md: alternative counter mode section with cross-reference
to CONFIG.md
- website/docs/reference/configuration.md: issue_id_mode under ID Generation
with comparison table
* fix: seed counter from existing issues when enabling counter mode (GH#2002)
When issue_id_mode=counter is enabled on a repo that already has manually-created
sequential IDs (e.g., plug-1 through plug-50), the counter used to start at 1,
causing immediate collisions.
Add seedCounterFromExistingIssuesTx() which scans existing issue IDs, finds the
highest numeric suffix for the given prefix, and seeds the issue_counter table
from there. The function is idempotent (skips if a counter row already exists)
and only counts purely-numeric suffixes (ignoring hash-based IDs like test-a3f2).
The seeding is called at first counter use: in generateIssueID() (issues.go) and
GetNextIssueCounter() (queries.go) when sql.ErrNoRows is returned for the prefix.
Add four tests covering: seeding from existing numeric IDs, mixed hash+numeric
IDs, fresh repos (counter starts at 1), and already-seeded counters (no regress).
* feat: add bd config schema and describe commands for agent discoverability (GH#2002)
Adds machine-readable config schema so agents can programmatically discover
all available configuration keys without reading source code.
- internal/config/schema.go: new ConfigKeyDef struct and Schema slice with
43 entries covering core, sync, routing, jira, linear, gitlab, team, mail,
and YAML-only keys; includes type, default, valid values, description, and
storage location per key
- cmd/bd/config.go: adds 'bd config schema' (table + --json) and
'bd config describe <key>' (single-key detail + --json) subcommands
Usage:
bd config schema
bd config schema --json | jq '.[] | select(.key == "issue_id_mode")'
bd config describe issue_id_mode
bd config describe jira.url --json
* refactor: remove overengineered config schema (keep docs only)
Remove the configSchemaCmd and configDescribeCmd subcommands added in
the previous commit, along with internal/config/schema.go (390 lines of
config key definitions). These are out of scope for GH#2002.
The daemon was removed in v0.50. Remove remaining references from
NEWSLETTER.md, docs/LINTING.md, website sidebar, and llms.txt files.
Regenerated llms-full.txt from clean source docs. CHANGELOG.md
historical entries preserved.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* feat(otel): comprehensive OpenTelemetry instrumentation
Phase 1 (telemetry foundation + SQL + CLI + AI):
- Add internal/telemetry package: Init/Shutdown, Tracer/Meter helpers,
stdout + OTLP/gRPC exporters, noop providers when disabled
- Add internal/telemetry/storage.go: InstrumentedStorage decorator for
SDK consumers with bd.storage.* counters and duration histograms
- Instrument DoltStore SQL layer (execContext, queryContext, queryRowContext)
with dolt.exec / dolt.query / dolt.query_row spans
- Instrument Anthropic API calls in compact/haiku.go and find_duplicates.go
with bd.ai.input_tokens, bd.ai.output_tokens, bd.ai.request.duration
- Add bd.command.<name> span in PersistentPreRun/PostRun with actor attribute
Phase 2 (VC ops, hooks, sync, metrics):
- Add dolt.commit / dolt.push / dolt.force_push / dolt.pull / dolt.branch /
dolt.checkout / dolt.merge spans for Dolt version-control procedures
(these bypass execContext so needed dedicated spans)
- Add bd.db.retry_count counter in withRetry (server mode retries)
- Add bd.db.lock_wait_ms histogram in AcquireAccessLock (flock contention)
- Add ephemeral.count / ephemeral.nuke spans for SQLite ephemeral store
- Add hook.exec spans in hooks_unix/windows runHook (background root spans)
- Add tracker.sync / tracker.pull / tracker.push / tracker.detect_conflicts
spans with per-phase stats attributes in tracker/engine.go
- Add bd.issue.count gauge (by status) in InstrumentedStorage.GetStatistics
- Fix: call initAIMetrics via sync.Once in newHaikuClient so ai metrics
are actually registered
Configuration:
BD_OTEL_ENABLED=true enable (default: off, zero overhead)
BD_OTEL_STDOUT=true write to stdout for dev/debug
OTEL_EXPORTER_OTLP_ENDPOINT=... ship to Jaeger/Grafana/Honeycomb/etc.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* refactor(otel): align with VictoriaMetrics HTTP stack
- Switch metric exporter: gRPC → HTTP (otlpmetrichttp)
- Activation: BD_OTEL_METRICS_URL presence (no more BD_OTEL_ENABLED flag)
matches GT_OTEL_METRICS_URL convention from the local observability stack
- BD_OTEL_METRICS_URL=http://localhost:8428/opentelemetry/api/v1/push
- BD_OTEL_LOGS_URL=http://localhost:9428/insert/opentelemetry/v1/logs (reserved)
- Traces: stdout only (BD_OTEL_STDOUT=true); noop otherwise since VictoriaMetrics
is a metrics-only backend — no trace overhead in production
- Remove: otlptracegrpc, otlpmetricgrpc
- Update docs/OBSERVABILITY.md to match the diffusiontown README style
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* feat(otel): capture hook stdout/stderr and bd.args in spans
- hook.exec span now records stdout and stderr as span events after
the hook process exits (including partial output on timeout)
- Output is truncated to 1024 bytes; the event carries both the text
(output) and the original size (bytes) as attributes
- bd.command.<name> span now includes bd.args with the raw CLI
arguments (e.g. "create 'title' -p 2")
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix(otel): address review feedback — stale comment, span leak, hot-path alloc
1. Fix stale BD_OTEL_ENABLED comment in main.go (actual env vars are
BD_OTEL_METRICS_URL and BD_OTEL_STDOUT)
2. Use defer+named returns in Merge() to prevent span leaks
3. Cache doltSpanAttrs() via sync.Once to avoid per-call allocation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: beads/crew/emma <steve.yegge@gmail.com>
Adds bd setup mux with support for layered AGENTS.md installation
(root, project .mux/, global ~/.mux/) and managed hook files
(.mux/init, .mux/tool_post, .mux/tool_env). Makes AGENTS removal
non-destructive (preserves user content outside managed markers).
From: PR #1888 by alexx-ftw (cherry-picked, rebased onto current main)
Co-Authored-By: Alexx <alexx-ftw@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
bd sync was calling CommitPending + Push on every invocation, causing
perceived slowness when agents call it at high velocity. Now prints a
deprecation message and exits immediately without opening the database.
Updated AGENTS.md, AGENT_INSTRUCTIONS.md, SKILL.md, copilot-instructions,
and init templates to reference bd dolt push/pull instead.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Fixes#1710 — bd init installs 5 hooks but UNINSTALLING.md only listed 4
(missing prepare-commit-msg). Also missing beads.role git config entry.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Delete broken store_nocgo_test.go (references undefined errNoCGO),
remove dead bootstrapEmbeddedDolt/hasDoltSubdir functions, and clean up
stale comments and docs that still referenced embedded mode, CGO
requirements, or in-process Dolt across 20 files.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Executed-By: beads/crew/emma
Rig: beads
Role: crew
- Remove stale "realtime" references from comments, docs, and config
(realtime mode was already removed from valid modes)
- Fix config validation to use actual mode/strategy/sovereignty values
instead of stale names (local/git-branch/external → git-portable/
dolt-native/belt-and-suspenders; lww → newest; none/isolated/federated
→ T1/T2/T3/T4)
- Remove 6 dead functions from config.go (IsSyncModeValid,
IsConflictStrategyValid, IsSovereigntyValid, ShouldExportOnChange,
ShouldImportOnChange, NeedsDoltRemote) — only used in tests,
redundant with existing validators in sync.go
- Update tests and docs to match
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Executed-By: beads/polecats/opal
Rig: beads
Role: polecats
Closed wisps accumulate rapidly and bloat the database. This adds a
--closed flag to wisp gc that uses batch deletion infrastructure for
efficient bulk purge, safe by default (preview-only without --force).
Also upgrades the existing abandoned-wisp deletion from O(n) per-issue
DeleteIssue calls to a single deleteBatch() call.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Executed-By: beads/crew/emma
Rig: beads
Role: crew
These documents described SQLite-specific features that no longer exist
after the Dolt migration. Preserved in git history. Updated references
in ARCHITECTURE.md and FAQ.md.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Executed-By: beads/crew/emma
Rig: beads
Role: crew
Delete migrate_hash_ids.go (760 lines) and remove hash-ids subcommand,
doctor checks, and readonly test cases. Relocate copyFile to migrate.go
for migrate_dolt.go and repair.go. Rename public API beads.NewStorage()
to beads.Open() across code, tests, examples, and docs. Clean up
transitional SQLite-era comments in store.go and context.go. Add server
mode watchdog with TCP+SQL health probes, auto-restart with stale PID
cleanup, exponential backoff, and clean shutdown.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Executed-By: beads/crew/emma
Rig: beads
Role: crew
Update documentation examples from deprecated NewSQLiteStorage to
NewStorage(ctx, path). Fix monitor-webui to import the public beads
package instead of internal/beads.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Executed-By: beads/crew/emma
Rig: beads
Role: crew
current documentation features an invalid command:
```
$ bd migrate --to=dolt
Error: unknown flag: --to
```
The intent was probably `bd migration --to-dolt`.
- Add unit tests for Dolt-specific ignore patterns
- Document manual cleanup steps for committed Dolt data
Coverage: gitignore validation logic in doctor command
Step-by-step procedure for validating push/pull/clone of Dolt databases
to real GitHub repos via refs/dolt/data. Covers SSH auth, data integrity,
incremental sync, git clone isolation, and cleanup with pass/fail checklist.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>