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)
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>
Introduces BEADS_DOLT_SHARED_SERVER mode where multiple beads projects
share a single Dolt server on a fixed port (3308), avoiding per-project
server sprawl. Includes `bd init --shared-server`, `bd dolt shared-*`
commands, doctor checks, and comprehensive tests.
Co-Authored-By: Shybko <shybko@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Replace stale `bd migrate --to-dolt` commands with deprecation
notes and reference to scripts/migrate-jsonl-to-dolt.sh
- Add TROUBLESHOOTING.md cross-reference for post-migration
connection errors in both DOLT-BACKEND.md and DOLT.md
Update documentation to reflect that only dolt-native sync mode is supported:
- docs/CONFIG.md: Remove git-portable and belt-and-suspenders references
- docs/DOLT-BACKEND.md: Simplify sync mode section
- FEDERATION-SETUP.md: Remove deprecated sync mode table
- agents.md.tmpl: Update "Git-friendly: JSONL" to "Version-controlled: Dolt"
The sync mode code was already cleaned up (only SyncModeDoltNative is valid
in internal/config/sync.go), but documentation still referenced removed modes.
w-bd-004
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
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>
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
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
Delete broken store_nocgo_test.go (references undefined errNoCGO),
remove dead bootstrapEmbeddedDolt/hasDoltSubdir functions, and clean up
stale comments and docs that still referenced embedded mode, CGO
requirements, or in-process Dolt across 20 files.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Executed-By: beads/crew/emma
Rig: beads
Role: crew
current documentation features an invalid command:
```
$ bd migrate --to=dolt
Error: unknown flag: --to
```
The intent was probably `bd migration --to-dolt`.
- Add unit tests for Dolt-specific ignore patterns
- Document manual cleanup steps for committed Dolt data
Coverage: gitignore validation logic in doctor command
Add detailed documentation for using Dolt as an alternative storage
backend to SQLite, including:
- Quick start guide with installation instructions
- Server mode vs embedded mode comparison
- Configuration options in metadata.json and config.yaml
- Migration guide from SQLite to Dolt
- AWS S3+DynamoDB remote sync setup
- Performance characteristics and benchmarks
- Troubleshooting common issues
This documentation complements the recently added Dolt test suite
and helps users adopt the Dolt backend for their workflows.
Co-authored-by: upstream_syncer <matthew.baker@pihealth.ai>
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>