Commit graph

516 commits

Author SHA1 Message Date
matt wilkie
dfa8ea4813
fix(docgen): generate CLI docs in one process (#4474)
Add a bulk help docs writer that emits the root CLI reference and website command pages from a single Cobra walk. Update the shell generator to call that mode, preserve the pure-Go docs binary guard, and refresh historical versioned CLI docs only when release snapshotting requests a specific version.

Agent-Signature: codex-gpt-5.5-medium on behalf of matt wilkie
2026-06-22 18:25:58 -07:00
silvanshade
4d3a552424
Fix rig bead durability (#4373)
* Fix rig bead durability (bds-vwz)

* fix: keep rig beads out of infra migration

* fix: repair durable rig wisps

Restore migration 0035 to its frozen upstream shape and add a forward repair migration for existing type=rig rows that were routed into wisps.

Keep type=rig durable while excluding it from ready work, and cover the repair path with CLI-backed schema tests plus Dolt-server tests where available.

Agent-Signature: codex-unknown-model-unknown-reasoning on behalf of matt wilkie

* fix: make rig wisp repair migration upgrade-safe

Guard migration 0053 so older workspaces without local wisp tables no-op instead of failing, while keeping the fresh-Dolt CLI migration bundle able to exercise rig wisp repair fixtures.

Regenerate CLI reference docs for the updated infra type help text.

Agent-Signature: codex-gpt-5.5-high on behalf of matt wilkie

---------

Co-authored-by: silvanshade <silvanshade@users.noreply.github.com>
Co-authored-by: matt wilkie <maphew@gmail.com>
2026-06-22 17:06:35 -07:00
CI Bot
37c97e0b79 fix(init): guard JSONL init against remote history
_codex-gpt-5.5-xhigh on behalf of CI Bot_

Agent-Signature: codex-gpt-5.5-medium on behalf of matt wilkie
Agent-Signature: claude-unknown-model-high on behalf of matt wilkie
Agent-Signature: codex-unknown-model-unknown-reasoning on behalf of matt wilkie
2026-06-22 15:28:38 -07:00
Stephanie Jarmak
749cc63e8d
docs(list): warn that repeated -s/--status silently overwrites (#3916) (#3917)
`bd list --status open --status in_progress` returns only `in_progress`
matches because cobra's StringP flag silently overwrites prior values
on repeat. The canonical multi-status form is the comma-separated
variant (`--status open,in_progress`), and the help text already names
it — but does not warn about the repeated-flag footgun.

Add a one-sentence note to the --status help text and regenerate the
checked-in CLI reference docs via
./scripts/generate-cli-docs.sh. No behavior change.

Closes gastownhall/beads#3916.

Co-authored-by: sjarmak <sjarmak@users.noreply.github.com>
2026-06-22 13:18:44 -07:00
matt wilkie
058134d81c
docs: align agent maintainer conventions (#4237)
* docs: align agent maintainer conventions

Agent-Signature: codex-gpt-5.5-medium on behalf of matt wilkie

* docs: refresh checked-in AGENTS.md managed block to generated content

The PR self-review flagged the execution metadata key rename (item 4) as a
local experiment; that content was already dropped from this branch. Upstream
PR #4358 has since documented the existing execution_* model/effort keys as
portable hints in docs/METADATA.md, which remains the canonical reference.

Refresh the checked-in AGENTS.md managed Beads block to the current rendered
full-profile section so the marker hash is truthful. This drops the
experimental "read execution metadata first" workflow step from the managed
block (execution hints stay documented in docs/METADATA.md and
AGENT_INSTRUCTIONS.md) and picks up the conservative agent context profiles
from #4220.

Agent-Signature: claude-unknown-model-high on behalf of matt wilkie
2026-06-20 20:44:08 -07:00
matt wilkie
b4d999fa9e
fix(compact): stop advertising the unimplemented Tier 2 compaction (#4465)
bd admin compact --tier 2 hard-errors "not yet implemented", yet the command
help, --stats output, and several docs advertised "Tier 2: Ultra compression
(90 days closed, 95% reduction)" as if it worked. Make the surface honest:

- Reject --tier != 1 early with a clear "not yet implemented; only --tier 1 is
  available" message instead of failing deep inside a mode.
- --stats labels Tier 2 "not yet implemented" and drops the bogus 95% savings
  estimate; the JSON tier2 block gains "implemented": false.
- Update command/flag help, the plugin skill doc, and the examples README;
  regenerate the generated CLI reference.

New embedded e2e asserts --tier 2 errors and --stats no longer advertises 95%.
No attempt to implement Tier 2 (semantics undefined); only the false
advertising is removed.

Refs #4463

Agent-Signature: claude-opus-4-8-high on behalf of maphew
2026-06-20 15:29:28 -07:00
matt wilkie
889ade6b7f
fix(compact): archive content before destructive compaction; make restore work (#4464)
Content compaction (bd admin compact) overwrote an issue's description and
cleared design/notes/acceptance_criteria in place with no archive, while the
issue_snapshots/compaction_snapshots tables built to hold that archive were
dead code (never written). The only recovery, bd restore, was display-only and
relied on a largest-history-row heuristic that dolt gc / history-squash can
erase. Net: compaction was effectively irreversible.

Wire the existing compaction_snapshots table: archive the full pre-compaction
content (snapshot_json BLOB) before the destructive overwrite, aborting if the
archive fails; add SnapshotIssue/GetCompactionSnapshot/RestoreFromSnapshot to
the CompactionStore interface on both Dolt and embedded stores; and rework
bd restore to restore from the snapshot (--apply writes it back; default stays
read-only display, with the old Dolt-history reconstruction as fallback).

Unit tests assert snapshot-before-overwrite ordering and abort-on-archive-
failure; an integration test covers the snapshot -> overwrite -> restore round
trip against a real Dolt store. CLI reference docs regenerated for the new flag.

Refs #4463

Agent-Signature: claude-opus-4-8-high on behalf of maphew
2026-06-20 14:12:07 -07:00
Steve Yegge
4e460b427b
fix(is_blocked): cross-mode full recompute repair for stale is_blocked (bd-6dnrw.37) (#4423)
* fix(is_blocked): cross-mode full recompute repair for stale is_blocked (bd-6dnrw.37)

The post-pull is_blocked recompute (bd-6dnrw.3) is scoped to the merge diff and
skips when a re-pull merges nothing (HEAD unchanged), so a recompute that failed
AFTER its merge committed — or a conflicted pull resolved by hand (which skips
the recompute) — left is_blocked stale with no repair: rerunning bd dolt pull
merged nothing and recomputed nothing. bd ready trusts is_blocked, so stale
values silently hide ready work or surface blocked work.

Core (internal/storage/issueops/blocked_consistency.go):
- RecomputeAllIsBlockedInTx: full mark/unmark fixpoint over every issue+wisp,
  returns rows corrected. Idempotent. Reuses the existing pass functions.
- CountIsBlockedInconsistenciesInTx: read-only COUNT of stale rows for detection.
  Its predicate mirrors the mark/unmark templates and is pinned to the repair by
  the dolt-package lockstep tests (a converged DB counts 0; any counted row is
  one a recompute pass flips), so detection cannot silently drift from repair.

Cross-mode repair:
- storage.BlockedRecomputer capability; DoltStore + EmbeddedDoltStore
  RecomputeAllBlocked (stage issues-only, matching the post-pull recompute).
- New 'bd recompute-blocked' command — works in BOTH embedded and server mode.
  bd doctor is server-mode only, so embedded users need a non-doctor entry point.
- bd doctor (server mode) gains a read-only "Blocked State" check and a
  'bd doctor --fix' dispatch running the same repair. Warn-only (does not fail
  OverallOK): new check shipping in a patch, is_blocked self-heals via the fix.

Secondary item (server recomputeBlockedAfterPull commits via s.Commit, which can
sweep a concurrent writer's changes) split to bd-6y5hx (P3, deferred): it is
subtle (after an auto-resolved merge the working set holds the whole merge
result, so a naive issues-only narrowing would drop merge results). The embedded
path already stages issues-only; the new repair path stages issues-only too.

Tests: 3 dolt lockstep tests (detect==repair, stuck-blocked, parent-child
cascade) + embedded wiring test. Smoke-tested on a real ~2000-issue embedded DB:
0 false positives. build/vet/gofmt/golangci-lint all clean.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* docs: regenerate CLI reference for `bd recompute-blocked`

Run ./scripts/generate-cli-docs.sh + ./scripts/generate-llms-full.sh with
the canonical CGO_ENABLED=0 gms_pure_go build to pick up the new
`bd recompute-blocked` command. The adopted PR added the command but did
not regenerate the CLI docs, failing the PR doc-flags freshness checks.

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

* fix(is_blocked): guard full recompute against dirty graph; pin doctor blocked-state last

Maintainer adoption fixes for PR #4423 review (bd-6dnrw.37):

- Refuse a full is_blocked recompute when the committable graph tables
  (issues, dependencies) carry uncommitted working-set changes, across the
  server, embedded, and doctor-fix paths. The recompute derives flags from
  the current graph and stages only `issues`, so running it dirty would
  sweep unrelated issue edits into the repair commit or publish is_blocked
  derived from uncommitted dependency state. Dolt-ignored wisp tables are
  deliberately excluded from the guard: they are never committed and show
  as perpetually modified in dolt_status, so guarding on them would refuse
  the recompute in any workspace that uses wisps.

- Pin the doctor "Blocked State" fix to an explicit terminal priority so it
  provably runs after every graph-mutating fix (Dependency Keys,
  Orphaned/Child-Parent Dependencies, Cross-Table Duplicates) instead of
  relying on check-append order. This fixes a stale is_blocked left after
  `bd doctor --fix --fix-child-parent` removed a child-parent edge.

- Surface (no longer swallow) the doctor-fix Dolt stage/commit errors, and
  tolerate only the benign nothing-to-commit case.

Tests: dirty-issues and dirty-dependencies refusal, dirty-wisps still
repairs, clean repair+commit idempotence (dolt server-mode); fix-ordering
regression covering the --fix-child-parent case (cmd/bd); embedded wiring
test now commits its seed to match the fresh-process clean-tree precondition.

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

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: Eddie the Engineer <ci@beads.test>
2026-06-19 23:14:09 -07:00
coffeegoddd☕️✨
9a8447ccf6 docs: regenerate CLI reference for bd ready --offset
Run ./scripts/generate-cli-docs.sh + ./scripts/generate-llms-full.sh
with the canonical CGO_ENABLED=0 gms_pure_go build to pick up the new
--offset flag.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-18 13:55:12 -07:00
Kevin Glynn
d585928bb3
feat(init): add --init-if-missing for idempotent init (#3490) (#4332)
* feat(init): add --init-if-missing for idempotent init (#3490)

bd init aborts with exit 1 when the workspace is already initialized,
forcing scaffold scripts to pre-stat .beads/embeddeddolt/<prefix> to tell
"already initialized" (benign) apart from real errors. Add an opt-in
--init-if-missing flag: when the workspace already exists, init prints a
benign "Skipping init: workspace already initialized." to stderr and exits 0.
Default behavior (flag absent) is unchanged - exit 1 with the existing
"already initialized ... Aborting" message.

The flag is intercepted only at the existing checkExistingBeadsData guard
call site; detection logic and the --force/--reinit-local paths are untouched.

Docs regenerated via scripts/generate-cli-docs.sh and generate-llms-full.sh.

Co-authored-by: Cursor <cursoragent@cursor.com>

* fix(init): abort --init-if-missing on explicit prefix mismatch

--init-if-missing silently skipped whenever a workspace already existed,
even if the caller passed an explicit --prefix that differed from the
existing workspace. That masked a real mismatch: `bd init --prefix bar
--init-if-missing` against an existing `foo` workspace exited 0 and
ignored the requested prefix.

Now, when --prefix is set explicitly (and --database is not), compare the
requested prefix against the existing workspace's recorded DoltDatabase
and abort on a genuine mismatch; matching or undeterminable cases still
skip benignly. Extracts the prefix->dbName normalization into shared
helpers so the guard derives exactly the same name init records, and
factors the decision into a pure, unit-tested helper.

Refs #3490

Co-authored-by: Cursor <cursoragent@cursor.com>

* fix(init): don't mask operational errors or --database mismatch under --init-if-missing

Two idempotent-init correctness fixes on top of #4332 (reviewer Bernoulli):

1. checkExistingBeadsData now distinguishes the benign "already initialized"
   outcome (errWorkspaceAlreadyInitialized, carried by a workspaceExistsError
   that keeps the user-facing message) from operational errors such as an
   unreadable .beads/embeddeddolt directory. --init-if-missing skips only the
   benign case; an operational error still aborts instead of being masked as a
   successful idempotent skip.

2. An explicit --database mismatch now aborts --init-if-missing, mirroring the
   existing --prefix guard. --database is the authoritative database selector,
   so it is checked even when --prefix is also set.

Tests: initIfMissingDatabaseMismatch table; checkExistingBeadsDataAt returns a
sentinel-matching error for an existing database and a non-matching
(operational) error when embeddeddolt is unreadable.

Agent-Signature: claude-opus-4-8-high on behalf of maphew

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: matt wilkie <maphew@gmail.com>
2026-06-18 09:51:27 -07:00
Jean Pierre
7b43aea058
Add bd-board to community tools (#4349) 2026-06-16 07:48:25 -07:00
Tom Ford
01ad6c215e
docs: add beads.nvim to community tools (#4390) 2026-06-16 07:46:06 -07:00
matt wilkie
a006a3369f fix(cli): implement children pretty and defer reason
Why: #4365 reports two documented CLI affordances that either fail or require a second command. children advertised --pretty but rejected it, and defer had no way to capture the reason at deferral time.

What: add the children --pretty flag by delegating to list's existing tree renderer, add defer --reason by appending to notes during the status update, and refresh generated CLI docs.

Agent-Signature: codex-unknown-model-unknown-reasoning on behalf of matt wilkie
2026-06-13 21:22:38 -07:00
Julian Knutsen
e8ae7a291a
feat(count): add --include-infra for exact bd list cardinality parity (#4389)
* feat(count): add --include-infra for exact bd list cardinality parity

bd count hardcoded filter.SkipWisps=true (9a29a158f, Q2 SQL-COUNT rewrite),
so it only counted the durable issues table. bd list --include-infra merges
the wisps table — including no_history beads, which are durable work — so no
count invocation could match a list cardinality. On the production gascity
rig store that meant bd count --type task = 23,777 vs a list --include-infra
cardinality of 33,601: a 29% undercount that blocks Gas City from
implementing an exact Counter over the bd CLI (its bounded-read pagination
needs Total to be exact).

Changes:

- cmd/bd/count.go: new --include-infra flag mirroring bd list's flag.
  applyCountIncludeInfra reproduces the buildListFilter defaults that
  determine list's cardinality under --include-infra: wisps merge
  (SkipWisps=false), template exclusion (IsTemplate=false), default gate
  exclusion unless --type gate, and infra-type routing to the ephemeral
  tier using the store-configured infra set. Without the flag the filter
  construction is unchanged (SkipWisps=true), keeping the widely-scripted
  default byte-identical.
- internal/storage/{dolt,embeddeddolt}/counts.go: CountIssues now delegates
  to issueops.CountIssuesInTx (extended with the query param) instead of a
  hardcoded SELECT COUNT(*) FROM issues, so SkipWisps/Ephemeral routing
  matches SearchIssuesInTx. CountIssuesInTx previously had no production
  callers.
- internal/storage/issueops/count.go: CountIssuesByGroupInTx now honors
  SkipWisps/Ephemeral with the same merge semantics, so --by-* grouped
  counts under --include-infra report merged buckets instead of
  silently-wrong durable-only numbers.
- Tests (TDD): cmd/bd/count_filter_test.go pins the count filter against
  buildListFilter field-by-field; internal/storage/dolt/
  count_include_wisps_test.go asserts CountIssues == len(SearchIssues) for
  the trap filters (templates, no_history, ephemeral) and merged grouped
  counts; cmd/bd/count_embedded_test.go adds CLI-level count==list parity.
- Docs: regenerated CLI reference (also picks up pre-existing dep/import
  help-text drift so scripts/check-doc-flags.sh passes) and one pre-existing
  gofmt fix in issueops/search.go for ci-pr-lint.

Verification on the production gascity rig store (read-only):

  bd count --include-infra --type task  = 33,601
  bd list  --include-infra --type task --all --json --limit 0 | len = 33,601
  bd count --include-infra              = 42,631  (list equivalent: 42,631)
  bd count --include-infra --status open = 1,969  (list equivalent: 1,969)
  bd count --include-infra --by-type    : total 42,631, task bucket 33,601
  bd count --type task (no flag)        = 23,777  (stock bd 1.0.5: 23,777)

Gates: make ci-pr-core (go test -race -short), ci-pr-policy, ci-pr-lint,
go vet ./..., embedded count/list suites, full dolt + embeddeddolt
storage packages.

Fixes #4387

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix(cli): write-intent routing for all mutating commands; count ephemeral parity; pin bulk dep cycle gate

Adopt-PR review fixes for PR #4389 on top of the pre-review CI repair.

Routed write surface (#4141, bd-6dnrw.32, GH#3231): bd-6dnrw.32 gave
read-only opens a real read-only path, which silently broke routed sibling
writes -- prefix-routed resolution opened the target read-only, so a mutating
command on a routes.jsonl-routed ID failed with "store is read-only". The
earlier CI repair restored update/comment/comments add/note/reopen; review
found the rest of the mutating surface still broken. Write intent now covers
every prefix-routed mutating command: assign, priority, tag, edit, delete
(single + batch), close (resolveCloseTargets), human respond/dismiss, link,
and dep add/--blocks/remove/bulk (via a new resolveIDWithRoutingForWrite).
The source issue's store opens writable so the write commits on the target
head; read paths, dependency-target ID resolution, dep tree, and contributor
auto-routing stay read-only, preserving the bd-6dnrw.32/GH#3231 guarantee
that routed reads never mutate a foreign project's history. Regression test
TestEmbeddedRoutedMutatingSiblingWritesCommitTargetHead pins assign/tag/
dep add/delete/close routed writes committing on the target head.

Count ephemeral parity (GH#4387): CountIssuesInTx returned the wisps count
unconditionally for an Ephemeral=true filter, while SearchIssuesInTx falls
through to the durable issues table when the wisps tier is empty. The scalar
fall-through landed first, but review (attempt 2) found the same fall-through
missing from the two sibling functions, so grouped counts and count-projection
searches still dropped a durable issues-table row flagged ephemeral=1:
CountIssuesByGroupInTx returned empty buckets while the scalar Total fell
through (sum(groups) != Total), and SearchIssuesWithCountsInTx returned nil
where SearchIssues returned the row. CountIssuesByGroupInTx and
SearchIssuesWithCountsInTx now mirror the scalar/list fall-through, so
bd count --include-infra --by-* and bd search --counts --include-infra match
bd list cardinality when only durable rows match. The scalar fall-through
comment is corrected to describe the durable ephemeral=1 defensive state
(a promoted bead carries ephemeral=0, so it never reaches this branch).
Regression tests TestCountIssuesEphemeralFallsThroughToDurable (scalar),
TestCountIssuesByGroupEphemeralFallsThroughToDurable (grouped), and
TestSearchIssuesWithCountsEphemeralFallsThroughToDurable (counts projection)
pin count==len(list) for that case; the merge path documents that list is the
disjoint-table corruption detector.

Bulk dep cycle gate (bd-6dnrw.8): unchanged from the pre-review repair --
TestEmbeddedDepBulkNoCycleCheckKeepsWholeGraphGate pins the whole-graph
cycle gate on bulk --no-cycle-check adds.

Validation (worktree, BEADS_TEST_EMBEDDED_DOLT=1, -tags gms_pure_go):
routed-write and count-parity regression tests pass; TestEmbeddedDep*,
cross-rig routing, dep/close/delete/link CLI suites, and the count
CLI/issueops suites pass; go build, go vet, gofmt, git diff --check clean.

Validation (attempt 2, grouped + counts-projection fall-through): go build
(issueops, dolt, cmd/bd) and go vet (issueops, dolt) clean; git diff --check
clean. The Dolt count/list parity suite passes against an isolated Dolt test
container (TestCountIssuesMergedMatchesSearch, the three ephemeral
fall-through regressions, TestCountIssuesByGroupIncludesWisps,
TestPR4107SearchIssuesWithCountsEphemeralFalseIncludesNoHistoryOnly); all
three fall-through regressions were verified failing on the pre-fix tree.
Embedded-engine fixtures that need the CGO/ICU build are exercised by the
GitHub PR workflow.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

---------

Co-authored-by: CI Bot <ci@beads.test>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-06-13 04:14:28 -07:00
Steve Yegge
7ebf4df6ac fix(linear): unwire staleness hook from core; gitignore last_pull (bd-6dnrw.12)
PR 3669 wired Linear-specific logic into every bd command: rootCmd
pre-run ran maybeWarnLinearStaleness (config reads, file stats, stderr
warnings, PPID-keyed temp markers) on all commands, and bd prime
silently shelled out to 'bd linear sync --pull --json' via whatever bd
was on PATH (version skew + network IO at session start). Both hooks
are removed; staleness checking stays opt-in via the existing
'bd linear sync --pull-if-stale' flag, which agents can run from a
session hook if they want fresh data.

The per-machine .beads/last_pull marker is now in the canonical
gitignore template and required patterns, so clones stop committing
and churning it. CONFIG.md updated to match.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-06-11 01:14:08 -04:00
matt wilkie
3bf890cb21
docs(metadata): document portability of execution model/effort hints (#4358)
State the rule that makes execution_reasoning_effort and
execution_suggested_model portable across agent runtimes: stored effort
values are a canonical advisory scale that consumers map to their own
runtime, and suggested models are capability-tier hints that consumers
on another provider substitute rather than drop. Also update the
gh-3541 reference: that issue resolved to keep execution hints
metadata-only with no first-class CLI helper.

Agent-Signature: claude-fable-5-high on behalf of matt wilkie
2026-06-10 09:30:41 -07:00
Steve Yegge
f97fd4a8b5 fix(dolt): detect Dolt ancestor-PK merge refusals and print bootstrap-canonical-clone recovery (bd-6dnrw.1)
Dolt refuses outright to merge a table whose primary key set differs
across the merging heads or in their common ancestor ("cannot merge
because table X has different primary keys [in its common ancestor]").
The refusal fires before any row conflicts materialize, so the pull
auto-resolver never runs and retrying can never converge the clones —
the residual #4259 hazard for v1.0.4 -> v1.0.6 upgrades with un-synced
dependency edits straddling the 0041/0043/0050 PK reshape.

bd dolt pull/push (and auto-push) now recognize this error class and
print the bootstrap-from-one-canonical-clone recipe (force-push the
canonical clone, export/re-clone/import everywhere else) instead of
just the raw error. Full playbook added as docs/RECOVERY.md#pk-fork-refused,
plus an Unreleased upgrade note: sync every clone before upgrading and
pull immediately after the designated migrator pushes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-06-09 23:41:19 -04:00
Dustin Brown
9a1c88b63a
/{.github,docs,go,internal,scripts}: bump driver/dolt version to 2.1.4 (#4326)
* /{.github,docs,go,internal,scripts}: bump driver/dolt version to 2.1.4

* /default.nix: update hash
2026-06-08 11:31:14 -07:00
Dustin Brown
d00b890a33
fix(remote): remove cli invocations of 'dolt remote' and exclusively use store method and sql (#4236)
* /{cmd,internal}: remove dolt cli commands

* /cmd/bd/dolt.go: change remote add and remove to do less

* /internal/storage/dolt/credentials_test.go: remove old tests

* /{docs,website}: regen docs

* /internal/storage/dolt: pr feedback

* /website/static/llms-full.txt: regen doc

* docs: refresh versioned CLI docs

* fix: guard CLI routing for SQL remotes (bd-wisp-6ukh)

---------

Co-authored-by: Eddie the Engineer <julianknutsen@users.noreply.github.com>
2026-06-05 13:58:21 -07:00
coffeegoddd☕️✨
14322af05b /{docs,website,scripts}: holy fuck again 2026-06-03 15:16:55 -07:00
coffeegoddd☕️✨
f9a6f503c4 /{docs,website,scripts}: holy fuck again 2026-06-03 15:10:34 -07:00
coffeegoddd☕️✨
a143374ea0 /{docs,website}: again 2026-06-03 14:59:23 -07:00
coffeegoddd☕️✨
04a65cce81 /{cmd,docs,internal,website}: more ci fixes 2026-06-03 14:56:34 -07:00
coffeegoddd☕️✨
f783cbbede /{docs,website}: gen docs 2026-06-03 14:30:53 -07:00
matt wilkie
cea892d43f
docs: publish community tools on website (#4299)
* docs: publish community tools on website

Mirror docs/COMMUNITY_TOOLS.md into Docusaurus so the Pages build publishes it for the default released docs and unreleased docs without relying on manual copy steps.

Agent-Signature: codex-gpt-5.5-high on behalf of matt wilkie

* docs: publish core support docs on website

Mirror Sync Concepts, Labels, Metadata, Uninstalling, and Antivirus docs into Docusaurus and include them in the default released snapshot and LLM bundle.

Clarify that agent execution and verification metadata are examples of metadata as a schema extension point, not native issue fields.

Agent-Signature: codex-gpt-5.5-high on behalf of matt wilkie

* docs: clarify metadata examples

Replace local verification queue metadata with a tracker round-trip example so public metadata docs show upstream-aligned schema extension patterns.

Agent-Signature: codex-gpt-5.5-high on behalf of matt wilkie
---------
2026-06-03 13:44:47 -07:00
Medhat Galal
4e8cedc961
Add Jira custom field support for push (#3678)
Allow Jira push to include configured project-specific fields such as Team. Custom field values can be plain strings or JSON objects/arrays for Jira field types that require structured payloads, and per-type config overrides global values after the Beads issue type is mapped to a Jira issue type.
2026-06-01 07:40:57 -07:00
matt wilkie
8de88e15b7
docs: link canonical SYNC_CONCEPTS.md from deeper docs (#4248)
* docs: link canonical SYNC_CONCEPTS.md from deeper docs

SYNC_CONCEPTS.md is the canonical cross-machine sync explainer but was only
linked from README.md. Add a one-line pointer from ARCHITECTURE, DOLT, FAQ,
GIT_INTEGRATION, and SYNC_SETUP so readers deep in those docs can find it.
Docs-only; all pointers steer toward bd dolt push/pull as canonical sync.

Salvages the still-relevant piece of #3726 (closed as superseded by #3909).

Agent-Signature: claude-opus-4-8-medium on behalf of maphew

* docs: dedupe duplicate DOLT.md entry in SYNC_SETUP See Also

The See Also list had two DOLT.md links with different descriptions
(pre-existing on main). Merge into a single entry.

Agent-Signature: claude-opus-4-8-medium on behalf of maphew
2026-05-29 22:44:54 -07:00
Julian Knutsen
9e8d411f71
Add PR CI wrapper command surface (#4211)
* ci: add PR wrapper command surface

* ci: collect wrapper timing in PR checks

* docs: record initial CI wrapper measurements

* ci: add manual measurement workflow

* ci: allow branch measurement dispatch

* ci: keep measuring independent commands after failures

* docs: record branch-dispatched CI measurement

* ci: keep measuring package suites after failures

* docs: record CI measurement batch

* fix: repair CI-measured test failures

* test: make local Go gates hermetic

* ci: add sharded integration measurement lane

* test: fix internal beads integration TestMain

* docs: record fixed integration shard measurement

* ci: add hybrid integration sharding measurement

* ci: speed up cmd/bd test shard discovery

* ci: add 16-way integration sharding measurement

* ci: measure prebuilt cmd bd sharding

* docs: record prebuilt sharding measurement

* docs: design CI build artifact stage

* docs: record repeat prebuilt integration measurement

* ci: add build artifact stage

* ci: reuse build artifact in linux test lane

* ci: promote main linux integration shards

* ci: gate legacy platform tests to main

* ci: satisfy workflow shell lint

* ci: ignore archived migrations in duplicate check

* ci: add package gate wrappers

* test: clean up testing short boundaries

* ci: allow unreleased version docs lag

* ci: gate releases on package checks

* ci: split workflow by tier

* ci: add aggregate PR gates
2026-05-29 18:52:53 -07:00
Jim Wordelman
278b24ab4b
fix(init): honor dolt local-only remote wiring (#4227)
* fix(init): honor dolt local-only remote wiring (ga-vjefud.1)

* docs: regenerate CLI reference for dolt.local-only config help

The dolt.local-only config-set example added in cmd/bd/config.go was not
reflected in the generated CLI docs, so the "Check doc flags freshness" CI
job failed on PR #4227. Regenerate from live bd help: docs/CLI_REFERENCE.md,
the website cli-reference page, the 1.0.0/1.0.4 versioned snapshots, and
llms-full.txt. Generated under LC_ALL=C to match CI's glob collation order.

_Claude Opus 4.7 (beads/investigator) on behalf of quad341_

* docs(config): tighten dolt.local-only help wording + cover isDoltLocalOnly()

Maintainer follow-up on #4227. Two non-blocking review nits:

- The config-set example said "Suppress Dolt remote wiring and sync", but
  dolt.local-only only gates remote wiring at `bd init` time; it does not
  gate runtime `bd dolt push`/`pull`. Reword to "Skip wiring a Dolt sync
  remote during bd init" so the help matches the implemented scope.
  Mirrored into the five generated CLI-reference artifacts.

- Add TestIsDoltLocalOnly to exercise the new isDoltLocalOnly() config
  reader through the env path (BD_DOLT_LOCAL_ONLY). The existing
  TestLocalOnlyInitSkipsConfigureButPersistsExplicitRemote passed localOnly
  directly and never covered the config-reading helper.

Doc artifacts verified fresh with CGO_ENABLED=0 -tags gms_pure_go (matching
CI): check-doc-flags.sh, check-doc-freshness.sh, and both generate-*.sh
--check all pass.

Agent-Signature: claude-opus-4-8-high on behalf of maphew

---------

Co-authored-by: Jim Wordelman <jim@wordelman.name>
Co-authored-by: matt wilkie <maphew@gmail.com>
2026-05-28 15:41:38 -07:00
matt wilkie
e1e97e6c58
docs: add conservative Beads agent profile (#4220)
* docs: add conservative beads agent profile

_codex-gpt-5.5-medium on behalf of maphew_

* docs: tighten agent-profile wording and cover no-push branches

Address PR #4220 review:

- Drop noisy "Profile model:" prefix from the default-branch profile
  rule; lead with the actual instruction.
- Break the single-sentence MCP closeProtocol into two for readability.
- Fix the user-facing repo URL in the generated recipe template
  (steveyegge/beads -> gastownhall/beads); Go module imports are
  unchanged.
- Add prime_test cases that exercise the no-push branch for both CLI
  and MCP outputs, via a new primeNoPushConfigured stub seam.

Naming-vs-mechanism feedback (treat "profile" as wording, not yet
runtime config) is tracked in a separate follow-up issue rather than
expanding this PR's scope.

Agent-Signature: claude-opus-4-7-medium on behalf of maphew
2026-05-28 15:20:25 -07:00
matt wilkie
2141b65823
Merge pull request #4201 from maphew/fix/setup-symlink-followups
fix(setup): harden symlink follow-up handling
2026-05-28 08:08:32 -07:00
matt wilkie
bc56d692b2
Merge pull request #4152 from quad341/feat/be-wwbsv-schema-skew-guard
feat(schema): schema-skew guard — hard fail on forward DB drift (be-wwbsv)
2026-05-28 08:06:46 -07:00
matt wilkie
8aefc326a6
test: improve coverage signal policy (#4219)
_codex-gpt-5.5-medium on behalf of maphew_
2026-05-27 22:05:14 -07:00
matt wilkie
32586cbf61
fix(dolt): detect managed handoff port conflicts (#4217)
Avoid persisting environment-supplied managed Dolt ports into the repo-local port file, and add a doctor warning plus recovery docs for standalone-to-managed-city handoff conflicts.

_codex-gpt-5.5-high on behalf of matt wilkie_
2026-05-27 21:48:35 -07:00
matt wilkie
602593b47d
fix(install): use declared module path for go fallback (#4215)
The repository has moved to gastownhall/beads, but released Go modules still declare github.com/steveyegge/beads. The installer fallback should use the declared module path, and the docs/check should keep future guidance from regressing.

_codex-gpt-5.5-medium on behalf of matt wilkie_
2026-05-27 21:48:24 -07:00
matt wilkie
a180c63066
fix(close): support per-id reasons (#4194)
* fix(close): support per-id reasons

Why: upstream GH#3279 reports repeated --reason values applying incorrectly across multi-ID close, while GH#3268 needs a ready zero-dependency regression guard to prevent queue drift.

_codex-gpt-5.5-medium on behalf of matt wilkie_

* docs: refresh close CLI references

_codex-gpt-5.5-medium on behalf of CI Bot_

* fix(close): preserve empty reason compatibility

Ignore empty --reason occurrences so explicit empty strings continue to fall back to the default close reason and do not conflict with --reason-file. Clarify that repeated reasons map to IDs by positional index.

_codex-gpt-5.5-medium on behalf of matt wilkie_
2026-05-27 20:41:07 -07:00
matt wilkie
7229fb1d11
import: skip stale JSONL issue snapshots (#4204)
* import: skip stale JSONL issue snapshots

Skip imported JSONL issue records when the local row has a newer updated_at timestamp, and report stale skips without creating no-op commits.

_codex-gpt-5.5-medium on behalf of matt wilkie_

* import: report stale skipped JSONL IDs

Expose stale_skipped_ids in import results so JSON callers can distinguish imported IDs from records that were intentionally skipped as stale.

_codex-gpt-5.5-medium on behalf of maphew_
2026-05-27 20:40:12 -07:00
Julian Knutsen
6fc67e6908 docs: record CI cleanup plan 2026-05-28 01:19:14 +00:00
CI Bot
20bb11d4f3 docs: finish Dolt and release doc consolidation
Main already converted docs/DOLT-BACKEND.md and docs/RELEASING.md into canonical pointer stubs. Finish the consolidation by moving the still-useful verified details into the authoritative docs and fixing stale inbound references that still sent readers to the pointer files.

DOLT.md keeps the server-mode Dolt install notes, remote setup guidance, macOS LaunchAgent setup, direct Dolt CLI usage, accidental data-directory commit cleanup, and the embedded-mode data path correction.

RELEASING.md keeps the release.sh easy path and Docusaurus versioning steps from the retired docs-level guide. AGENT_INSTRUCTIONS.md now links directly to the root releasing guide, and the init error path now links to the canonical Dolt guide under gastownhall/beads.

Refs: GH#3683, PR#3706

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

_codex-gpt-5.5-medium on behalf of matt wilkie_
2026-05-27 18:10:47 -07:00
coffeegoddd☕️✨
316cfc697b /{cmd,docs,internal,website}: remove pass 2026-05-27 16:32:28 -07:00
coffeegoddd☕️✨
a106722705 /{cmd,docs,internal,website}: wire up 2026-05-27 15:30:47 -07:00
coffeegoddd☕️✨
e4b4d846c4 /{docs,website}: gen docs for new flags 2026-05-27 14:43:15 -07:00
coffeegoddd☕️✨
885eacb3df /{docs,website}: gen docs 2026-05-27 13:40:11 -07:00
matt wilkie
86545f64f3 fix(setup): harden symlink follow-up handling
Refuse setup atomic writes through symlinks unless a caller explicitly opts into following the link, and report partial Claude/Mux setup when agent instructions are skipped.

Document repair steps for repositories already affected by corrupted mode-120000 CLAUDE.md entries.

Refs #3722.

_codex-gpt-5.5-medium on behalf of matt wilkie_
2026-05-27 13:32:00 -07:00
Chris DiMartino
0afd3d5b94
fix(codex): ship hook release safely
Move Codex native hook metadata under the Codex-only plugin directory so Claude keeps using only its inline `bd prime` hooks.

Leave release version bumps to the maintainer release flow while documenting hook metadata isolation under Unreleased.

Refs #3924.

_codex-gpt-5.5-medium on behalf of matt wilkie_
2026-05-27 13:19:41 -07:00
matt wilkie
5feba36752
docs: design required CI gate topology (#4179)
_codex-gpt-5.5-high on behalf of CI Bot_
2026-05-26 15:58:04 -07:00
matt wilkie
ade96333fd
docs: guard plugin CLI reference pointer (#4177)
Record the plugin CLI reference as a pointer-only resource and extend the doc freshness check so it fails if that resource drifts back into a copied command reference.

_codex-gpt-5.5-medium on behalf of CI Bot_
Co-authored-by: CI Bot <ci@beads.test>
2026-05-26 15:31:24 -07:00
matt wilkie
5de494b85e
Merge pull request #3562 from quad341/release/be-l9q
feat(list): add --skip-labels hydration toggle
2026-05-26 15:13:54 -07:00
Julian Knutsen
aa9ee7f632 docs: audit CI test surface (bd-jot) 2026-05-26 20:18:40 +00:00
Eugene Brevdo
5d33b4c891
init: run Codex project setup by default
Run Codex project setup during `bd init` using the existing setup installer, and stage generated Codex project files in the bootstrap commit.

Also refresh the generated setup/init docs for the new default behavior.

Co-authored-by: Eugene Brevdo <ebrevdo@gmail.com>

_codex-gpt-5.5-medium on behalf of CI Bot_
2026-05-26 13:03:37 -07:00