* build(deps): bump fastmcp, pydantic, pydantic-settings and regen uv.lock in /integrations/beads-mcp
Absorbs dependabot PRs #4386 (fastmcp 3.3.1->3.4.2), #3825 (pydantic
2.13.3->2.13.4), and #4457 (pydantic-settings 2.14.0->2.14.2) into one
change, adding the uv.lock regeneration none of them carried. The
Package Gate (MCP) runs 'uv sync --locked', so a pyproject-only bump
can never pass it; landing the three pins together needs only one
lockfile regen and one CI cycle instead of three conflicting ones.
Transitively picks up starlette 1.0.0->1.3.1 (fastmcp 3.4.1's CVE
floor) and pydantic-core 2.46.3->2.46.4.
Verified locally: make ci-package-mcp (uv sync --locked + 228 tests + build) passes.
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Agent-Signature: claude-fable-5-high on behalf of matt wilkie
* ci(dependabot): use uv ecosystem for beads-mcp so bumps update uv.lock
With package-ecosystem "pip", dependabot edits only pyproject.toml and
leaves uv.lock stale, so every beads-mcp bump fails the Package Gate's
'uv sync --locked' (#4386, #3825, #4457 all hit this). The "uv"
ecosystem updates pyproject.toml and uv.lock together.
Agent-Signature: claude-fable-5-high on behalf of matt wilkie
---------
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Why: MCP-only agents had no way to leave a readable per-turn trail - the MCP
server exposed no comment tools, so agents could only overwrite the single
notes field, and show() reports comment_count without the bodies. This adds
comment / comments / note MCP tools wrapping the existing bd CLI commands
(arg construction and the Comment model verified against the Go source), with
the same @with_workspace / @require_context decorator split as the existing
write tools. Purely additive.
Includes a maintainer follow-up commit completing the test story at all three
tiers to actually mirror the add_dependency approach the description cites:
wrapper-level success/error tests (documenting that BdError propagates from
these passthrough wrappers), a real-bd client round-trip test, and an
end-to-end MCP-client test. Mocked tiers verified locally (93 passed, ruff
clean); the integration tiers mirror the adjacent add_dependency tests and
run under the manual beads-mcp workflow as before.
Co-authored-by: banozz <svenmedina07@gmail.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Agent-Signature: claude-fable-5-high on behalf of matt wilkie
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
* Retire legacy Homebrew tap publishing
Stop the release workflow from publishing the independent bd tap formula, and document Homebrew core beads as the supported Homebrew package with migration commands for legacy tap users.
Agent-Signature: codex-gpt-5.5-medium on behalf of matt wilkie
* Sync beads-mcp uv.lock with pyproject version
CI Package Gate (MCP) fails on `uv sync --all-groups --locked` because
integrations/beads-mcp/uv.lock still pins the editable package at 1.0.5
while pyproject.toml declares 1.1.0-rc.1. This drift exists on
upstream/main itself, not from this branch (PR #4478 only retires the
legacy Homebrew tap and touches no MCP package files), so the branch is
already on top of the latest upstream/main and a rebase cannot resolve it.
Regenerate the lockfile with `uv lock`. The only change is the package's
own version (1.0.5 -> 1.1.0rc1); no dependency versions change.
Agent-Signature: claude-opus-4-8-high on behalf of matt wilkie
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
Why: MCP validation was failing on hard-coded local paths, shared Dolt test
locations, and a missing build dependency, which made dependency PR checks
noisy.
Squashed rebase of the original two PR commits onto the rewritten
gastownhall/beads history. Composed with 6d7eb5b3b "fix(mcp): tolerate
current bd JSON shapes (#4253)": upstream's MCP_ROOT path fixes and
tolerant embeddeddolt assertions are kept, while this PR adds the
bd-init isolation-flag skip fixture, per-test BEADS_DIR workspaces,
the PYTHONPATH subprocess helper, removal of the no-signal compaction
test, and the build dev dependency.
Agent-Signature: codex-gpt-5.5-medium on behalf of matt wilkie
Agent-Signature: claude-unknown-model-high on behalf of matt wilkie
Adds tests asserting validate() and detect_pollution() build the expected
'bd doctor --check=...' argv (GH#4037), including --fix/--yes and --clean/--yes
flag forwarding. Also documents that the legacy validate(checks=...) arg is no
longer forwarded — bd doctor has no subset-selection flag — so the docstring no
longer advertises behavior the routing cannot honor.
Co-authored-by: kev <kglynn@pryoninc.com>
The beads-mcp admin tool's validate action called bd validate which
does not exist as a standalone command. Similarly, detect-pollution
called bd detect-pollution which is also not a standalone command.
Both are subcommands of bd doctor:
- validate → bd doctor --check=validate [--fix --yes]
- detect-pollution → bd doctor --check=pollution [--clean --yes]
Map the MCP client methods to the correct bd doctor invocations.
* fix(mcp): detect Dolt-backed projects in workspace discovery (GH#2997)
The MCP `context()` tool reported "Database: Not found" for embedded Dolt
projects because `_find_beads_db()` and `_find_beads_db_in_tree()` only
globbed for `*.db` files. Embedded Dolt projects keep their data under
`.beads/embeddeddolt/` and declare the backend in `.beads/metadata.json`
— there is no `*.db` file to find.
Adds `_has_beads_project_files()` mirroring Go's `hasBeadsProjectFiles`
(metadata.json, config.yaml, dolt/, embeddeddolt/, or non-backup *.db).
Both Python discovery functions (and `.beads/redirect` validation) now
use this check, so SQLite, embedded Dolt, and server Dolt projects are
all recognized.
`context()` now reports the project root and backend when no SQLite db
is present, instead of the misleading "Not found".
* fix: delegate _find_beads_project to _find_beads_db_in_tree for redirect support
Addresses review item #2: _find_beads_project duplicated the upward
directory walk but skipped .beads/redirect handling. Now delegates to
_find_beads_db_in_tree, inheriting redirect, symlink, and all backend
detection for free.
Amp-Thread-ID: https://ampcode.com/threads/T-019d84e2-3a96-7263-a399-c3b2cc0ba6bb
Co-authored-by: Amp <amp@ampcode.com>
---------
Co-authored-by: Amp <amp@ampcode.com>
Thanks @GGPrompts — clean fix, good reasoning. The `str` approach is clearly right here given `IssueStatus` and `IssueType` already made the same call. Added a CHANGELOG entry before merging.
Stable release. Embedded Dolt default on all platforms, critical
reliability fixes (concurrent panic, spaces in path, schema migration),
22 community PRs merged, tracker hardening across all backends.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Only Linux amd64/arm64 can cross-compile with CGO on the CI runner.
macOS needs CoreFoundation/Security frameworks, Windows needs mingw
with framework support, and Android/FreeBSD lack sysroot headers.
These platforms use server mode; embedded Dolt is Linux-only for now.
Removes zig setup (no longer needed — Linux arm64 uses system gcc).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Gate embeddeddolt package on //go:build cgo with stub files for !cgo.
Android and freebsd targets use CGO_ENABLED=0 since zig lacks sysroot
headers for these platforms. Server mode still works on all targets.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Zig lacks sysroot headers for android and freebsd targets, causing
stdlib.h not found errors. Revert these two targets to CGO_ENABLED=0
(they do not need embedded Dolt). Remove unused zig wrappers.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Embedded Dolt is now the default storage backend. Adds multi-project/team
sync for Linear/Jira/ADO, Notion and GitLab sync, bd create --graph,
simplified backup system, and 18 bug fixes from 18 contributors.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add category-aware custom statuses that control behavior in bd ready
and bd list. New config format: bd config set status.custom
"in_review:active,qa_testing:wip,archived:done,on_hold:frozen".
Backward compatible with old flat format. New bd statuses command
lists all statuses with --json support.
Also fix TestKillStaleServersPreservesOtherRepoServers to clear
BEADS_DOLT_AUTO_START env var, since the new IsAutoStartDisabled guard
in killStaleServersForDir short-circuits when set.
PR: #2665
Co-Authored-By: Harry Miller <harry-miller-trimble@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Thread issue_type through ReadyWorkParams model, CLI client, tools,
and MCP server layers. The CLI already supported --type but MCP wasn't
exposing it.
Co-Authored-By: Stuart Parmenter <stuartparmenter@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The Stats model was changed to nested summary/recent_activity in #1392
but test_bd_client.py was missed. Update fixture and assertions.
Co-Authored-By: Stuart Parmenter <stuartparmenter@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>