* fix: enable auto-export by default with canonical issues.jsonl name (GH#2973)
Users expected JSONL export to refresh automatically but export.auto
defaulted to false, requiring explicit opt-in. Also the default filename
(export.jsonl) didn't match the canonical issues.jsonl used in docs and
git hooks. Change defaults: export.auto=true, export.path=issues.jsonl,
export.git-add=true so viewers (bv) and git workflows see fresh data
without extra configuration.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat(init): add auto-export prompt and document export.* config (GH#2973)
Interactive bd init now asks whether to enable auto-export (default: yes).
Users can opt out during setup instead of discovering the setting later.
Also documents the export.* config namespace in bd config --help with
all four keys (export.auto, export.path, export.interval, export.git-add)
and adds export examples.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* docs: document export.* auto-export config keys (GH#2973)
Document the export.auto/path/interval/git-add keys in docs/CONFIG.md
and note the default-on switch in CHANGELOG.md [Unreleased].
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix(export): don't prime throttle on empty init and skip git-add without git (GH#2973)
Review feedback on #3204 surfaced two regressions in the default-on
auto-export path:
1. bd init's PersistentPostRun fired maybeAutoExport with zero issues,
writing an empty .beads/issues.jsonl and saving export-state.json with
the current dolt commit + timestamp. The next `bd create` was then
throttled for up to export.interval (default 60s) because the
timestamp check in maybeAutoExport returned before considering the new
commit, leaving issues.jsonl stale on fresh repos.
Skip saving state and remove the empty file when the export produced
no issues and no memories. The next write runs a real export
immediately.
2. export.git-add defaulting to true emitted
`Warning: auto-export: git add failed: exit status 128` on every
write in the supported standalone BEADS_DIR flow where init
intentionally skips `git init`. Gate the git add call on isGitRepo()
so standalone users get silent, working auto-export.
Adds a scripttest regression guard for the init -> immediate create
path.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* test(memory): disable auto-export in concurrent test (GH#2973)
TestEmbeddedMemoryConcurrent started failing on this branch after
auto-export became the default: every concurrent 'bd remember'/'bd
forget' call now fires maybeAutoExport, which reads store state after
the write. Under 8-worker contention this intermittently leaves a
forgotten key visible to 'bd memories'.
The test exercises memory concurrency, not export behavior; opt it
out of auto-export so the signal stays focused. Followup: investigate
the race between write commit and post-write auto-export read in
embedded Dolt concurrent paths.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix(workspace): align resolved workspace messaging and config lookup
intent(workspace): pure worktrees and external BEADS_DIR setups should work without implying a local .beads directory is required
decision(config): derive config repo roots from FindBeadsDir-backed workspace resolution instead of a local-only .beads walk
constraint(workspace-detection): keep FindBeadsDir ordering and storage behavior unchanged while making bd where the primary diagnostic hint
learned(testing): shared-server env and global .beads ignore rules can distort CGO suites, so regression coverage now normalizes those test paths
* fix(bootstrap): align no-workspace JSON wording
intent(bootstrap): machine-readable no-workspace output should match the resolved-workspace guidance used elsewhere on this branch
decision(bootstrap-json): reuse the shared workspace error helpers through a dedicated payload builder so tests can lock the JSON contract
constraint(review-loop): keep the bootstrap CLI flow unchanged outside the no-workspace JSON branch while adding a focused regression test
* fix(where): allow no-workspace diagnostics without db (beads-9f74-5l1)
intent(where): no-workspace guidance should point to a command that actually runs when workspace resolution fails
decision(startup): treat top-level where as a no-db command so it reaches its own handler before database preflight
constraint(where-tests): subprocess mode can change the exact hint text, so the regression test locks the JSON contract and stable guidance fragments instead
* fix(bootstrap): restore bd where guidance for no-workspace output (beads-9f74-3c3)
intent(bootstrap): no-workspace bootstrap guidance should match the resolved-workspace diagnostics introduced on this branch
decision(no-workspace-hints): reuse the shared hint that mentions bd where instead of the bootstrap-specific fallback text
constraint(bootstrap-tests): cover both the payload helper and subprocess CLI path so wording regressions are caught before release
* fix(workspace): remove no-workspace .beads fallbacks (beads-9f74-gr1)
intent(workspace-resolution): finish the GH#3124 follow-up for runtime paths that still fabricated local .beads state
rejected(no-workspace-fallback): inventing ./ .beads paths outside an active workspace hid shared-worktree resolution and created stray files
decision(setup-recipes): keep built-in bd setup recipes usable without a workspace but require an active workspace for custom recipe state
constraint(worktree-support): completion and backup helpers still need to resolve shared main-repo workspaces from a git worktree
* fix(config): skip no-workspace store init for store-free commands
intent(config): review-fix-loop found no-workspace config commands should reach their own graceful paths instead of failing in PersistentPreRun
decision(config-preflight): detect store-free config subcommands before DB synthesis so config.yaml, git-backed, and diagnostic flows can run without an opened store
constraint(json-contract): keep bd config validate --json machine-readable on stdout once pre-run stops short-circuiting into low-level DB errors
learned(config-preflight): the parent config command not being in noDbCommands leaked store init into show, validate, drift, apply, and yaml-only config helpers
* fix(ci): restore init prefix normalization and formatting
intent(ci): clear the current PR failures instead of leaving the branch blocked behind known red checks
decision(init-prefix): normalize dotted prefixes before persisting issue_prefix so config, metadata.json, and Dolt database naming stay aligned for Julia-style repos
constraint(fmt-check): CI runs gofmt over the whole repo, so the existing spacing drift in internal/jira/tracker_test.go had to be cleaned up on this branch to get a green run
learned(ci): the latest main CI was already red on the same formatting file and the same embedded shard, so rebasing surfaced pre-existing blockers rather than introducing a new shard-only regression
Add az:// (Azure Blob Storage) as a recognized Dolt remote URL scheme.
Azure Blob Storage URLs were already functional for bootstrap via sync.git-remote, but the URL validator didn't recognize az:// — so config validate and error hints were incomplete.
Thanks to @harry-miller-trimble for the contribution!
* fix: make auto-export and auto-backup errors visible on stderr
Previously, failures in auto-export (JSONL flush) and auto-backup were
logged only via debug.Logf, invisible to normal users. One user lost 46
issues because JSONL export silently stopped working with no warnings.
Upgrade critical error paths from debug.Logf to fmt.Fprintf(os.Stderr)
so users see warnings when their backup/export pipeline breaks. Keep
debug.Logf for non-critical diagnostics (throttle, no-change skip).
Closes#2489
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* docs: remove stale sync references
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add docs/ICU-POLICY.md as the authoritative reference for how ICU is
handled across all platforms. Update CONTRIBUTING.md and INSTALLING.md
to stop listing ICU as a build requirement (it's test-only since all
builds use gms_pure_go).
Resolves confusion from overlapping PRs (#2991, #3066, #3112) where
agents and contributors were doing/undoing each other's ICU fixes
without a written policy.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat(docs): version Docusaurus site and align llms-full with snapshots
Add docs version 1.0.0, version dropdown, lastVersion defaulting to stable,
merged markdown config, and RELEASING steps for future doc snapshots.
generate-llms-full.sh reads the latest entry in versions.json.
README links the published documentation site.
Closes#2644
Made-with: Cursor
* fix(docs): update org URLs to gastownhall and refresh 1.0.0 snapshot
- Update default orgName in docusaurus.config.ts from steveyegge to
gastownhall to match the repo's new home
- Update hardcoded steveyegge URLs in generate-llms-full.sh
- Refresh versioned_docs 1.0.0 snapshot to include quickstart changes
from #3032 which merged after the original snapshot was taken
- Regenerate llms-full.txt with corrected URLs and updated content
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: matt wilkie <maphew@gmail.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Single full tutorial on website/docs/getting-started/quickstart.md; docs/QUICKSTART.md
is a short pointer with stable anchors. Update npm and Claude plugin links.
Closes#3014
Made-with: Cursor
* fix: narrow cross-version smoke CI triggers and warn on high skip rate
Remove push-to-main and PR triggers from cross-version smoke test
workflow — 30-45 min runtime is too costly for every push. Keep tag
pushes (releases/RCs) and manual dispatch.
Add a visible warning when >80% of tested versions are skipped, printed
to stderr and GitHub step summary. Prevents silent "all passed" when
nearly nothing actually ran.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* chore: add .buildflags for consistent ICU build configuration
Amp-Thread-ID: https://ampcode.com/threads/T-019d5c3f-42eb-7794-8d59-524bbf77bdf8
Co-authored-by: Amp <amp@ampcode.com>
* Add analysis of getting-started docs: necessity vs. fixable errors
Analyzes ~3,200 lines of getting-started documentation across 9 files.
Finds ~50% of the content compensates for tool-level UX gaps that should
be fixed rather than documented. Categorizes every section as genuinely
necessary, useful reference, workaround for fixable issue, or redundant.
Includes specific recommendations for both tool fixes and doc consolidation.
Requested by @csells.
https://claude.ai/code/session_01Fak22deVmDX3KRBKVptJBL
* Streamline getting-started docs: reduce noise, fix user-facing paths
QUICKSTART.md:
- Change all ./bd to bd (reflects installed binary, not local build)
- Replace go-build install section with brew/npm + link to INSTALLING.md
- Remove Notion sync, database maintenance, and migration sections
(these are advanced topics, not quickstart material)
- Add "Database maintenance" link to Next Steps
README.md:
- Consolidate installation from ~30 lines to ~8 lines
- Remove CGO/build-from-source details (belong in INSTALLING.md)
- Add links to INSTALLING.md sections for all install methods
INSTALLING.md:
- Demote go install/source to "Contributors / Go developers" in matrix
- Move Build Dependencies section after platform installs, retitle to
"Build Dependencies (Contributors Only)" with skip-if-prebuilt note
- Add cross-reference to TROUBLESHOOTING.md in troubleshooting section
Net effect: -91 lines, clearer separation between user and contributor
paths, less noise in the first-time experience.
https://claude.ai/code/session_01Fak22deVmDX3KRBKVptJBL
* fix: detect permission errors in bd init with platform-specific guidance
On Windows, Controlled Folder Access can block bd init from creating
.beads/ with no useful error. Now detects os.IsPermission and prints
specific guidance for Windows (CFA whitelist instructions) and Unix
(ls -la / chmod suggestions) instead of a generic failure message.
https://claude.ai/code/session_01Fak22deVmDX3KRBKVptJBL
* fix: add circuit breaker cleanup to bd doctor --fix
Stale circuit breaker files in /tmp/beads-circuit/ can block all bd
operations. Previously users had to manually rm these files. Now
bd doctor detects stale breaker files as a fixable check, and
bd doctor --fix clears them automatically via CleanStaleCircuitBreakerFiles.
https://claude.ai/code/session_01Fak22deVmDX3KRBKVptJBL
* feat: warn about multiple bd binaries in PATH
bd version now scans PATH for duplicate bd executables and warns when
more than one is found. This catches the common case where go install
and Homebrew binaries coexist, causing version confusion. Symlinks
are resolved to avoid false positives.
https://claude.ai/code/session_01Fak22deVmDX3KRBKVptJBL
* fix: show holding process PID in database lock errors
When the Dolt database is locked, the error message now tries to
identify the holding process by scanning /proc for bd/dolt processes.
On Linux, users see e.g. "Process 12345 (bd/dolt) may be holding
the lock." Gracefully degrades to the previous message on platforms
without /proc (macOS, Windows, FreeBSD).
https://claude.ai/code/session_01Fak22deVmDX3KRBKVptJBL
* fix: only flag circuit breaker files as stale after TTL expires
CheckCircuitBreaker() was counting any open/half-open breaker as stale
regardless of age. This could reset a legitimately active breaker
during a real outage. Now uses the same 5-minute staleness threshold
as CleanStaleCircuitBreakerFiles() — only breakers older than 5 minutes
(from TrippedAt or LastFailure) are flagged for cleanup.
https://claude.ai/code/session_01Fak22deVmDX3KRBKVptJBL
* fix: correct broken doc anchors in README installation links
The "go install" and "from source" links pointed to nonexistent anchors
in INSTALLING.md. Found during review checklist testing.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: suppress gosec G304 false positive in circuit breaker check
Path comes from filepath.Glob with a controlled pattern, matching
the same nolint pattern used in internal/storage/dolt/circuit.go.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: Amp <amp@ampcode.com>
* feat: add credentials file support for Dolt server passwords
Add INI-style credentials file (~/.config/beads/credentials) as a
fallback for Dolt server passwords, keyed by [host:port] section.
This lets users working with multiple servers avoid juggling env vars
per project.
Lookup order: BEADS_DOLT_PASSWORD env var > credentials file > empty.
Path overridable via BEADS_CREDENTIALS_FILE env var.
Warns on overly permissive file permissions (unix only, mirrors ssh).
* docs: document credentials file in DOLT.md
Add credentials file section to the Dolt backend docs covering file
format, default location, permission warnings, and password resolution
order. Update the config reference and env var table to reference the
new feature.
* fix: use resolved runtime port for credentials file lookup
The credential file lookup in GetDoltServerPassword() used the port
from metadata.json, but the actual connection port comes from
doltserver.DefaultConfig() which has its own priority chain (port file >
config.yaml > metadata.json). When these diverge — e.g., IAP tunnel on
3308 vs local Dolt on 3307 — the credentials file lookup used the wrong
[host:port] section.
Add GetDoltServerPasswordForPort() that accepts an explicit port, and
use it in main.go where the resolved runtime port is already known.
Existing GetDoltServerPassword() delegates to the new method for
backward compatibility.
* fix: use mysql.Config.FormatDSN for proper password escaping
Passwords with special characters (& < > / % etc.) were inserted raw
into the DSN string, breaking go-sql-driver/mysql parsing. Passwords
like "zId&z,L9P4X,%k4n4rylGV<Ibos9<)/p" would cause "Access denied"
errors even though the password was correct.
Switch from manual fmt.Sprintf DSN construction to mysql.Config's
FormatDSN(), which handles escaping correctly. This also consolidates
timeout and TLS configuration into the typed Config struct instead of
string concatenation.
* test: add DSN special character password roundtrip tests
Covers passwords with &, <, >, /, ?, %, @, :, and () — all of which
broke the old fmt.Sprintf DSN construction. Verifies that FormatDSN
produces a parseable DSN and the password survives the roundtrip.
Filesystem-only tooling to detect contradictions, near-duplicates,
and merge opportunities in .claude/rules/*.md files.
- `bd rules audit` scans rules for contradictions and merge candidates
using Jaccard similarity, antonym detection, and scope analysis
- `bd rules compact` merges related rules into composites (manual or auto)
- 20 tests, no new dependencies (stdlib + cobra only)
- CheckReadonly guard on compact for consistency with other write commands
Resubmission of #1625, rebased cleanly on current main.
Co-authored-by: anupamchugh <anupamchugh@gmail.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
- Add docs/RELEASE-STABILITY-GATE.md defining the upgrade matrix,
verification criteria, and sign-off process
- Add scripts/upgrade-smoke-test.sh that tests data preservation,
mode preservation, role preservation, and doctor health across
upgrade scenarios (embedded maintainer, contributor, mode flip)
- Add 'make test-upgrade' target
- Update RELEASING.md checklist with upgrade smoke tests, regression
tests, and breaking-change documentation requirements
- Links to #2764, #2765, #2949, #2950 for related test gap work
Amp-Thread-ID: https://ampcode.com/threads/T-019d4a99-63c8-779f-bb8e-ee8522b61cdf
Co-authored-by: Amp <amp@ampcode.com>
Formally documents what beads tracker integrations will and will not build.
Establishes that integrations are an adoption bridge, not a product.
Explicit out-of-scope: webhooks, cross-tracker orchestration, attachment
sync, comment mirroring, credential vaults, UI parity features.
Includes design guidelines for new integrations and a decision log.
Fixes: bd-9go
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Adds internal/notion/ package with direct REST API client, field mapping,
and tracker adapter. Adds bd notion init/connect/status/sync commands.
Enhances tracker engine: conflict detection before pull, label sync,
no-op skip, batch push interface, RFC3339Nano timestamps. Removed dead
matchesFetchOptions function, added gosec nolint for Notion API client.
Co-Authored-By: Osamu Okano <okano.osamu@gmail.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add Lista Beads to the Editor Extensions section of COMMUNITY_TOOLS.md.
Full-featured VS Code extension with tree view, dashboard, dependency
graph, CodeLens, wisps/formulas, and multi-tracker sync.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The 30s default was killing legitimate chained pre-commit pipelines
(linters, formatters, type-checkers) before they could complete.
Increase to 300s with BEADS_HOOK_TIMEOUT env var documented as
escape hatch. Users can still Ctrl-C out of truly hung hooks.
PR: #2746
Co-Authored-By: matt wilkie <maphew@users.noreply.github.com>
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>
Replace gastown-specific references with generic alternatives throughout
the codebase:
- Rename --gastown flag to --orchestrator in bd doctor
- Rename gastownMode/gastownThreshold params to orchestratorMode/orchestratorThreshold
- Rename isGasTownTownRoot() to isOrchestratorRoot()
- Replace "gastown" in CLI examples with generic rig names (my-project, other-project)
- Update comments replacing "Gas Town" with "orchestrator" or "multi-agent workspace"
- Update active docs (DOLT.md, CONFIG.md, ADVANCED.md, etc.)
- Update test data to use generic names instead of "gastown"
- Update role templates (deacon, witness, refinery) to use generic language
Preserved as historical (not changed):
- CHANGELOG.md entries (historical record)
- ARTICLES.md (links to real published articles)
- info.go version notes (historical release notes)
- gastown/ file path references in dolt-concurrency.md (point to actual repo)
Replace ~/gt/ and ~/hop/ hardcoded paths with generic placeholders:
- routes.go comments: use <town-root> and <town> placeholders
- routing_test.go comments: use <town> placeholder
- deacon.md.tmpl: use {{ .TownRoot }} template variable
- witness.md.tmpl: use {{ .TownRoot }} template variable
- docs/DOLT.md: use <town-root> placeholder in example
- scripts/release.sh: reference docs by name, not path
- federation_test.go: reference HOP docs by name, not path
CHANGELOG.md entries left unchanged (historical records).
Simplify actor resolution chain to: --actor > BEADS_ACTOR > BD_ACTOR (deprecated) >
git config user.name > $USER > "unknown". BD_ACTOR still works for backwards compat
but BEADS_ACTOR is now the canonical beads-native env var. Updates all code paths,
tests, and documentation.
Session handoff skills for Claude Code with beads integration.
Fixed typo in original PR (stray 'n' prefix).
Co-Authored-By: REMvisual <noreply@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Three fixes for validation consistency:
1. bd create --validate now uses LintIssue() instead of ValidateTemplate(),
bringing it to parity with bd lint. A non-empty --acceptance field now
satisfies the "Acceptance Criteria" requirement without needing the
heading in --description. (GH#2468 parity)
2. --dry-run no longer bypasses --validate. Validation now runs before the
dry-run exit, so users get feedback on template issues during preview.
3. New validation.on-close config option (none|warn|error, default: none).
When enabled, warns on terse close reasons (<20 chars) or default
"Closed" reasons. Mirrors existing validation.on-create pattern.
Co-Authored-By: seanmartinsmith <114885497+seanmartinsmith@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Remove all remaining string/comment references to the removed SyncMode type.
Purely cosmetic cleanup with no behavioral changes.
- config.go: remove sync.mode from yamlKeys, update validate help text
- contributor_routing_e2e_test.go: rename TestRoutingWithAllSyncModes to
TestRoutingWithAllOperationalModes (also fixes unrenamed loop variable)
- kv_test.go: change test case from sync.mode to sync.git-remote
- Comment updates across test helpers and config packages
- TROUBLESHOOTING.md: update example from sync.mode to sync.git-remote
- .gitignore: add .opencode/
Co-Authored-By: Amperstrand <amperstrand@localhost>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Task 8: bd init now upgrades legacy beads sections to versioned format
instead of silently skipping them. New files created via EmbeddedDefault()
also get versioned markers.
Task 9: Replace stale bd sync references with bd dolt push in recipes
template. Add bd prime SSOT messaging.
Task 10: installAgents resolves symlinks via ResolveForWrite before
reading content. Profile precedence: if file already has full profile
and minimal is requested, full is preserved to avoid information loss.
Task 11: Added tests for staleness detection, profile extraction,
profile precedence, symlink safety, and legacy-to-new migration.
checkAgents now reports stale/current/missing status.
Task 12: Updated SETUP.md with prime SSOT, profiles, and profile
precedence documentation. Updated CLI_REFERENCE.md with --check
behavior and Gemini integration description.
Amp-Thread-ID: https://ampcode.com/threads/T-019ced7a-0c86-708d-930c-ee35d00eda8d
Co-authored-by: Amp <amp@ampcode.com>
Add new section to DOLT-BACKEND.md covering:
- Embedded vs central server comparison table
- Why 'brew services start dolt' silently ignores config
- Step-by-step custom LaunchAgent setup with plist
- Environment variables to point beads at central server
- Service management (stop/restart/logs)
Also fix default port from 3306 to 3307 in the server
configuration table to match DefaultSQLPort in code.
Closes#2323
Amp-Thread-ID: https://ampcode.com/threads/T-019ced53-6c5c-71de-8092-b834c879a68a
Co-authored-by: Amp <amp@ampcode.com>
Probe origin for refs/dolt/data during bootstrap and auto-clone
the database if found. bd init warns when existing data is detected.
Eliminates the no-common-ancestor error in fresh clones.
PR: https://github.com/steveyegge/beads/pull/2585
Author: cwalv
Key circuit breaker state files on host:port instead of port only,
preventing cross-host blocking when multiple servers share a port.
PR: https://github.com/steveyegge/beads/pull/2604
Author: trillium
The circuit breaker was keyed on port number only, causing a breaker
tripped for one host (e.g. localhost:3307) to block connections to a
completely different host on the same port (e.g. 100.111.197.110:3307).
Changes:
- Add host field to circuitBreaker struct
- newCircuitBreaker now takes host+port, file path includes sanitized host
- probe() dials actual host:port instead of hardcoded 127.0.0.1
- Log messages include host:port for better diagnostics
- Add test verifying different hosts have independent breaker state