Re-cut of the burned v1.2.0: that tag failed pre-publish in goreleaser on
the freebsd cross-compile break (no artifacts were published), and a
burned tag is never reused (v1.1.1 precedent), so the same content ships
as 1.2.1 with the fix (#5661) included. The [1.2.0] changelog section is
renamed to [1.2.1] with a note; versionChanges rides along. Also the
first bump to regenerate the tracked .githooks markers via the previous
commit's update-versions.sh fix, clearing the main-red from fa3d8cc5c.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Cuts the [Unreleased] changelog (1,223 commits since the v1.1.2 hotfix,
mainline's first release since v1.1.0) as 1.2.0. Headliners in
versionChanges: migration 0062 (events -> dolt_ignored, one-time
self-committing flip), bd sync, --brief listings, defer auto-wake,
telemetry startup + eventsData bounding. Includes the uv.lock refresh
(the v1.1.1 lesson: the MCP gate must never meet a stale lock after the
tag exists).
* docs: caveat --parent label inheritance with size/effort labels (#4562)
Children inherit parent labels by default. Examples that use --parent with
size/effort labels on epics silently double-label every child, which breaks
effort queries. Document --no-inherit-labels in labels.md and parent-create
examples (skill, quickstart, molecules, multi-agent coordination).
* docs(labels): consolidate example commands and fix issue-ref style
Maintainer commit per vishnujayvel's request on PR #5123: fold the
two-step "create then label" example under Size/Effort Estimates into
one bd create -l invocation, and normalize the bare #2100 reference
to the GH#NNNN style used elsewhere in the docs.
Agent-Signature: claude-code-sonnet-medium on behalf of matt wilkie
* docs: revert no-op --no-inherit-labels edits, cross-link instead (GH#4562)
--no-inherit-labels was a no-op in the quickstart/molecules/coordination
examples (none created labels), inverting the deliberate #2100 default
for readers who don't have the problem yet. Revert those three plus the
same no-op edit in the plugin's INTEGRATION_PATTERNS.md to match main,
and add a one-line cross-link to the labels.md caveat/worked example
instead, per maphew's review on #5123.
---------
Co-authored-by: matt wilkie <maphew@gmail.com>
Commit ab3feda00 removed the len(prefix) > 8 check from validatePrefix,
but "Max length: 8 characters" survived in the command's Long help text,
the plugin skill page, and docs/reference/advanced.md. Remove from all
three sources; generated CLI docs are release-pinned and untouched.
* docs(async-gates): fix nonexistent gate subcommands in skill resource
ASYNC_GATES.md documented `bd gate eval`, `bd gate approve`, `bd gate
close`, and a combined `--await <type>:<id>` flag — none of which exist
in cmd/bd/gate.go. The real subcommands are create/list/show/check/
resolve/add-waiter/discover, with separate --type/--await-id/--reason
flags and no standalone close/approve (resolve covers both). Also
dropped the "Mail" gate type row, which has no implementation on main.
Discovered while building community skills against bd 1.0.4; verified
every replacement command against main's cmd/bd/gate.go and the
auto-generated docs/cli-reference/gate.md.
* docs(async-gates): align guide with resolve/escalate + timeout semantics
Address maphew review on #4913:
- Resolve only on success/merge/timer; escalate on failure/closed-unmerged
- Timeout is enforced only for timer gates
- Find-by-reason uses JSON filter (list text has no description)
- Document the implemented bead gate type
* docs(async-gates): bead gates await local bead IDs; cross-rig IDs are not evaluable
Cross-vendor review caught that the cross-rig example documents an
--await-id form gate.go treats as permanently pending (colon-qualified
IDs are unevaluable). Point the table and example at local bead IDs and
warn explicitly.
Agent-Signature: claude-fable-5-high on behalf of maphew
---------
Co-authored-by: matt wilkie <maphew@gmail.com>
Every multi-machine beads deployment hand-rolls the same shell loop around
pull/push; this ships it as `bd sync [--remote <name>] [--attempts N]`.
Three properties are the point of the verb, and each is a lesson paid for by
the reference deployment (a two-machine federation on a 60s timer):
- Conflicts are detected POSITIVELY, from the merge's own captured conflict
rows and from dolt_conflicts — never inferred from the pull's exit status.
A pull fails for reasons that are not conflicts, and a settled merge that IS
conflicted aborts and leaves dolt_conflicts empty, so an exit-status guess
both invents phantom conflicts and misses real ones. A pre-flight check also
halts on conflicts left live by an earlier halted sync, which Dolt otherwise
refuses to merge over with an opaque transport error.
- A conflict sync cannot settle is NEVER resolved by picking a side: it halts
before recomputing or pushing, with no --strategy-style override. A timer
that silently picks a side loses work on a schedule. The halt message
reports whether the conflict rows are live or were aborted away, read from
WHICH detection source fired rather than assumed — the SQL pull route aborts
and restores the working set, the CLI/git-protocol route deliberately leaves
the rows live, and an operator told the wrong one looks in the wrong place.
- The is_blocked recompute runs unconditionally, on every attempt. That is
deliberate and load-bearing: RecomputeAllBlocked is specifically the repair
that does NOT depend on a merge advancing HEAD (bd-6dnrw.37), so it is what
recovers a column left stale by a conflicted pull an operator resolved by
hand — a state this verb manufactures itself by exiting 2. Gating it on "did
this tick merge anything" re-imposes the condition it exists to escape, and
from then on no tick merges anything, so the repair would never run again
while every tick reported success. HEAD is the wrong instrument for that
question anyway: the pull's own pre-merge auto-commit (GH#2474) moves it for
purely local dirty state, and an auto-resolved merge can land in the working
set without moving it at all (bd-6dnrw.39).
Exit codes are the machine contract so a timer can branch without parsing
output: 0 synced, 1 error, 2 merge conflict (halted, nothing pushed), 3
push-race retries exhausted (transient). --json reports the same outcome.
Push-race classification is deliberately narrow — race signatures (behind /
non-fast-forward / a lost --force-with-lease: stale info, fetch first, "contains
work that you do not have"), not the word "rejected". A protected branch or a
declining pre-receive hook also rejects, permanently; treating that as a race
burns the whole attempt budget every tick and reports exit 3 ("retry next tick")
forever instead of surfacing the failure.
Also: hasNoRemoteConfigured split out of isConfirmedNoRemote so sync can reuse
the structural no-remote proof with its own (broader) error hint without
loosening it — a solo rig must not fail every tick, but a typoed or broken
remote must still exit non-zero. The command doc and the doc-flags gate are
updated: `bd sync` is live again, so the stale reference to hunt is docs still
calling it removed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Normalize every shared command argument-hint to an explicit YAML string and enforce the schema across LF and CRLF checkouts so Copilot plugin skills load reliably.
Agent-Signature: codex-gpt-5.6-sol-high on behalf of matt wilkie
Use the command's supported --all example so agents are not directed to a nonexistent --status flag.
Agent-Signature: codex-gpt-5.6-sol-high on behalf of matt wilkie
Remove the obsolete sync-branch, redirect-file, and forced-embedded model. Document supported Git/common-directory discovery, current command syntax, and Dolt remote synchronization.
Agent-Signature: codex-gpt-5.6-sol-high on behalf of matt wilkie
Document current Dolt storage modes, conservative cloud-folder diagnostics, authoritative remote sync, and mode-aware Dolt-native backups.
Agent-Signature: codex-gpt-5.6-sol-high on behalf of matt wilkie
Document the supported commit-pull-push handoff, safe Git-origin auto-adoption, and committed-HEAD limits of opt-in auto-push.
Agent-Signature: codex-gpt-5.6-sol-high on behalf of matt wilkie
Document active JSONL import usage, timestamp and ID merge semantics, chunk recovery, memory round trips, and the final commit's working-set safety constraints.
Agent-Signature: codex-gpt-5.6-sol-high on behalf of matt wilkie
* docs: redirect legacy Pages site to Mintlify (mybd-aokv)
Agent-Signature: codex-gpt-5.6-sol-high on behalf of matt wilkie
* docs: harden legacy Pages redirect
Agent-Signature: codex-gpt-5.6-terra-medium on behalf of matt wilkie
Per decision 6: the eleven pointer stubs at old top-level docs/ paths are
deleted; the docs.json redirects array now maps every moved page's old
route to its new home (43 entries covering the full pre-port top-level
namespace). The docsync exemption list shrinks to the one generated file
(docs/CLI_REFERENCE.md). Plugin and npm-package quickstart pointers now
link the real in-repo page.
Old GitHub deep links to the deleted paths 404 from here on — accepted in
the decision record; bd's own printed paths are updated to the new
locations in the next commit, so only already-released binaries are
affected.
- mint.sh + make docs-dev: local preview of the docs/ Mintlify site
(Node 22 handling modeled on the Gas City wrapper).
- test/docsync: Go guard keeping docs/ and docs.json in exact
correspondence — every nav entry has a file, every page is in the nav
(tiny stub allowlist for paths released bd binaries print), published
pages use root-relative extensionless links that resolve, and engdocs/
plus curated root markdown keep exact GitHub-style paths. Wired into
make check-docs.
- .github/workflows/docs-mintlify.yml: docsync + baseline-aware
mint broken-links check on PRs touching docs/**.
- Retire scripts/sync-website-docs.sh and its mirror-drift gate: the six
mirrored files now live once in the Mintlify site; the committed
Docusaurus mirrors stay frozen so the parallel-run site keeps building.
- Repoint inbound links to moved docs across README, guides, examples,
npm-package, plugin resources, and Go comments; add docs/SYNC_CONCEPTS.md
pointer stub (bd's agent templates print that path). Runtime strings in
cmd/bd (prime.go, store_factory_nocgo.go, init_git_hooks.go) still print
old paths — covered by stubs, flagged in the PR.
Second release candidate for 1.1.0. rc.1 is superseded: two
upgrade-breaking migration regressions were reported against it (#4502
v53 fails on pre-rig issues tables; #4534 one orphaned child_counters
row bricks every create) and both fixes plus the remote-migrate gate
hardening (#4515/#4516), the schema-newer fail-fast (#4531), the
prerelease-correct install header (#4530), and the validated upgrade
recipe (#4514) landed after the rc.1 tag.
CHANGELOG gains the dated 1.1.0-rc.2 section, info.go the whats-new
entry, update-versions.sh 1.1.0-rc.2 bumped the version files, and the
beads-mcp lockfile is resynced (1.1.0rc2). check-versions.sh passes.
Agent-Signature: claude-fable-5-high on behalf of matt wilkie
Claude-Session: https://claude.ai/code/session_0167xsjJDukVKE7BE1i4W2wE
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Re-lands the v1.1.0-rc.1 release prep so the candidate can be reviewed before
the tag is cut (#4476 auto-merged the original prep; #4477 backed it out).
Restores v1.1.0-rc.1 version metadata across all package manifests, the
prerelease-aware release workflow and version scripts (prerelease tags skip the
stable docs-snapshot requirement and stay off the stable Homebrew/PyPI/npm
channels), the CHANGELOG and cmd/bd/info.go entries, and regenerates uv.lock to
1.1.0rc1.
Beyond the straight re-land:
- fix(release): match the winres/manifest numeric PE versions on the base
version in update-versions.sh, so a later prerelease-to-different-base bump
does not silently leave them stale.
- docs(release): document the prerelease / release-candidate workflow in
RELEASING.md.
Agent-Signature: claude-opus-4-8-xhigh on behalf of matt wilkie
* revert: back out v1.1.0-rc.1 release prep
Reverts merge commit 427fdd0c85 from #4476 so the RC release prep can go back through maintainer review.
Agent-Signature: codex-gpt-5.5-xhigh on behalf of matt wilkie
* fix(mcp): sync uv.lock to reverted 1.0.5 version
The #4476 revert rolled integrations/beads-mcp/pyproject.toml back to
1.0.5 but left uv.lock pinned at 1.1.0rc1, so `uv lock --locked` (the
Package Gate (MCP) check) failed and the aggregate CI Gate went red.
Regenerate the lockfile so pyproject and uv.lock agree on 1.0.5.
Agent-Signature: claude-unknown-model-high on behalf of matt wilkie
Allow prerelease version bumps without promoting stable docs, keep Windows resource versions numeric for prerelease builds, and skip Homebrew/npm/PyPI publishing for prerelease tags while still producing GitHub prerelease artifacts.
Agent-Signature: codex-gpt-5.5-xhigh on behalf of matt wilkie
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
PR #4188 moved hook files from plugins/beads/hooks/ to
plugins/beads/.codex-plugin/hooks/ to stop Claude from discovering
Codex-only hooks. However, the hooks path in .codex-plugin/plugin.json
remained "./hooks/hooks.json" which Codex resolves relative to the
plugin root (plugins/beads/), not relative to .codex-plugin/. This
caused a runtime error:
failed to read .../beads/1.0.5/hooks/hooks.json: No such file or directory
Fix: update the hooks path to "./.codex-plugin/hooks/hooks.json" so
it correctly resolves to plugins/beads/.codex-plugin/hooks/hooks.json.
Update TestPluginLayoutUsesSharedBeadsRoot to assert the corrected path.
Fixes#4210. Follow-up to #4188.
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_
the claude plugin manifest declared agents at ./skills/beads/agents/, which
also contains openai.yaml (codex interface metadata). claude code's plugin
loader scans that dir and rejects non-md files, failing manifest validation
with 'agents: Invalid input'.
move task-agent.md back to plugins/beads/agents/ (the claude default, what
v1.0.0 used) and drop the explicit agents key from .claude-plugin/plugin.json.
codex's openai.yaml stays at skills/beads/agents/openai.yaml where bd setup
codex writes it and where the embed in internal/templates/ lives.
shared skill tree and dual claude/codex manifests are preserved per #3664.
Fixes#3741