Commit graph

321 commits

Author SHA1 Message Date
beads/crew/lizzy
431d84040b fix(docs): disambiguate duplicate nvim-beads entry in COMMUNITY_TOOLS.md
Add author handle to display name and missing language tag for the
fancypantalons/nvim-beads entry to distinguish it from joeblubaugh/nvim-beads.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-03 17:16:15 -08:00
gastown/crew/max
637c817b9a Merge PR #2318: docs: update GIT_INTEGRATION.md re deprecated beads-merge binary and Jujutsu integration
Documents that the standalone beads-merge binary is deprecated in favor of
bd merge, and adds Jujutsu (jj) integration instructions for resolving
beads merge conflicts.

PR: https://github.com/steveyegge/beads/pull/2318
Author: maphew
2026-03-03 16:49:46 -08:00
gastown/crew/max
7a537252e6 Merge PR #2319: docs: add fancypantalons/nvim-beads to Community Tools
Adds a second nvim-beads plugin (by @fancypantalons) to the community
tools listing.

PR: https://github.com/steveyegge/beads/pull/2319
Author: maphew
2026-03-03 16:49:36 -08:00
Ohad Basan
2d9ad516ef fix(docs): correct misleading examples in QUICKSTART.md
Two issues:

1. Epic child creation commands were missing the --parent flag,
   making it appear that child tasks are automatically associated
   with the most recently created epic. The --parent flag is required.

2. The dependency visibility example (bd list showing "blocked by"
   annotations) was placed immediately after issue creation, before
   any dependencies were added. Moved it after the "Add Dependencies"
   section where it makes sense.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-04 00:24:31 +02:00
Matt Wilkie
571323c013 docs: add fancypantalons/nvim-beads to Community Tools
Closes #482

Amp-Thread-ID: https://ampcode.com/threads/T-019cb569-6bbd-73fd-85a8-0b1dc28c1c20
Co-authored-by: Amp <amp@ampcode.com>
2026-03-03 13:38:49 -07:00
Matt Wilkie
2dc18d8064 docs: update GIT_INTEGRATION.md re deprecated beads-merge binary and Jujutsu integration
Add Custom Merge Driver section documenting:
- Deprecation of standalone beads-merge binary (previously at neongreen/mono)
  in favor of built-in bd merge command
- Updated Jujutsu (jj) integration config using bd as the merge program

Fixes #906

Amp-Thread-ID: https://ampcode.com/threads/T-019cb569-6bbd-73fd-85a8-0d5dcb78b711
Co-authored-by: Amp <amp@ampcode.com>
2026-03-03 13:38:43 -07:00
Pablo LION
76aec3cc55
refactor(testutil): expand Dolt readiness to 5-state enum (#2304)
* refactor(testutil): consolidate Dolt readiness into enum

Expand from 3-state to 5-state doltReadiness enum:
- doltNoDocker (renamed from doltNoDaemon for clarity)
- doltNoImage (no image at all)
- doltWrongVersion (repo cached but wrong tag)
- doltSkipped (explicit BEADS_TEST_SKIP=dolt opt-out)
- doltReady

Add isDoltRepoImageCached() to distinguish "no image" from "wrong
version". Add hasTestSkip() for comma-separated BEADS_TEST_SKIP
parsing. Silent skip for explicit opt-out avoids ~1s docker info
overhead.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* docs: clarify scope of ddfc5e94

ddfc5e94 title says "consolidate" but actually expands the design:

Code changes (internal/testutil/testdoltserver.go):
- Expand doltReadiness enum from 3 to 5 states
- Rename doltNoDaemon → doltNoDocker (clarity)
- Add doltWrongVersion state (image repo cached, wrong tag)
- Add doltSkipped state (explicit opt-out)
- Introduce BEADS_TEST_SKIP env var (comma-separated service list)
  replacing the owner's implicit Docker-only detection with an
  explicit opt-out mechanism that skips the ~1s docker info cost
- Add isDoltRepoImageCached() helper (docker images <repo> -q)
- Add hasTestSkip(service) helper (parses BEADS_TEST_SKIP)
- Extract doltDockerRepo package var to deduplicate strings.Cut
- Silent skip for doltSkipped (no WARN in StartTestDoltServer)

Documentation (docs/TESTING.md):
- Add 5-state readiness table
- Document BEADS_TEST_SKIP usage and evaluation order

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-03 03:55:54 -08:00
beads/crew/lizzy
2329f4ef5c docs: update embedded Dolt references for upcoming reintroduction
Embedded Dolt is being reintroduced for standalone/solo Beads users
(Dolt team delivering improved embedded support). Update docs and code
comments that asserted embedded was permanently removed. Gas Town
continues to use server mode exclusively.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-02 21:45:47 -08:00
obsidian
89569b914e feat: add --backend flag to bd init with SQLite deprecation notice (bd-7xj5)
Dolt is now the default (and only) storage backend for bd init. Add a
--backend flag that accepts "dolt" (default) or "sqlite" (prints a
deprecation notice with migration instructions and exits). Unknown
backends produce a clear error.

Update QUICKSTART.md and DOLT-BACKEND.md to reflect that SQLite is no
longer supported and Dolt is the sole backend.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-02 18:33:12 -08:00
jasper
f1a299d15d feat: add --stdin flag as alias for --body-file - on bd create/update (bd-gz2o)
Adds --stdin boolean flag to bd create and bd update that reads the
description from stdin. This is a natural desire path -- agents frequently
try --stdin before discovering --body-file -. Uses cobra
MarkFlagsMutuallyExclusive to prevent conflicts with other description flags.
2026-03-02 15:34:08 -08:00
gastown/crew/mel
7239c66816 docs: update stale references to JSONL and SQLite architecture
- Remove obsolete config.yaml comments for no-db, no-daemon,
  no-auto-flush, no-auto-import (all pre-Dolt options)
- Update COMMUNITY_TOOLS.md migration notice and tool descriptions
- Update init template README: JSONL storage -> Dolt database
- Update init template config comments to remove SQLite references
- Update .gitignore comment: "legacy files" -> "legacy artifacts"

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-02 14:11:12 -08:00
lydia
52d7447698 feat(show): add --current flag to show active issue (GH#2184)
Adds `bd show --current` which resolves the currently active issue using
priority: in-progress assigned to actor > hooked > last touched. Exits
non-zero when no current issue is found, fixing the exit code problem
where unrecognized flags silently exited 0 with help text.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-01 20:18:33 -08:00
beads/crew/emma
a444bc2fc3 fix: close 3 easy-win GHIs — stealth outside git, dead docs link, holder field
- #2250: setupStealthMode skips git-exclude when not in a git repo
- #2239: remove dead Monitor WebUI reference from COMMUNITY_TOOLS.md
- #2183: add "holder" to isAllowedUpdateField so merge-slot acquire/release works

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Executed-By: beads/crew/emma
Rig: beads
Role: crew
2026-03-01 14:56:47 -08:00
Mitesh Ashar
20516a4907 feat(dolt): dual-surface remote management (SQL + CLI)
bd dolt remote add/remove/list now operate on both the SQL server and
filesystem CLI config, ensuring dolt push/pull via CLI can always find
the remote.

- remote add: writes both surfaces, prompts before overwriting
- remote list: shows both surfaces, flags discrepancies
- remote remove: removes both, refuses on URL conflict (--force to override)
- dolt show: includes remotes section
- dolt test: tests remote connectivity (SSH/HTTP)
- doctor: CheckRemoteConsistency in Data & Config, fixable for one-side-only
  (conflicts skipped even with --yes)
- docs: update DOLT-BACKEND.md with dual-surface behavior and refs/dolt/data note

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Executed-By: beads/crew/emma
Rig: beads
Role: crew
2026-02-28 23:53:39 -08:00
Mitesh Ashar
2b354ffd5e fix(dolt): use CLI fallback for push/pull on SSH remotes (#2118)
CALL DOLT_PUSH/DOLT_PULL through the SQL server times out for SSH
remotes — the MySQL connection drops before the SSH transfer completes.

Detect SSH remote URLs (git+ssh://, ssh://, git@) and shell out to
`dolt push`/`dolt pull` from the database directory instead. Hosted
Dolt, DoltHub, S3, GCS, and file remotes continue using SQL as before.

Also updates DOLT-BACKEND.md to document `bd dolt remote add` (added
in 573bdd1b) instead of the stale `cd .beads/dolt && dolt remote add`
pattern. Remotes added via CLI are not visible to the running SQL
server, causing the "remote 'origin' not found" error in #2118.

Tested with git+ssh:// remotes to GitHub on two standalone repos.
Other remote types (Hosted Dolt, S3, etc.) are untested by this change.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Executed-By: beads/crew/emma
Rig: beads
Role: crew
2026-02-28 23:53:39 -08:00
Steve Yegge
2a1c7a1047
Merge pull request #2195 from pae23/docs/otel-design
docs(otel): add OTel architecture and data model design docs
2026-02-28 21:20:35 -08:00
Steve Yegge
60ad58c55b
Merge pull request #2213 from maphew/docs/revise-community-tools-2134
docs: revise COMMUNITY_TOOLS.md for Dolt migration (#2134)
2026-02-28 19:33:08 -08:00
Steve Yegge
26ee432cb5
Merge pull request #2206 from maphew/fix/stale-doc-references
docs: remove stale daemon and bd sync --status/--merge references
2026-02-28 19:32:51 -08:00
maphew
1478fb57c6 docs: revise COMMUNITY_TOOLS.md for Dolt migration (#2134)
- Add Dolt migration compatibility notice at top
- Add Mardi Gras (Dolt-compatible TUI via bd list --json)
- Add BeadBoard (JSONL-era, Dolt compatibility TBD)
- Move beads_viewer to Historical/Stale (confirmed broken with Dolt)
- Note beads-ui uses bd CLI (Dolt-compatible)
- Fix duplicate 'insights' typo in beads-dashboard description

Addresses #2134

Amp-Thread-ID: https://ampcode.com/threads/T-019ca75d-c29a-74d8-9f43-9bdad824dabe
Co-authored-by: Amp <amp@ampcode.com>
2026-02-28 20:29:03 -07:00
maphew
4f60f320cf docs: remove stale daemon refs and bd sync --status/--merge references
Fix #1982: Remove obsolete 'bd daemon' references from docs that
survived the daemon-to-Dolt migration. Files cleaned:
- docs/ERROR_HANDLING.md (daemon_sync.go → sync.go)
- docs/COMMUNITY_TOOLS.md (remove DaemonSocket reference)
- docs/dev-notes/TEST_SUITE_AUDIT.md (note daemon tests removed)
- docs/dev-notes/ERROR_HANDLING_AUDIT.md (daemon_sync.go → sync.go)

Fix #2007: Replace stale 'bd sync --status' and 'bd sync --merge'
references with current equivalents (bd dolt show, git merge, etc.).
bd sync is now a deprecated no-op. Files cleaned:
- docs/GIT_INTEGRATION.md
- docs/PROTECTED_BRANCHES.md
- examples/protected-branch/README.md
- claude-plugin/commands/sync.md (rewritten as deprecation notice)

Amp-Thread-ID: https://ampcode.com/threads/T-019ca749-d4f2-7289-b085-52e17436e950
Co-authored-by: Amp <amp@ampcode.com>
2026-02-28 19:54:49 -07:00
Steve Yegge
b367e36876
Merge pull request #2182 from jhult/feat/hooks-hk
feat: add hk (hk.jdx.dev) as supported git hook manager
2026-02-28 18:33:25 -08:00
Pierre-Alexandre Entraygues
cef38b2dd5 docs(otel): remove absent metrics section from data model appendix
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-02-28 22:33:59 +01:00
Pierre-Alexandre Entraygues
56a5ae6af2 docs(otel): re-verify data model appendix line numbers against main@371df32b
All line numbers in the Source Reference Audit appendix were stale
(written against the branch commit 986a284c). Re-verified every
reference against main@371df32b:

- retry_count registration: 265 → 302
- lock_wait_ms registration: 269 → 306
- circuit_trips/rejected: remove "on main" qualifier (now the audit ref)
- bd.command span attrs: main.go:266-271 → 262-266
- bd.actor: main.go:478 → 474
- dolt.exec span: 312-318 → 363-368
- dolt.query span: 346-352 → 400-405
- dolt.query_row span: 372-378 → 429-434
- dolt.commit: 913 → 1086
- dolt.push: 1058,1093 → 1231,1266
- dolt.pull: 1122 → 1295
- dolt.merge: 1216 → 1389
- dolt.branch: 1184 → 1357
- dolt.checkout: 1199 → 1372
- hooks_otel.go: 14-25 → 14,20
- haiku.go model/op attrs: 128-131 → 129-130
- haiku.go token attrs: 164-168 → 165-167

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-02-28 22:33:59 +01:00
Pierre-Alexandre Entraygues
f41397b605 docs(otel): correct data model doc against source code audit
- Add metric naming convention table (SDK dot-notation → Prometheus underscores)
- Move doltserver.* events to roadmap — zero OTel imports in doltserver package
- Clarify hook.exec as span-only (no metric counters or histograms)
- Flag bd.db.lock_wait_ms as registered but never recorded
- Add circuit breaker metrics (bd.db.circuit_trips/rejected)
- Add source reference appendix: every span, metric, and attribute
  backed by file:line to prevent documentation drift
- Correct Init()/Shutdown() signatures to match actual telemetry.go
- Fix SQL span section to reflect actual dolt.query/exec/query_row spans

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-02-28 22:33:58 +01:00
Pierre-Alexandre Entraygues
8c6375ff13 docs(otel): add OTel architecture and data model design docs
- otel-architecture.md: component overview, implementation status,
  roadmap (Tier 1: trackers/git/doltserver, Tier 2: query/validation,
  Tier 3: command spans/test suite)
- otel-data-model.md: complete event schema for all telemetry signals,
  including new §7 for AI events (compact + find_duplicates),
  AI metrics (bd.ai.input_tokens, bd.ai.output_tokens, bd.ai.request.duration)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-02-28 22:33:58 +01:00
Steve Yegge
371df32b51
Merge pull request #2188 from aaronlippold/fix/guard-create-database-shadow-db
Reviewed by refinery: Well-executed fix for shadow database creation. CreateIfMissing guard with comprehensive test coverage. All CI green.
2026-02-28 11:03:16 -08:00
mayor
397618ece1 docs: update dolt docs with current reality
DOLT.md: fix data location paths to ~/gt/.dolt-data/
dolt-concurrency.md: status from draft to implemented

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-28 10:46:00 -08:00
Aaron Lippold
f7fd46ad36 fix: address Copilot review — context timeout, nolint comment, version refs
- findGitRoot: use exec.CommandContext with 5s timeout to prevent hangs
- store.go nolint: clarify that safety comes from escaping, not validator
  rejecting wildcards (underscores ARE allowed in DB names)
- TROUBLESHOOTING.md: replace ambiguous "this version" with changelog refs

Authored by: Aaron Lippold<lippold@gmail.com>
2026-02-28 13:29:51 -05:00
Aaron Lippold
63418ae549 fix: guard CREATE DATABASE to prevent shadow databases on wrong server
bd unconditionally ran CREATE DATABASE IF NOT EXISTS on every connection.
When connecting to the wrong server (auto-started from .beads/dolt/ or
Homebrew default), this created an empty shadow database hiding real data.

Changes:
- Add CreateIfMissing field to Config — only bd init sets it true
- SHOW DATABASES LIKE check before CREATE (with underscore escaping)
- Network error handling for SHOW DATABASES failure
- Suppress auto-start when metadata.json has explicit dolt_server_port
- Fix backup git push across .beads/redirect (findGitRoot)
- Fix macOS CanonicalizePath case resolution (walk dirs, not realpath)
- Add CreateIfMissing to all migration and create paths
- 10 regression tests covering guard, auto-start, ReadOnly, underscore
- CHANGELOG and TROUBLESHOOTING docs

Authored by: Aaron Lippold<lippold@gmail.com>
2026-02-28 13:29:51 -05:00
Jonathan Hult
eafff366b4
feat: add hk (hk.jdx.dev) as supported git hook manager 2026-02-28 07:28:06 -06:00
Steve Yegge
68752a6c51
Merge pull request #2167 from peterkc/docs/dependencies
docs(deps): add DEPENDENCIES.md for dependency system and gates
2026-02-27 13:08:49 -08:00
quartz
f710909589 feat(dolt): auto-push to Dolt remote with 5-minute debounce
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
2026-02-27 10:22:53 -08:00
Peter Chanthamynavong
b59486cc59
docs(deps): add DEPENDENCIES.md covering dependency system and gates
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
2026-02-27 10:09:05 -08:00
beads/crew/emma
d82110945a feat(backup): add JSONL backup command and auto-backup support
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
2026-02-26 16:31:31 -08:00
Pablo LION
332b4f457b refactor(output): simplify title-length semantics and default to 255 2026-02-26 19:46:27 +01:00
Alex Sharp
6c9054536a
Remove dolt embedded mode docs
Embedded mode was removed in v0.56.0
2026-02-26 00:23:18 -06:00
Steve Yegge
e54b89a83c
Merge PR #2109: docs: use make install instead of go build
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)
2026-02-25 10:44:36 -08:00
l0g1x
b652fbee8c docs: use make install instead of go build for bd binary
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`.
2026-02-25 09:11:08 +00:00
vp
4f4cc4118e docs(faq): clarify atomic self-pick claim wording 2026-02-25 10:44:22 +03:00
vp
999d158cc3 docs(faq): reorder assigned-vs-claim note 2026-02-25 10:43:24 +03:00
vp
05727efe2d docs(faq): restore assigned-work flow and clarify claim semantics 2026-02-25 10:40:40 +03:00
vp
95c86e1160 docs(faq): require assignee in claim example 2026-02-25 10:25:26 +03:00
vp
06cc556a33 docs(faq): note optional assignee with claim 2026-02-25 10:19:34 +03:00
vp
f78df9b7d7 merge: sync docs/claim-start-work-followup with upstream main
Resolve merge conflicts and keep review-driven doc semantics:\n- PATTERNS: use --status in_progress for unblock/resume\n- FAQ: simplify multi-agent flow to atomic claim\n- llms short ref: keep Start work comment\n- mol_current: keep upstream wisp-create guidance
2026-02-25 10:04:00 +03:00
vp
f5c2da1d2f docs(claim): address review nits and unblock resume semantics
- use --status in_progress for unblock/resume example\n- fix llms short reference comment to 'Start work'\n- simplify FAQ multi-agent claim flow
2026-02-25 10:01:52 +03:00
darcy
f9b306f152 docs(claim): standardize start-work semantics to --claim (#2070)
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>
2026-02-24 22:11:39 -08:00
Valeriy Pavlovich
3a86e9fdde
feat(mcp): add dedicated claim tool for atomic start-work (#2071)
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>
2026-02-24 22:10:01 -08:00
vp
fbc90a3e75 docs(claim): use --claim for start-work flows across docs, examples, and templates 2026-02-24 04:17:48 +03:00
Giulio Mecocci
87f32865cf
feat: support issue_id_mode=counter for sequential IDs (#2013)
* 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.
2026-02-22 23:49:46 -08:00
beads/crew/elinor
90da8f6028 docs: remove stale JSONL references from ~73 markdown files (bd-9ni.4)
Replace JSONL storage/sync references with Dolt-native equivalents across
documentation, plugin resources, website docs, agent instructions, and
example READMEs. Preserves legitimate JSONL references (bd import/export
commands, CHANGELOG history, routes.jsonl/interactions.jsonl concepts).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-22 22:18:02 -08:00